Choose a product you personally use and like. Evaluate it as a Product Manager. Explain who the target users are, what features or experiences make the product strong, one important area to improve, and what success metrics you would track after launching that improvement. ### Constraints & Assumptions - Pick one product and one clear target segment. - Do not list many unrelated improvements; choose one focused opportunity. - Connect the improvement to user value and business value. - Include success metrics and guardrails. ### Clarifying Questions to Ask - Should I choose a consumer product, marketplace product, enterprise product, or product relevant to this company's domain? - Should the answer focus more on product design, strategy, metrics, or growth? - Am I expected to propose a new feature or evaluate an existing experience? - How much detail should I provide on metrics? ### Part 1 - Choose And Frame The Product Which product do you choose, and who are the target users? #### What This Part Should Cover - A specific product and target segment. - The core job to be done and why users like the product. - A concise explanation of the product's current value proposition. ### Part 2 - Explain What Works Well What features or experiences make the product strong? #### What This Part Should Cover - Two or three strengths tied to user needs, not just UI preferences. - Evidence from usage patterns, user behavior, or product judgment. ### Part 3 - Identify One Improvement What is one important area to improve, and why? #### What This Part Should Cover - A specific pain point and the user segment affected. - A focused product change, not a broad redesign. - Tradeoffs, edge cases, and why this improvement is worth prioritizing. ### Part 4 - Define Success Metrics What metrics would you track after launching the improvement? #### What This Part Should Cover - Primary success metric tied to the improvement. - Supporting metrics for adoption, completion, retention, satisfaction, or revenue. - Guardrails for quality, trust, cost, operational burden, or unintended behavior. ### What a Strong Answer Covers - Shows user empathy and product judgment. - Uses a clear product-sense structure rather than a casual product review. - Prioritizes one meaningful improvement and defends it. - Defines metrics that would prove the improvement worked. ### Follow-up Questions - Why is this the highest-priority improvement? - What segment would you not optimize for first? - What experiment would you run before a full launch? - What guardrail would make you roll back the change? - How would your answer change for a different user segment?