60 product manager interview questions,
with answers

1. Clarify the goal, constraints and what "good" means.
2. Focus on a specific user or segment.
3. Explore problems before solutions.
4. Decide with explicit trade-offs.
5. Measure — define success metrics and risks.

1. How would you improve WhatsApp? — Pick a user segment (small businesses, elders), find their biggest pain, propose one focused improvement, define success.
2. Design an app for elderly people living alone. — Clarify the goal (safety, connection, health), segment, prioritise one need, design the core flow simply.
3. What's your favourite product and why? — Explain the user problem it solves and the design decisions behind its success; suggest one improvement.
4. Improve Google Maps for two-wheeler riders in India. — Consider lane access, narrow roads, parking, rain; prioritise one pain with evidence.
5. Design a product to help students prepare for exams. — Choose the exam and student type; focus on one problem like revision or motivation.
6. How would you improve UPI payments for first-time users? — Trust, errors, language; design for confidence at each step.
7. Should Swiggy launch a grocery subscription? — Define the user and job, economics, cannibalisation, test design.
8. Design an alarm clock for the deaf. — Clarify context; explore vibration, light, wearables; pick and justify.
9. What feature would you remove from Instagram? — Show judgment: what doesn't serve core users, and the cost of keeping it.
10. Improve the experience of booking a doctor's appointment. — Map the journey; find the biggest pain (finding the right doctor, waiting).
11. Design a product for farmers. — Narrow down (crop prices, advice, credit); consider connectivity and language.
12. How would you increase engagement on LinkedIn for Indian students? — Clarify engagement; find what students need; propose and measure.

13. How do you prioritise features? — Describe a framework (impact, effort, confidence — e.g. RICE²) and stress judgment and strategy alignment.
14. You have three critical bugs and one big launch. What do you do? — Assess user impact and risk; communicate trade-offs; decide.
15. Engineering says your feature will take three months. Now what? — Break it down, find the smallest valuable slice, de-scope.
16. How do you decide when a feature is ready to launch? — Success criteria, quality bar, risk, rollback plan.
17. A launch is going badly. What do you do? — Diagnose, communicate, decide to roll back or fix, learn.
18. How do you handle a stakeholder demanding a feature? — Understand the underlying need; evaluate against goals; explain decisions.
19. How do you write a PRD? — Problem, goals, users, requirements, metrics, scope, open questions.
20. How do you work with designers? — Share problems not solutions; involve them early; test with users.
21. How do you say no? — Tie decisions to strategy and data; offer alternatives.
22. How would you plan a quarter's roadmap? — Outcomes first, then bets; leave room for learning.

23. What metrics would you track for a food delivery app? — North star (orders delivered), then funnel, quality, unit economics.
24. Daily active users dropped 15% yesterday. Why? — Check data, segment, internal changes, external factors; hypotheses.
25. How do you define success for a new feature? — Adoption, engagement, outcome, guardrails.
26. What's a North Star metric? — The metric that best captures value delivered to customers and predicts long-term success³.
27. How would you measure the success of a search feature? — Search success rate, time to result, clicks, refinements.
28. Retention is falling. What do you do? — Cohort analysis; where in the lifecycle; qualitative research.
29. How do you design an A/B test? — Hypothesis, metric, sample size, duration, guardrails.
30. Conversion rose but revenue fell. Why? — Mix shifts, discounts, cheaper plans, refunds.
31. Which metrics matter for a subscription app? — Trial conversion, churn, retention, ARPU, LTV.
32. How would you measure user satisfaction? — NPS, CSAT, reviews, behavioural proxies.
33. What are guardrail metrics? — Metrics that must not get worse while you optimise another.
34. How would you measure the impact of a notification campaign? — Holdout group, opens, downstream actions, opt-outs.

35. Should Zomato enter a new market? — Market size, fit, capabilities, competition, risks.
36. How would you compete with a larger incumbent? — Find an underserved segment; a wedge.
37. What's the biggest threat to Google Search? — AI assistants; discuss responses.
38. How would you monetise a free app? — Match model to usage; test.
39. Build or buy? — Core competency, speed, cost, control.
40. How would you price a new product? — Value, competition, willingness to pay, tests.
41. What makes a product defensible? — Network effects, data, switching costs, brand.
42. How would you launch a product in tier-2 India? — Language, distribution, trust, device constraints.

43. What happens when you type a URL into a browser? — DNS, TCP/TLS, HTTP, rendering — at a PM-appropriate level.
44. Explain an API to a non-technical person. — A waiter taking orders between you and the kitchen.
45. How would you make an app work offline? — Local storage, sync, conflict resolution.
46. What is latency and why does it matter? — Delay; affects conversion and satisfaction.
47. How do recommendation systems work? — Collaborative and content-based filtering; feedback loops.
48. What trade-offs exist in building with an LLM? — Quality, cost, latency, safety, evaluation.
49. How would you scale a system for a sale day? — Load testing, caching, queues, graceful degradation.
50. What is technical debt and how do you manage it? — Shortcuts with future cost; reserve capacity.

51. Tell me about a product you shipped. — Problem, your role, decisions, results, learning.
52. Tell me about a time you failed. — Own it; what you learned and changed.
53. Describe a conflict with engineering. — Understand their view; find shared goals; resolve with data.
54. How do you influence without authority? — Evidence, empathy, alignment on goals.
55. Tell me about a hard trade-off you made. — Options, criteria, decision, outcome.
56. When did you use data to change your mind? — Show humility and rigour.
57. How do you handle ambiguity? — Clarify goals, make assumptions explicit, learn fast.
58. Tell me about a time you said no to a senior stakeholder. — Respectful, evidence-based.
59. Why product management? — Specific, genuine reasons tied to your experiences.
60. Why this company? — Show you've studied its products, users and challenges.

• Practise out loud with peers, recording yourself
• Prepare 6–8 stories that cover ownership, conflict, failure, impact and leadership
• Study the company's product deeply; use it for a week
• Learn frameworks, then drop the jargon in answers
• Think aloud — interviewers grade your reasoning

For the hardest round, see how to crack product sense interviews; for metrics rounds, see product metrics every PM must know. Marty Cagan's overview of the PM role is useful context for "why PM" questions¹.

Product sense — judgment about what to build. North Star metric — the metric capturing core customer value. Guardrail metric — a metric that must not worsen. STAR — situation, task, action, result. RICE — reach, impact, confidence, effort.