The PM resume

Your resume has one job: to get you a conversation. It doesn't need to tell your whole career story. It needs to convince a busy recruiter or hiring manager, often in a quick first pass, that you have done product work at the right scope and that you are worth thirty minutes on the phone.

This module uses one idea throughout, from resume to negotiation: lead with evidence, then ask clearly. On a resume, evidence means results you can measure and explain. This lesson covers what screeners look for, a one-page structure that works for most PM candidates, and how to adapt it if you are switching into product or early in your career. The next lesson, Writing resume bullets that land, goes deep on the bullets themselves.

#What a PM resume screen looks for

Every company screens differently, but most PM screens come down to a few questions:

1. Does this person meet the basic requirements? Years of relevant experience, technical background if the role asks for one, domain experience if it is listed as required. Google's hiring page, for example, tells applicants to make sure their resume clearly shows they meet the minimum qualifications for the role.
2. Have they done product work? Not just the title. Did they decide what to build, work with engineering and design to ship it, and measure what happened?
3. At what scope? How many users, how much revenue, how large a team, how complex a launch. Scope is how screeners judge which level you fit.
4. Did it work? Results, ideally with numbers, that show the work changed something.
5. Is it easy to read? A clear, short resume suggests clear thinking. A dense or messy one suggests the opposite, fairly or not.

Notice what isn't on this list: a long skills section, a personal mission statement or a list of every tool you have touched. Those take space and rarely change a decision.

Key idea Screeners look for product decisions, scope and results. Every line on your resume should show at least one of the three.

#The one-page structure

One page suits most PM candidates; with well over ten years of relevant experience, two pages is common and acceptable. Google says it has no length requirement but that being clear and succinct is key. If you are deciding whether a line earns its place, it probably doesn't.

Use this order:

1. Header. Name, city and state (or "open to relocation"), email, phone, and a link to your professional profile. Add a portfolio or project link only if it shows product work. Leave out photos, full street address, date of birth and marital status.

2. Summary (optional). One or two lines, only if they add something your experience section doesn't show at a glance. Good use: "Engineer turned PM; four years building payments infrastructure, two leading product for merchant onboarding." Bad use: "Passionate, results-driven product leader who loves building great products."

3. Experience. Most of the page. Reverse chronological order. For each role: company, title, location, dates, then three to five bullets. Put the most relevant and impressive bullet first in each role. Give your most recent role the most bullets.

4. Projects (if useful). For career switchers, students and anyone whose day job doesn't show product work. Treat projects like jobs: what you built, for whom, and what happened.

5. Education. Degree, school, year. Add honors or relevant coursework only if you are early in your career.

6. Skills (short). One or two lines at most: technical skills that matter for the role (SQL, experimentation, a programming language you actually use) and languages. Skip soft skills; show them in bullets instead.

#Formatting rules that save you

• One column, standard section headings and a common font. Many companies use applicant tracking software to store and search resumes, and a simple layout is the safest choice for both software and people.
• Consistent dates, aligned to the right.
• Enough white space that each role is easy to find.
• Save as PDF unless the application asks for another format. Name the file with your name and the role.
• No spelling mistakes. Read it aloud, then have someone else read it.

#A skeleton you can adapt

Here is the outline of a one-page resume for a fictional mid-career PM, with placeholders for the bullets:

#Tailoring for each role

Google's hiring advice is direct about this: start with a blank document and create a resume specifically designed for each job you want, tying your work to the role's qualifications and including data. You don't need to start from scratch every time, but you should do these four things for each application:

1. Reorder bullets so the experience most relevant to this role comes first in each job.
2. Match the language of the job description where it truthfully describes your work. If they say "growth" and you wrote "acquisition," consider their word.
3. Swap one or two bullets for ones that show the skill the role stresses most.
4. Adjust the summary, if you use one, to name the domain or skill they care about.

Keep a master resume with every bullet you have ever written, and build each tailored version from it.

#If you are switching into product

Most career switchers already have product work on their resume; it's just labeled as something else. Look for times you:

• Decided what to build or change, not just how.
• Talked to users or customers to understand a problem.
• Worked across functions to ship something.
• Measured the result and acted on it.

Then lead your bullets with that part of the work. An engineer's bullet can start with the user problem and the decision, not the technology. A consultant's bullet can start with the client's product decision and what changed. A designer's bullet can include the metric the design moved. See the before-and-after examples in Writing resume bullets that land.

#If you are early in your career

Put education higher (just below the header) and use a strong projects section. Show leadership in clubs, teaching or organizing, and anything you built that real people used. Associate PM programs often look for exactly this kind of evidence; see Associate PM programs.

#A weak resume and a strong one

A weak PM resume lists responsibilities: "Responsible for the product roadmap. Worked with engineering and design. Managed stakeholders." Every PM could write this. It shows no decisions, no scope and no results.

A strong PM resume shows what changed because of you: "Led redesign of self-serve signup after interviews showed most drop-off came from a confusing pricing step; trial-to-paid conversion rose from 9% to 13% in one quarter." One bullet like that tells a screener more than a page of responsibilities.

Try it Take your current resume and highlight every bullet in three colors: one for bullets that show a product decision, one for scope, one for a result. Any bullet with no highlight is a candidate to rewrite or cut.

#Sources

• Google, "Our hiring process" (resume advice, minimum qualifications, length): https://www.google.com/about/careers/applications/how-we-hire/

#Recap

• A resume exists to get you a conversation. Show product decisions, scope and results.
• Use one page in most cases: header, optional summary, experience, projects if useful, education, a short skills line.
• Keep the layout simple and single-column, and proofread it twice.
• Tailor every application by reordering and swapping bullets from a master resume.
• Career switchers and early-career candidates should surface the product work they already did and lean on projects.