Product Manager interview questions
The 7 questions that actually come up, each with what a strong answer covers. These are not scripts to memorise — interviewers can tell — they are the shape of the answer that gets a yes.
7 questionsProduct Manager career guide →
Tell me about a product decision you got wrong.
What a strong answer coversA real one, with the flawed reasoning named and the process change that followed. Polished non-failures fail this question.
How would you improve our product?
What a strong answer coversDo the homework: use it beforehand, structure the answer (user, problem, evidence, one sharp bet), and scope small. Generic answers end interviews.
Engineering says the roadmap item takes three months; you have three weeks. Now what?
What a strong answer coversCut scope to the riskiest assumption, not proportionally. Show you know an MVP is a test, not a small product.
Pick a metric for a chat feature. Defend it.
What a strong answer coversOne north star (e.g., conversations with a reply within a day) plus guardrails; explain the gaming risk of whatever you choose.
How do you prioritise when three stakeholders each call theirs P0?
What a strong answer coversA visible framework (impact × confidence / effort or similar), a decision log, and the courage to publish the ordering with reasons.
How do you write a spec engineers actually read?
What a strong answer coversProblem and success criteria first, edge cases enumerated, open questions flagged honestly — a page, not a novel.
A launched feature shows flat metrics. What do you do?
What a strong answer coversSegment before judging, check discovery vs usability, decide kill/iterate against pre-registered success criteria — and say 'kill' without flinching if warranted.