Skip to main content
CreateCVOnline

CV example · Eleven years, business change and systems

Project manager CV example

The job title tells a reader almost nothing in this profession, so this CV is built to answer one question fast: how big are the things this person has run, and did they land? Every project on the page carries a budget, a headcount, a duration and a variance — including the one that slipped and the one that was cancelled.

The example CV, rendered at full page size in the Management CV template. The full text of the summary and the highlighted bullet points is reproduced below in selectable form.

Marta Example is a fictional person. The employers, budgets and project outcomes shown are illustrative and exist only to demonstrate how a CV of this kind is constructed.

The text, in full

The professional summary

Reproduced as selectable text so you can read it closely, take the structure and write your own version.
Senior project manager, eleven years delivering systems and business change in manufacturing and utilities. Largest programme to date: a €2.4m ERP migration across four European sites, 26 people and three vendors over 14 months. I report variance against the original baseline rather than the reforecast, which is usually the more useful number and occasionally the less flattering one.

Why it is written this way: The largest programme appears in the second sentence with all four sizing facts attached — value, sites, headcount, duration — because that single line does more than a paragraph of methodology vocabulary. The third sentence is unusual and deliberate: stating that variance is reported against the original baseline rather than the reforecast tells an experienced sponsor exactly what kind of project manager they are dealing with.

The text, in full

4 experience bullets, and why each one works

Taken from the Senior Project Manager entry at Calder Industrial Group — the current role, which is where the strongest material always belongs.

  1. Bullet 1

    Delivered a €2.4m ERP migration across four European sites — 26 people, three vendors, 14 months — five weeks behind the original baseline and 3% under budget after absorbing two approved scope changes.

    The flagship project, sized four ways and then reported honestly. Admitting the five weeks is what makes the rest of the page believable — a sponsor knows a whole career of on-time delivery does not happen, and the phrase "after absorbing two approved scope changes" is the professional way to explain a slip without excusing it.

  2. Bullet 2

    Flagged a single-supplier dependency on the warehouse integration at initiation and ran a parallel proof of concept with a second vendor; when the primary supplier slipped its certification by nine weeks, go-live moved by four days rather than a quarter.

    A risk bullet written as a story with an outcome. Generic risk-management claims are worthless; this one names the specific dependency, the mitigation chosen at initiation, the event that actually occurred and the difference the mitigation made. It is also, structurally, a ready-made interview answer.

  3. Bullet 3

    Chaired a fortnightly steering group of nine directors and replaced a 20-page status pack with a one-page decision log, cutting average time-to-decision on escalated issues from three weeks to six days.

    Governance reframed as something that changed. "Chaired a steering group" is attendance; replacing a 20-page pack with a one-page decision log and measuring the effect on decision speed is a demonstrable improvement to how the organisation ran.

  4. Bullet 4

    Recommended stopping a £600k warehouse automation project at the second stage gate after a supplier failure made the business case unviable; ran the close-down, redeployed six of eight staff and recovered £180k of committed spend.

    The cancelled project, included on purpose. Stopping something at a stage gate for the right reason, then closing it down cleanly and recovering committed spend, demonstrates judgement that no successful delivery can show. Most candidates leave these off; it is usually a mistake.

Section by section

Why the CV is built the way it is

Every choice on the page, in the order you meet it — including the things that are deliberately missing.

Certifications visible but not leading

PRINCE2, PMP and AgilePM sit in the sidebar where a screener can find them in a second. They are not in the summary, because certifications are a filter rather than a reason to hire — the letters get the CV past the sift, and the budget figures get the interview. Inverting that order is the most common structural error in project management CVs.

The context line under each employer

Sector, company size, the value band of the projects run and the reporting line. This lets a reader place the whole role before reading a bullet, and it explains why the same job title covers a £150k rollout in one entry and a €2.4m programme in another.

Every project sized the same way

Value, headcount, duration, vendors, sites. Once the reader learns the pattern in the first bullet, they can size each subsequent project at a glance. Consistency is itself a signal in this profession — the CV reads like something produced by a person who keeps a register.

Variance reported against the baseline

Five weeks late, 3% under budget, on the baseline date, no service interruption. Each project carries an outcome measured against something. This is the section of the document that separates a delivery record from a work history, and the honesty in it is the reason the good numbers are credible.

A two-column layout, chosen deliberately

The sidebar holds skills, certifications and languages — short, self-contained blocks — while the wide column runs the narrative. Two columns are riskier in a parser than one, which is an acceptable trade here because delivery roles are often filled through agencies and direct approaches. For a large corporate portal, the same content in a single-column template is the safer send.

Methodology named per project, not listed as a set

There is no paragraph claiming Agile, Waterfall, Scrum, Kanban, Lean, SAFe and hybrid all at once. Stage-gate governance appears where it was used, hybrid delivery appears as a skill, and the certifications carry the rest. Naming the method where it was applied is a claim; listing nine of them together is not.

A promotion kept as one entry

The early role reads "Project Coordinator → Junior Project Manager" with a single date range. Splitting it would fragment a short period into two thin entries and make the tenure look unstable; the arrow shows the progression in four characters.

Adapt it

What to change if you have less experience

  • Four or five years in: keep the sizing discipline exactly as it is, but expect smaller numbers. A £120k project run properly, reported with its variance, is more convincing than a vague association with a large programme.
  • If you have run projects without the job title — in operations, engineering, clinical or finance roles — put a "Key projects" section directly under the summary and let the employment history sit beneath it as context.
  • Without a certification, make the budget and outcome figures unmissable in the top third of the page, and consider adding "PRINCE2 Practitioner — exam booked for March" if that is true.
  • One page until roughly six or seven years. Compress the coordinator roles to a line each and give the space to the two largest deliveries.
  • Include a project that went badly and was recovered. Early-career CVs are the ones most likely to read as uniformly successful, and that is exactly when a sponsor becomes sceptical.

US market

What to change for a US résumé

  • PMP is the dominant credential in the US: keep it, spell out PRINCE2 and AgilePM in full, and do not assume either is recognised.
  • One page until around ten to twelve years, which here means folding the third role into a single line and trimming the sidebar.
  • Convert budgets to USD or state the currency next to each figure, and give team size as headcount rather than day rates.
  • "Programme" becomes "program", and be careful with the title: in US technology companies a "program manager" often does cross-team coordination rather than capital delivery.
  • Keep the variance reporting. It is unusual in every market and it works in all of them.

The conventions behind those edits are set out in full on the US résumé guide.

Use the structure, not the sentences

Everything above is fictional, and it is meant to be studied rather than copied. Recruiters in a given field read hundreds of CVs a month and recognisable phrasing is noticeable — the value of a worked example is in showing you what to include, how a claim is constructed and where it belongs on the page. The specifics have to be yours, because the specifics are the only part that persuades anyone.

The most portable things here are the scope line under each employer, the distribution of bullets across the roles, and the habit of ending a sentence with a number and its method rather than with an adjective. Those three transfer to almost any profession. For the advice that does not transfer — the metrics, the section order, the terms a parser in your field is matching for — read the profession guides.

Project manager CV example: common questions

Yes, if you can explain it in a clause. Experienced sponsors read a perfect record as either a junior career or a lack of candour, and both are worse than a slip with a reason. The framing that works is variance against the original baseline plus what caused it — "five weeks behind after absorbing two approved scope changes" is an entirely respectable outcome, and it makes every other number on your page more believable.

Keep going

Start from this project manager example

Open the editor with the same template already selected, then replace the content with your own. Switching to another design later keeps every word you have written.

Start from this exampleRead the profession guide

Free to start. A Pro or Lifetime plan unlocks this design and every other one.