Skip to content
US resume & UK CV

Project manager resume: scope, delivery and the numbers behind them

A project manager resume is judged on the size of what you ran and whether it landed. Budget, team and deadline are the three numbers that matter.

Job titles this covers

Meridian
  • Project Manager
  • Programme Manager
  • Delivery Manager
  • PMO Lead

Classic single-column with strong section hierarchy — ideal when each role carries a scope line plus several bullets.

  • Starts from the recommended template
  • Section order matches this role
  • Export as Letter or A4

What this document has to prove

Project management is one of the few disciplines where the metrics are almost universal: budget, headcount, duration, scope, and whether the thing shipped when it said it would. That makes a strong PM resume unusually easy to write — and unusually obvious when it has not been.

The trap is describing process instead of delivery. Everyone runs a RAID log. Not everyone has rescued a project.

What a recruiter searches for

These are the terms a hiring team filters on. Include the ones that are true of your work — our checker tells you which are missing, it never inserts them for you.

Methodology
Agile, Scrum, Waterfall, PRINCE2, SAFe, Kanban — name the ones you have genuinely worked inside.
Certifications
PRINCE2, PMP, APM, CSM, SAFe — commonly used as a hard filter in both markets.
Project scale
Budget, team size, number of workstreams, duration, geography.
Tools
Jira, Confluence, MS Project, Asana, Smartsheet, Monday.
Stakeholder vocabulary
Steering committee, governance, risk register, dependency management, RAG reporting.
Domain
Construction, IT, healthcare, financial services — sector experience is usually the second filter after methodology.

How to write it, section by section

Put the numbers in the first line of each role

For every project role, open with a scope line: budget, team, duration and outcome. It gives the reader a frame for everything that follows, and it is the fastest possible way to show seniority.

  • Scope line: "£2.4m platform migration, 14 people across three suppliers, 11 months, delivered four weeks early."
  • Then outcome bullets: what was hard, what you did about it, what changed.
  • Then governance: how you reported, to whom, and how decisions were made.

Show the recovery, not only the success

Delivery managers are hired for what happens when things slip. One bullet about a project you rescued is worth more than three about projects that ran smoothly, because it demonstrates the judgement the role is actually about.

  • Weak: "Managed project risks and issues."
  • Better: "Inherited a project eight weeks behind; re-baselined scope with the steering group and delivered the critical modules on the revised date."
  • Strongest: "Inherited a project eight weeks behind after a supplier failure; re-baselined with the steering group, replaced two workstreams and delivered the critical modules on the revised date, with the remaining scope pushed to a funded phase two."

Methodology, described accurately

Most organisations run a hybrid, whatever the job advert claims. If you worked in an Agile team with a fixed deadline and a governance board, say that — "Agile delivery within a stage-gated governance model" is a true and credible sentence, while "Agile" alone invites a question about velocity metrics you may not have.

Keep certifications in one line with the year. PRINCE2 and PMP are filters; the year signals whether you are current.

US resume vs UK CV for PM roles

US: Letter, one to two pages, quantified bullets, no photo. UK: A4, two pages standard, a short personal statement at the top, British spelling — programme with an -mme in the UK, program in the US.

In the UK, PRINCE2 is close to a currency; in the US, PMP carries more weight. If you hold both, both belong on the page.

If you are moving into PM from a delivery role

Engineers, nurses, teachers and coordinators all do project work without the title. Rebuild the resume around the coordination you already ran: the migration you sequenced, the rota you planned, the rollout you coordinated. Then add the methodology vocabulary once you have genuinely worked inside it.

Mistakes that end the first read

Each of these is common in this role specifically, and each one costs a real application.

  • Listing "managed projects" with no budget, team size or duration.
  • A wall of methodology acronyms with no evidence of delivery.
  • Describing process artefacts (RAID log, status reports) as achievements.
  • No mention of stakeholders or governance for a mid-level or senior role.
  • Hiding a failed project — a well-described recovery is stronger than silence.
  • Certifications with no year, or expired ones presented as current.

Questions people ask

Do I need PRINCE2 or PMP to get a PM job?
Often it is listed as desirable rather than essential, but in large UK organisations PRINCE2 frequently acts as a filter, and in the US PMP does the same for enterprise roles. Check the advert: if it is listed under essential, it is a filter.
How many projects should I list?
Three or four substantial ones, described properly, beat twelve one-liners. If a role involved ten small projects, summarise the portfolio and then give detail on the two most significant.
What if I do not know the exact budget of a project?
Use a range and mark it ("approx. £2m"). An honest approximation with a qualifier is far better than a precise figure you cannot defend.
Should a PM resume be one page or two?
US: one page if under about ten years, two otherwise. UK: two pages is standard. PM resumes carry more per role than most, so two pages is usually justified.

Build a project manager resume in the builder

Fill in the real details, let the checker tell you what is missing, and export a text-based PDF when it reads cleanly.

No credit card · Unlimited manual editing · Your documents stay private