[ RESUME EXAMPLE · 3 ROLES · 14 KEYWORDS TUNED ]
Project Manager Resume Example
This project manager resume example shows a PMP-certified PM who moved from project coordinator to running a $22M portfolio. Every role quantifies budget size, schedule performance, and stakeholder count, while the skills block uses common project-management posting terms such as Agile, Scrum, risk management, Jira, and vendor management. Load it into the free builder, substitute your own programs, and run the ATS check against the posting.
Marcus Thompson, PMP
Senior Project Manager
marcus.thompson.pm@email.com · (720) 555-0119 · Denver, CO · linkedin.com/in/marcusthompsonpm
Summary
PMP-certified project manager with 11 years delivering software and infrastructure programs from $250K to $8M. Ran a 14-month EHR migration for 1,200 users that finished 3 weeks early and 6% under budget. Currently manage a $22M annual portfolio across 6 concurrent workstreams.
Experience
Senior Project Manager · Meridian Health Systems
Jan 2021 – Present
Denver, CO
- Direct a $22M annual portfolio of 6 concurrent clinical and infrastructure projects with a team of 4 PMs.
- Delivered a 14-month EHR migration for 1,200 users 3 weeks early and 6% ($480K) under budget.
- Introduced risk burn-down reporting that cut late-stage scope surprises 70% across the PMO.
- Manage vendor contracts worth $4.5M annually with 96% SLA compliance.
Project Manager · Summit Construction Tech
Mar 2017 – Dec 2020
Boulder, CO
- Ran 20+ software implementation projects with a 94% on-time delivery rate across 3 regions.
- Built the PMO intake and prioritization process later adopted by 45 stakeholders company-wide.
- Recovered a stalled $1.8M field-services rollout, delivering within 5 months of takeover.
Project Coordinator · BuildRight Inc.
Jun 2015 – Feb 2017
Aurora, CO
- Coordinated schedules, RFIs, and change orders for 8 concurrent commercial builds totaling $30M.
- Automated the weekly owner-reporting package, saving the PM team roughly 10 hours per week.
- Tracked and cleared 300+ submittals with a 98% first-pass approval rate.
Education
B.B.A. Management, University of Colorado Denver — Minor in Information Systems
2015
Skills
Project management · Program management · Agile · Scrum · Waterfall · Risk management · Budget management · Stakeholder management · Vendor management · Change management · Jira · Confluence · MS Project · Smartsheet
Certifications
- Project Management Professional (PMP) · PMI · 2018
- Certified ScrumMaster (CSM) · Scrum Alliance · 2020
What a project manager resume has to show in the first six seconds
Budget and portfolio size
PM resumes are screened on scope before anything else: the dollar value you controlled, the number of concurrent projects, and team size. '$22M annual portfolio across 6 workstreams' positions you in one line; 'managed projects' positions you nowhere.
Schedule and budget performance, with variance
'On time and on budget' is claimed by everyone; variance numbers are believed. '3 weeks early, 6% under budget' is a verifiable claim that survives an interview. If a project overran, own the recovery story instead — recovered projects demonstrate more than easy ones.
Methodology fluency matched to the role
Software shops screen for Agile/Scrum/SAFe; construction and infrastructure screen for Waterfall, CPM, and Primavera; hybrid orgs want both. Mirror the posting's methodology language exactly — 'Agile delivery' and 'sprint-based development' should both appear if the posting uses both.
Stakeholder altitude
Who did you report to, and how many groups did you align? 'Presented monthly steering updates to 4 VPs and 45 stakeholders' signals you can operate at the level the role requires. Coordinator-level resumes describe tasks; manager-level resumes describe constituencies.
Four ways project manager resumes get filtered out
✕ Listing responsibilities instead of delivery record.
FIX → 'Responsible for project plans and status reports' describes the job description, not you. Replace each duty with a delivered outcome: what shipped, when, at what budget, for whom.
✕ No numbers anywhere on the page.
FIX → PM is the most quantifiable white-collar role there is — budgets, schedules, headcount, vendor spend, defect rates. A PM resume without numbers reads as a coordinator resume regardless of title.
✕ Certification soup without the PMP where it matters.
FIX → For most mid-to-senior PM roles the PMP is the filter. Put it after your name and in a certifications section with the year. Drop expired or vanity certificates that dilute it.
✕ Applying with one generic PM resume.
FIX → A healthcare IT posting and a construction posting want different keywords, different tool names, and different headline projects. Reorder the resume per posting and run the checker here to confirm the keyword overlap before you submit.
Common questions
Does the PMP still matter on a resume in 2026?
Yes — it remains the most common hard filter in PM recruiting, especially in healthcare, government, construction, and enterprise IT. If you hold it, put 'PMP' after your name and list it with the year. If you are sitting for it, 'PMP (exam scheduled Q3 2026)' is honest and still catches the keyword.
How do I write bullets for internal projects with no revenue numbers?
Use time, adoption, and efficiency metrics instead: users migrated, hours saved per week, teams onboarded, incident reduction, adoption percentage. 'Migrated 1,200 users to a new EHR with 3 weeks of schedule margin' is a complete PM result without a dollar figure.
Should a project manager resume list every project?
No. Pick the three or four largest per role — highest budget, most stakeholders, or best recovery story — and quantify those. A project list that runs a full page reads as padding; a short list of big, measured results reads as seniority.
Agile or waterfall vocabulary — which should I use?
Use whichever approach the posting names, plus the other if you genuinely work with it. This site's keyword check treats 'sprints', 'ceremonies', and 'SAFe' as different terms from 'critical path', 'Gantt', and 'CPM'. Run the checker against your target posting to see which terms are missing.
How do I explain a failed or cancelled project?
Frame the recovery, not the failure: 'Took over a stalled $1.8M rollout; delivered within 5 months' is one of the strongest bullets on this example for exactly that reason. If the project was cancelled for business reasons, say what you salvaged — migrated data, retained team, closed vendor contracts under budget.
How do I tailor this example to a specific posting?
Copy the example into the builder, replace the content with your own, then paste the job posting into the ATS checker. It lists the posting's keywords you are missing — add the truthful ones (say, 'SAFe' or 'risk register') to your skills and bullets, and re-scan. As a rough rule of thumb many people aim for a match around 80%, but there is no universal passing score — treat it as a 'looks strong' guideline, not a guarantee or a target every employer shares.