Product Manager Interview Questions for Indian Companies 2026

Indian PM interviews typically cover 5 question types:

1. Product Sense: 'Design a new feature for Swiggy.' 'How would you improve Razorpay's dashboard?' These test whether you understand users, can prioritise, and make product trade-offs.

1. Estimation: 'How many UPI transactions happen per day in India?' 'How many food orders does Swiggy process daily?' These test structured thinking under ambiguity.

1. Analytical / Metrics: 'Swiggy's DAU dropped 10% week-over-week. Walk me through how you would diagnose this.' Tests your ability to break down data problems systematically.

1. Strategy: 'Should Razorpay enter the lending space?' 'What is the biggest threat to Meesho's business in the next 3 years?' Tests business acumen and strategic frameworks.

1. Behavioural: 'Tell me about a time you shipped a product with limited data.' 'How did you handle a situation where engineering said something was impossible?' Tests interpersonal and leadership skills via STAR framework.

'How would you improve Google Pay's UX for tier-2 Indian users?'

Strong answer structure:

1. Clarify: 'By tier-2 users, I mean users in cities like Jaipur, Coimbatore: likely on lower-end Android phones with intermittent 4G.'
2. Identify users: Primary user is a small business owner or young professional making 3–10 transactions per week: bill payments, UPI transfers, merchant payments.
3. Identify pain points (from knowledge of this user): Slow load times on low-end devices, confusion with multi-step UPI flow for first-time users, distrust of digital payments due to failure anxiety.
4. Propose solutions ranked by impact: (a) Offline mode: queue transactions when connectivity is lost and retry automatically. High impact, solves the core anxiety. (b) Simplified first-time UPI setup flow: reduce steps from 6 to 3, with vernacular language support. (c) 'Recent' shortcut on home screen for repeat transactions: most tier-2 users repeat the same 5–10 transactions. Reduces time-to-complete.
5. Success metrics: UPI setup completion rate (new users), transaction success rate on ₹1–10k range, D7 retention of new activations from tier-2 cities.

Common mistake: Jumping to features without articulating users and pain points first.

'How many food orders does Swiggy process daily in India?'

Structured answer:

• Urban India internet population: ~700M total internet users, ~350M in cities
• Regular food delivery users: ~10–15% of urban internet users = 35–50M
• Order frequency: Average Swiggy user orders 2–3 times per month = roughly 2.5 times/month
• Daily orders from regular users: 40M users × 2.5 orders/month ÷ 30 days = ~3.3M orders/day
• Adjust for market share: Swiggy and Zomato split ~50/50 = ~1.6–1.8M Swiggy orders/day
• Round answer: ~1.5–2M food orders per day

Actual: Swiggy publicly disclosed ~3M daily orders in 2024. The estimation is in the right order of magnitude: that is the goal.

'DAU dropped 10% week-over-week: how do you diagnose this?'

Structure: Funnel the investigation:

1. Is it a data/tracking issue? Check analytics pipeline for reporting errors.
2. Segment the drop: Platform (iOS vs Android), geography (specific cities?), user type (new vs returning), cohort (recent signups only?)
3. External factors: Competitor campaign? Public holiday? News event?
4. Internal changes: Code deployment that week? UX change? Server error rate spike?
5. Form a hypothesis: 'The drop is concentrated in Android + users who signed up in the last 30 days, coinciding with last Tuesday's push notification change.' → Test by rolling back the notification change.

'Tell me about a product you managed that failed. What did you learn?'

Strong STAR answer: Situation: 'We launched a social sharing feature on our fitness app, allowing users to post workout summaries to their timeline.' Task: 'I owned the feature end-to-end: from user research to launch: with a 6-week timeline.' Action: 'We shipped the feature on schedule. Usage was 60% below our forecast in week 1.' Result/Learning: 'We had assumed users wanted public sharing based on fitness app benchmarks from the US. Our research with 8 users missed the privacy sensitivity of Indian users who did not want their fitness habits visible to family members on the same platform. We added a "friends only" privacy setting in the next sprint: usage recovered to 80% of forecast. Learning: competitive benchmarks from different cultural contexts are leading indicators only: user research in the actual market is irreplaceable.'

PM interviews at Indian companies: Product companies (Meesho, Razorpay) expect strong product thinking and data rigour. APM programmes (Amazon, Meesho, Swiggy) for freshers require intellectual curiosity and structured thinking more than domain knowledge.