Product Manager Interview Questions India 2026: Product Design, Metrics, and Case Studies

Product design questions ('Design a feature for X to achieve Y') are the most common PM interview question at Indian product companies. The framework that works:

(1) Clarify before designing: 'Before I start designing, I want to make sure I understand the constraints. Who is the primary user? Is this a new feature or improving an existing flow? Are there platform or resource constraints I should assume?' Spend 1-2 minutes clarifying; it signals structured thinking.

(2) Define user segments: list 2-3 user segments with different needs. 'For Zomato, I'll consider: frequent orderers (order 4+/week), occasional orderers (order once every 2-3 weeks), and first-time users. The problem of [increasing reorder rate] is most relevant for occasional orderers.' Pick one segment to focus on for depth.

(3) Identify pain points: for the chosen user, what are the top 2-3 barriers to achieving the goal? Use data or user insight to justify.

(4) Brainstorm solutions: generate 3-4 options without filtering. 'I could do A, B, C, or D.' Signal creativity.

(5) Prioritise and go deep on 1-2: 'I'll prioritise B because it addresses the highest-impact pain point with moderate engineering effort. Here's how it would work...' Include the UX flow, the data inputs needed, and how it integrates with the existing product.

(6) Define success metrics: North Star + 2-3 supporting + 1 guardrail.

(7) Consider risks: 'The biggest risk is that X. I'd mitigate it by Y.'

Metrics framework: (1) North Star metric: the single metric that most directly reflects the value users get from the feature. (2) Supporting metrics: 3-5 that explain WHY the North Star is moving (or not moving). (3) Guardrail metrics: metrics that should NOT worsen; they prevent local optimisation that hurts the broader product. (4) Leading indicators: metrics that predict future North Star movement before you can measure the outcome directly.

Example: 'How would you measure the success of Razorpay's new one-click checkout feature?' North Star: checkout conversion rate for merchants using one-click vs the standard flow. Supporting: time from cart to payment, drop-off rate at each checkout step, % of users who complete setup for one-click. Guardrail: merchant dashboard satisfaction score should not drop (merchants must not find it complex to set up); payment failure rate should not increase. Leading: % of returning customers who see the one-click option after first use.

Root cause analysis questions: 'DAU dropped 15% this week. Walk me through how you would investigate.' Structure: (1) Clarify: is this 15% across all segments or concentrated? Is it on one platform (iOS, Android, web)? Is it in one geography? Is it on one feature? (2) Rule out data issues: tracking bug, deployment of new tracking code, dashboard calculation error. (3) Check internal changes: was there a product release this week? (4) Check external factors: competitor launch, media event, seasonality. (5) Segment to find the localisation of the drop. (6) Propose the investigation plan and the next action based on what you find.

Prioritisation frameworks: RICE (Reach Impact Confidence / Effort, gives a score to rank features), MoSCoW (Must-have, Should-have, Could-have, Won't-have for scoping releases), ICE (Impact * Confidence / Effort, simpler variant of RICE). Indian PM interviewers most commonly ask for RICE reasoning but accept any framework that is applied consistently.

Prioritisation question structure: 'Given these 5 features and limited eng bandwidth, how would you prioritise?' (1) Understand the goal: what is the company trying to achieve this quarter? (2) Score each feature on Reach (how many users affected), Impact (how much does it move the North Star), Confidence (how well do we understand the user need and the likely impact), and Effort (engineering and design cost). (3) Calculate RICE scores. (4) Sanity-check the ranking against business context: is there a regulatory deadline? A competitor feature that makes one option more urgent? Adjust with explicit reasoning.

Estimation questions: 'How many UPI transactions happen in India per day?' Approach: (1) Establish anchor numbers you know (India population: 1.4B; smartphone penetration: ~65%, so ~900M smartphone users; UPI active users in 2024: ~350M based on NPCI data; typical active user transacts 3-4x per month). (2) Calculate: 350M users * 3.5 transactions/month / 30 days = ~40M transactions/day. Sanity-check against known data (NPCI reports ~150-200M daily transactions including all UPI rails in 2024; adjust your model if off by more than 3x and explain the adjustment).

Common PM behavioural questions at Indian product companies:

'Tell me about a product you built from scratch.' Best structure: the problem you identified and how you validated it, the process of building (what you built, decisions you made), the metrics outcome, and one thing you would do differently. Do NOT just describe features; describe decisions and their outcomes.

'Tell me about a time you had to say no to a stakeholder.' Key signal: saying no with data and an alternative, not just 'no'. Your answer should include what you said no to, why (data or reasoning), what alternative you offered, and the outcome.

'Tell me about a time your product or feature failed.' Own your specific contribution to the failure (do not blame the team or external factors). Describe what you learned. Show how you changed your process as a result. This is the most important PM behavioural question and the most often answered poorly.

'How do you work with engineers who disagree with your prioritisation?' Strong answers: bring data to the conversation (user research, usage metrics, business impact), create shared understanding of the user problem before proposing a solution, incorporate engineering constraints into your prioritisation process, and describe a specific situation where you changed your mind based on engineering input.

'What product do you admire and why?' Pick something you use and genuinely find interesting. Analyse a specific design or product decision (not just 'the UX is great'). Connect it to a business or user insight you find non-obvious.