32 product manager interview questions (with answer frameworks)

PM interviews test four dimensions: product sense, analytical thinking, execution ability, and leadership. The most common failure mode isn't wrong answers, it's structureless answers that reveal unclear thinking. These 32 questions cover all four dimensions with answer frameworks for each.

"The best PM candidates don't just answer the question, they show you how they think. The question is a prompt; the thinking is the interview."

— Jordan P., Head of Product at a Series B company and former PM interviewer at a FAANG

Product sense questions

1. "Design a feature for [product] that improves [metric]."
Framework: User → Problem → Solution → Tradeoffs → Success metrics. Never jump to solution. Always start with which user and what specific problem.

2. "What's your favorite product and how would you improve it?"
Framework: Choose a product you genuinely use. Identify a real pain point (backed by behavioral observation, not assumption). Propose one specific improvement with a success metric.

3. "How would you prioritize a backlog of 15 features?"
Framework: RICE score each feature. Explain your Reach and Impact estimates. Note what data you'd need to reduce confidence uncertainty.

4. "A VP wants to add a feature that you think is wrong. What do you do?"
Framework: Gather data to validate the disagreement. Present alternative analysis. If still disagreed, propose a small test to resolve with data. Frame as hypothesis, not opinion.

Analytical questions

5. "Our DAU dropped 15% last week. Walk me through your investigation."
Framework: Segment first (platform, geo, cohort). Check for external factors (outage, campaign end). Look at funnel steps to isolate the drop. Identify leading indicators. Form 2 to 3 hypotheses before diving into data.

6. "How would you measure the success of [feature]?"
Framework: Primary metric (directly measures the user value). Secondary metric (leading indicator). Guardrail metric (what you're not willing to hurt). Define baseline and 30/90-day targets.

7. "We have two hypotheses for why retention is low. How do you decide which to test first?"
Framework: Estimate the impact of each hypothesis if true × confidence level × cost to test. Test the high-impact, high-confidence, low-cost hypothesis first.

Execution questions

8. "Walk me through how you write a PRD."
Framework: Discovery → Problem statement → User stories → Acceptance criteria → Edge cases → Success metrics. Emphasize that acceptance criteria and edge cases are where most PRDs fail.

9. "Engineering says a feature will take 3x longer than expected. What do you do?"
Framework: Understand why (scope clarity? complexity? tech debt?). Scope the MVP, what's the minimum that delivers the core value? Communicate timeline changes to stakeholders with context.

10. "How do you handle scope creep?"
Framework: Document agreed scope in the PRD. When new requests arrive, evaluate against PRD scope. Use RICE to compare: is the new request worth what it displaces? Push nice-to-haves to v2 explicitly.

Behavioral questions

11. "Tell me about a time a feature you built failed."
Framework: STAR (Situation, Task, Action, Result). Focus on what you learned. Show that failure is data, what did it change in how you work?

12. "How do you work with a difficult engineer?"
Framework: Engineers push back when requirements are unclear or scope is unreasonable. Show that you address the root cause (better specs, earlier involvement) not the relationship symptom.

Questions to ask your interviewer

Always prepare 3 to 4 questions. High-signal questions: "What does a typical PRD review meeting look like here?", "How do you measure PM performance?", "What's the biggest product problem you're working on right now?", "What separates your best PM from your average PM?"