10 resume10 Start — it's free to try
Resume examples by role

Project manager resume: format, metrics & examples

Project management is a role defined by outcomes — budgets kept, deadlines hit, teams coordinated. Your resume should read the same way: every bullet point tied to a scope, a timeline, or a number.

Section order that works

  1. Contact info — name, phone, email, city/state, LinkedIn if it's current.
  2. Summary — years of experience, industry or project type (software, construction, marketing, healthcare), and methodology strength (Agile, Waterfall, hybrid).
  3. Certifications — PMP, CAPM, CSM, PMI-ACP, Six Sigma — listed with the issuing body.
  4. Experience — reverse chronological, each role naming project scope, team size, and budget where relevant.
  5. Tools — Jira, Asana, MS Project, Smartsheet, Confluence — whatever the role's postings actually mention.
  6. Education — degree, school, graduation year.

Every bullet point needs a number

More than almost any other role, a PM resume lives or dies on quantification, because the entire job is about managing scope, time and budget — all of which are numbers.

Weak: "Managed cross-functional projects and communicated with stakeholders."
Stronger: "Led a 12-person cross-functional team through a $2.4M platform migration, delivering two weeks ahead of schedule and 6% under budget."

If you don't have access to budget figures, use team size, number of stakeholders, number of deliverables, or percentage improvement in a process (e.g., "cut sprint planning time by 30% by introducing a standardized backlog template").

A simple formula for each bullet

Action verb + project or scope + your specific contribution + the measurable outcome. Led, coordinated, delivered, negotiated, and streamlined all read stronger than "responsible for" or "involved in."

Matching methodology language to the job posting

PM job postings usually signal their methodology clearly — sprints, backlogs and standups mean Agile/Scrum; phases, gates and milestones mean Waterfall or a hybrid approach. Mirror that language in your summary and bullet points rather than defaulting to generic project-management terms, since it's often the exact phrase an ATS or recruiter is scanning for.

Transitioning into project management

If you're moving into PM from an adjacent role (coordinator, analyst, team lead), pull out the project-management-shaped parts of your current job explicitly: any time you coordinated a timeline, managed a budget line, ran a meeting cadence, or shipped a cross-team deliverable, describe it using PM language even if "project manager" wasn't your title.

Build your project manager resume in 10 minutes

Answer 10 short questions and Ava — resume10's built-in writing assistant — helps turn your project history into bullet points like the ones above.

Start — it's free to try

Which template fits a PM resume?

The Ledger and Compact Pro are strong defaults — clean enough for corporate ATS systems, with Compact Pro especially useful if you have a long project history to fit on one page. See the full breakdown in the resume templates guide.

Frequently asked questions

Should I list PMP or Scrum Master certifications even if I'm early career?+
Yes — certifications like PMP, CAPM, CSM or PMI-ACP signal formal training and are often searched for directly by recruiters, so they're worth including even with limited years of experience.
How do I quantify a project that didn't have hard financial numbers?+
Use scope-based metrics instead: team size managed, number of stakeholders coordinated, timeline met or shortened, or number of deliverables shipped on schedule.
Agile or Waterfall — which should my resume emphasize?+
Mirror the language in the job posting. If it mentions sprints and backlogs, emphasize Agile/Scrum experience; if it mentions phases and gates, emphasize traditional Waterfall or hybrid methodology experience.