Question 1

Tell me about a time you had to prioritise between two things that both seemed important.

Accepted Answer

The two options, what each stakeholder wanted, the evidence you gathered (usage data, revenue at stake, customer interviews, effort estimates), the framework if you used one, the decision, and how you communicated it to the side that lost. Include the outcome and whether you would decide the same way now. Common mistake: Naming a framework (RICE, MoSCoW) as the answer. The panel wants to see the messy inputs and the judgment, not the acronym.

Question 2

Describe a time you said no to a senior stakeholder.

Accepted Answer

What they asked for, why it conflicted with the roadmap or the data, how you framed the no — usually as "not now, and here is what we would drop to do it" — and how you kept the relationship. Show that you went in with numbers and an alternative, not just a refusal. Common mistake: A story where you said yes and quietly deprioritised it later. Panels see that as avoiding conflict, not managing it.

Question 3

Tell me about a launch that failed or underperformed. What did you learn?

Accepted Answer

What you shipped, the metric you expected and what you got, the real reason in hindsight (wrong problem, wrong segment, poor discovery, bad timing), what you did in the weeks after (iterate, kill, reposition), and the specific change to how you work now. Own the miss without blaming engineering or marketing. Common mistake: Choosing a "failure" that was really a success in disguise. The panel is testing candour; give them a real one.

Question 4

How do you decide which metrics to track for a new feature?

Accepted Answer

Start from the behaviour change the feature should cause, pick one primary metric that measures it and one or two guardrails (the things that must not get worse), decide the target before launch, and say how you instrument it. Give a real example with actual numbers — adoption within 30 days, task completion, retention delta. Common mistake: Listing every metric you can think of. A feature with eight KPIs has none.

Question 5

Walk me through how you do discovery before committing to build something.

Accepted Answer

Your actual method: customer interviews (how many, how recruited, what you asked), support tickets and usage data, a problem statement written before any solution, a cheap test (prototype, fake door, concierge) to check demand. Give an example where discovery killed something you personally wanted to build. Common mistake: Describing discovery as "talking to customers" without a method or a case where it changed your mind.

Question 6

Tell me about a time engineering said a feature would take far longer than you expected.

Accepted Answer

How you understood the reason (a technical constraint, hidden complexity, debt), how you renegotiated scope to find the version that delivered most of the value in a fraction of the time, and what you told stakeholders. Show respect for the estimate and creativity on scope, not pressure on the team. Common mistake: Framing the story as convincing engineers to work faster. Every engineering lead on the panel will hear that and mark you down.

Question 7

How do you communicate a roadmap to leadership, and how do you handle changes to it?

Accepted Answer

Roadmap as outcomes and bets with confidence levels, not a list of dated features; a regular cadence for updates; and a clear rule for what counts as a change worth escalating. Give an example of a mid-quarter change, how you presented the trade-off, and what leadership decided. Common mistake: Presenting the roadmap as a promise and then apologising for every slip. Set it up as bets from the start.

Question 8

Describe an unpopular product decision you made and how you handled the reaction.

Accepted Answer

The decision (removing a feature, changing pricing, deprioritising a loud customer's request), the evidence behind it, who pushed back and why, how you communicated — early, directly, with the reasoning — and what the result was six months later. Panels are scoring backbone plus empathy. Common mistake: Picking a decision that was unpopular with one junior person. Choose one with real stakes and real resistance.

Question 9

How do you work with designers and engineers day to day?

Accepted Answer

The rituals you actually use (kickoffs, refinement, demos, retros), how early you bring engineering into problem definition, how you write requirements (problem, user, constraints, success measure — not pixel specs), and one example of a conflict inside the trio and how it was resolved. Common mistake: Describing yourself as the "CEO of the product." Engineers and designers on the panel hate that phrase.

Question 10

Tell me about a time you used data to change a plan.

Accepted Answer

The plan, the data that contradicted it (a funnel drop, a cohort that did not retain, an experiment result), how you checked the data was trustworthy, the new plan, and the outcome. Include the moment you had to tell people the original plan was wrong. Common mistake: Vague "data-driven" claims without a specific number that changed a specific decision.

Question 11

How would you improve a product you use every day?

Accepted Answer

Pick one product, name the user and the job they hire it for, identify one real friction with evidence from your own use, propose one change, say how you would measure success, and name the trade-off or risk. Keep it to a few minutes and structured — this is a mini product review. Common mistake: Listing five feature ideas. The panel wants one problem, well reasoned, not a brainstorm.

Question 12

Describe a situation where you did not have enough information to decide but had to anyway.

Accepted Answer

What you knew, what you did not, the cheapest way you found to reduce the biggest uncertainty in the time available, the decision, and how you set it up to be reversible if wrong. Show comfort with "70% confidence, decide now" rather than paralysis or bravado. Common mistake: Presenting the decision as a lucky guess. Show the reasoning and the escape hatch.

Question 13

How do you handle a customer request that only one big client wants?

Accepted Answer

Understand the underlying need, check whether other customers have the same problem in different words, size the revenue at risk against the roadmap cost, and either find a general solution, a configuration, or a clear no with the reasoning. Give a real example and what happened with the client. Common mistake: Either "we always build for our biggest customer" or "we never build one-offs." The panel wants judgment, not a rule.

Question 14

Why product management, and why this company?

Accepted Answer

A real reason you do this job (the decision-making, the customer problem), two specific things about the company — a product bet you find interesting, a market you know, a stated strategy — and an honest view on one thing you would want to understand better in your first month. Common mistake: Flattery about the company's mission without a single specific observation about its product.

Product Manager interview questions — and what a strong answer includes

Tell me about a time you had to prioritise between two things that both seemed important.

Describe a time you said no to a senior stakeholder.

Tell me about a launch that failed or underperformed. What did you learn?

How do you decide which metrics to track for a new feature?

Walk me through how you do discovery before committing to build something.

Tell me about a time engineering said a feature would take far longer than you expected.

How do you communicate a roadmap to leadership, and how do you handle changes to it?

Describe an unpopular product decision you made and how you handled the reaction.

How do you work with designers and engineers day to day?

Tell me about a time you used data to change a plan.

How would you improve a product you use every day?

Describe a situation where you did not have enough information to decide but had to anyway.

How do you handle a customer request that only one big client wants?

Why product management, and why this company?

Answer these out loud, get coached

More technology roles

Before the interview

Get new product manager questions by email

Product Manager interview questions — and what a strong answer includes

Tell me about a time you had to prioritise between two things that both seemed important.

Describe a time you said no to a senior stakeholder.

Tell me about a launch that failed or underperformed. What did you learn?

How do you decide which metrics to track for a new feature?

Walk me through how you do discovery before committing to build something.

Tell me about a time engineering said a feature would take far longer than you expected.

How do you communicate a roadmap to leadership, and how do you handle changes to it?

Describe an unpopular product decision you made and how you handled the reaction.

How do you work with designers and engineers day to day?

Tell me about a time you used data to change a plan.

How would you improve a product you use every day?

Describe a situation where you did not have enough information to decide but had to anyway.

How do you handle a customer request that only one big client wants?

Why product management, and why this company?

Answer these out loud, get coached

More technology roles

Before the interview

Get new product manager questions by email