45 product manager interview questions, with frameworks and model answers

Product manager interview questions fall into six groups: product sense, execution and metrics, strategy, estimation, behavioural and technical. Interviewers are rarely looking for a right answer; they are scoring how you structure an ambiguous problem, choose a user and a problem to focus on, make trade-offs out loud and define how you would measure success. Below are 45 questions, a framework for each group, sketched model answers and a four-week prep plan.

Key takeaways

• Learn one framework per question type, then practise until it disappears into natural conversation. Reciting a framework word for word is a red flag.
• In product sense questions, the most common mistake is jumping to solutions. Spend the first third of your time on users and problems.
• In metrics questions, always check whether the data is right before you diagnose the product.
• Estimation questions test structure and sanity checks, not arithmetic.
• Behavioural answers need specifics: what you did, what changed, and what you would do differently.

How product manager interviews are structured

Most product companies run four to six rounds. In India, expect a guesstimate and often a take-home assignment; at startups, a founder round.

Product sense interview questions (8)

Framework: clarify the goal and constraints, pick a user segment, list their problems, prioritise one problem, generate three solutions, choose one with trade-offs, define success metrics, name the risks. Lewis Lin's CIRCLES method is a well-known version of this sequence.

1. How would you improve an app you use every day?
2. What is your favourite product, and why?
3. Which product do you think is badly designed, and how would you fix it?
4. Design a product for first-time smartphone users in a small town.
5. Improve a navigation app for two-wheeler riders in Indian cities.
6. Design a feature that helps families split household expenses over UPI.
7. Design an app for elderly parents who live alone.
8. Should a food delivery app add a grocery section? How would you design it?

Model answer sketch: improve a navigation app for two-wheeler riders

• Clarify: engagement, safety or revenue? Assume the goal is more weekly active riders who use it for commutes.
• Users: delivery partners, daily commuters and occasional riders. Pick daily commuters: large, frequent and underserved by car-first routing.
• Problems: cannot look at the phone while riding; routes through lanes that are technically allowed but unsafe; no sense of where parking is; voice instructions are hard to hear with a helmet on.
• Prioritise: "cannot safely follow directions while riding" affects every trip and is a safety issue. Choose it.
• Solutions: (a) richer audio cues for helmet earpieces with landmark-based phrasing ("turn left after the petrol pump"); (b) a glanceable, high-contrast mode with only the next turn; (c) haptic patterns for left and right through a paired wearable.
• Choose: (a), because it works on existing hardware and fits how people already give directions in India. Trade-off: landmark data quality varies by city.
• Metrics: share of two-wheeler trips completed without rerouting; weekly active commuters; guardrail: no rise in reported route errors.
• Risks: landmark changes, local-language coverage, distraction.

Model answer sketch: what is your favourite product?

Pick a product you have specific opinions about, not the most famous one. Cover who it is for, the job it does, two decisions that make it work, and one change you would make with its metric. A product teardown habit gives you three of these ready to go.

Execution and metrics interview questions (8)

Framework for diagnosis: confirm the metric definition and time window, check data and instrumentation, separate internal causes (releases, experiments, pricing) from external ones (seasonality, competitors, outages, holidays), segment the drop (platform, city, new versus returning, funnel step), form a hypothesis, validate it and propose a fix.

Framework for defining metrics: goal, then the user actions that show progress towards it, then one primary metric plus guardrails.

1. Orders dropped 10% week on week. What do you do?
2. Daily active users are up, but revenue is flat. Why might that be?
3. An A/B test shows higher conversion but lower 30-day retention. Do you ship it?
4. How would you measure the success of a new search feature?
5. What should the North Star metric be for a quick-commerce app?
6. How would you set quarterly goals for a payments onboarding team?
7. How would you decide whether to remove a feature few people use?
8. Signups doubled after a campaign, but activation fell. What happened?

Model answer sketch: orders dropped 10% week on week

1. Clarify: is it orders placed or completed? Which week? Is 10% outside normal weekly variation?
2. Check the data: any tracking or pipeline change? Do other sources (payments, partner app) show the same drop?
3. Internal causes: releases, experiments, price or delivery-fee changes, catalogue or supply changes in the period.
4. External causes: festivals, weather, exams, a competitor's offer, a payments outage.
5. Segment: by city, platform, app version, new versus returning, and funnel step. Suppose the drop is on Android, at cart-to-payment, from the day a new version shipped.
6. Hypothesis and test: the new version broke something in payments. Check error logs, compare old and new version cohorts, and roll back or hotfix.
7. Close: add an alert on cart-to-payment conversion by app version so it is caught in hours next time.

Interviewers are watching for step 2; many candidates skip it.

Model answer sketch: measure the success of a new search feature

Goal: help users find what they want quickly. User actions: searches, result clicks, add-to-cart from search. Primary metric: share of searches that lead to an add-to-cart within the session. Guardrails: search latency, zero-result rate, overall conversion. Supporting: time from search to first click, reformulation rate. For more on choosing a single guiding number, see our guide to the North Star metric.

Product strategy interview questions (7)

Framework: state the company's goal, describe the market and customer, identify the company's right to win (its assets, data, distribution, brand), list options, pick one with trade-offs, name the risks and propose the cheapest way to test it.

1. A well-funded competitor has launched a free version of your paid product. How do you respond?
2. How would you take a metro-focused consumer product to smaller cities?
3. Should an Indian B2B SaaS start-up sell to Indian customers or US customers first?
4. How would you monetise a free product with ten million monthly users?
5. Which adjacent market should a stockbroking app enter next?
6. What would you build in your first year if you joined us, and why now?
7. How would you decide between three roadmap bets with the same expected impact?

Model answer sketch: a competitor launched a free version

• Don't panic-match the price. First understand which customers are at risk: compare churn and pipeline by segment since the launch.
• Find the line. Free versions usually win the low end. If your profit comes from larger customers, protect them with what free products rarely offer: support, integrations, reliability, compliance.
• Options: (a) launch your own limited free tier as a funnel; (b) double down on the premium segment; (c) compete on switching costs through data and workflows.
• Pick: (b) plus a narrow version of (a) if low-end users later upgrade. Trade-off: you may lose share at the bottom.
• Test: a limited free tier in one segment for one quarter, measuring upgrade rate and support cost.

If the bets are close, interviewers want to hear how you would compare them; our guide to product prioritisation frameworks covers the common ones.

Estimation and guesstimate questions (7)

Framework: clarify scope and units, choose top-down or bottom-up, segment the population, state each assumption out loud, calculate in round numbers, sanity-check against something you know, then say which assumption the answer is most sensitive to.

1. How many food delivery orders happen in Mumbai on a Saturday?
2. How many cups of chai are sold in Delhi in a day?
3. Estimate the market size for a pet-care app in India.
4. How many two-wheelers are on the road in Pune?
5. Estimate the daily revenue of a coffee kiosk at a busy metro station.
6. How much storage would a photo-sharing app need per year?
7. How many orders a day does a single quick-commerce dark store handle?

Model answer sketch: orders per day at one quick-commerce dark store

Every number here is an assumption to state and defend, not data.

• Approach: bottom-up from capacity, then cross-check from demand.
• Capacity: assume the store is open 18 hours, with 12 pickers, each packing one order in about 3 minutes at a steady pace, so about 20 orders an hour each. At an average utilisation of 40%, that is 12 × 20 × 0.4 × 18, roughly 1,700 orders a day.
• Demand cross-check: assume the store serves a 2–3 km radius with about 100,000 households, 10% of which order in a given week, about twice. That is 20,000 orders a week, or about 2,900 a day.
• Reconcile: the two estimates are within a factor of two, so a reasonable answer is 1,500–3,000 orders a day, most sensitive to utilisation and weekly ordering rate.
• Close: say what you would check first if you had data: peak-hour throughput.

Behavioural interview questions (8)

Framework: STAR (situation, task, action, result) plus one more beat: what you learned or would do differently. Keep the situation short and spend most of the time on your actions and the result.

1. Tell me about a product or feature you shipped that failed.
2. Tell me about a time you disagreed with an engineer or designer.
3. Tell me about a time you said no to a senior stakeholder.
4. Describe a decision you made with incomplete data.
5. How do you prioritise when everything is urgent?
6. Tell me about a time you influenced a team you did not manage.
7. Why product management, and why this company?
8. What feedback changed how you work?

Model answer sketch: a feature you shipped that failed

• Situation: "We launched a referral programme to lower acquisition cost for a lending product."
• Action: "I wrote the spec, set a target of 15% of new signups from referrals, and launched to all users at once."
• Result: "Referral signups were well below target, and a share of them were low-quality applications."
• Learning: "I skipped a staged rollout and did not interview existing users about whether they would recommend a loan product to friends. Since then I run a small pilot first and talk to five users before writing a spec."

Use your own story and real numbers, and say "I", not "we", for decisions you made.

Technical interview questions for product managers (7)

Framework: pitch the explanation at the right level for the audience, name the trade-offs (speed, cost, reliability, security), and ask clarifying questions before designing anything.

1. What happens when you type a URL into a browser and press enter?
2. Explain what an API is to a non-technical stakeholder.
3. At a high level, how would an OTP login system work at scale?
4. When would you choose a relational database over a document store?
5. Write a query to find users who ordered in their first week and again in their fourth week.
6. How would you evaluate an AI-powered support assistant before launch?
7. An engineer estimates six weeks for a feature you expected to take two. What do you do?

Model answer sketch: evaluate an AI support assistant before launch

• Define the job: which questions it should answer, which it must hand off to a human (refunds, account security, complaints).
• Build an evaluation set: a few hundred real, anonymised past tickets with known good answers, including hard and adversarial cases.
• Score: answer accuracy, correct hand-off rate, harmful or made-up answers, tone, and latency.
• Set launch bars: for example, no unsafe answers in the evaluation set and a hand-off rate that support can absorb.
• Launch safely: shadow mode first, then a small share of traffic, with a one-tap path to a human.
• Monitor: resolution rate, re-contact rate and customer satisfaction against the human baseline.

For the SQL question, interviewers want correct logic more than perfect syntax. One approach:

SELECT u.user_id
FROM users u
JOIN orders o1 ON o1.user_id = u.user_id
  AND o1.created_at <  u.signup_at + INTERVAL '7 days'
JOIN orders o2 ON o2.user_id = u.user_id
  AND o2.created_at >= u.signup_at + INTERVAL '21 days'
  AND o2.created_at <  u.signup_at + INTERVAL '28 days'
GROUP BY u.user_id;

A four-week prep plan for product manager interviews

Daily, spend 20 minutes using the target company's product and form one opinion on what you would change. If there is a take-home assignment, write it like a short PRD; our guide on how to write a PRD has a template.

Common product manager interview mistakes

• Jumping to solutions before naming a user and a problem.
• Choosing every user segment instead of committing to one.
• Skipping data checks in metric questions.
• Unstated assumptions in guesstimates.
• "We" stories in behavioural rounds that hide what you did.
• No metrics at the end of a design answer.

Frequently asked questions

What are the most common product manager interview questions?

The most common are "How would you improve a product you use?", "What is your favourite product and why?", "A key metric dropped; how do you investigate?", a guesstimate, and "Tell me about a time you failed." Prepare structured answers for these first.

How do I answer product sense questions?

Clarify the goal, pick one user segment, list their problems, prioritise one, propose a few solutions, choose one with trade-offs and end with success metrics. Spend at least a third of your time on users and problems before solutions.

Are guesstimates common in Indian PM interviews?

Yes, guesstimate and market-sizing questions are common in Indian product interviews, especially for APM and early-career roles. They are scored on structure, stated assumptions and sanity checks rather than the final number.

How long should I prepare for a product manager interview?

Four weeks of focused practice, about an hour a day, is enough for most people with some product experience. Career switchers may need longer and should build a small portfolio alongside; see our guide on how to become a product manager in India.

Practise with people who have been on the other side of the table

Mock interviews are more useful when the person across the table has hired PMs. Product Circle's weekly AMA is a place to ask working PMs and founders the questions you cannot ask at work, including how they run interviews. Membership is by application; see how to join.

• Interviews
• Careers
• Product sense