Product Manager Interview Questions: What to Ask and What a Good Answer Contains
Product management interviews are prone to rewarding fluent talkers. These questions ask for decisions the candidate actually made, with the evidence they had, the trade-off they accepted and what happened. Fluency does not survive that.
- Ask about work the candidate owned, not opinions: every question below asks for a system, a deal, a campaign or a decision that actually happened, with what they did and what came of it.
- Score each answer against the note beside it. The notes describe observable things a strong product manager answer contains, so two interviewers write down the same evidence and reach the same score.
- Use the scorecard: decision quality; prioritisation; discovery, and two more. Five criteria, scored 1 to 4, with a sentence of evidence each.
- Ask five questions well rather than eight in a rush. The first one, about something the candidate owned end to end, sets the tone: specifics, not generalities.
- Watch for the red flags listed below, which are patterns rather than single answers: every decision was a group consensus; nothing was theirs, for one.
The questions
1. Tell me about a product decision you made that you would make differently now. What did you know then, and what do you know now?
What a strong answer contains: A real decision with a real cost, the information they had at the time, and a specific lesson. Look for someone who separates a bad outcome from a bad decision.
2. How did you decide what to build last quarter, and what did you say no to?
What a strong answer contains: A method (customer evidence, data, strategy, capacity) applied to real items, and at least one "no" with the reason and who was unhappy about it. A candidate with no "no" was not prioritising.
3. Walk me through how you would find out whether a feature is worth building, before building it.
What a strong answer contains: Talks to users, looks for the problem in support tickets and behaviour data, tries the smallest test that would change their mind, and names what result would kill the idea.
4. Describe a disagreement with an engineer about scope. How was it settled?
What a strong answer contains: Understood the engineer's reasons, brought the user's reasons, found the cut that preserved the outcome, and wrote it down. Look for respect and for a decision, not a compromise nobody wanted.
5. What metric did you own, and what did you do when it moved the wrong way?
What a strong answer contains: A named metric with a definition, a specific dip, a diagnosis with segments, and an action. Someone who owned a metric can tell you its value last week.
6. How do you write a spec, and who is it for?
What a strong answer contains: Starts with the problem and the user, states what success looks like, leaves the how to engineering and design, and is short enough to be read. Bonus for an example of a spec that changed after review.
7. Tell me about a launch that went badly. What did you miss?
What a strong answer contains: Owns the miss, names it precisely (a segment, a migration, a support team not briefed), and has a checklist item now. Blaming the timeline is a weak answer.
8. What would you do in your first 30 days here?
What a strong answer contains: Listen, use the product, read the support queue, meet the people who ship it, and find one small thing to improve. Suspicious of anyone with a strategy for a product they have used for an hour.
Scorecard
Score each 1 to 4 with one line of evidence. A total is less useful than a pattern.
- Decision quality: separates bad outcomes from bad decisions and learns from both
- Prioritisation: a method, applied, with real refusals
- Discovery: tests ideas before building and names the killing result
- Working with engineering: settles scope with reasons on both sides
- Metric ownership: knows the definition and last week's value
Red flags
- Every decision was a group consensus; nothing was theirs
- Cannot name a feature they killed
- Describes users in aggregate only; has not talked to one recently
- A 30-day plan that is a strategy
How to run the interview
Every question here asks for something that happened. Keep it there. When a candidate drifts into how they would approach it in general, bring them back to the specific quarter, launch or metric. Product judgement is only visible in decisions.
The prioritisation question is where most candidates are weakest and most product teams are weakest, so it deserves the most time. Ask what was on the list, what fell off, who wanted it, and what they told them. A candidate who has said no well is rare and worth a lot.
If you use a case exercise, use your own product and a real problem you have not solved. You will learn how they think and you might get a useful idea. Avoid the "design an app for X" format; it rewards performance.
Frequently asked questions
Should we ask estimation questions like "how many piano tuners are there"?
No. They test composure and arithmetic, and product managers need neither more than anyone else. The metric and discovery questions above test the reasoning that matters.
How do we assess a PM from a very different domain?
Domain knowledge is the fastest thing to acquire. Score the method: how they found problems, tested ideas and made calls. A strong PM from fintech will be strong in healthcare in six months.
Who should interview a product manager?
An engineer they would work with, a designer, someone from sales or support, and their future manager, each with their own questions. Product managers work across functions; the interview should too.
Related guides
- Data Analyst Interview Questions: What to Ask and What a Good Answer Contains
- UX Designer Interview Questions: What to Ask and What a Good Answer Contains
- Marketing Manager Interview Questions: What to Ask and What a Good Answer Contains
- Account Executive Interview Questions: What to Ask and What a Good Answer Contains
- Operations Manager Interview Questions: What to Ask and What a Good Answer Contains
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