Project Manager resume examples

Colin's summary opens with his kind of work (process and system rollouts), his load of 6 to 8 projects a year and the $250K to $2M budget range. A hiring manager can match him to an operations or financial services role from that one line. PMP closes the summary with the year he earned it.

His most useful bullet is the warehouse system rollout at the freight company. It names the slip (a vendor's scanner integration 5 weeks late), the three changes he made, and how the project finished against the original date and budget. Start from this example if you run internal business or systems projects and want your record to read as delivered work.

Each of the next four examples changes one thing from Colin's: the level (senior or junior) or the setting (construction or software). Each uses the tools and document names that appear in job ads for that setting.

The keywords that matter on a project manager resume are the tools and terms in the ad you are answering, and they change with the setting. A construction ad asks for change order processes and Primavera P6. A software ad asks for Jira, dependencies and releases.

Put each tool in two places: the skills list, and the bullet where you used it, as in "Tracks budget, schedule and risks in Smartsheet and MS Project." A tool that appears only in the skills list is a claim. In a bullet, it shows what you used it for.

Copy the ad's exact wording for methods and documents. If it says "recovery plan", "RAID log" or "change order process", use that phrase in a bullet about work you did. Leave out tools you have only seen in a demo, because interviewers ask how you set them up.

A strong project manager bullet tells the reader how big the project was and how it finished against plan, in one sentence. Write the budget, the team size, the length and the result against the original date and budget.

Use the budget you managed or tracked. If you never saw the budget, give another measure of size: sites, users, contract value or the number of trade packages. Add the people the project reached when that was its point, such as 240 claims adjusters or 12,000 field technicians.

State the finish plainly, including when it was late. "2 weeks past the original date and $40K under budget" is more believable than "on time and on budget" on every project. For a portfolio, give the rate instead, as in "9 of the last 10 closed projects within 5% of approved budget."

Claim PMP only after PMI confirms you passed the exam, and show your real status if you haven't. Most ads call it preferred, and some give you time after hire: one health system asks for PMP within a year, and an engineering firm hiring for electric power projects would like it within two.

PMI requires 36 months of experience leading projects in the past 10 years if you have a bachelor's degree, or 60 months with a high school diploma, plus 35 hours of project management training. Most junior candidates can't meet that yet, so they list a credential they hold, such as the Google Project Management Certificate.

When you hold PMP, put it in the credentials section with the year and end your summary with it too, as the mid-level, senior and IT examples do.

Your best bullet is often a project that went off plan, because it shows the judgment a hiring manager is paying for. Name the cause in a few words, list what you changed, and give the finish against the original date and budget.

Make the cause specific: a vendor integration 5 weeks late, a 5-week switchgear delay, a tax table update that arrived late, or client content that missed its date. "Overcame challenges" doesn't tell the reader how big the problem was.

Describe the actions as changes to the plan. Colin resequenced three site go-lives, added two weekend cutovers and moved training online. Mateo resequenced drywall and ceiling work around late switchgear. Leah split a release so most of it shipped on its planned date.

Close with the landing, even when the project was late. Colin's warehouse rollout finished 2 weeks past the original date and $40K under budget. Avery's website refresh launched its core pages 1 week behind instead of 4.

Scope changes count too. Show the requests that came in and what happened to them, as in "sponsors have approved 5 of 14 scope requests and moved 9 to a second phase." Use one recovery bullet per job, two at most, so the resume doesn't read as a run of rescued projects.

A senior project manager resume describes a portfolio and the people running it, a mid-level one describes projects you ran yourself, and a junior one shows project work done under a coordinator, analyst or engineer title.

If you're senior, open the summary with the annual portfolio budget, the number of projects and the number of project managers you lead. Then write bullets for decisions only a senior person makes: what you paused or rescoped with the steering committee, which vendor terms you negotiated, and what you report each month and to whom.

Keep one or two bullets about individual projects with their numbers, because senior hiring managers still check that you have delivered. A budget record across the portfolio, like Rachel's 9 of 10 projects within 5%, covers the rest in one line.

At mid level, give your yearly project count and budget range in the first bullet of your current job, then pick the two or three projects that best match the ad for their own bullets.

If you're junior, keep your real title and let the bullets show ownership. Write "Runs 4 to 6 client projects at a time, $20K to $80K each" instead of "Supported project managers." Early in your career, add a student or volunteer project that had a budget and a team, like Avery's 200-person career fair.

In construction the usual ladder is project engineer, assistant project manager, then project manager. List each title with its own bullets, as Mateo does, so the reader sees when you started pricing change orders and buying out subcontracts.