Project manager CV example and writing guide
Updated 22 June 2026
A strong project manager CV makes the scale and outcome of your work easy to grasp. This guide shows how to structure yours, write a convincing personal statement and turn routine duties into evidence of delivery.
Project Manager CV examples
Junior Project Manager
JuniorJunior Project Manager with experience supporting business change and operational improvement projects from planning through handover. Comfortable maintaining schedules, tracking budgets, coordinating stakeholders and turning project data into clear progress reports. Brings a practical approach to risk, change control and team communication.
Why it works: This example shows project scope, delivery methods, stakeholders, tools and measurable results while keeping the level of responsibility believable for an early-career candidate.
Project Manager
Mid-levelProject Manager with six years of experience delivering operational change, systems implementation and process improvement projects in hybrid and Waterfall environments. Experienced in coordinating multi-skilled teams, controlling budgets and schedules, managing risks and changes, and giving senior stakeholders concise progress reports. Known for bringing delayed work back under control and turning complex requirements into practical delivery plans.
Why it works: This project manager CV sample shows increasing ownership, names the delivery environment and backs each project claim with defensible figures covering budget, schedule, risk and stakeholder outcomes.
Senior Project Manager
SeniorSenior Project Manager with 12 years of experience delivering technology, operational change and business transformation projects. Leads multidisciplinary teams, controls seven-figure budgets and turns complex requirements into practical delivery plans, with a record of recovering delayed work and improving cost, quality and stakeholder confidence.
Why it works: Shows leadership, delivery scale, commercial control and measurable outcomes across complex programmes.
How to write a project manager CV
Use a clean, reverse-chronological format, placing your latest employment first. Most candidates should aim for two pages, although an entry level project manager CV with limited experience may fit naturally on one. Put your name and contact details in a simple header, then use familiar headings and enough white space to make the document easy to scan. Do not add a photo or date of birth.
| Section | What to include |
|---|---|
| Personal statement | Your level, delivery setting and strongest evidence of impact |
| Core skills | A focused selection matched to the vacancy |
| Employment history | Recent roles, relevant projects and measured outcomes |
| Education | Qualifications listed in reverse-chronological order |
| Extras | Relevant languages, volunteering or professional development |
Open with a short personal statement tailored to the role. In your experience section, establish each project's scope before explaining what you changed and what happened as a result. Name the delivery environment where relevant, whether Agile, Waterfall, hybrid, IT, construction or change and transformation.
Keep the skills section selective. Reflect the methods, tools and capabilities that appear in the vacancy, but only include those you can discuss confidently. Education and role-specific qualifications should sit after experience unless you are a recent graduate or apprentice, in which case they may deserve greater prominence. Extras earn their place only when they strengthen your application.
A project manager CV template can organise the page, but it cannot supply the evidence. Edit every section so the language, priorities and examples fit the post.
Personal statement examples
Project manager with six years' experience delivering business change projects in hybrid environments. Led multi-skilled teams on programmes valued at up to £1.8 million, recovering a delayed workstream and bringing the revised delivery date forward by four weeks. Confident in planning resources and costs, managing risks and change, and reporting clear decisions to senior stakeholders.
Hard-working project manager looking for a new opportunity in a successful company. I am a good communicator, work well alone or in a team and can manage many different tasks. I am passionate about projects and always give 100%.
Writing your experience
Project management bullets work best when they answer three questions: what did you own, what did you do and what changed? Start with an action verb, add enough scope to make the work understandable, then finish with a result you can substantiate. Useful measures include budget, savings, delivery time, milestone performance, team size, supplier count, defect rate or stakeholder adoption.
| Before | After |
|---|---|
| Responsible for project plans | Rebuilt the delivery plan for a £420,000 systems rollout, resolving 18 task dependencies and restoring the agreed launch date |
| Managed risks and issues | Introduced weekly risk reviews across five workstreams, closing 21 overdue actions and cutting high-rated open risks from nine to three |
| Worked with stakeholders | Ran fortnightly decision sessions with 12 operational leads, securing sign-off two weeks before the scheduled gateway |
The improved versions establish scale and connect the candidate's action to an outcome. They also show several parts of the job that matter in project delivery: detailed planning, timescales, resources and costs; progress, issue, quality and risk reporting; adapting plans when circumstances change; and working with senior management. Evidence of scope delivery is more persuasive than a list of meetings attended.
Use verbs that describe genuine ownership: delivered, planned, recovered, coordinated, negotiated, resolved, forecast, mitigated, governed, streamlined, reconciled and implemented. Choose "supported" or "assisted" when that is the honest description, especially on a junior project manager CV. Inflating your authority weakens credibility in interview.
Vary the evidence by role. A project coordinator might quantify schedules maintained, actions closed or reporting time saved. A mid-level manager can show budgets, suppliers, dependencies and changes controlled. A senior candidate should make portfolio scale, governance decisions, leadership and commercial outcomes visible. If your evidence focuses on technical design and engineering coordination rather than delivery ownership, see the project engineer CV guide.
Avoid cramming several achievements into one sentence. One action and one clear result usually read better. If a project was confidential, describe the sector, scale and outcome without naming the client or exposing sensitive details.
Key skills & ATS keywords
Hard skills
Soft skills
ATS keywords
Education & certifications
List education in reverse-chronological order with the qualification, institution and completion year. Recent graduates can add two or three relevant modules or a substantial project; experienced candidates usually need only the core details. Keep professional development separate so a reader can distinguish formal qualifications from short courses and internal training.
For the UK Project Manager apprenticeship standard, apprentices achieve either a BA Honours degree in Project Management or a BSc Honours degree in Project Management. Before the end-point assessment, apprentices are required to achieve an International Project Management Association (IPMA) Level D qualification or an accepted equivalent. The accepted equivalents in the supplied route are APM's Project Management Qualification, PMQ; Agile Project Management Practitioner (AgilePM); PRINCE2 Agile Practitioner; PRINCE2 Practitioner; and PMI Project Management Professional (PMP). These are route-specific provisions, not universal entry requirements for every project manager vacancy.
Apprentices who do not already have Level 2 English and Maths need to achieve that level before the end-point assessment. State this condition precisely if it applies to you rather than presenting it as a general requirement for the occupation.
Outside that apprenticeship route, follow the vacancy. Put a role-specific qualification near the top only when it materially supports your fit; otherwise keep it in the education or professional development section. Give the exact title and issuer, plus the completion year. Never imply that a course is complete when it is still in progress, and do not add initials or credentials that you cannot verify.
Common mistakes to avoid
Listing routine duties without showing what changed because of your work.
Turn each duty into a result-led bullet. State the action, the delivery scope and a figure you can defend, such as project value, time saved, cost avoided or a milestone reached.
Leaving the delivery environment unclear.
Name the relevant setting, such as Agile, Waterfall, hybrid, IT, construction or change and transformation. Add the method only where it accurately describes your work.
Writing vague claims such as "managed projects successfully" without explaining scale.
Give the reader context: budget, duration, team size, workstreams, locations, stakeholders, dependencies or delivery stage. Use only figures supported by your records.
Treating risks, issues and changes as interchangeable.
Show how you identified and mitigated risks, resolved live issues and controlled changes to scope, schedule, cost or quality. A short outcome makes each example more credible.
Using dense formatting, unusual headings or long blocks of text.
Use familiar headings, readable white space and concise bullets so recruiters and screening software can identify your experience, education and skills quickly.
Sending the same project manager CV for every vacancy.
Adjust the personal statement, core skills and strongest delivery examples to the advertised environment and responsibilities. Keep the underlying facts unchanged.
Junior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Personal statement | Lead with transferable delivery experience, education and the type of projects supported. Keep the scope honest and specific. | Open with portfolio or programme scale, leadership remit, delivery environment and two defensible outcomes. |
| Delivery ownership | Show ownership of defined tasks, small projects or workstreams, including plans, actions, risks and reporting. | Show accountability for project scope, governance, business cases and delivery across several workstreams or complex dependencies. |
| Team and stakeholders | Describe coordination with team members and stakeholders, including meeting support, updates and follow-up actions. | Demonstrate leadership of multi-skilled teams and work with senior management, suppliers or stakeholders across organisational boundaries. |
| Measures of success | Use modest measures such as milestones met, actions closed, reporting time reduced or records improved. | Use broader measures such as project value, budget performance, savings, delivery time, benefits achieved or quality improvement. |
| Risk and change | Show accurate maintenance of risk, issue and change records, plus examples of escalating concerns promptly. | Show evaluation, mitigation and decision making across schedule, cost, quality, scope and interdependent changes. |
| Commercial and strategic context | Mention exposure to budgets, procurement or business cases where it formed part of the role. | Connect investment decisions, contracts, resources and project outcomes to organisational objectives and value for money. |
Frequently asked questions
Two pages is a sensible target for most applicants, although relevance matters more than filling a fixed length. Keep early or unrelated roles brief and give more space to recent project delivery evidence.
Use examples from study, volunteering or another job where you planned work, coordinated people, tracked actions, handled a change or met a deadline. Describe your contribution accurately and use defensible measures rather than adopting a project manager title you did not hold.
No. Under British CV conventions, use the space for your name, mobile number, email address, location and professional profile URL instead.
List only qualifications you have completed, giving the exact title and issuer. If a vacancy asks for a role-specific qualification, place the closest relevant evidence prominently, but do not imply equivalence or completion unless you can verify it.
State your level, delivery environment and strongest areas of ownership, then add one or two outcomes with figures you can defend. A junior project manager CV can lean on transferable evidence, while a senior statement should make scale and leadership clear.
Translate relevant work into project language without changing the facts. Planning, budget exposure, supplier coordination, risk handling, stakeholder updates and delivery against deadlines can all provide useful evidence when they genuinely formed part of your role.