The PM interview question types, how to structure product design answers, metrics frameworks, and what top companies look for.
Product Design ("Design a product for X"): Tests user empathy and design thinking. Product Improvement ("How would you improve YouTube?"): Tests analytical ability and prioritization. Metrics ("How would you measure success for Instagram Stories?"): Tests data-driven thinking. Estimation ("How many pianos are in Chicago?"): Tests structured reasoning. Behavioral ("Tell me about a time you shipped a product that failed"): Tests experience and judgment.
Step 1 — Clarify goals and constraints (2 min). Step 2 — Define the user and their pain (3 min). Step 3 — Identify 3–5 specific user pain points. Step 4 — Prioritize one pain point with reasoning. Step 5 — Brainstorm solutions (quantity, then quality). Step 6 — Pick a solution and explain why. Step 7 — Define success metrics. Step 8 — Identify risks and trade-offs. Interviewers care more about your reasoning at each step than the specific idea you land on.
HEART (Google): Happiness, Engagement, Adoption, Retention, Task Success. Use it for consumer products. AARRR (Pirate Metrics): Acquisition, Activation, Retention, Revenue, Referral. Use it for growth-focused products. Don't just list metrics — explain leading vs. lagging indicators, and what you'd do if each metric moved in the wrong direction.
What candidates think: creative product ideas. What FAANG actually looks for: Structured thinking (can you break down complex problems?), Customer empathy (do you start with the user?), Data fluency (can you define and interpret metrics?), Prioritization (can you say no, and explain why?), Cross-functional leadership (can you influence without authority?). Your ideas matter less than how you arrived at them.
Jumping to solutions before defining the user (the #1 mistake). Not quantifying impact when estimating trade-offs. Saying "I would" instead of "I did" in behavioral answers. Picking the first idea instead of comparing options. Not knowing the company's business model deeply enough to reason about product trade-offs.