Product Manager interview questions
Grouped by interview stage, with what a strong answer actually sounds like — the part most question lists leave out.
When interviewing a product manager, structure questions by stage and assess against the role's actual requirements. Product managers decide what gets built and why. The questions below cover screening through final round, each with what a strong answer sounds like and the warning signs of a weak one.
How to use these
Pick four to six for a 45-minute interview — not all 7. A well-followed-up question takes six to eight minutes, and the information is almost always in the follow-up rather than the first answer. Ask the same core questions of every candidate so you can actually compare them; vary the follow-ups.
Screening questions
Tell me about something you decided not to build.
Why ask it: Prioritisation is the job. Anyone can list what they shipped.
A strong answer: A real, contested decision with reasoning and the cost of saying no.
A weak answer: Cannot think of one, or only trivial examples.
How do you know your last launch worked?
Why ask it: Many PMs ship without ever closing the loop.
A strong answer: Defined the measure beforehand, checked it, and can say honestly whether it moved.
A weak answer: Talks about shipping on time, or cites usage with no baseline.
Core questions
Walk me through how you talk to users.
Why ask it: Separates PMs who do research from those who read summaries.
A strong answer: Regular direct contact, asks about behaviour not preference, distinguishes what users say from what they do.
A weak answer: Relies entirely on sales or support as a proxy.
Engineering says your top priority will take three months. What do you do?
Why ask it: The everyday reality of the job.
A strong answer: Understands what is driving the estimate, looks for a smaller version that tests the hypothesis.
A weak answer: Pushes for a faster estimate, or accepts and waits.
How do you handle a senior stakeholder demanding a feature you think is wrong?
Why ask it: Tests whether they have influence or just compliance.
A strong answer: Understands the underlying need, brings evidence, offers an alternative that serves it.
A weak answer: Builds it resentfully, or refuses flatly.
Final questions
What is your relationship with design like?
Why ask it: The PM–design relationship predicts a lot about how the team will function.
A strong answer: Collaborative from problem definition; does not hand over solutions as requirements.
A weak answer: Specifies the solution and asks design to make it pretty.
Tell me about a product decision you got wrong.
Why ask it: Product work is full of wrong calls; denial signals inexperience.
A strong answer: Specific, owns it, explains what evidence would have changed the decision.
A weak answer: Blames the market, engineering or leadership.
Red flags for this role
- Has never spoken to a user directly
- Cannot name a trade-off
- Describes the role as writing tickets
What a product manager actually does
Product managers decide what gets built and why. The role has responsibility without direct authority, so it runs on evidence, judgement and the ability to say no clearly.
See the full product manager job description, including how to assess each requirement.
Generate questions specific to your role — and that account for what previous interviewers already asked — with the free interview question generator.