Launch prices end Friday-d --h --m --s left

Product manager interview questions

22 questions · 5 answer outlines · Updated Oct 6, 2026

Product manager interviews usually combine product sense questions, where you design or improve a product, analytical questions about metrics, an execution case on prioritisation or a launch, and behavioural rounds about leading without authority. Many companies add a take-home or a presentation. They are looking for structured thinking, a clear focus on users and sound judgement on trade-offs.

Five questions to prepare first

These come up in most interviews for this role. For each one: what the interviewer is checking, and the points a strong answer covers, in order.

1

How would you improve a product you use every day?

What they're checking

Whether you start from users and problems, and can prioritise among your own ideas.

A strong answer covers

  1. Name the product and who it is for, then choose one group of users to focus on.
  2. Identify that group's biggest pain point and explain how you know it matters.
  3. Suggest two or three solutions, then pick one and say why it beats the others.
  4. Define how you would measure success and mention one risk or trade-off.
2

Should we build a feature our biggest customer is asking for?

What they're checking

Your judgement when one loud customer and the wider product pull in different directions.

A strong answer covers

  1. Find out the problem behind the request, since the feature asked for is only one possible answer.
  2. Check how many other customers share the problem, using data, sales and support.
  3. Weigh the value against the cost and the fit with strategy, including the cost of maintaining it later.
  4. Lay out the options, build, adapt, offer a workaround or decline, and how you would explain the decision.
3

Which metrics would you use to judge whether a new feature succeeded?

What they're checking

Whether you can tie metrics to goals and spot unintended effects.

A strong answer covers

  1. Start from the goal of the feature, then choose one primary metric that reflects it.
  2. Add supporting metrics that explain the primary one, and guardrails that would reveal harm, such as cancellations.
  3. Explain how you would measure it, ideally with an experiment against a baseline.
  4. Say in advance what result would make you roll back or change course.
4

How do you prioritise a backlog when everything seems important?

What they're checking

Whether you prioritise from goals rather than from whoever shouts loudest.

A strong answer covers

  1. Start from the product goals for the period, since priorities only make sense against them.
  2. Compare items on impact, confidence and effort, using a framework such as RICE as an aid, not an answer.
  3. Account for dependencies, risk and commitments already made.
  4. Make the trade-offs visible to stakeholders and revisit the order as you learn.
5

Tell me about a time you influenced a decision without having authority.

What they're checking

How you get people to act when you can't tell them to.

A strong answer covers

  1. Describe the decision and who you needed to convince.
  2. Explain how you learned what mattered to them, and framed your case in those terms.
  3. Show the evidence you used, such as user research, data or a prototype.
  4. Give the outcome and what you would do the same way next time.

Product sense

Pick a user, find their problem, and only then talk about solutions.

  1. 1How would you improve a product you use every day?Answer outline
  2. 2Should we build a feature our biggest customer is asking for?Answer outline
  3. 3Design a product for people who have just moved to a new city.
  4. 4What is your favourite product, and why?
  5. 5How would you improve the onboarding of an app where most new users drop off?
  6. 6Which recent product launch would you have done differently?

Metrics and analytics

Expect to define success, read a metric change and decide what to do about it.

  1. 7Which metrics would you use to judge whether a new feature succeeded?Answer outline
  2. 8Daily active users fell 5% this week. What do you do?
  3. 9How would you choose a north star metric for a marketplace?
  4. 10A feature raised engagement but lowered revenue. What now?
  5. 11How do you decide whether an A/B test result is worth acting on?

Execution and prioritisation

How you turn a strategy into shipped work, and what you cut when you can't do everything.

  1. 12How do you prioritise a backlog when everything seems important?Answer outline
  2. 13Tell me about a time you cut scope to hit a date.
  3. 14What goes into a good product spec?
  4. 15A critical bug appears two weeks before launch. What do you do?
  5. 16How do you plan a quarter with your engineering team?
  6. 17How do you know when a product is ready to ship?

Leadership and behavioural

Product managers rarely have authority over the people they work with. These questions test influence.

  1. 18Tell me about a time you influenced a decision without having authority.Answer outline
  2. 19Tell me about a product decision that turned out to be wrong.
  3. 20How do you say no to a senior stakeholder?
  4. 21How do you resolve disagreements between design and engineering?
  5. 22Why do you want to be a product manager here?

Product manager interview tips

  • Use a simple structure for product sense questions, user, problem, solutions, choice, metrics, and say it out loud so the interviewer can follow.
  • Use the company's own product before the interview, and come with one considered improvement.
  • Prepare stories that show influence, a launch, a failure and a hard trade-off, each with a measurable result.
  • Ask clarifying questions before answering cases. Interviewers often leave the prompt vague on purpose.

Product manager interview FAQ

For most roles they are light, such as how an API works or what makes a feature hard to build. Technical product manager roles go deeper, sometimes including system design.

A round where you design a new product or improve an existing one out loud. Interviewers judge how well you understand users, how you prioritise and how clearly you communicate, not whether your idea is the best one.

Use examples from your current role where you worked out what users needed, prioritised or influenced a decision. Many product skills show up outside the job title.

Related roles

All interview questionsHow a mock interview works

Say these answers out loud before the real interview.

A free mock interview for this role asks five questions you haven't seen, scores each answer and shows a stronger one.

Start with a free mock interview
Start a free mock interview