Translating a humanitarian CV for the private sector

The most common mistake humanitarians make when applying for private-sector roles is submitting a CV written for the sector they are trying to leave.

The format of a humanitarian CV (long, detail-heavy, agency-focused, heavy on programme names) is designed for donors and peer organisations who already know what REACH, IMPACT Initiatives, MSH, or DT Global are. A private-sector reader does not. They will not spend the time to decode it. They will skim, find nothing that matches the shape of a role they understand, and move on.

The translation is not a rewrite of your experience. It is a re-pointing of your vocabulary.

Lead with capability, not agency. Each role should start with what you were doing (actionable writing, research coordination, cross-functional communications, product-adjacent operations) not with the agency’s acronym.

Translate programme names. REACH and IMPACT Initiatives become “primary-data research organisations producing evidence for UN and donor agencies.” AECOM becomes “USAID implementing partner managing transition and conflict-mitigation programmes.” The reader does not need the acronym to respect the work.

Convert donor language to market language. “Donor reporting” reads outside the sector like internal bureaucracy; “executive reporting to institutional stakeholders” reads like the senior-communications work it actually was. “Beneficiary” becomes “end user” everywhere it appears. “Programme” becomes “initiative” or “product” where the shape fits.

Quantify ruthlessly. Not because numbers are magic, but because specificity travels. “Produced the REACH February 2017 Briefing on displacement dynamics, carrying figures on 78,321 people from Greater Torit who had reportedly fled to Uganda; used by humanitarian partners to shape emergency funding decisions.” That sentence is legible to anyone.

Name what you built, not only what you reported on. If you built a methodology, a reporting workflow, an editorial standard, a cross-team process, that is a product. Call it one. “Designed the Settlement-Level Actors Mapping methodology (V7) adopted as the standard for U-Learn’s Uganda refugee response programme” is a product sentence, not a reporting sentence.

Close with a short capability summary at the top of the CV (three to five lines) that frames the whole document: what you do, what you have done, what you are moving toward. That paragraph is doing most of the work for a skim reader. Write it last, when the rest of the CV has told you what your own through-line actually is.

You are not inventing experience you do not have. You are describing experience you do have in a vocabulary the reader can use.