Interview guide

Product manager interview questions, and how to answer them

By James Nicholls, Lead Product Manager · 7 min read

Most PM interview loops ask the same five kinds of question. Candidates who struggle usually aren’t short of experience. They just haven’t worked out which kind of question they’re answering, so they give a strategy answer to a behavioural question, or a feature list to a metrics one. Here are the five types, what each is really testing, and the questions to practice.

The 5 types of product manager interview question

BeforeBehavioural
After“Tell me about a time you…” Tests whether you’ve actually done the job, and how you behave when it gets hard.
BeforeProduct sense
After“How would you improve…?” Tests whether you can turn a vague problem into a clear, reasoned decision.
BeforeMetrics and analytics
After“How would you measure…?” or “Sign-ups dropped 20%. Why?” Tests whether you can pick the right number and reason about it.
BeforeStrategy and prioritisation
After“Should we build X or Y?” Tests whether you can make a call, explain the trade-off and say what you’d not do.
BeforeStakeholders and delivery
After“Engineering says it’ll take six months. What now?” Tests whether people will follow you without you being their boss.

Before you answer, name the type to yourself. It tells you what structure to use and what the interviewer is scoring.

Behavioural questions: use STAR, but lead with the result

STAR stands for Situation, Task, Action, Result. Most candidates spend 80% of their time on the situation. Flip it: one sentence of context, then what you did and what changed because of it.

Weak: “We had a lot of churn, so the team decided to look into onboarding…” Strong: “I cut onboarding from nine steps to four, and 30-day retention rose 6 points. Here’s how I got the team to agree to it.”

Behavioural questions to practice

  1. Tell me about a product you launched. What would you do differently?
  2. Tell me about a time you said no to a senior stakeholder.
  3. Describe a decision you made with incomplete data.
  4. Tell me about a time a launch didn’t go to plan.
  5. Tell me about a time you changed your mind because of customer research.
  6. How have you handled a disagreement with an engineer or designer?

Build 6 to 8 stories that you can bend to fit most of these. If you’re switching into product, stories from design, analysis or product ownership count. Show the product decision you made, not just the task you delivered.

Product sense questions

These ask you to improve or design something. Start with the goal and a specific user before any ideas. The full method, with a worked example and 12 practice questions, is in the product sense interview guide.

Metrics and analytics questions

Interviewers want one clear success metric, a couple of guardrails, and a calm way of working through a drop. For a “metric fell” question, check in this order:

  1. Is it real? A tracking change, a data delay or a public holiday.
  2. Where is it? Split by platform, country, new versus returning users, and acquisition channel.
  3. What changed? A release, a pricing change, a competitor launch or a seasonal pattern.
  4. What would you do? Name the test you’d run to confirm the cause, and the fix.

Metrics questions to practice

  • How would you measure the success of a food delivery app’s new tipping feature?
  • Daily active users fell 10% overnight. Walk me through what you’d check.
  • What’s the one metric you’d use for a project management tool? Why that one?

Strategy and prioritisation questions

There’s no right answer, so the interviewer is scoring how you choose. Say what the business is trying to achieve, list two or three options, pick one, and say what you’d give up. Hedging (“it depends”) without landing on a choice is the most common way to lose these.

  • You can build one of three features this quarter. How do you decide?
  • Should a subscription app add a cheaper, ad-supported tier?
  • Your biggest customer wants a feature no one else has asked for. What do you do?

Stakeholder and delivery questions

These test influence. Strong answers show you understood the other person’s goal, brought evidence, and found a smaller first step everyone could agree to.

  • Engineering says your top feature will take six months. What do you do?
  • Sales has promised a customer a feature that isn’t on the roadmap. How do you handle it?
  • How do you keep leadership updated without drowning them in detail?

How to prepare in two weeks

Days 1–3 · Stories

Write 6 to 8 behavioural stories, each led by the result and a number. Say them out loud until each fits in two minutes.

Days 4–7 · Product sense and metrics

Do one product sense and one metrics question a day, timed. Record yourself and listen back once.

Days 8–11 · The company

Use their product for real. Write down three things you’d change and how you’d measure each. Interviewers notice.

Days 12–14 · Mock interviews

Do at least two mocks with a working PM. Ask them what would make an interviewer say no.

Try it this week: pick your best project and rewrite its story so the first sentence is the result, with a number. That one change lifts most behavioural answers.

How ready are you to be a PM?

Check your PM level free in Product Lab: a few quick questions, your biggest gap and a plan for your next level. Or get the LIFT guide, the framework behind everything on this page.

Or turn it into a plan: try Product Lab free →

Want 1:1 help making the move? See the PM Career Accelerator →

Frequently asked questions

How many rounds are there in a product manager interview?

Usually three to five: a recruiter screen, a hiring manager call, then a loop covering product sense, metrics, behavioural questions and sometimes a case study or presentation.

What’s the hardest PM interview question?

For most people it’s a metrics drop question, because it needs a calm, ordered approach under pressure. Practice the four-step check above until it’s automatic.

Do I need technical knowledge for a PM interview?

You need to talk comfortably with engineers about trade-offs, not write code. Technical PM roles go deeper, and the job ad will say so.

How do I answer if I’ve never been a PM?

Use stories from your current role where you made a product decision: what to build, what to cut, or how to measure it. Interviewers score the thinking, not the title.

More guides