Product interviews often give you an open problem and watch what you do before the solution appears. The interviewer wants to see how you understand users, choose a goal, compare options, and make a decision when the information is incomplete.
Jumping straight to features can feel productive. It can also produce a beautifully organised solution to the wrong problem.
The main product interview question types
| Type | What it tests | Example |
|---|---|---|
| Product sense | Users, problems, solution choices | Improve a product you use every week |
| Prioritisation | Goals, trade-offs, decision rules | Choose between two urgent requests |
| Metrics | Success measures and product health | How would you measure a new onboarding flow? |
| Execution | Delivery, risk, communication | A launch is late. What do you do? |
| Strategy | Market, advantage, long-term choices | Should the company enter a new segment? |
| Behavioral | Leadership, conflict, failure, learning | Tell me about a decision people disagreed with |
A practical order for product cases
- 1
Clarify the goal
Ask what the product or business is trying to improve. Growth, retention, revenue, and trust lead to different choices.
- 2
Choose the user
Name the group and the situation. ‘Everyone’ is usually a sign that the problem has not been narrowed enough.
- 3
Understand the problem
Describe the user need and why current options fail before creating features.
- 4
Compare solutions
Generate a few options, then choose using impact, confidence, effort, risk, or another clear rule.
- 5
Measure and limit risk
Choose a main measure, guardrails, and a small way to test the biggest assumption.
Product questions worth practising
QUESTION 01
What would you remove from a product you use often?
Why they ask: This tests whether you can identify low-value complexity rather than always adding more.
- Choose a user and goal
- Explain the cost of the current feature
- Describe how you would test removal
Likely follow-up: Which users would complain?
QUESTION 02
Two important teams need different features. How do you choose?
Why they ask: This tests whether priority comes from a shared goal instead of the loudest meeting.
- Clarify the product goal and impact
- Compare evidence and cost
- Explain the decision and what happens to the other request
Likely follow-up: What if leadership disagrees?
QUESTION 03
A launch increased signups but reduced retention. Was it successful?
Why they ask: This tests metric judgement and whether you can handle mixed results.
- Return to the intended goal
- Check user groups and time periods
- Consider guardrails and next tests
Likely follow-up: Would you roll it back?
Show the decision, not only the framework name
Framework as decoration
“I would use RICE to score both features and then build the one with the highest score.”
A framework can organise thinking, but the interviewer still needs to hear the assumptions and judgement inside the numbers.
Decision with reasons
“I would first check which company goal the quarter is meant to move. If retention is the goal, I would compare how many at-risk users each request affects, the confidence behind that estimate, and the delivery risk. I would share the assumptions with both teams, choose the request with stronger evidence, and define what would cause us to revisit the choice.”
The answer uses a clear goal, evidence, communication, and a way to update the decision.
Prepare these product stories
- A decision made with incomplete information
- A launch that did not produce the expected result
- A priority you defended or changed
- A disagreement with design, engineering, sales, or leadership
- A user insight that changed the plan
- A product or feature you stopped
Product manager interview checklist
- Cases begin with a goal and user
- Solutions follow the problem
- Priorities use clear assumptions
- Metrics include guardrails
- One failed launch story is ready
- Frameworks support judgement instead of replacing it
Sources and further reading
These links support the advice above and give you somewhere useful to continue reading.
Product judgement needs a follow-up
Practise making product decisions out loud
Try product cases, metrics, priorities, and experience questions in a product manager mock interview.
Start a product manager interview