Resumes and cover letters
What to put on a product manager resume
In this lesson9 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
A product manager resume gets a few seconds of a screener's attention, often after software has already parsed it, so your choices about length, layout and sections decide what they learn about you. There's a second test inside the first one. The page is a small product you designed for a single user, and the people hiring a PM will judge the design.
We'll audit one whole page. Nadia spent four years as a dispatch lead at a regional refrigerated trucking company, then three as a PM at Corvane (we made the name up), which sells route-planning software to trucking fleets. Her draft runs one page plus five lines. It uses a two-column template with a photo and skill bars in a sidebar, opens with an objective, and lists an award by its name alone. Neither employer gets a word of explanation.
Who reads the page, and for how long
Start where any product starts: with the user. A PM resume usually meets two readers in a row. First an applicant tracking system turns the file into fields (name, employers, titles, dates, skills) so a recruiter can search and filter, and some employers add an AI model that ranks applicants against the posting. Then a person skims whatever comes through for a few seconds before deciding whether to read on. Our guide to ATS resume scores covers the software step in more depth.
That skim changes what "more" means. A recruiter who gets through a third of your page learns a third of what's on it, and you don't get to pick which third. Four weak lines don't give them more to go on. They lower the odds that your best line is the one they see.
So every line has to earn its place: it stays only if the few-second skimmer would miss it more than the stronger line it might push out. Nadia's draft has a bullet saying she "ran weekly status meetings with engineering." Her bullet about launching route re-planning for broken-down trucks already shows she works closely with engineers, and shows it better. A skimmer who never saw the status line would lose nothing, so almost any line with something new to say beats it. It goes.
Ask what each line fails to prove
Decide what the page has to prove before you worry about length or looks. Read your draft one line at a time, the way a PM screener would, and ask what each line leaves them unable to believe. Here are four of Nadia's:
| Draft line | What a PM screener can't tell from it | What she found |
|---|---|---|
| Launched route re-planning for broken-down trucks | Whether it changed anything, or why it was built | Amplitude: rebuilding a broken-down truck's route now takes dispatchers about 4 minutes, down from 25. Her weekly SQL query for late-running routes, which nobody had asked for, was why it got built |
| "Customer interviews" | How many, or what she did with them | 22 carriers interviewed before the build, then a 12-carrier pilot with engineering, support and sales working to her plan though none reported to her |
| "SQL" in skills | Whether she uses it for real work | The same late-routes query |
| Dispatch lead at a trucking company, unexplained | Why a product team should care | She had been Corvane's customer, and the spreadsheet planner she built for all six dispatchers cut late deliveries from 7% of stops to 4% |
None of the fixes came from rewording. Each was work she had done and left out. The late-routes query went into the re-planning bullet, which now carries the number, the query behind the idea and the fact that she started it herself. The pilot became a bullet of its own.
Your own audit may turn up a line with nothing behind it anywhere in your history, like a bare "SQL" with no query you ever ran. No wording will fix that. Earn it instead: an internal tool you build, a side project with real users, or a working prototype you made with an AI coding tool and put in front of people. Any of those is stronger now than a course certificate. Our lesson on PM side projects goes further.
To practise the audit, take Describe relevant PM experience and, before you answer, pick the line of your own draft that each part of it is really testing.
Employer, title and a line of context
Put employer names in bold, and use bold for nothing else. Nearly every PM applicant has "Product Manager" on the page, so the title rarely sets you apart, while the company often does. Still keep the title accurate and easy to find, in regular weight, since a parser files it as your title. When a title changed, as Nadia's did from dispatch to product, the change is part of the story.
A screener who has never heard of your employer can't picture your work. "PM at Corvane" could mean a six-person startup or a company of thousands, and every bullet underneath reads differently. Give them one line under the employer's name: what the company does, how big it is, and a reason to take it seriously, such as a known investor, a funding stage, a recognizable customer or a customer count.
Nadia's Corvane entry now opens like this (company name in bold):
Corvane Remote | 2023-present
Route-planning software for regional trucking fleets; 320 people, Series C, 380 carrier customers.
Product Manager, route planning
Now her re-planning bullet reads at the right scale: a cut from 25 minutes to 4 means more once a reader knows Corvane serves 380 fleets, not three. Under the trucking company she added: "Refrigerated carrier, 85 trucks, delivering for regional grocery chains." A household-name employer needs no such line.
Give every award a yardstick
Nadia's draft said "Corvane Spark Award, 2024." To a screener that's a name and a year. The fix is a yardstick, and where it sits in the line matters as much as what it says. Tacked on at the end, it arrives after a name that means nothing outside Corvane, and a skimmer reading the start of the line may never reach it. Her edit puts the yardstick first and moves the in-house name into brackets:
Given to 6 of Corvane's 320 staff, 2024 (Spark Award)
Pick the yardstick that fits the honor: your placing and the field size for a competition, the acceptance rate for a selective program or fellowship, the money raised or turnout for something you organized.
Don't drop an award for being off-topic. A chess title or a scholarship says nothing about product work, but with a yardstick it still shows you can win something hard. If the honest yardstick is weak, though, the line may not beat the stronger one it would push out.
The top of the page: objective, headline, summary
Write the top of the page last, once you know what the rest proves. Start by cutting the objective. Nadia's read "Objective: a senior product role where I can grow my strategic and leadership skills." It tells the reader which job she applied for, which they already know, and then claims things nobody can check.
A one-line headline is a different thing, and it's common now: the role you're targeting plus your specialty. Nadia's reads "Product manager, B2B logistics software: routing and dispatch." It puts the posting's own words where a parser and a skimmer both meet them first. It helps most when your titles don't tell the story yet, as for someone switching careers.
Nadia's draft summary called her a "passionate, data-driven product leader with a proven track record." Any PM could sign that, and no reader can check a word of it. Lines like it are now so often written by AI tools that many recruiters skip the block. She deleted it and let the headline do the work, since a tight one-page resume summarizes itself.
A summary earns its lines only when it shows something the layout can't, such as a career change or a big result buried in an old role. Then hold it to one or two lines of facts a stranger could verify. Had Nadia been applying outside trucking, where her titles wouldn't explain themselves, she might have written: "Seven years in trucking: four dispatching 85 refrigerated trucks, then three as PM for the routing software dispatchers use."
A line like that also makes a good opening for the spoken career overview many first interviews begin with, which runs about two minutes. Try PM Intro Question: Summarizing Your Career, Scope and Outcomes as a Narrative with no adjectives about yourself. Our tell me about yourself lesson covers the rest.
How long the page should be
For US tech roles, one page is the norm until you have around ten years of experience. Past that, and especially after several quite different roles, a page and a half or two can be justified. In the UK and much of Europe a two-page CV is ordinary, and senior resumes often run to two pages anywhere, so follow the norm where you apply.
The weakest length is a page plus a few lines. It reads as a page filled without choosing, a poor first signal from someone applying to prioritize for a living.
Nadia's draft ran five lines over, and the tempting fix was to shrink it: quarter-inch margins, 9-point type. That trades one problem for another. The skimmer now meets a wall of small text, and the same few seconds cover less of it. Margins of roughly half an inch to an inch, with body text around 10 to 11 points, suit most pages. Keep that size and cut lines until it fits on one page.
When one role seems to need more room, ask what single thing about it a PM hiring manager should walk away with. For Nadia's dispatch job, the takeaway was that she had been Corvane's customer, planning routes for 85 trucks by hand and in spreadsheets for four years. Six bullets about shift rotas and driver hours became two that show it: the spreadsheet planner she built and the late-delivery rate it brought down. The page fit with room to spare.
To practise picking one takeaway per job out loud, try Recruiter screen: tie your career history to the skills a product manager job demands.
Skills and programming languages
A short skills line is worth keeping, partly because recruiters and tracking software search by keyword. Use the posting's words where they're true: if it says "routing optimization" and you did that work, say it their way. A list proves nothing on its own, though, so every item should have a bullet above it that shows the skill in use.
Leave out what every applicant has: office suites, video calls, chat apps, shared documents. Leave out soft skills too ("communication," "leadership"), since they're claims, and your bullets are where you show them.
Nadia's draft line had Microsoft Office, Slack, Zoom, Agile, Leadership, Communication, SQL, Python, Java and Figma. The new one reads: "SQL (daily), Amplitude, Figma." The late-routes query backs SQL, the re-planning result backs Amplitude, and the pilot bullet names the Figma mockups she tested with carriers. Python and Java went: she had used each a few times, and anything you list is fair game for twenty minutes of questions in a technical round. Our lesson on coding and technical rounds for PMs shows how deep those questions go.
Technical signals for PMs now reach past programming languages to SQL, analytics tools, experiment design and AI features. A short languages line lets a reader confirm depth at a glance, but one bullet showing technical work counts for more.
A plain layout that software and people can both read
Nadia's draft put a photo and a column of skill bars in a sidebar beside her jobs. Tracking software can scramble a page split into columns, tables or text boxes, so her sidebar skills could land inside a job entry and the fields a recruiter filters on come out wrong. The skimmer gets little more from it. A bar filled to 80% beside "SQL" tells nobody what she did with SQL, and the photo and bars take room a bullet could use. Her page now runs in one column with plain section names (Experience, Education, Skills), so a parser files each part correctly, and keeps contact details and links in the body, since some tracking software skips header and footer fields. To see what the parser sees, paste the finished text into a plain-text box and check it still reads in order. Then proofread it with the pass that ends the resume bullets lesson.
Lead with whichever you most want a screener to meet first, your school or your employer. After a few years of work that's usually the employer; for students it's usually the school. Nadia's supply chain degree goes at the bottom, on one line.
Then hold the page at arm's length and squint. The employer names you set in bold should be the first words you can make out. If something else wins, such as a colored heading, your own name in huge type, a second typeface or a fourth type size, turn it down.
Links: LinkedIn, a portfolio, a demo
Put your LinkedIn URL at the top of the page, and make the profile match the page, with the same titles and dates. Recruiters usually look you up there whether you link it or not.
A personal site, portfolio, GitHub profile or newsletter holds the detail you cut, and it's often the page an interviewer opens before a project deep-dive.
Nadia's portfolio link goes to one page about the re-planning feature: the problem in two sentences, her role, before and after screenshots with customer names blurred, the result, and a 90-second demo video. She used only what Corvane had already made public, such as release notes and help-center pages.
That page invites the request a project deep-dive usually opens with: walk me through it. Expect close questions on anything you link. Try both questions below with the project you'd put behind your own portfolio link.
PM Technical Deep Dive: Architecture and Trade-offs of a Project You Shipped
A Stripe product manager interview prompt that asks the candidate to present a past project in technical depth.
Technical Project Deep Dive: Explaining a Project You Built and Care About
A product manager interview question asking the candidate to walk through a technical project they worked on and care about.