Aspirational Hub

Project Manager Resume Example (+ Template)

A full mid-level sample you can copy, plus bullet formulas, skills, and the certifications hiring managers actually look for.

Table of contents

A project manager resume works best when it shows scope — budget size, team size, number of projects, delivery dates — rather than listing duties. Below is a complete mid-level sample you can model, an entry-level variant, and section-by-section instructions for writing your own.

Tailor the summary and the top three bullets of your most recent job to each posting. Everything else can stay fixed.

Sample resume

This is a mid-level example — roughly five to seven years of experience, managing projects rather than programs. Replace the content with your own; keep the shape.

JORDAN A. REYES

Austin, TX | (512) 555-0142 | jordan.reyes@email.com | linkedin.com/in/jordanareyes

PROJECT MANAGER

Project manager with 6 years delivering software and process-improvement projects in regulated industries. Managed portfolios of 4–6 concurrent projects with budgets to $1.8M and cross-functional teams of up to 22. PMP certified; comfortable running waterfall, Scrum, and hybrid delivery.

EXPERIENCE

Project Manager — Midwest Health Systems, Austin, TX — Mar 2021 – Present - Manage a portfolio of 5 concurrent IT projects with a combined annual budget of $1.8M, reporting status to a steering committee of 7 executives every two weeks. - Delivered a claims-processing platform migration across 3 sites and 340 end users, closing 4 weeks ahead of the baseline schedule and 6% under budget. - Rebuilt the intake process for new project requests, cutting average time from request to approved charter from 9 weeks to 4. - Run risk reviews on a 60-item register, escalating 8–12 items per quarter to the PMO with mitigation owners and dates. - Coach 3 associate project managers on scheduling in MS Project and status reporting; 2 have since taken on their own projects.

Associate Project Manager — Midwest Health Systems, Austin, TX — Jun 2019 – Mar 2021 - Supported 2 senior PMs on a $4.2M ERP implementation, owning the 1,100-line schedule in MS Project and the weekly critical-path review. - Coordinated 14 vendor deliverables and tracked acceptance against contract milestones, resolving 9 disputed items without schedule slip. - Produced a one-page executive dashboard in Power BI, replacing a 12-slide status deck and cutting reporting prep from 6 hours to 90 minutes a week. - Facilitated sprint ceremonies for a 9-person development team during the hybrid-delivery phase, maintaining an average velocity within 10% of commitment.

Project Coordinator — Lanier Consulting Group, Dallas, TX — Jul 2017 – Jun 2019 - Maintained schedules, RAID logs, and meeting minutes for 6 client engagements running concurrently. - Processed 60+ change requests per year through the change control board, tracking approved scope and budget impact in Smartsheet. - Onboarded 25 contractors across 4 projects, including access, tooling, and timesheet setup.

SKILLS Scheduling and critical path (MS Project, Smartsheet) | Budget and forecast tracking | Risk and issue management (RAID) | Change control | Agile/Scrum ceremonies | Jira, Confluence, Asana | Stakeholder and steering-committee reporting | Power BI, Excel (pivot tables, index/match) | Vendor and SOW management | Requirements gathering

EDUCATION B.B.A., Management — University of North Texas, Denton, TX — 2017

CERTIFICATIONS Project Management Professional (PMP), Project Management Institute — 2022 Certified ScrumMaster (CSM), Scrum Alliance — 2020

Entry-level variant

If you have not yet held the project manager title, lead with coursework, a certification in progress, and any coordination you have done — the work counts even when the title did not say "project."

PRIYA N. SHAH

Columbus, OH | (614) 555-0198 | priya.shah@email.com | linkedin.com/in/priyanshah

PROJECT COORDINATOR / ASPIRING PROJECT MANAGER

Operations coordinator with 2 years scheduling and tracking work for cross-functional teams, now moving into formal project management. CAPM certified; built and maintained schedules, budgets to $150K, and status reporting for 8 concurrent initiatives.

EXPERIENCE

Operations Coordinator — Buckeye Facilities Services, Columbus, OH — Aug 2022 – Present - Track 8 concurrent facility upgrade projects in Smartsheet, publishing a weekly status summary to 12 stakeholders. - Manage purchase orders and invoices against a $150K annual project budget, flagging variances above 5% to the operations director. - Coordinate 3 vendor crews and internal staff across a 6-week office relocation for 85 employees, completed with no business-day downtime. - Document meeting decisions and action items for a standing 10-person planning group; follow up on 20–30 open actions per month.

Administrative Assistant (part-time) — Scioto Valley Nonprofit Alliance, Columbus, OH — Sep 2021 – Aug 2022 - Built the event schedule and volunteer roster for an annual conference with 400 attendees and 45 volunteers. - Maintained the task tracker for a grant reporting cycle with 11 deliverables and fixed funder deadlines.

PROJECTS - Capstone: planned a 12-week simulated product launch, producing a charter, WBS, risk register, and baseline schedule in MS Project; presented to a faculty panel.

SKILLS Scheduling (Smartsheet, MS Project) | Status reporting | Budget tracking | Meeting facilitation | RAID logs | Jira | Excel | Vendor coordination

EDUCATION B.S., Business Administration — The Ohio State University, Columbus, OH — 2022

CERTIFICATIONS Certified Associate in Project Management (CAPM), Project Management Institute — 2023 Google Project Management Certificate — 2022

How to write each section

1. Header

Name, city and state, phone, email, LinkedIn. That is all you need.

  • Do not put a street address. City and state is enough, and it tells a recruiter whether you are in commuting range or applying remote.
  • Use a plain email address with your name in it.
  • Add your target title as a line under your name if your current title does not match what you are applying for — for example "Project Manager" above a resume that says Project Coordinator. It frames everything below it.
  • Skip photos, headshots, graphics, and icons. US employers do not expect them and they break text extraction in some applicant tracking systems.

2. Summary

Three sentences, no more. A formula that works:

Summary formula

[Title] with [X] years delivering [project types] in [industry or domain]. Managed [number] concurrent projects with budgets to [$] and teams of [number]. [Certification] certified; experienced in [delivery methods].

Two worked examples:

Construction / capital projects

Project manager with 9 years delivering commercial construction and tenant improvement projects in the Southeast. Managed 3–4 concurrent jobs with contract values to $12M, directing subcontractor teams of 40+. PMP certified; fluent in Procore, RFI and submittal workflows, and GMP contracts.

Marketing / agency

Project manager with 5 years running integrated campaign delivery for B2B clients. Managed 10–14 concurrent workstreams across creative, media, and web with budgets to $600K. CSM certified; runs agile ceremonies in Jira and resource planning in Float.

What to avoid: "seeking a challenging role where I can grow." The summary is for the employer's benefit, not a statement of your hopes.

3. Experience

Use reverse chronological order. Company, title, city and state, month and year range. If you were promoted inside one company, stack the titles under one company heading so the progression is obvious.

Every bullet follows one shape:

Bullet formula

[Action verb] + [what you managed or changed] + [scope: budget, headcount, project count, duration, sites, users] + [outcome, if you have one]

Scope is the part most project managers leave out. "Managed a software project" could mean two developers for a month or forty people for two years. Say which.

Example bullets, drawn from different sectors and levels:

  • Delivered a 14-month warehouse automation project with a $3.4M capital budget, handing over 3 weeks ahead of the baseline finish date.
  • Managed 6 concurrent client projects with a combined contract value of $900K, maintaining an on-time delivery rate across all 6 for 4 consecutive quarters.
  • Ran weekly change control for a program of 9 projects, processing 70 change requests per year and documenting cost and schedule impact for each.
  • Built the resource plan for a 32-person delivery team across 5 projects, reducing double-booked assignments from 11 per month to 2.
  • Chaired a steering committee of 8 directors, producing a 2-page status pack every two weeks and escalating 3–5 decisions per meeting.
  • Led the discovery phase for a CRM replacement, running 18 stakeholder interviews and producing 140 documented requirements signed off by 4 business owners.
  • Negotiated scope and schedule with 5 vendors under fixed-price SOWs, recovering 6 weeks of slippage without a change in contract value.
  • Closed out 12 projects to PMO standards, including lessons-learned sessions, financial reconciliation, and benefit-realization handover to operations.
  • Migrated 240 active tasks and 9 project plans from spreadsheets into Smartsheet, cutting status-report preparation by roughly 5 hours per week.
  • Coordinated a phased go-live across 4 locations and 1,100 users, with a 48-hour hypercare rota and 31 logged defects resolved inside 5 business days.

Three to five bullets per job for recent roles, two or three for older ones. Anything more than ten years back can be a single line or dropped.

4. Skills

Keep it to one block of 8–12 items, grouped so a reader can scan it. Name tools by their real names — MS Project, Smartsheet, Jira, Confluence, Asana, Monday.com, Primavera P6, Procore, Power BI, SAP, Workday — not "project management software."

Mix three things:

  • Delivery methods: waterfall, Scrum, Kanban, SAFe, hybrid.
  • Process skills: scheduling and critical path, budget and forecast tracking, risk and issue management, change control, earned value, resource planning, vendor and SOW management.
  • Tools: whichever you can actually use in an interview.

Do not list a tool you would not want to be asked about. Interviewers ask.

5. Education

Degree, major, institution, city and state, graduation year. One line each.

  • Drop your GPA once you are more than two or three years out.
  • If you did not finish a degree, you can list the institution and the coursework completed without implying a credential — for example "Coursework in Business Administration, 2018–2020."
  • No degree at all is common in project management, particularly in construction, manufacturing, and trades-adjacent work. In that case lead with certifications and let experience carry the resume.

6. Licences and certifications

Give the full name, the issuing body, and the year. If it is in progress, say so with your exam date.

The credentials that carry weight in US project management hiring:

  • PMP (Project Management Professional) — Project Management Institute. The most widely recognized. Requires documented project experience plus the exam, and periodic renewal through professional development units.
  • CAPM (Certified Associate in Project Management) — Project Management Institute. The entry-level version, aimed at people without the experience hours for PMP.
  • PMI-ACP (Agile Certified Practitioner) — Project Management Institute, for agile-heavy delivery.
  • CSM (Certified ScrumMaster) — Scrum Alliance; PSM (Professional Scrum Master) — Scrum.org. Common where delivery is in sprints.
  • PRINCE2 — more often asked for by employers with UK or European parent companies, and on some government-adjacent work.
  • CCM (Certified Construction Manager) — Construction Management Association of America, for capital and construction projects.
  • Lean Six Sigma Green or Black Belt — relevant where the projects are process improvement.

True occupational licences are rare for project managers, but they do appear in construction: a state contractor's licence, or a Professional Engineer (PE) licence, where the scope of work requires it. Licensing rules are set state by state — check with the licensing board in the state you will be working in rather than assuming what applies elsewhere carries over. Security clearances, where you hold one, go here too, listed by level and status.

Formatting

  • One page if you have under 10 years of experience; two pages is accepted above that. Never three.
  • 10 to 12 point body text, 14 to 16 point for your name.
  • Margins of 0.5 to 1 inch on all sides.
  • One standard typeface throughout — Calibri, Arial, Garamond, Georgia.
  • Submit as PDF unless the posting asks for .docx. Name the file FirstnameLastname-Resume.pdf.
  • No tables, text boxes, columns, or headers-and-footers containing information you need read. They can scramble in automated parsing.

Weak vs strong bullets

The difference is almost always scope. The weak version describes a duty anybody with the title would have; the strong version attaches numbers a reader can picture.

Pair 1 — Budget

Weak

Responsible for managing project budgets and tracking spend.

Strong

Managed a $1.8M annual portfolio budget across 5 projects, producing monthly forecasts and closing the fiscal year 6% under plan.

Pair 2 — Schedule

Weak

Created and maintained project schedules using MS Project.

Strong

Owned a 1,100-line MS Project schedule for a 14-month ERP rollout, running weekly critical-path reviews and absorbing 3 scope additions without moving the go-live date.

Pair 3 — Stakeholders

Weak

Communicated project status to stakeholders and senior leadership.

Strong

Chaired a biweekly steering committee of 7 executives, presenting a 2-page status pack and securing decisions on 4–6 escalated risks per meeting.

Pair 4 — Team leadership

Weak

Led cross-functional project teams to successful outcomes.

Strong

Directed a cross-functional team of 22 across engineering, QA, and operations through a 3-site deployment to 340 users, with 31 defects cleared inside a 5-day hypercare window.

If you genuinely do not have a number, use a different kind of scope: duration, number of sites, number of workstreams, number of vendors, headcount. One of those is nearly always available.

Skills to include

Pick the 8–12 that match the posting. Listing a skill is cheap; the right-hand column is where it becomes credible.

SkillHard or softHow to show it on the resume
Scheduling and critical pathHardName the tool and the size: "1,100-line MS Project schedule, weekly critical-path review."
Budget and forecast managementHardState the budget you owned and the variance you landed on.
Risk and issue managementHardGive register size and escalation rate: "60-item RAID register, 8–12 escalations per quarter."
Change controlHardVolume and process: "70 change requests per year through a formal CCB."
Agile and Scrum deliveryHardName the ceremonies you ran and team size; back it with CSM or PSM in certifications.
Earned value managementHardMention CPI/SPI reporting if you actually produced it — common on federal and construction work.
Resource planningHardHeadcount across projects, and what the plan fixed.
Vendor and contract managementHardNumber of vendors, contract type (fixed price, T&M, GMP), and what you negotiated.
Reporting and dashboardsHardName the tool — Power BI, Tableau, Smartsheet — and the audience.
Stakeholder managementSoftShow it through seniority and forum: steering committees, sponsors, client executives.
FacilitationSoftWorkshops, discovery sessions, retrospectives — with participant counts.
Conflict resolution and negotiationSoftAttach it to an outcome: disputed deliverables resolved, scope renegotiated without cost change.

Soft skills do not belong in a standalone list of adjectives. Put the evidence in a bullet and let the skill be the conclusion a reader draws.

Pay and outlook

Project manager pay in the US varies more than almost any other job title, because the title covers very different work. A project manager running $200K marketing campaigns and one running a $40M capital construction program share a job title and little else.

What moves the number:

  • Industry. Construction, engineering, pharmaceuticals, aerospace, and IT infrastructure tend to pay differently from nonprofit, education, and internal operations work. The same resume lands in different bands depending which sector you aim at.
  • Budget and team size. The scope you have carried is the single strongest signal of level, which is why it belongs in your bullets rather than on a separate line.
  • Location. Metro area makes a substantial difference, and the gap between high-cost coastal markets and the rest of the country is real. Remote roles sometimes anchor pay to the employer's location, sometimes to yours — ask early.
  • Certification. PMP in particular is treated as a level marker by many employers, and some postings make it a requirement rather than a preference. Whether it changes your offer depends on the employer.
  • Employer type. Government, government contractors, consultancies, and in-house corporate teams each structure pay differently. Federal and state roles usually sit on published pay schedules; consultancies more often pay a lower base with a utilization or billing-linked bonus; corporate roles commonly add an annual bonus tied to company and individual performance.
  • Contract versus permanent. A lot of project management work is contract or fixed-term, paid hourly or on a day rate, usually without benefits. Compare total package, not headline rate.

For current, impartial numbers, use the US Bureau of Labor Statistics — the Occupational Outlook Handbook and the Occupational Employment and Wage Statistics program both publish wage data by occupation and by metro area, including project management specialists. Your state's labor market information office publishes state and regional breakdowns, which are often closer to what you will actually be offered. Check both before you name a figure in a negotiation.

On outlook: demand for project managers tracks capital spending and transformation programs in whichever sector you work in, so it moves with the industry rather than with the job title. If you want to see where hiring is concentrated right now, read the postings in your target metro area for a month and note which sectors appear repeatedly and which certifications they ask for. That tells you more about your local market than any national figure will.

Outside the US, pay structures and the weight given to particular certifications differ — PRINCE2 is more commonly requested in the UK and parts of Europe, for example — so check local sources rather than applying US benchmarks.

Related guides

For the same role

  • Project Manager Cover Letter Example (+ Template)
  • Project Manager Interview Questions and Answers
  • How to Explain a Failed Project in an Interview
  • PMP Certification: What It Is and Who Needs It

Neighbouring roles

  • Project Coordinator Resume Example (+ Template)
  • Program Manager Resume Example (+ Template)
  • Scrum Master Resume Example (+ Template)
  • Product Manager Resume Example (+ Template)
  • Construction Project Manager Resume Example (+ Template)
  • IT Project Manager Resume Example (+ Template)
  • Business Analyst Resume Example (+ Template)
  • Operations Manager Resume Example (+ Template)

Resume mechanics

  • How Long Should a Resume Be?
  • How to Write a Resume Summary
  • Resume Formatting: Fonts, Margins and File Types

Frequently asked questions

How do I write a project manager resume with no project manager experience?

Change the label, not the facts. Most people moving into project management have already coordinated work — a system rollout, an office move, an event, a grant reporting cycle, a product launch — without the title attached. Write those up as projects, with the same scope units you would use in a PM bullet: duration, headcount, budget, number of stakeholders, number of deliverables. Three things help on an entry-level resume. First, add a Projects section if your paid work is thin; academic capstones and volunteer project work are legitimate content when they include a charter, a schedule, and a risk register. Second, get a credential started and list it as in progress with an exam date — CAPM or an introductory project management certificate shows intent and gives you vocabulary. Third, name the tools, because tool familiarity is checkable and lowers the perceived risk of hiring you. Set your target title at the top of the resume, but be realistic about which rung you are applying for. Project coordinator, project analyst, and associate project manager are the usual entry points, and most project managers came through one of them.

What format should a project manager resume use?

Reverse chronological, almost always. Employers hiring project managers want to see a progression of increasing scope, and that is only visible when jobs run newest to oldest with dates attached. Functional or skills-based formats hide dates, which reads as evasive in a field where delivery history is the point. A hybrid works if you are changing industries: keep the reverse chronological job list, but add a short block near the top that groups transferable delivery experience, so a reader sees the relevance before they see unfamiliar company names. Mechanically: one typeface, 10–12 point body text, 0.5–1 inch margins, clear section headings, and no multi-column layouts or text boxes. Export to PDF unless the application form asks for a Word file. Keep bullets to one or two lines each — a project manager who cannot summarise is a bad sign, and your resume is the first sample of your reporting.

How long should a project manager resume be?

One page under roughly ten years of experience. Two pages above that, or when you are listing a long portfolio of distinct projects — common in construction and consulting, where a project list is part of how you are assessed. Three pages is too many outside academia, and a federal resume is a separate format with its own rules. If you are over by a few lines, cut from the oldest roles first, then trim bullets that describe duties rather than scope. Jobs more than ten to fifteen years back can be a single line with title, employer, and years, or left off entirely.

Should I list every project I have managed?

No. Pick the ones that match the posting and show the widest range of scope. Three to five bullets per recent role is enough, and each should carry a different kind of evidence — one budget, one schedule, one stakeholder, one team or vendor. If the detail genuinely matters for your field, add a short Selected Projects section with one line per project: name or type, value, duration, your role. That is standard on construction and consulting resumes, and it keeps your experience bullets from turning into an inventory.