Product Manager Interview Questions India 2026: Frameworks, Case Studies, and Answers

Product design question framework: The most common PM question type. Question example: 'How would you improve Swiggy's reorder experience?' Framework to use: (1) Clarify the goal (2 minutes): 'Before I start, can I confirm: are we trying to increase the frequency of orders from existing users, or also trying to reduce the time between decision and order? And are we targeting all users or a specific segment?' (2) Define user segments (3-4 minutes): identify 2-3 distinct user types and their specific frustrations with the current reorder experience. 'Three segments: (a) daily lunch orderer (orders from the same 2-3 restaurants every weekday; frustrated by the 4-tap flow to reach the reorder button); (b) weekend family (larger orders, more variety, less frequent; frustrated by the inability to reorder the exact previous order quantity when group size changes); (c) new user (does not have enough history to benefit from reorder; irrelevant for this feature).' (3) Pick one segment to solve for (1 minute): 'I will focus on the daily lunch orderer because they represent the highest frequency and therefore the highest reorder GMV potential.' (4) Brainstorm solutions without filtering (3-4 minutes): list 4-6 potential solutions. Then prioritise with an explicit framework: 'Using impact (how many users benefit) times feasibility (how long to build) as a quick filter, I would prioritise: (a) one-tap reorder from the home screen showing last 3 orders, (b) push notification at 12 PM for users who have ordered lunch on at least 3 of the last 5 weekdays.' (5) Define success metrics (2 minutes): 'I would track: reorderrate (orders marked as reorders / total orders), timefromopento_checkout (reduced from current baseline), and guardrail: that the feature does not cannibalise browse-and-discover behaviour for users who sometimes order from new restaurants.'

Metrics questions: (1) 'What would be your north star metric for Swiggy Instamart and why?' (north star metric should capture value delivery to the user AND correlate with business health; options: number of orders delivered in under 10 minutes (captures the core value proposition: speed), repeat order rate (captures habit formation and retention), or GMV per active user per week (captures monetisation); argument for 'orders delivered in under 10 minutes': it is specific to Instamart's differentiation from regular grocery delivery, it drives retention (a fast delivery creates a repeat habit), and the 10-minute threshold is a hard quality bar, not just a volume number). (2) Root cause analysis: 'Razorpay's payment success rate dropped 3% yesterday. Walk me through how you would investigate.' Framework: (a) Is this a real drop or a data/logging error? (b) Segment: which payment method (UPI, card, net banking)? Which bank? Which merchant category? Which time of day? Which geography? (c) Check for infrastructure changes (new API version deployed, upstream bank system change). (d) Check external: did any bank or UPI rail report an incident? (e) Form hypotheses and assign priority by probability and ease of check. (3) 'How do you decide if an A/B test result is significant enough to ship?' (statistical significance: p < 0.05; practical significance: is the effect size large enough to matter for the business? a feature that improves conversion by 0.001% is statistically significant with a large enough sample but not practically significant; also check: did the test run long enough to avoid novelty effects? did it affect all user segments equally or only some?).

Execution and prioritisation: (1) 'You have 3 feature requests from your top enterprise clients and a 4-engineer team for 3 weeks. How do you decide what to build?' Framework: (a) understand each request's user problem (not just the request itself; clients often request features that address a symptom, not the root cause; dig to find the actual pain point), (b) estimate impact for each: which affects the most users / highest value segment? (c) estimate effort for each: work with the engineering lead for T-shirt sizing (S/M/L/XL), (d) apply RICE scoring or ICE scoring as a structured decision (RICE = Reach Impact Confidence / Effort; ICE = Impact * Confidence / Effort), (e) check for dependencies (can Feature B not be built without Feature A?), (f) communicate the prioritisation back to stakeholders with the rationale. (2) 'Tell me about a time you made a product decision that turned out to be wrong.' Structure: describe the decision and the reasoning at the time, what happened, what the data showed, how you pivoted, and what you changed about your decision-making process. The learning is the signal. A PM who cannot recall a wrong decision is either dishonest or not shipping enough. (3) 'How do you manage competing priorities between engineering, design, and business stakeholders?' Own the trade-offs, not just the communication. Be specific about how you weigh each stakeholder's input, how you communicate decisions, and what you do when there is genuine disagreement at the PM level.

PM estimation question framework: 'Estimate the number of food delivery orders in India per day' (1) Start with a known anchor: India population approximately 1.4 billion. (2) Segment by target user: urban India (population in cities with food delivery availability): approximately 500 million. Of those, adults with disposable income who use smartphones for food delivery: estimate 20-25% = approximately 100-125 million potential users. (3) Active users: not all potential users order regularly. Estimate monthly active users on Swiggy + Zomato combined: publicly, Swiggy has reported approximately 45 million monthly order users; Zomato similar; total approximately 80-90 million monthly active users across both platforms. (4) Order frequency: average user orders approximately 3-4 times per month = approximately 3.5/30 = 0.12 orders/day per active user. (5) Daily calculation: 85 million users * 0.12 orders/day = approximately 10 million orders/day total across platforms. (6) Sanity check: Zomato has reported approximately 3-4 million daily orders in its earnings; Swiggy is approximately similar. Combined approximately 7-8 million orders/day; our estimate of 10 million is in the same order of magnitude, slightly optimistic but plausible. State your estimate as a range: 7-10 million daily food delivery orders in India. Structure > precision: the exact number is less important than the structured thinking and explicit assumptions.