LUCERIA
Sign in
Business, operations and administration · Mid level · US conventions

Project manager: resume example, explained

This fictional example shows a project manager delivering business systems and relocation projects since 2019 and applying for a senior project manager role: every project carries its budget, duration and team size, method is shown through the artifacts the candidate actually runs, and the certification is listed once as held rather than required. Each decision is explained, three weak bullets are rewritten from the evidence behind them, and the editable download lets you replace every detail with your own. Nothing here describes a real person.

Illustrative example. An illustrative, invented project manager delivering projects at a fictional regional insurer since 2019, moving from coordinator to project manager, now applying for a senior project manager role at a fictional logistics software company. Every employer, date and figure is fictional.

Editable version of this example (.docx)

The example document

Daniela Okafor-Reyes

Project Manager · business systems and facilities projects · budgets to $1.8M, teams to 14

Columbus, Ohio · 555-0142 · daniela.okafor-reyes@example.com

Profile

Project manager delivering business systems and office relocation projects for a fictional regional insurer since 2019, managing budgets up to $1.8M and cross-functional teams of up to 14. Runs projects on a stage-gate method with weekly status reporting, a maintained risk register and formal change control. Seeking a senior project manager role across a larger portfolio.

Experience

Project Manager, Business Operations — Fictional Scioto Valley Mutual Insurance

May 2022 – present · Portfolio of three to five concurrent projects; matrixed team members from IT, finance, claims and facilities.

  • Delivered the claims document-imaging replacement ($1.8M, 11 months) on schedule and within 3% of budget, coordinating a 14-person team across IT, claims operations and the vendor.
  • Led the relocation of 220 staff to a new office over one weekend with no claims-processing downtime, sequencing moves with facilities and the telephony and network vendors.
  • Run formal change control on every project: all 11 change requests in the past year were costed and approved by the steering group before work started.
  • Report weekly status (schedule, budget, risks, decisions needed) to a steering group of four directors on a one-page dashboard the PMO has since adopted for all projects.
  • Coach two project coordinators on scheduling and status reporting; both now run small projects independently.

Project Coordinator, then Associate Project Manager — Fictional Scioto Valley Mutual Insurance

August 2019 – May 2022 · PMO support across 6 to 8 projects at a time.

  • Built and maintained schedules and action logs for a portfolio of 6 to 8 projects, chasing around 40 open actions a week to closure.
  • Managed a $350K meeting-room technology refresh across 18 rooms as a first lead project, finishing within budget and ahead of the planned 5-month schedule.

Education

  • BS Business Administration — Fictional State University, 2019

Certifications

  • Professional project management certification, earned 2024, renewal 2027

Skills

Stage-gate delivery and schedule management · Budget tracking and variance reporting (budgets to $1.8M) · Risk registers, issue logs and formal change control · Vendor selection and statement-of-work management · Steering group reporting and executive dashboards · Project scheduling software and collaborative task boards · Stakeholder communication across IT, operations and finance

Bullet rewrites, and the evidence behind them

Each rewrite was produced by asking an evidence question and using only the (fictional) answer. No number appears in a rewrite that is not in its evidence.

  1. Before

    Managed a large systems implementation project.

    Evidence question

    Which system, what budget, how long, how many people, and against what baseline?

    Evidence (fictional)

    Claims document-imaging replacement; $1.8M budget; 11 months; 14-person team from IT, claims operations and the vendor; delivered on schedule and within 3% of budget.

    After

    Delivered the claims document-imaging replacement ($1.8M, 11 months) on schedule and within 3% of budget, coordinating a 14-person team across IT, claims operations and the vendor.

  2. Before

    Handled change requests and project risks.

    Evidence question

    How many changes, who approved them, and what did the process prevent?

    Evidence (fictional)

    11 change requests in the past year; each costed and approved by the steering group before work began; no unapproved scope added to any project.

    After

    Run formal change control on every project: all 11 change requests in the past year were costed and approved by the steering group before work started.

  3. Before

    Coordinated an office move.

    Evidence question

    How many people moved, over what window, and which service had to keep running?

    Evidence (fictional)

    220 staff; one weekend; claims processing live on Monday morning; moves sequenced with facilities and the telephony and network vendors; no downtime.

    After

    Led the relocation of 220 staff to a new office over one weekend with no claims-processing downtime, sequencing moves with facilities and the telephony and network vendors.

Try it on your own bullets with the bullet workbench, which asks the same questions and never adds a figure you did not supply.

Transferable skills in this example

  • Budget and schedule control

    Evidence: A $1.8M, 11-month project delivered on schedule and within 3% of budget.

    Where it helps: Program management, operations management and finance business-partner roles.

  • Formal change control

    Evidence: 11 change requests costed and approved before work started, across a year.

    Where it helps: Contract management, product operations and compliance roles.

  • Executive reporting

    Evidence: A one-page weekly dashboard for four directors, adopted by the PMO.

    Where it helps: Chief of staff, business analyst and PMO roles.

  • Vendor coordination

    Evidence: An imaging vendor managed to a statement of work; telephony and network vendors sequenced on a relocation.

    Where it helps: Procurement, IT service management and facilities management.

Occupation notes

Hard requirements

  • The BLS Occupational Outlook Handbook lists no license for project management specialists. It describes a bachelor's degree as the typical entry education, notes that some positions require relevant work experience, and says professional certification, although not always required, demonstrates competency to clients and employers. Treat a certification as a credential to list with its dates, never as something a posting is assumed to require.
  • Postings usually name a method, a scheduling tool and a budget range; match the wording only where it is true of you, and attach your largest comparable project to it.

Vocabulary that belongs on the page

  • Charter, scope statement, work breakdown structure (WBS)
  • Baseline, critical path, schedule variance
  • Risk register, issue log, RAID log
  • Change control, change request, steering group
  • Stage gate, go/no-go decision, lessons learned
  • Statement of work (SOW), vendor deliverables, acceptance criteria
  • PMO, portfolio, resource leveling

Pitfalls specific to this occupation

  • Listing methodologies as skills ('agile, scrum, waterfall') with no project that used them; the interviewer will ask which one and what you changed because of it.
  • Claiming 'on time and on budget' for every project with no budget or duration given; one honest variance figure is more credible than a perfect record.
  • Describing the team's technical work as your own; a project manager's evidence is coordination, decisions and control, not the code or the cabling.
  • Letting the certification acronym do the work of the resume; it belongs in the certifications section, not the headline.

UK and US differences

  • US: US postings for this work sit under project manager, project management specialist or program coordinator; use the posting's title in your headline where it describes your role accurately.
  • US: Give budgets in dollars with the project duration; omit employer-confidential figures and say 'approximately' where you must round.

US occupation: Project Management Specialists (O*NET code 13-1082.00, O*NET 31.0 Database (O*NET-SOC 2019 taxonomy)). O*NET 31.0 Database code and title are used under the Creative Commons Attribution 4.0 International License (CC BY 4.0): https://creativecommons.org/licenses/by/4.0/. Source: U.S. Department of Labor, Employment and Training Administration; Luceria paraphrases independently and is not endorsed by O*NET. Identifies the US occupation for readers and search engines; the example's content is Luceria's own and is not derived from O*NET descriptions. Licence.

Common questions

Do I need a project management certification to apply for project manager jobs?

Not as a rule. The BLS notes that certification is not always required, although it demonstrates competency to employers and clients. List one if you hold it, with its dates; if you do not, show the artifacts and results that a certification is meant to stand for.

How many projects should a project manager resume list?

Enough to show range at your level: the largest, the most complex, and one that went wrong and was recovered. Each needs budget, duration and team size, or it cannot be compared with the posting.

Sources

Keep going

Published 6 November 2026 · Every person, employer and figure in this example is fictional. Drafted with AI assistance and checked against Luceria’s editorial standards.