Resumes and cover letters

How to critique and rewrite your PM resume

Lesson 30 of 45~11 min read
In this lesson11 sections

An unofficial lesson drawing on the methods in the Real Resumes: Before & After chapter of Cracking the PM Interview by Gayle Laakmann McDowell and Jackie Bavaro (2014). PracHub is not affiliated with the authors or publisher. Buy the book

Rewriting a PM resume means turning a list of duties into results a stranger can check: which project, what changed, by how much, and how you know. The last part matters more than people expect. A recruiter gives your page a short skim, and if you get the interview, someone may spend ten minutes on a single line of it.

We'll critique one invented resume: its latest role in depth, then the rest of the page. Joelle is a product manager at Ferrowin (we made the name up), which sells booking and records software to independent vet clinics. Before that she was operations manager for a group of 14 animal hospitals. Here is her current role as she first wrote it: it fits on one page and says very little.

Ferrowin, Product Manager, 2022 to now

  • Responsible for the appointment reminders roadmap.

  • Held calls every two weeks with clinic managers.

  • Improved engagement for pet owners.

  • Launched SMS reminders, which reduced no-shows by 32% and sped up onboarding.

  • Led Project Falcon end to end.

  • Made releases smoother for clinics.

Keep only the lines you could defend for ten minutes

Her best result, the no-show drop, sits fourth, after a duty, a meeting and a vague claim, where a skimmer may never reach it. Worse, an interviewer can pick any line and ask about it for ten minutes, and several of these give her nothing to talk about, or something she can't back up.

So she decides which lines stay before she edits any of them. She sets the draft aside and writes down what is different at clinics because she was there. What she owned or attended doesn't count, only what changed:

  1. No-shows at clinics fell after reminder texts went live.

  2. The texting bill per clinic fell after she merged reminders for households with several pets into one text and stopped the second reminder once an owner had confirmed.

  3. New clinics went live faster after her team shipped a records import she had scoped.

  4. Fewer bugs reached clinics after she changed how the team released.

A draft line stays only if it traces to something on this list, because then she has a story behind it. "Responsible for the reminders roadmap" is a duty, and the calls are a meeting on her calendar. Neither says what changed, so both go. This is the move the resume chapters of Cracking the PM Interview keep coming back to, and the one most candidates skip.

The list also exposes a claim she couldn't defend. It puts faster onboarding under the records import, the draft's Project Falcon, not under reminders. Leave the reminders line as it is, and the first interviewer who asks "how did reminders speed up onboarding?" finds a claim Joelle can't explain. So each result goes with the work that caused it: onboarding moves to the Falcon line, and the texting bill, which the draft never mentioned, gets a line of its own.

To practise this step, try Present Your Three Proudest Achievements, Your Role and Their Impact. Write the list of wins for one role first, and only then choose what to talk about.

Critique each bullet with four questions

With the list beside you, ask four things of each draft line:

  1. Does it show a result, something that changed, rather than a task?

  2. Is there a number, or at least a sense of size?

  3. Can the reader tell what you did, as distinct from what the team did?

  4. Would someone outside your company understand every noun in it?

Here are the four lines that survived the cut, scored honestly:

LineResultNumberHer partClear to an outsider
Launched SMS reminders, which reduced no-shows by 32%OneYes, with no baseline"Launched" hides who did whatMostly
Improved engagement for pet ownersClaimedNoneUnclearNo: engagement with what?
Led Project Falcon end to endNoneNone"Led", but how?No
Made releases smoother for clinicsClaimedNoneUnclearNo: smoother how?

A line that fails one question needs a fix. A line that fails two or more needs a rewrite from the win it came from.

Name the project and how the gain happened

"Improved engagement for pet owners" fails because the reader can't tell which project it means or what Joelle did to cause it. What she meant was specific. After a reminder text, an owner could confirm or move the visit with one tap. About 7 in 10 owners replied that way, where roughly 4 in 10 used to pick up when the front desk phoned the day before. It isn't a separate win: it's how the no-show win worked, so it moves into that bullet.

"Project Falcon" is an internal name. Everyone at Ferrowin knew it; to a recruiter it's a bird. Swap any label like that for a plain description of what the thing was. Falcon let a new clinic load its own patient list and booked visits without waiting for an engineer, so it could take its first booking sooner. The same goes for team nicknames, internal metric names and acronyms nobody outside uses. An unknown employer needs the same plain description, so Joelle adds one line under the company's name: "Booking and records software for about 900 independent vet clinics."

Give every number a baseline or a scale

"Reduced no-shows by 32%" leaves the reader guessing: 32% of what, and compared with when? Joelle's rate went from 14.5% of booked appointments to 9.8%. That's 4.7 points, and 4.7 ÷ 14.5 is the 32% she had written. Both are true, but the two rates let a reader judge the size without trusting her arithmetic.

Before versus after is the simplest comparison. Others work too: against a group that didn't get the change, against the person who held the job before you, or against similar teams in the same quarter. Joelle's other wins get the same treatment:

  • Texting cost per clinic: from $38 a month to $21.

  • Time from signed contract to a clinic's first booking: a median of 19 days down to 6.

  • Bugs reported by clinics after a release: from 14 a month to 5.

Some results have no before and after at all. Then show scale instead: how many users, clinics, people, systems or sites were involved. From Joelle's hospital-group job: "Moved 14 hospitals onto one shared booking calendar and trained 85 front-desk staff in three weeks." There's no percentage, and the reader still sees the size of the job.

Follow the result through to the business

A strong bullet runs a chain: what you built, what it changed for users, and what that meant for the company. Joelle's no-show line stopped at the middle link. The last one was there to be had: clinics paid for reminders as a $49-a-month add-on, and 410 of them bought it. That's 410 × $49 × 12 = $241,080, about $241,000 a year in new recurring revenue.

The cost win has a chain too. At $49 a month, a texting bill of $38 left the add-on a margin of about 22%; at $21 it's about 57%. "Saved money" becomes a reason the add-on was worth selling.

Tie a process claim to its result

"Made releases smoother for clinics" says things got better without saying what she changed. She keeps only the result she can show: clinic-reported bugs fell from 14 a month to 5 once every release ran with 20 pilot clinics for a week. "Smoother" goes, because she never measured it.

Make each verb say what you did

One column of the table is still open: her part. "Launched" and "Led" don't say what Joelle did. An engineer built the texting service and three engineers built Falcon, so a bullet that opened with "Built" would claim their work, and the first deep-dive question would expose it.

The fix is to swap a verb that hides who did what for the decision or piece of work that was yours. For reminders, she designed the one-tap reply and decided which clinics got it first. For Falcon, she chose which records it would load and wrote the spec. How to write product manager resume bullets covers openings like "Partner with" and "Worked with".

The rewritten role

Each bullet now opens with its result and names her part in the clause on how. The strongest goes first:

Ferrowin, Product Manager, 2022 to now

  • Cut no-shows from 14.5% to 9.8% of appointments by designing one-tap replies to reminder texts; sold to 410 clinics as a $49/month add-on, about $241K a year

  • Lowered texting cost per clinic from $38 to $21 a month by merging texts for multi-pet homes, lifting add-on margin from 22% to 57%

  • Shortened median contract-to-first-booking time from 19 to 6 days by specifying a self-serve records import

  • Reduced clinic-reported bugs from 14 a month to 5 by piloting releases with 20 clinics for a week

The last two fit on one line; the first two spend a second line on the business result, the one detail worth the room.

Then run the same pass on each earlier role. Joelle's hospital-group job kept two bullets, the scale line from before and one with a baseline:

  • Moved 14 hospitals onto one shared booking calendar and trained 85 front-desk staff in three weeks

  • Cut front-desk overtime from 260 hours a month to 110 by setting one staffing schedule for all 14 hospitals

Lay the page out so the best line gets seen

Joelle's first draft fit on one page only because she had shrunk the margins and the font. Three roles of six or more bullets each made one long gray column, and the no-show line was lost in the middle of it.

Meeting the length norm isn't enough on its own. What counts is whether your best material is where the eye lands. With six lines under her current role, the no-show result competed with five weaker ones for a skimmer's attention. After the rewrite that role has four bullets, the no-show line first, and each one gets read. Each older role has two, and there's white space between roles. What to put on a product manager resume covers length, layout and sections.

Run a skim test on someone outside your field

Hand the finished page to a friend who doesn't work in product. Give them half a minute, take it back, and ask what you did. Do they describe what you were in charge of, or what you achieved?

Joelle's first draft got this back:

"She's a PM who works on reminders, and she has a lot of meetings."

The rewrite got this:

"She cut no-shows at vet clinics by about a third, and clinics paid for it."

The second answer is the target. After a skim, the reader knows she succeeded, and not only what she was responsible for. If your friend repeats your duties, find the line their eye hit first and put it back through the four questions.

Get every number ready for the deep dive

An interviewer picks one line from your page and keeps asking: what exactly did you do, how was this measured, and how do you know the change came from your work rather than something else? A number you can't defend does more damage than one you left off. With so many resumes now polished by AI tools, numbers you can explain are what set yours apart, and they're what interviewers probe.

So Joelle keeps a private sheet with one line per number. It never goes on the resume:

NumberHow it was measuredHer part, and others'Other explanation, and her answer
No-shows 14.5% to 9.8%Booking records for the 410 clinics that bought reminders, the quarter before and after each got themThe one-tap reply and the rollout plan; an engineer built the texting serviceThe season. Buyers got reminders in two waves, split by account number before launch, and in the first wave's quarter the clinics still waiting stayed at 14.2%
$38 to $21 a monthThe texting provider's invoices divided by clinics using remindersMerging multi-pet texts and dropping the second reminder; the same engineer built itA price cut by the provider. There wasn't one that year
19 days to 6Contract date and first booking for each of 150 new clinics, taking the medianChose which records it loads and wrote the spec; three engineers built itMore small clinics, which go live faster. The mix shifted the other way
14 bugs a month to 5Support tickets tagged as bugs within 14 days of a releaseThe pilot group, the clinic calls, and acceptance checks written with QAFewer releases. Releases per month held steady

The third column lets her draw the line herself when the question comes:

"An engineer built the texting service. My part was the one-tap reply and the rollout plan. I split the clinics into two waves by account number before launch, so the second wave showed what the season alone would have done."

If a number can't survive questions like these, cut it back to what you can show, or drop it. Each line is also the start of a story, and a PM behavioral story bank builds those out.

To practise defending your numbers out loud, take Your Launch and Growth Track Record: Deep Dive on a Product You Owned and Prove your analytical ability as a PM with one data-driven decision story. Pick one line from your own resume for each, and answer the three deep-dive questions about it before you start.

All project deep dive questions