Product manager job description
Product management is the role where the strongest resume and the strongest candidate diverge most often, and the reason is structural. At a large product company, much of the judgement the job is famous for has already been exercised by somebody else before the product manager arrives at the problem. Below is a description for a seat where that is not the case, and how to screen for the difference.
The job description
We are looking for a product manager who will decide what we do not build. You will own a problem area end to end, from working out what is genuinely wrong through to what happened after release.
What you will own
- A problem area, its outcomes, and the argument for why it deserves a team
- Discovery at first hand: customer conversations, usage data, and what support and sales are hearing
- The specification, at whatever fidelity the team needs and no more than that
- Trade-off conversations with engineering and design where you do not get to pull rank
- What happened after launch, including the launches that did nothing
What the job needs
- Experience choosing between problems, not only executing against one already chosen
- Enough technical literacy to understand the cost of what you are asking for
- The ability to write one page that makes a decision legible to everybody who missed the meeting
Signals we weight heavily
- You have removed a feature
- You can name a launch that underperformed and what you did about it
- You changed your mind because of one customer conversation, and can say why that one
What a product manager is actually accountable for
The artefacts are roadmaps and specifications, and both are easy to produce convincingly. The seat answers for what the company chose to build, what it refused to build, and whether the thing that shipped moved anything.
- Choosing the problem, and being able to say why it beat the other three
- A shipped change that moved a number somebody in the business cares about
- Stopping work in progress when the evidence changes, rather than finishing it because it started
- Holding a position against the loudest stakeholder without turning it into a standoff
- Knowing what customers actually do, from having watched them, rather than from a summary of a survey
Four ways a product manager hire looks right and is not
Every one of these passes a resume screen. Ladders eye-tracking study timed the average initial scan at just 7.4 seconds, which is long enough to check the four signals below and not long enough to check anything that would contradict them.
Looks right
Product manager at a well-known product company
At that size the strategy, the designer, the researcher and often the prioritised roadmap arrive with the job. The candidate may be excellent at running a team against a chosen problem and have never chosen one. Choosing the problem is exactly what breaks product hires in smaller companies, and it is invisible on the resume that looks strongest.
Looks right
Fluent in the frameworks: prioritisation scoring, opportunity trees, jobs to be done
Framework fluency is the output of a large coaching industry and takes a weekend to acquire. Every scoring model is only as good as the guesses fed into it. The useful question is what a framework told them to do that they overruled, and why they trusted their own read instead.
Looks right
Shipped a long list of features
Shipping volume is often the failure mode rather than the achievement, because a product manager who ships everything requested has not been doing the deciding part of the job. The candidates worth hiring can tell you what they killed, what they cut from a launch, and which shipped feature they later removed.
Looks right
Former engineer, technically strong
It buys credibility in the room and gets mistaken for product judgement. An engineer turned product manager who is happiest specifying implementation has quietly moved back into the job they came from. The team enjoys working with them, and discovery stays unowned for a year before anybody names it.
What to ask for evidence of instead
Four questions, and what the answer actually tells you. Take these into your own process whether or not you ever talk to us.
- Tell me about something you decided not to build that the team wanted to build.
- What it tells you: The clearest test of whether the seat carried authority. Listen for how they took the team with them. Product managers who have only ever said yes were running a backlog for somebody else, whatever the title said.
- What did you learn from a customer that changed the roadmap, and how did you learn it?
- What it tells you: The mechanism matters more than the insight. First-hand conversations, watching somebody use the thing, or sitting on support calls are different from receiving a research summary. Second-hand discovery produces second-hand judgement.
- Which of your launches underperformed? How did you find out, and what did you do next?
- What it tells you: Whether anybody was measuring, and whether the product manager stayed with the feature after release. A candidate who cannot name an underperforming launch either has not shipped much or has not looked.
- How do you and engineering disagree, and who wins by default?
- What it tells you: Every functioning product team has a real disagreement to describe. An answer with no conflict in it usually means the product manager was writing tickets, or that engineering had already decided and the specification followed.
How Continuity1 runs this funnel
The screening above is the job. These are the numbers it produces when a function owns it end to end, set against the published benchmarks for the same market.
- 1 in 3
- Shortlisted candidates you meet who become the hire
- Aligned engagements run nearer 1 in 2, distant ones nearer 1 in 10. The market takes about 180 applicants to make one hire, and that sifting lands on your team rather than ours.
- Continuity1 tracked engagements
- ~3
- Interviews your team sits in, per hire
- Ashby puts technical roles at 17.6 interviews per hire across the whole process, up 52% since 2021. The rest of that load sits with the function, not with you.
- Ashby talent-trends report
- 1 in 9
- Accepted offers that ghost before joining
- Indian employers report nearly 4 in 10 offers dropped. We lose 1 in 9.
- nasscom community
- 95%
- Offers that close inside your stated band
- 20 of the last 21. A flat fee earns nothing from an inflated offer; a percentage of CTC earns more.
- Continuity1 tracked engagements
Every brief becomes a success profile before sourcing starts, calibrated with the people who will manage the role. That calibration is the step most hiring skips, and it is why a shortlist either matches the job or matches the job advert.
You review a scored shortlist and make the calls. The filtering never lands on your calendar.
Questions teams ask
Product manager or product owner?
Product owner as commonly practised is a delivery role attached to a team, refining a backlog somebody else prioritised. If your person has to decide what is worth building at all, hire a product manager and write the advert that way, because both populations will apply and only one of them has done the deciding.
Do we need a product manager before we have product-market fit?
Usually the founder is the product manager at that stage, and hiring does not transfer that judgement. What does work is hiring for the parts the founder has become the bottleneck on. Be explicit about which decisions stay with the founder, or the hire fails on ambiguity that was never theirs to resolve.
Should a product manager be technical?
Enough to understand what they are asking for and to be taken seriously in a design discussion. Past that point the risk inverts: a technically strong product manager who prefers specifying implementation leaves discovery unowned while being pleasant to work with, which takes a long time to detect.
What is a fair interview exercise?
Anything that asks them to critique or prioritise, using a public product or a problem you have already solved and know the answer to. Do not ask candidates to produce a strategy for your live roadmap. It is unpaid work, strong candidates recognise it as such, and the output is unassessable because only you know the constraints.
Related