Your P11 did its job inside the UN system. It captured every duty, every grade, every contract detail, in the order a personnel file wants them. In the private market that same habit buries you. Going from a UN P11 to resume format means throwing out most of what the form trained you to include and rebuilding the rest around outcomes a reviewer outside the system can price.
Two pages. Plain English. Market titles instead of grade codes. That is the whole conversion, and the rest of this guide is how to do it without losing the parts of your record that impress people.
One honest note first. Humanitarian and development budgets have been squeezed hard since 2025, and a lot of strong UN profiles are hitting the same private pipelines at once. A clean resume gets you into the conversation. It does not shorten the search by itself, so widen the target list further than feels comfortable: operations, program delivery, risk, compliance, PMO, supply chain.
From UN P11 to resume: why the form works against you
The P11 rewards thoroughness. Duties and responsibilities, project by project. Contract type, grade, and step. Every committee and training course. That is compliance gold, and dead weight for a hiring manager who has never seen a P11 and has no idea what a P4 is.
The mismatch is simple. Duty lists say what you were told to do, not what happened because you were there. The same tasks repeated across four contracts read as noise. Grade, step, and contract type eat space that should carry scope, and every unexplained acronym makes the reader decode before deciding.
So compress. One line per outcome, strong verb first, then the concrete change, then the scope it covered. Take one recent role tonight, circle the five bullets a reviewer outside the UN would care about, and cut the rest. Five good bullets beat fifteen accurate ones.
Grades and contract types on a resume: what to translate, what to drop
Grade codes do not travel. Private readers judge seniority by scope and decision rights, so keep the codes off the page and translate the letter into reach.
Instead of P4 or G6, use the title your target job family uses: Program Manager, Operations Lead, Partnerships Manager, Risk and Compliance Manager. Put the scope in the bullets. Country, regional, or global portfolio. Budget you actually controlled. People who reported to you, formally or otherwise. Show promotion as movement from one country to several, or from execution to ownership, since grade progression means nothing outside.
Whatever title you choose, change LinkedIn to match it. Recruiters check, and a Program Manager on the resume who shows up online as P4 Programme Management Officer creates a question you do not want to spend the first five minutes of a screening call answering.
If you are G-grade staff, the trap is different. Your work was operational and real: procurement runs, travel and visa pipelines, payroll and vendor files, front-office coordination for a country director. Private employers buy exactly that as Operations Coordinator, Procurement Specialist, Executive Assistant, Office Manager, or Logistics Coordinator. Lead with volume and reliability, because that is what the role is hired on. Do not call yourself support staff. Describe the process you ran.
National Officers have the opposite problem: what makes you valuable is what the resume hides. You stayed while international colleagues rotated out, which means continuity, government relationships built over a decade, working language, and a feel for local law and procurement no incoming expat has. Put that in the summary line, not on page two.
UN Volunteer assignments belong on the resume when the work maps to the job you want, described by scope like anything else. Keep the arrangement honest, though. Most US employers of any size run third party employment verification before an offer is final, and a resume implying salaried staff employment for a stipend based UNV assignment surfaces at the worst possible moment. Be ready to describe it plainly: stipend rather than salary, hours, who you reported to. Nobody holds a UNV year against you. Getting caught smoothing it over at the offer stage is a different story.
Staff roles do not need contract labels at all. Fixed-term and temporary appointment are internal vocabulary. For consultancy and volunteer work, name the client and the channel, then go straight to scope.
Naming agencies so a reviewer can place them
Acronyms are fast for insiders and slow for everyone else. Spell out the employer on first mention and add a clause saying what it does. United Nations Development Programme, the UN agency for development and governance reform. United Nations Office for the Coordination of Humanitarian Affairs, which coordinates humanitarian response across agencies. After that, the acronym alone is fine.
Skip the country office shorthand: full agency name, then the country. If you worked through a firm or a roster, say so, with the firm as employer and the UN client in parentheses. Reviewers want to know who paid you and who you served, and vagueness costs more than the extra line does.
Consultancy chains: put dates on them, then group the work
Serial consultancies are normal in the international system and read as instability everywhere else. Grouping fixes most of that. Dates fix the rest.
Dates are the first thing a screener checks, before a single bullet. A grouped block with no date range does not look tidy, it looks like you are hiding the timeline. Put an overall range on the group header, and a short range on any single engagement that matters for the role you want.
A structure that works, with illustrative dates:
Governance and operations consultant, multilateral and government clients, 2018 to 2024
Clients: United Nations Development Programme, United Nations Office for Project Services, plus national ministries and INGOs
Channel: mixed direct awards and firm subcontracts
Then roll the engagements up into bullets that cut across contracts instead of repeating them. For example:
- Stood up program delivery playbooks with ministries and partners, clarifying roles, budgets, procurement steps, and reporting lines under strict donor compliance.
- Coordinated incident response and recovery planning across many stakeholders in fast moving contexts.
- Rebuilt vendor management processes, cutting backlog and rework while keeping audit trails intact, and co-designed donor reporting that met complex guidance.
If one client dominated the period, nest the smaller work under that engagement. The test is whether a reader outside the system can tell who the work was for, why it mattered, and how big it was.
What UN experience signals, and where it meets resistance
Translated well, a few things land hard.
The strongest is stakeholder management without formal authority. You moved work through ministries, agencies, and implementing partners with no power to make anyone do anything, and most private candidates have never had to. Close behind is compliance rigor, since few applicants have delivered under real donor rules and audit scrutiny. If you served in a hardship or non-family duty station, name it. That reads instantly as resilience to someone who has never heard of an R and R cycle.
Now the part most guides leave out. Plenty of hiring managers walk in assuming multilateral work means slow decisions, no cost discipline, and no commercial pressure. You will not argue that away in the abstract. Get ahead of it with one story of fast delivery under a hard constraint: the procurement you closed in weeks because a clinic sat idle, the budget you cut without dropping coverage.
If you are aiming at revenue owning roles in sales, business development, or general management, expect to be asked flat out about P and L, targets, and unit economics. Either reframe budget stewardship in commercial terms with figures you can defend, or aim first at operations, program management, risk, and PMO tracks, where the mapping is direct.
A worked before and after example
Here is a composite entry, kept generic on purpose, with illustrative dates.
Before, P11 style:
United Nations Development Programme, P4 Programme Management Officer, Fixed-Term Appointment, March 2019 to August 2024
Duties and responsibilities:
- Provide oversight and coordination for program implementation across country offices and projects.
- Draft TORs, facilitate procurement processes, monitor budgets at output and activity level in alignment with policy.
- Prepare donor reports and briefing notes. Coordinate with ministries, NGOs, and UN entities. Serve on compliance and procurement committees.
After, private market style:
United Nations Development Programme, the UN agency for development and governance reform
Program Manager, Governance Portfolio, 2019 to 2024
- Owned delivery of a multi-country governance portfolio, from planning and procurement through donor reporting, with ministries, NGOs, and vendors.
- Built operating rhythms for planning, procurement, and reporting that shortened delivery cycles and cut rework while meeting audit standards.
- Turned dense policy and donor guidance into steps teams could follow, coaching project staff and partners and clearing bottlenecks.
- Wrote leadership updates and donor reports that showed progress and risk without jargon.
Four things changed. The grade code became a market title. The employer picked up a descriptor. Duties became outcomes with scope attached. Compliance still shows, but it serves the delivery story instead of being the story. Both versions carry dates, because yours always should. Read yours out loud when you finish. If a smart friend outside the UN world follows it, you are close.
Fitting it on two pages
Two pages suits most people making this move, but match the track. Senior operations, program leadership, and executive roles carry two pages comfortably. Individual contributor roles at many tech and startup companies still expect one, however long your record is.
The order barely differs from any other resume: contact line, a two line summary naming the target role, a strengths band using the terms your target postings use, experience in reverse order, then education, certifications, and languages. The question specific to an international organization CV is where the grouped consultancy block goes. Put it in the chronological flow at its date range, not in a separate section at the bottom, or you reintroduce the gap you were closing.
What to cut, in order: internal committees unless they support the target role, training lists beyond the certifications that matter, and early roles, which collapse into one Additional experience line. Set the two page stop first and let it force the tradeoffs.
Before you hit send: pay, LinkedIn, and the first call
The resume is one piece of this. Two things trip people at the same stage, almost every time.
Pay first. UN compensation is not a salary in the private sense. Post adjustment, dependency and education allowances, hardship and mobility elements, pension treatment, and often tax exemption sit inside a package no private offer reproduces. Benchmark base salary for that role in that city on its own terms, and decide your number before the screening call. Recruiters raise expectations early, and a figure derived from a UN package lands either wildly high or oddly low.
Then LinkedIn and outreach messages. Every translation here applies there too: same market title, same spelled out employer names, same outcome language. If the resume says Program Manager and the profile still says P4, you have done half the work twice.
If you want help with the drafting, HiringCoachAI can turn a duty list into outcome bullets aimed at a specific posting, and a tool for the two line summary at the top of the resume. Neither writes your record for you. A free account keeps drafts in one place while you iterate.
None of this asks you to reinvent the work you did. It asks you to describe it in language a reader who has never seen a P11 can follow.