Project Manager CV: How to Write Achievements Instead of Tasks
Most project manager CVs list what the job involved instead of what the person achieved. That makes every candidate look the same. This guide shows how to turn task lines into achievement bullets, with before-and-after examples you can adapt.
Why task lists fail on a project manager CV
Open ten project manager CVs and most bullets will look like this: "Managed project schedules", "Coordinated stakeholders", "Prepared status reports", "Managed risks and issues". Every one of those lines is true, and none of them helps you.
The problem is that tasks describe the job, not the person doing it. Every project manager manages schedules. A recruiter reading "managed project schedules" learns nothing about whether you did it well, on what size of project, or with what result. When forty candidates write the same lines, the reader has no reason to pick yours.
Hiring managers screening a PM CV are trying to answer three questions quickly:
- What size and type of projects has this person run?
- What did they personally decide or change?
- What was better at the end because of them?
Achievement bullets answer those questions. Task bullets do not.
The structure of a strong achievement bullet
A good PM achievement bullet usually contains three parts:
- Context and scale: what the project was and how big it was (budget, duration, number of people, sites, users, vendors).
- Your action: the specific thing you did or decided, with a strong verb. "Led", "renegotiated", "restructured", "introduced", "recovered".
- Result: what changed. Time saved, cost avoided, delivery date held, adoption reached, risk removed.
You do not need all three in every line, but you need at least two. A line with only the action ("Introduced weekly risk reviews") is better than a task. A line with action and result ("Introduced weekly risk reviews that surfaced a supplier delay six weeks early, allowing the go-live date to hold") is much better.
Keep each bullet to one or two lines. If you need three lines to explain it, the bullet is trying to tell a story that belongs in the interview.
Before and after: real-style examples
Here are typical task lines rewritten as achievements. The numbers in the "after" versions are illustrations: use your own.
Managed project schedules and deadlines.
Rebuilt the schedule for a delayed 9-month warehouse fit-out, re-sequencing 3 contractors to recover 5 weeks and open on the original date.
Coordinated with stakeholders across departments.
Aligned finance, IT and operations on a single go-live plan for a new billing system used by 200 staff, after two earlier attempts had stalled.
Responsible for budget tracking.
Tracked a budget of around $1.2M monthly and flagged a 12% overrun risk in month 4, leading to a scope change approved by the sponsor before costs were committed.
Prepared weekly status reports.
Replaced a 10-page weekly report with a one-page decision summary, cutting steering meeting time in half.
Managed vendors.
Managed 2 software vendors under fixed-price contracts; used change control to reject out-of-scope requests that would have added several weeks.
How to find achievements when you think you have none
Many people say their work was "just normal project work" and nothing stands out. That is rarely true. Achievements are usually hidden in problems you solved. Go through each project and ask:
- What was going wrong when I joined, and what was different when I left?
- What would have happened if I had not been there?
- Which decision did I push for that someone resisted?
- What did I set up that the team kept using afterwards (a template, a meeting format, a tracker, a process)?
- Was there a deadline that looked impossible but was met?
- Did I save money, time, or someone's job from a bad outcome?
Old emails, steering committee slides, project closure reports and performance reviews are good sources. They often contain the numbers you have forgotten.
If you are switching into project management, the same method applies to work that was not called a project. Our guide on becoming a project manager with no experience shows how to identify project work in a non-PM job.
What to do when you don't have exact numbers
You will not always have precise figures, and you should never invent them. Interviewers ask about numbers on your CV, and a figure you cannot explain does more damage than no figure. Use these alternatives instead:
| Situation | What to write |
|---|---|
| You know the approximate size | Use a rounded or hedged figure: "around 40 users", "budget of roughly $500K" |
| The figure is confidential | Use relative terms: "the largest project in the business unit", "seven-figure contract" |
| No money or time result | Use scope and scale: number of teams, sites, vendors, users, countries |
| The result was qualitative | Describe the observable change: "adopted as the standard template for all regional projects" |
| The result was avoiding a problem | Name the problem: "avoided a contract penalty", "prevented a missed regulatory deadline" |
Match your achievements to the job you want
Once you have a list of achievements, do not use all of them. Read the job posting and pick the ones that prove what that employer cares about.
If the posting talks about vendor management and contracts, lead with your vendor and budget bullets. If it talks about agile delivery and product teams, lead with achievements about release cadence, backlog decisions and team coordination. If it emphasises stakeholders and change, lead with adoption and alignment results.
Your most relevant achievement should be the first bullet under your most recent role. Recruiters often read only the first two or three bullets per job before deciding whether to keep going.
Engineers and technical specialists moving into PM should pay extra attention here, because their strongest achievements are often written in technical terms. The article Engineer to Project Manager covers how to translate them.
Common mistakes when rewriting bullets
Once people start writing achievements, a few new problems tend to appear. Watch for these:
- Claiming the team's result as yours alone. "Delivered a new CRM platform" suggests you built it. "Led delivery of a new CRM platform across 3 teams" is accurate and still strong. Interviewers notice when a candidate cannot explain their own part.
- Stacking numbers without meaning. "Managed 12 projects, 45 stakeholders, 8 vendors and $3M" is a list of figures, not an achievement. One number tied to one result reads better than four numbers with no outcome.
- Vague results. "Improved efficiency" or "enhanced communication" sound like results but say nothing. Ask yourself how you would prove it. If you cannot, describe the concrete change instead.
- Jargon from one company. Internal project names, system acronyms and team nicknames mean nothing to an outside reader. Replace them with a plain description: "the new customer billing system" rather than "Project Phoenix".
- Every bullet sounding the same. If all your lines follow "Led X, resulting in Y% improvement", the CV starts to feel generated. Vary the structure while keeping the substance.
A quick checklist before you send your CV
- Every bullet starts with a verb that shows ownership, not "Responsible for" or "Helped with".
- At least half of your bullets contain a number, a scale indicator or a concrete result.
- No bullet contains a figure you could not explain in an interview.
- The first bullet under each recent role matches something in the job posting.
- You have three to six bullets for recent roles and fewer for older ones.
- Nothing is repeated across roles with the same wording.
- Someone outside your industry could understand what you achieved.
Rewriting a CV this way takes a few hours the first time. After that, adapting it for each application becomes a matter of choosing and reordering bullets rather than starting again.
Want to know where you stand?
Send your CV and one project manager posting you'd like to get. Within 48 hours you get a written report: your fit for that role, the gaps that matter, rewritten CV lines, and the roles you can target now.
Get my PM Fit Report — $39