Resumes and cover letters

How to write product manager resume bullets

Lesson 29 of 45~9 min read
In this lesson6 sections

An unofficial lesson drawing on the methods in the Resumes 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

Product manager resume bullets decide whether you get a first call. A recruiter skims them fast, and a strong candidate whose bullets read like a job description often loses to a weaker one whose bullets show what changed.

We'll rewrite one job on one resume. Tessa has spent three years as a data analyst at an invented home-insurance startup of about 80 people that sells policies online, and she's applying for PM roles. Here is that job on her resume today:

  • Partner with claims and engineering teams on the claims filing experience. Analyze funnel data to understand where customers drop off and support improvements to the flow, including research on photo requirements and helping with the launch of in-app photo upload.

  • Own pricing analytics for the underwriting team. Build and maintain reporting, including a pricing dashboard, and handle ad hoc data requests from underwriters and leadership.

  • Member of the underwriting rules working group. Worked with underwriting and engineering to review rules and drive process improvements that helped make quotes faster.

There's good work hidden in those three entries. By the end of this lesson they become three one-line bullets.

How a PM resume gets read

At many larger companies your resume lands in an applicant tracking system (ATS) first. It pulls your text into fields, and some employers add keyword filters or an automated ranking before a person looks. Then a recruiter skims the page, usually for well under a minute, and decides whether a hiring manager should see it.

Plain bullets like Tessa's come through a parser intact. Text boxes, tables and graphics can come out scrambled or empty, so keep yours as plain text in a single-column layout. Where the posting names something you really did, use its word. Our guide to ATS resume scores covers the parsing side.

Skim Tessa's draft as a recruiter would and your eye lands on the first words of each entry, "Partner with", "Own" and "Member of", while the one result she names, faster quotes, sits at the far end of the third.

Every choice on the page is a prioritization call: what gets a line and what gets cut, which bullet goes first, how much white space you leave. A hiring manager reads all of it as a hint of whether you can pick what matters, and, as Cracking the PM Interview points out, a PM's resume gets judged more closely than most.

Rebuild a role from a blank page

The facts behind Tessa's final bullets came from a fresh list, not from her old entries. Each time she tried editing an old entry she got the same duty back with a new verb, so she cleared the role down to its title and dates and listed her work from scratch. If your resume has been patched for years, do this pass before you rewrite a single bullet.

First, write down everything from the role you'd still bring up if a friend asked what you're proud of. Don't filter yet. Then ask someone who worked beside you, a manager or a close teammate, which of your work they'd name first. You need both lists, because you'll overrate what was hard for you and underrate what came easily.

Tessa wrote eight items. Her manager named the underwriting rules change first, and Tessa had put it last, since to her it was "mostly a spreadsheet". To cut the list, she read each item on its own and finished this sentence about whoever did it: "They did well in this job because ___." If the blank filled with a result, the item stayed. If it filled with a task, or she couldn't fill it at all, it went. Moving reports to a new tool went, and so did the quarterly board deck: a duty she did well, but still a duty.

Tessa could fill the blank from memory because she knew the backstory. A recruiter holding only the bullet can't, so once your items are bullets, have someone who doesn't know your job run the same test on each one.

Three items passed, one behind each old entry:

  • On claims, she found that almost a third of people who started a claim stopped at a separate screen asking for damage photos. She proposed moving the upload into the damage-description screen and wrote the requirements. One engineer built it.

  • On pricing, she built a self-serve dashboard of loss ratios by region to replace a weekly spreadsheet she used to send. Its view logs show 9 of the 11 underwriters opening it most weeks, and their data requests to her team dropped.

  • On underwriting rules, she analyzed two years of claims and showed that one group of low-risk homes was going to manual review for no good reason. The head of underwriting approved the rule change she drafted.

The struck duties were real work, and she still wanted a screener to see that scope without spending a bullet on it. So beneath her title she set one short italic line, apart from the results:

Analytics for the claims, pricing and underwriting teams; weekly loss and funnel reporting

Run the same blank-page pass for every role you keep, starting with your most recent.

To practise this step, try Behavioral PM Story: The Career Achievement You Are Proudest Of and Why. Make the blank-page list across your whole career, choose the item you'd tell, and finish the because sentence for it before you rehearse the story.

Show which part was yours

Two of Tessa's old openings, "Partner with" and "Member of", hide her part, and so does "Worked with underwriting and engineering" in her third entry. That line could mean Tessa ran the project or that she sat in its meetings. So ask of each line: could this be true if you had only sat in the meetings? If it could, rewrite it around the part that was yours. When the result really was a group effort, name your piece of it. "Wrote the analysis that..." is honest and still yours.

The other opening, "Own", claims the work and still shows no result. When she first edited her draft, "Own pricing analytics" became "Spearheaded pricing analytics strategy." The verb got louder, and the line still says nothing about what changed. Recruiters see a lot of this now, because AI writing tools are very good at making a duty sound grand. Only you know what actually moved, and a bullet that opens with "Drove" or "Spearheaded" means little until it says.

All three openings share one more fault. Each describes a standing arrangement, as true on her first day as it is today, so a reader has no way to check it. Each fact on her blank-page list says what changed, and someone could check it.

To practise this step, try PM behavioral: walk through the impact you have delivered in your present job. Write your current job as outcome bullets that pass the meetings question, then use them as the outline when you answer out loud.

Put the result first, with a number you can defend

Here's Tessa's first try at the rules bullet, with the order backwards:

  • Analyzed two years of claims data, presented findings to underwriting leadership and updated the routing rules with engineering, which sped up quotes.

The result is the last three words, and it has no size, so a skimmer misses it and anyone who gets there has no reason to believe it. Flipped and measured:

  • Cut median quote turnaround from 26 hours to 4 for low-risk homes by rewriting manual-review rules

The change and its size now open the line, where a skimming eye lands. The method still belongs, because it shows how you think, but it comes second and gets fewer words.

Tessa found more counts than she expected in systems she already used: the claims funnel, the quoting system's logs, the dashboard's view logs and her team's request queue.

Not every number has a clean record behind it. Her dashboard's time saving is an estimate: about 20 fewer requests a week at roughly 45 minutes each is 900 minutes, or about 15 analyst hours a week. That's fine as long as you can show the working, and you'll be asked to. PM interviewers commonly pick a line from your resume and ask you to walk through it, and numbers draw the first questions: how did you measure that, and what else changed at the same time? Tessa's answer for the dashboard:

"The request queue showed about 25 underwriter requests a week before the dashboard and about 5 after. I timed a month of requests at roughly 45 minutes each, so the analytics team got back about 15 hours a week."

She could also have claimed the rise in quote-to-purchase conversion after the rules change. She left it off, and if asked she'd say:

"Conversion went up too, but marketing launched a spring campaign the same month, so I can't say how much of that was mine."

A number you can't explain does more harm in that conversation than a missing one. Our lesson on how PM behavioral answers are scored covers the layers of follow-up a resume line gets.

To practise, try Behavioral: Showcasing Your Strongest Product Achievement and Its Measured Impact. Before planning your answer, write the achievement as a single resume bullet with the result at the front, and note where each number in it came from.

All career and values questions

Fit each bullet on one line

Here's the claims bullet as Tessa first wrote it after the rewrite:

  • Raised claim completion from 64% to 78% after funnel analysis showed 31% of filers stalling at the separate photo screen; wrote the proposal and requirements, ran a two-week test with one engineer, and moved photo upload into the damage screen.

That's three lines, more than a skimmer will read. The funnel analysis, the 31%, the test and the engineer all happened. They're her answer when an interviewer asks how she did it, so they can wait for the interview. The bullet needs only the change and the one detail that explains it:

  • Raised claim completion from 64% to 78% by folding the photo-upload screen into the damage form

In a single-column layout with ordinary margins and type, one line holds roughly 90 to 110 characters. If a long bullet holds two separate wins, make them two bullets rather than cutting one.

Here are her three finished bullets:

  • Raised claim completion from 64% to 78% by folding the photo-upload screen into the damage form

  • Saved about 15 analyst hours a week with a pricing dashboard now used by 9 of 11 underwriters

  • Cut median quote turnaround from 26 hours to 4 for low-risk homes by rewriting manual-review rules

Each fits on one line and leads with a number she can explain. Every cut in this step is the prioritization call from the first section: the reader judges you by what you kept.

Proofread the numbers first

Tessa's last pass caught five things her spell checker didn't. Three were in her numbers:

  • In one draft the claims bullet said 87%, not 78%.

  • The same bullet had "64%" and then "78 percent".

  • She wrote "hrs" in one place and "hours" in another.

So check every number and unit against your notes, and write each one the same way throughout. Her other two catches: one bullet ended with a period and the others didn't, so she dropped it, and her LinkedIn URL still used an old custom handle that no longer opened her profile.

Print the page, or read it at a different zoom, so you see it fresh. Then hand it to one other person before you send it.

For the layout and sections around your bullets, see what to put on a product manager resume. If you already have a whole resume to fix, rewrite a product manager resume takes one through a full critique. Our product manager resume examples show more bullet rewrites across roles.