Describe a high-impact product project

A strong answer should sound like a product leader who uses data, not a report generator. ## Recommended structure: STAR with product depth ### 1. Situation Give the product context in one or two sentences. Example: - "Our marketplace was seeing rising cancellations during dinner hours, which hurt customer retention and merchant satisfaction." ### 2. Task State your role clearly. - What decision needed to be made? - Why were you the right owner or partner? Example: - "I was asked to determine whether the problem was driven by merchant prep delays, low dasher supply, or ETA misestimation, and to recommend a product change." ### 3. Action This is the most important section. #### A. Show product sense Explain how you framed the problem. - What was the user pain point? - Which side of the marketplace was most affected? - What were the key trade-offs? #### B. Show metric judgment Do not say only "I built a dashboard." Instead say: - north-star metric - leading indicators - guardrails - why those metrics were selected over alternatives Example: - "I used cancellation rate as the core outcome, but I paired it with on-time delivery, support contacts, and contribution margin so we would not solve cancellations by creating new problems elsewhere." #### C. Show analytical rigor Mention the method that fit the problem: - funnel analysis - cohort analysis - segmentation - A/B test - switchback experiment - causal inference / diff-in-diff - forecasting or modeling if relevant #### D. Show influence Explain how you turned analysis into a decision. - Who disagreed? - What trade-off did you communicate? - How did you get buy-in from product, engineering, ops, or leadership? ### 4. Result Quantify impact. Strong answers include numbers such as: - reduced cancellations by 80 bps - improved conversion by 3.2% - increased contribution profit by $1.1M annualized - reduced support tickets by 12% If exact numbers are confidential, use ranges or percentages. ### 5. Reflection This is where seniority shows. Say what you learned, what risk remained, and what you would improve. ## What good answers sound like "I noticed our initial proposal optimized order volume, but that would have increased discount spend too much. I reframed the decision around incremental contribution margin and customer retention. I partnered with product and operations, designed a market-level switchback test because of marketplace interference, and found that the feature improved completion rate in low-supply markets but hurt margins in dense markets. We launched only to the segments with positive unit economics, which improved fulfillment by 2.4% and saved roughly $800K annually." ## Common mistakes - describing tasks instead of decisions - focusing on tools rather than business impact - naming metrics without explaining why they mattered - claiming impact without a credible counterfactual - ignoring trade-offs or stakeholder disagreement ## Simple template to memorize 1. Problem 2. Decision needed 3. Metrics chosen and why 4. Analysis / experiment 5. Recommendation 6. Business impact 7. Stakeholder management 8. What you learned If the interviewer is a Head of Product, emphasize that you understand user behavior, business goals, and trade-offs—not just statistical output.