Operations
Project Manager CV: what employers ask for
Project manager CVs are judged on delivery: what you delivered, how large and complex it was, and whether it landed on time and on budget. Screeners also look for how you handled risk, change and stakeholders when things did not go to plan.
From real postings
We read 37 Project Manager job postings from 19 companies on 6 November 2026. The most named asks were Stakeholder management (27), Cross-functional work (22) and Timelines / scheduling (21). 29 postings stated years of experience; the middle value was 5.
One-time analysis • $2.99 • No subscription
What a strong Project Manager CV looks like
Start here if you are editing a CV today. The evidence for each point follows below.
Section order, top to bottom
- HeaderName, email, phone, city and a LinkedIn link. Put a certification after your name only if the posting asks for it, for example "PMP".
- SummaryTwo or three lines: your title, years of experience, the kind of projects (software, construction, operations), and the largest scope you have run.
- ExperienceMost recent first. One bullet per project that matters, each with budget, team size, duration and how it landed.
- CertificationsPMP, PRINCE2, CAPM or a Scrum certification, near the top if the posting names one, otherwise near the end.
- Skills and toolsMethods (Agile, Waterfall, hybrid) and tools (Jira, Smartsheet, MS Project). Short, and matched to the posting.
- EducationDegree and institution. Some postings in our sample mentioned a degree; fewer than half.
The summary
Lead with scope and domain. A reviewer wants to know quickly whether you have run projects of this size, in this kind of work. Managing stakeholders was the most named ask in our sample, so one concrete line about who you report to helps.
Project manager with six years of experience delivering IT and facilities projects of up to $2M. I run schedules, budgets and vendors, and report to senior sponsors on risk and progress.
Skills: show them, do not just list them
Stakeholders, timelines, vendors and budgets each came up in more than half the postings we read. Show each one through a project: whose sign-off you needed, the deadline you held, the vendor you managed, the budget you tracked. Tool names such as Jira or Smartsheet support that evidence but never replace it.
Weak and strong bullets
Illustrative rewrites, not real candidates. Use your own work, and only numbers you can back up.
Weak: Managed IT projects.
Stronger: Led the rollout of a new CRM to 350 sales staff across 6 offices, delivered in 7 months and 4% under a $600k budget.
Why it works: Scope, duration, budget and outcome in one line. That is the shape every project bullet should have.
Weak: Handled risks and issues.
Stronger: Spotted a vendor delay early and re-sequenced testing, keeping go-live on its original date.
Why it works: A real risk, the action you took, and what it protected. It shows judgement, not a duty.
Weak: Reported to stakeholders.
Stronger: Ran fortnightly steering meetings with the CFO and COO, using a one-page status report that replaced a 20-slide deck.
Why it works: Names who the stakeholders were and what you changed about reporting.
Weak: Managed contractors.
Stronger: Coordinated four contractors on an office fit-out, holding them to a shared weekly schedule and closing the snag list two weeks before move-in.
Why it works: Vendor and contractor management ranked high in our sample. This shows it with a schedule and a result.
What Project Manager job postings ask for
Counted from 37 real postings, not guessed. When you paste a posting into Resymetry, it checks each of these asks against your CV and marks it as shown, only listed, or missing.
| Skill or ask | Postings naming it | Only as nice to have |
|---|---|---|
| Stakeholder management | 27 of 37 | 1 |
| Cross-functional work | 22 of 37 | 1 |
| Timelines / scheduling | 21 of 37 | – |
| Vendors / third parties | 21 of 37 | 1 |
| Budget | 20 of 37 | – |
| Risk management | 13 of 37 | – |
| Metrics / KPIs | 10 of 37 | 1 |
| Status reporting | 10 of 37 | 1 |
| Jira | 9 of 37 | 3 |
| PMP / PRINCE2 | 8 of 37 | 2 |
Show 8 more
| Skill or ask | Postings naming it | Only as nice to have |
|---|---|---|
| Agile | 7 of 37 | – |
| Smartsheet / MS Project | 7 of 36 | 2 |
| Change management | 6 of 37 | 1 |
| Prioritisation | 5 of 37 | 1 |
| Scrum | 5 of 37 | – |
| B2B / SaaS | 4 of 37 | 1 |
| Monitoring / observability | 4 of 37 | – |
| AWS | 3 of 37 | – |
This is a small sample, so read it as a direction rather than a measurement. Many of these postings were for construction, facilities and hardware projects at engineering companies, not software delivery. That is why vendors, budgets and schedules rank high, and Agile and Scrum lower than you might expect.
How we counted
On 6 November 2026 we read 37 live Project Manager postings from 19 companies, through their public job boards (Greenhouse, Lever and Ashby). A posting counted when its title matched the role. We took at most three per company, so no single employer sets the result.
A skill counts once per posting, when it is named outside the benefits and company boilerplate. Matching is by keyword, so read the numbers as “named in”, not “strictly required”. “Only as nice to have” means it appeared only under a heading such as “Nice to have” or “Bonus”. 25 of the 37 postings had such a heading, so that column is a floor.
By location on the posting: 24 US, 5 UK, 1 India, 7 elsewhere or remote. Most employers in the sample are technology companies, which skews the result towards their stacks.
Companies sampled: Anduril, Asana, Carvana, Databricks, Deliveroo, GitLab, Graphcore, Lucid Motors, MongoDB, Nuro, OpenAI, Oscar Health, Paytm, Redwood Materials, Relativity, Samsara, SpaceX, Stripe, Zscaler.
The script that produced these numbers is scripts/role-postings.mjs in the Resymetry repository. It stores counts only, never the text of a posting.
What employers look for in a Project Manager CV
Screeners check these first. Each one should be visible in your job entries, not only in a skills list.
- Projects you led, with budget, team size, duration and outcome.
- The delivery method the posting uses, such as Agile, Scrum, Waterfall or a mix.
- Risk, issue and change management with real examples.
- Stakeholder communication, from team members to senior sponsors.
- Certifications the posting names, such as PMP, PRINCE2 or a Scrum certification.
5 common Project Manager CV mistakes and how to fix them
Listing duties like "managed timelines and budgets".
Fix: Describe specific projects with their size and result.
No figures on scope.
Fix: Add budget, team size, number of sites or users, and duration.
Only successes, no sign of problems solved.
Fix: Include one example of a risk you caught or a project you brought back on track.
No sign of who you worked with.
Fix: Name the sponsors, vendors and teams. Stakeholder and vendor management were among the most named asks.
Certifications buried at the bottom.
Fix: If the posting asks for one, put it near the top.
Starting from scratch, or the layout is the problem rather than the content? There are free ATS CV templates to start from.
Know your chances for Project Manager roles
Your score and your biggest problems are free. The full report is a one-time $2.99.
Project Manager CV questions
- What should a project manager CV include?
- A summary with your domain and largest scope, then one bullet per important project with budget, team size, duration and outcome. Add certifications, methods and tools, and education.
- Is PMP or PRINCE2 required for project manager jobs?
- Usually not. In our sample, fewer than one in four postings named PMP, PRINCE2 or a similar certification, and some of those listed it only as a nice to have. Where a posting asks for one, show it near the top.
- What numbers should a project manager CV include?
- Budget, team size, duration, number of sites or users, and how the project landed against its plan. Use only numbers you can back up in an interview.
- How do I write a project manager CV with no project manager title?
- Find the projects you already ran inside another job, such as a migration, an office move or a launch. Write them as project bullets with scope, deadline and result, and say plainly what you coordinated.
- How is a project manager CV different from a product manager CV?
- A project manager CV shows delivery: scope, schedule, budget and risk. A product manager CV shows decisions: what to build, why, and what changed for users. Read the posting carefully, because the titles are often mixed up.