Product Manager Interview Guide for Indian Startups and Tech Companies

Indian PM interviews: especially at product-first companies: are structured around five dimensions. Knowing which dimension each question targets helps you answer at the right altitude.

• Product sense: 'Design a product for X.' Tests creativity, user empathy, and structured thinking
• Metrics and analytics: 'How would you measure success of Feature Y?' Tests data orientation
• Execution/prioritisation: 'Your engineering team has bandwidth for 3 of 10 features: how do you choose?'
• Strategy: 'Should Swiggy enter grocery delivery?' Tests market thinking and business judgment
• Leadership and behavioural: STAR-format stories about handling conflict, failure, stakeholder pushback

The most common PM interview question type is 'design a product for X.' Most candidates fail because they jump to features without understanding users.

• Step 1: Clarify the goal: 'Are we designing to acquire users, retain them, or monetise?'
• Step 2: Define user segments: pick 1–2 to go deep rather than listing 10 superficially
• Step 3: Map user journey and identify the biggest pain points
• Step 4: Prioritise features using Impact × Reach / Effort
• Step 5: Define success metrics for your top feature before finishing

Metrics questions test whether you can translate a business goal into measurable numbers. A common version: 'Feature X was launched: is it successful?'

• Always start by clarifying the goal: acquisition, engagement, revenue, or retention?
• Decompose: 'Daily active users' = new users + returning users – churned users
• Guardrail metrics: what should NOT go down even as your target metric goes up?
• Sample answer for 'Is Swiggy's new order-tracking feature successful?': adoption rate, tracking-screen open rate, customer support contacts about order status (should drop), NPS
• Common mistake: giving only one metric: interviewers always push back with 'what else?'

Execution questions test whether you can make hard trade-offs clearly. The RICE and Opportunity Scoring frameworks are both acceptable in Indian interviews.

• RICE: Reach × Impact × Confidence / Effort: quick to apply in an interview setting
• Always layer in strategic constraints: 'This feature has high reach but conflicts with our core value prop'
• Common question: 'Engineering says the feature will take 6 weeks but PM wants it in 3: what do you do?'
• Answer structure: understand the constraint fully, explore trade-offs, escalate with a clear recommendation
• Show that you work with engineers, not around them: mention tech debt and build quality

Indian companies increasingly use structured behavioural interviews for PM roles, especially at Series B+ startups and FAANG. STAR format is expected.

• Prepare stories for: overcoming scope creep, a feature that failed, influencing without authority
• India-specific: 'Tell me about a time you had to work with a difficult engineering lead': very common
• Strong PM stories show data-driven decisions, stakeholder alignment, and measured outcomes
• Weak stories describe what happened without showing what YOU specifically did differently
• Have at least 6–8 unique STAR stories ready: interviewers share notes and will notice repeats

The PM interview process varies meaningfully across company types in India.

• Flipkart: strong commerce domain knowledge expected; SQL and funnel analysis in technical screen
• Razorpay/PhonePe: payments and compliance fluency tested; fintech PM case studies
• Swiggy/Zomato: hyperlocal logistics context; operations and supply-side metrics matter
• Google India APM: case studies, leadership principles, coding screen (not always)
• Early-stage startups: expect to be given a real problem to solve in 48 hours as a take-home