product · Experienced
Product Manager interview questions on product sense, metrics, prioritization, and case studies asked at Indian product companies.
What is the difference between a product roadmap and a product backlog?
Tip: Roadmap: high-level, time-bound plan showing themes and initiatives for the next 3-12 months — for stakeholder communication. Backlog: prioritised list of specific tasks (user stories, bugs, tech debt) — for the engineering team.
How do you prioritise features? Explain the RICE framework.
Tip: RICE = (Reach x Impact x Confidence) / Effort. Reach: users in a time period. Impact: how much it moves the metric. Confidence: how sure you are (%). Effort: person-weeks. Compare features by RICE score to remove gut-feel bias.
What is a North Star metric? How do you identify the right one for a product?
Tip: A North Star metric captures the core value delivered to users — not revenue (a lagging indicator), but the activity that drives revenue. Examples: Spotify's monthly listening time, Airbnb's nights booked. It must be measurable, actionable, and reflect genuine user value.
How would you design a feature to improve 30-day user retention for a B2C app?
Tip: First define the problem: where in the retention curve is the drop-off? Analyse cohorts. Identify the 'aha moment' that correlates with retention. Build towards that moment faster (onboarding optimisation, progress tracking, notifications). A/B test. Measure day-7 retention as a leading indicator.
What is A/B testing? How do you determine if a result is statistically significant?
Tip: A/B test: randomly split users into control (A) and variant (B), measure a metric for each. Statistical significance (p < 0.05) means the result is unlikely by chance. Practical significance matters too. Power analysis determines sample size needed.
Tell me about a product decision you made with incomplete data. How did you handle the ambiguity?
Tip: Show structured ambiguity handling: what data you DID have, what assumptions you made explicit, how you reduced uncertainty cheaply (user interviews, landing page test), what reversible decision you made, and how you set up a feedback loop.
DAUs dropped 20% overnight. Walk me through your investigation process.
Tip: Rule out before concluding: data pipeline issue? Seasonal effect? Recent release or infrastructure change? Then segment: which platform? Which geography? Which user segment? Correlate with deployment logs. Only then hypothesise user behaviour causes.
Engineering says a feature takes 3 months; the CEO wants it in 3 weeks. How do you handle this?
Tip: Do not promise what engineering cannot deliver. Instead: present a scoped MVP in 3 weeks that delivers the core value, with a clear plan for the full version. Show the CEO the trade-off explicitly. PMs negotiate scope, not deadlines.
How do you handle conflicting feedback from engineering and business stakeholders?
Tip: Conflicts usually stem from different constraints or different goals. Facilitate a shared understanding: bring both parties together, articulate the trade-off clearly, and make a decision aligned to the product strategy. Own the decision, do not defer.
What is user story mapping? How is it different from a flat backlog?
Tip: User story mapping: activities (top row), user tasks (second row), user stories (below, ordered by priority). A flat backlog loses the user journey context. Story maps reveal the MVP slice (horizontal cut through the activities).
Describe a product you launched. What went wrong and what did you learn?
Tip: Authenticity matters more than perfection here. Describe a real failure: wrong assumption about user behaviour, underestimated adoption friction, missed a technical constraint. Show what you changed for the next launch.
What product do you use daily that you think is excellently designed? What makes it excellent?
Tip: Pick something you genuinely use and analyse at PM depth: what problem does it solve? What onboarding decisions reduce friction? What metric is it clearly optimising for? What would you change? Interviewers are evaluating your product thinking.
Recruiters test these skill areas specifically. Click any topic to see curated questions.
Practice, not just reading
Upload your resume and practice a full Product Manager mock interview with AI-generated questions and rubric-based scoring across 5 dimensions — free to start.