CV gaps
CV gaps for Project Manager
Project manager CVs most often fall short by listing projects without their size, listing tasks instead of outcomes, and naming methods without showing them in use. A reader wants scope, delivery and the level of people you worked with.
The 4 gaps to check
No scope or scale
Why it matters: A project with no budget, team size or duration cannot be compared with the job you want.
How to close it honestly: State what is true: budget managed, team or workstreams, number of stakeholders, and how long it ran.
Tasks instead of outcomes
Why it matters: "Coordinated meetings and reports" describes activity, not delivery.
How to close it honestly: Say what was delivered, whether it was on time and on budget, and what changed for the organisation, using only facts you can support.
Method and certification vague
Why it matters: Listing PRINCE2, Agile or similar without context invites doubt.
How to close it honestly: Name a method only where you used it, say how, and list a certification only if you hold it, with the level.
Stakeholder level unclear
Why it matters: Readers look for who you reported to and who you influenced.
How to close it honestly: Name roles, not people, such as "reported to the Operations Director" or "worked with three heads of department".
Questions that find your real evidence
- What was the biggest project you delivered, and how big was it?
- What would have gone wrong without you?
- Who relied on your updates to make a decision?
Only add what is true. If you cannot back a line up with a real example, leave it out.