A strong project manager CV proves three things fast: what you delivered, at what scope, and how you handled people and risk along the way. Project management is a results discipline, so a CV that lists processes and methodologies without outcomes misses the point. The reader wants evidence that you can be trusted with their project — budget, timeline, stakeholders and all.
Put your scope in the first line
Open with a summary that sizes you up immediately: the kinds of projects you run, typical budget and team size, the sectors you know, and your core methodologies. Something like 'Project manager delivering change and technology projects up to £2m, leading cross-functional teams of 10–15 across financial services' tells a reader in one sentence whether you fit. Vague openings ('experienced, motivated project manager') waste the most valuable line on the page.
Quantify the scope of each project
For every project that matters, capture the numbers that convey scale: budget, team size, duration, number of stakeholders or workstreams, and the outcome. These figures are how a reader calibrates seniority. 'Managed a website project' could mean almost anything; 'Delivered a £750k website replatform over nine months, coordinating five suppliers and reporting to the executive board' is unmistakable.
Lead with outcomes, not process
Listing that you 'maintained RAID logs and ran stand-ups' describes activity, not achievement. Anyone can run a stand-up; the question is what the project delivered. Frame each entry around the result — delivered on time and under budget, launched the new system, realised the saving, resolved the at-risk programme — and let the methods sit underneath as supporting detail. Process is assumed; outcomes are what get you shortlisted.
Show how you handled people and risk
Projects are rarely smooth, and hiring managers know it. Evidence that you managed stakeholders, resolved conflict, recovered a slipping timeline or handled a significant risk is genuinely persuasive, because it shows judgement under pressure. Include at least one example of navigating difficulty, not just of things going to plan.
Methodologies and certifications — honestly
Name the frameworks you genuinely work in — Agile, Scrum, waterfall, PRINCE2, MSP — and any certifications you hold, but do not overstate. If you have run Agile deliveries, say so and show it; if you sat a course but have never applied it, be careful how you phrase that. A certification list is useful shorthand, but evidence of applying the method is what carries weight.
A worked example
Before: 'Responsible for managing projects and liaising with stakeholders.' After: 'Delivered a £1.2m ERP rollout across three sites in eight months, leading a 12-person cross-functional team and recovering a two-month slippage by re-sequencing the plan and renegotiating supplier deadlines.' Same role — but the second version proves scope, leadership, and how you handle risk, all in one bullet.
Tailor to the sector
Project management translates across industries, but the language and priorities do not. A construction programme, a software delivery and an NHS transformation value different things. Read the advert, mirror its terminology, and bring forward the projects and skills closest to the target sector so a reader sees relevance immediately.
Common mistakes to avoid
- Describing process instead of delivery
- Omitting the numbers that convey scope
- A generic summary that doesn't size you up
- No evidence of handling risk or difficult stakeholders
- Overstating methodologies you haven't actually applied
Length and what to cut
Two pages is normal for an experienced project manager; resist stretching further. Give recent, relevant programmes room to breathe and compress older or smaller ones to a line or two. Cut the generic responsibilities every PM shares — running stand-ups, keeping logs — because the space is far better spent on the deliveries that prove your scope and judgement.
Common questions
What should a project manager CV focus on?
Delivery: what you delivered, the scope (budget, team size, duration, stakeholders), and how you handled people and risk. Lead with outcomes and let methodologies sit underneath as supporting detail.
How do I show scope on a project manager CV?
Quantify each project — budget, team size, duration, number of workstreams or stakeholders — and pair it with the result. Numbers are how a reader calibrates your seniority.
Should I list PRINCE2 and Agile on my CV?
List the frameworks and certifications you genuinely use, but back the important ones with evidence of applying them. A method you've delivered with is far more persuasive than a certificate you've never used in practice.