How to write it
Budget and headcount establish your level instantly
A hiring manager's first question about any project manager is what size of thing you can be trusted with, and the answer is a number. Put the budget range and the team size in the summary and in the current role's first bullet.
"Deliver enterprise IT programmes of $4M–$14M with matrixed teams of up to 60 people across 4 vendors" answers the seniority question, the complexity question and the vendor question in one line. A page of methodology terms answers none of them.
Turn delivery into a record
Everyone says they deliver on time and on budget. Almost nobody quantifies it, which means the person who writes "23 of 25 projects delivered on time and within budget" is making a materially different claim from everyone else in the pile.
Be honest about the ones that didn't land — the ratio is more believable than perfection, and a reviewer who has managed projects knows that a 25-for-25 record means either very easy projects or creative accounting.
- Budget range, and total portfolio value delivered
- Team size, and whether matrixed or direct
- On-time and on-budget ratio across a stated number of projects
- Schedule slip percentage, before and after a process you changed
- Stakeholder or client satisfaction score
The recovery story is your best asset
A project that was always going to succeed says little about you. A project you inherited eight months late and landed inside the fiscal year says almost everything: triage, renegotiation, stakeholder management under pressure, and the judgement to change the plan rather than defend it.
If you have one of these, it belongs in the summary as well as the experience section. It's the story your interview will be built around anyway.
Domain match matters more than methodology
Construction project management, IT delivery, pharmaceutical programme management and marketing campaign management share vocabulary and almost nothing else. Recruiters screen for domain first, and a PMP does not bridge those gaps.
So make the domain unmissable: the sector, the systems, the regulatory environment. "Insurance and healthcare payer systems implementations" tells a specialist recruiter more than any list of frameworks. If you are changing domain, name the transferable machinery — vendor management, governance, budget scale — and be direct about the move in your summary.
Certifications, where the sector actually screens on them
PMP carries real weight in North American enterprise and government contexts; PRINCE2 does the same in the UK, Europe and Australia; CSM and SAFe appear in agile-heavy software environments. In those markets the certification is often a hard filter, so list it with the issuer and year.
In startups and smaller software companies it counts for much less than a delivery record, and a resume that leads with certifications there reads as process-heavy. Same document, different order.