This is a complete, editable sample for a project manager — seven years of software and platform delivery in Seattle, a PMP, and projects described by what shipped, on what budget, with how many people. Open it, replace the details with yours, and export.
- Delivery ownership, with the numbers
- Projects delivered, budget managed, team size, and whether the work shipped on time and on budget. A project manager is judged on scope, schedule and cost — so those are the numbers the resume has to carry.
- The methodology, and the domain
- Agile, Waterfall or hybrid, plus the environment you ran it in — software, infrastructure, marketing, construction. Two PMs with the same certification fit very different programs, and naming both places you.
- The tools by name
- Jira, Confluence, Microsoft Project, Smartsheet, Asana. Teams standardize on a toolchain, and naming the one you run shortens the ramp and signals you have done the job, not just studied it.
- Risk and dependency management
- How you surfaced risk, owned the RAID log, and unblocked teams before a slip became a delay. This is the core of the job, and a resume that only lists status reporting misses it.
- Stakeholder and executive communication
- Steering committees, sponsors, cross-functional partners. Say who you reported to and how often, because the ability to hold a room of directors is what a senior PM is hired for.
- Certifications with their issuing body
- PMP, CAPM, PMI-ACP, CSM — with the body (PMI, Scrum Alliance) and the year. PMP in particular is often named as required or preferred in postings, so it belongs on the page, not inferred.