Skip to content
Business

Project Manager CV example

A project manager CV is judged on scope. Reviewers are trying to establish, quickly, whether you have run projects at the size they are hiring for. A £200k internal system upgrade and a £14m programme with six workstreams both count as project management, and confusing the two wastes everyone’s time.

That means every project entry needs four numbers: budget, duration, team size and the outcome against plan. The last one is where most CVs go quiet. Reviewers know that projects slip; a CV that admits a delay and explains the recovery is more convincing than one where everything landed perfectly.

The methodology question is usually less important than applicants think. Most organisations run something hybrid, and what they want is evidence you can adapt rather than a certificate in a particular framework.

This example is written for a project manager with eight years of experience delivering business change and technology projects.

Opens in the editor with this content already filled in, so you can replace it with your own.

Project Manager example on the Modern Professional layout. All details are fictional and shown for demonstration only.

What recruiters expect

Before writing anything, it helps to know what the person reading is checking for. In this field that is usually a short, specific list:

  • Budget, duration, team size and business area for each significant project.
  • Delivery outcomes stated honestly, including variance against plan.
  • Governance experience: steering committees, RAID logs, stage gates, benefits realisation.
  • Stakeholder seniority - who you report to and who you have to influence without authority.
  • Methodology fluency across waterfall and agile, and judgement about when each applies.

Recommended CV structure

This is the running order the example uses. It is a starting point rather than a rule, but the order reflects what tends to be read first in this profession.

  1. Profile — Three or four lines positioning you for the role.
  2. Core Skills — Grouped skills, for example "Languages" and "Tooling".
  3. Professional Experience — Paid roles, in reverse chronological order.
  4. Selected Projects — Work you built, with outcomes and the stack used.
  5. Professional Qualifications — Completed certifications with the issuing body.
  6. Education — Degrees, diplomas and school-leaving qualifications.
  7. Languages — Spoken languages with CEFR levels.

Sections worth adding

  • Continuing Professional Development — Useful where certification renewal or new framework training is recent.
  • Professional Memberships — APM or PMI membership is worth a line in some markets.

Skills worth including

Grouped rather than listed in one block. Grouping makes a long list readable and shows that you can tell the difference between the things you use daily and the things you have touched.

Delivery

Project planning · Critical path analysis · Resource planning · Dependency management · Stage gate governance

Financial Control

Business case development · Budget forecasting · Cost tracking · Benefits realisation · Change control

Risk & Quality

RAID management · Risk mitigation planning · Issue escalation · Quality assurance · Post-implementation review

Methodology

PRINCE2 · Agile (Scrum, Kanban) · Hybrid delivery · Waterfall · MSP awareness

Tools

Microsoft Project · Jira · Azure DevOps · Smartsheet · Power BI reporting

Beyond the technical list: Influencing without authority, Chairing steering committees, Negotiating scope, Delivering bad news early, Coaching project coordinators. These belong inside your experience bullets, demonstrated, rather than in a list of adjectives.

Example professional summary

Three or four lines, positioned for the role rather than describing your personality. Two versions you can adapt:

Project manager with eight years delivering business change and technology projects in logistics and manufacturing. Currently run a portfolio of three concurrent projects with combined budgets of £4.6m and teams of 8 to 22. Recent delivery includes a six-site warehouse management system replacement within its approved budget. PRINCE2 Practitioner and Certified ScrumMaster.
Delivery-focused project manager comfortable in hybrid environments where the plan is fixed and the build is iterative. Eight years across system implementations, site moves and process change, with a record of escalating problems early rather than reporting green until the last week.

Writing your experience

The difference between a CV that gets a call and one that does not is almost always in the bullet points. Each pair below shows a real rewrite of the kind of line that appears on most CVs in this field.

Weak

Managed multiple projects simultaneously.

Stronger

Run a portfolio of three concurrent projects with combined budgets of £4.6m, teams of 8 to 22 people, and durations between 9 and 18 months.

Gives the reviewer everything needed to place your level in one sentence.

Weak

Delivered the project successfully.

Stronger

Delivered the warehouse management system replacement across six sites, six weeks later than the original plan after a supplier data migration issue, and within the £1.8m approved budget including the change request.

Honest about the slip, specific about the cause, and clear that the financial control held.

Weak

Managed project risks and issues.

Stronger

Escalated a supplier resourcing risk to the steering committee ten weeks before it would have hit the critical path, which allowed a contract variation to be agreed without extending the go-live date.

Shows the value of early escalation, which is the actual skill behind RAID management.

Weak

Worked with stakeholders across the business.

Stronger

Chaired a monthly steering committee of four directors, and negotiated a scope reduction with the operations director that removed two low-value modules and recovered four weeks of schedule.

Names the seniority and describes a real negotiation with an outcome.

Taken from the example

The sample CV for this profession is fully written. A few sections from it, so you can see the level of specificity that works:

Experience

Senior Project Manager, Meridian Distribution UK

  • Run a portfolio of three concurrent projects with combined budgets of £4.6m, teams of 8 to 22 people, and durations between 9 and 18 months.
  • Delivered the warehouse management system replacement across six sites, six weeks later than the original plan after a supplier data migration issue, and within the £1.8m approved budget including the change request.
  • Escalated a supplier resourcing risk to the steering committee ten weeks before it would have hit the critical path, which allowed a contract variation without extending go-live.
  • Negotiated a scope reduction with the operations director that removed two low-value modules and recovered four weeks of schedule.

Projects

  • Warehouse management system replacement — Six sites, £1.8m budget, 18 months, team of 22 including three third-party suppliers.
  • Transport planning consolidation — Merged three regional planning teams onto a single system, £1.1m budget over 11 months.

Education

  • BEng (Hons) Manufacturing Engineering, Coventry University — Upper Second Class (2:1)

Certifications and registration

  • PRINCE2 Practitioner — PeopleCert
  • Certified ScrumMaster (CSM) — Scrum Alliance
  • APM Project Management Qualification (PMQ) — Association for Project Management

Common mistakes

Projects with no numbers

Without budget, duration and team size a reviewer cannot place your level, and will assume the smaller end of the range.

Methodology as the headline

Leading with "Agile practitioner" says little about what you delivered. Certifications belong in their own section, not in place of results.

Perfect delivery records

A CV where every project came in on time and under budget reads as unlikely. One honest recovery story is more persuasive than five flawless ones.

Confusing project management with coordination

If you maintained the plan rather than owning the outcome, say so. Overstating authority is exposed quickly in a competency interview.

No benefits

Delivering on time is process success. What the organisation got afterwards is the actual point, and it is usually missing.

ATS considerations

Applicant tracking systems behave differently by sector, and generic advice is often wrong for a given field. These points are specific to project manager applications:

  • State certifications exactly: "PRINCE2 Practitioner", "PMP", "Certified ScrumMaster". These are frequently used as hard filters.
  • Include "stakeholder management" as a phrase; it appears in the majority of project manager adverts.
  • Write budget figures in plain text with the currency symbol so they survive parsing.
  • Include both "programme" and "project" if you have programme-level experience, since spelling and scope both vary by employer.

The Minimal ATS layout is built for this, and the ATS guide covers what parsers do to a file in more detail.

Guides that go deeper

This page applies general CV advice to one field. The full treatment of each part is here:

  • How to Describe Work Experience — The difference between listing duties and demonstrating impact, and a repeatable way to rewrite any weak bullet point.
  • How Long Should a CV Be? — Two pages for most people, and a clear method for getting there when you have more experience than space.
  • How to List Skills on a CV — Group them, be specific, and cut anything you would not want to be interviewed on for ten minutes.

Questions about project manager CVs

PRINCE2, PMP or Agile certification?
PRINCE2 is dominant in the UK and parts of Europe, PMP in North America and the Middle East, and agile certifications are complementary rather than alternatives. Match the certification to the market you are applying in.
How do I show delivery when a project was cancelled?
Cancelled projects are normal and often the right decision. Describe what you delivered up to the stop point and what evidence informed the decision to stop.
Should I list every project I have run?
No. Three to five that show range in size, sector and type is more useful than a complete list. Summarise the rest in one line.
How long should a project manager CV be?
Two pages. The project detail justifies the space, but a third page usually means older projects are being described at the same length as recent ones.

Related CV examples

Europass CV Maker is an independent CV-building service and is not affiliated with or endorsed by Europass or the European Commission.