How to Screen a Product Manager Resume: Must-Haves, Red Flags and a Scoring Rubric
Product manager CVs are the hardest to screen because the job is decisions and CVs list activities. Read for ownership of outcomes, for evidence of saying no, and for the scale and kind of product, which matters more than the title.
- Read for evidence before matching keywords: a product manager CV should show what the candidate built, ran, closed or decided, with a result. The must-haves below are the four things the job cannot be done without.
- Must-haves: owned a product or area with a metric they can name and a result they can state; evidence of discovery: talking to users, analysing behaviour, testing before building. Nice-to-haves raise a candidate; they do not rescue one missing a must-have.
- Red flags are patterns, not single lines: launched a great many features and moved no metric, and product management as project management: timelines, tickets, status.
- Use the five-criterion rubric on the page, weighted so that outcomes owned counts more than job description match. It is written to be pasted into WadeCV as a role and scored automatically.
- Spend three minutes per CV with the rubric and write one line of evidence per criterion. Screening decisions with evidence attached can be explained to the candidate, to the hiring manager, and to anyone who audits them later.
Must-haves
- Owned a product or area with a metric they can name and a result they can state
- Evidence of discovery: talking to users, analysing behaviour, testing before building
- Worked directly with engineers and designers to ship, with specifics
- Product type close enough to yours to transfer (B2B vs consumer, technical vs not, stage)
Nice to have
- Data literacy: reads dashboards, writes simple queries, designs experiments
- Pricing, packaging or go-to-market involvement
- Writing samples or public product thinking
- Domain knowledge for your market
Red flags
- Launched a great many features and moved no metric
- Product management as project management: timelines, tickets, status
- No 'no' anywhere: every request became a roadmap item
- Title inflation: 'Head of Product' for one product and no reports
The rubric
Score each criterion from what the CV shows; weight 3 counts three times weight 1. In WadeCV, create the role with these criteria and every CV is scored this way automatically.
| Criterion | How to measure it | Weight |
|---|---|---|
| Job description match | Match between product type, stage, market and the role as written | 2 |
| Years of relevant experience | Years owning a product area, not total years adjacent to product | 2 |
| Outcomes owned | Named metrics with stated results the candidate was accountable for | 3 |
| Discovery practice | Evidence of user research, data analysis and testing before building | 2 |
| Working with engineering and design | Concrete shipping stories that show partnership, not hand-off | 2 |
How to read the CV
The single best screening question is 'what did this person's product do differently because they were there?' Read each role looking for the answer. Metrics moved, features killed, decisions made against the grain. A CV that never answers it belongs to someone who was near the product rather than driving it.
Match on product type before matching on industry. A consumer PM moving to B2B, or a PM from a platform team moving to a customer-facing product, faces a bigger adjustment than one changing industries within the same type.
Discount titles heavily. 'Senior', 'Lead' and 'Head' mean different things everywhere; the scope described under the title is what you are hiring.
Frequently asked questions
Should product managers have a technical background?
For a technical product, some fluency helps; for most products, it is optional. Screen for the ability to work with engineers, which the CV shows in shipping stories, not in a computer science degree.
How much does an MBA count?
Nothing on its own. Score the work before and after it.
What if the candidate comes from consulting or engineering rather than product?
Score them on the same rubric with what they have. Engineers who drove product decisions and consultants who owned outcomes can score well; the rubric will show whether they did.
Related guides
- How to Screen a Data Analyst Resume: Must-Haves, Red Flags and a Scoring Rubric
- How to Screen a UX Designer Resume: Must-Haves, Red Flags and a Scoring Rubric
- How to Screen a Marketing Manager Resume: Must-Haves, Red Flags and a Scoring Rubric
- How to Screen a Frontend Engineer Resume: Must-Haves, Red Flags and a Scoring Rubric
- How to Screen a Account Executive Resume: Must-Haves, Red Flags and a Scoring Rubric
- How to Screen a Customer Success Manager Resume: Must-Haves, Red Flags and a Scoring Rubric
Screening product manager CVs this week?
Paste the job description into WadeCV, check the rubric it drafts, and upload the CVs. Each one is read against the rubric and scored with an explanation. Ten screenings are free; there is no subscription.
Screen your first CVs free