Explain a Difficult Product Call and the Evidence You Used to Justify It

Walk me through a difficult product decision you owned. Why was it hard, what evidence and reasoning did you use to support it, and what happened as a result? ```hint Make the support concrete The second half of the question carries the weight. Choose a decision where you can name the specific data, research or experiment that informed it, and explain what you did where that evidence ran out. ``` ### Clarifying Questions - Does "difficult" mean a call made with incomplete or conflicting data, one that disappointed a stakeholder or customer, or one with a real cost such as cutting a feature or delaying a launch? Is one of these preferred? - Should the decision come from an AI or model-backed product, or is any product fine? - Is a decision that turned out to be wrong acceptable, if I explain what I learned from it? ### What a Strong Answer Covers - Why the decision was genuinely hard: the options, the trade-off between them, and what was at stake for users and the business - The evidence behind the call (data, experiments, user research, technical constraints) and the judgment applied where evidence was missing or conflicting - How the candidate brought skeptical stakeholders along and handled disagreement after the call was made - A measured outcome and an honest reflection on what the candidate would change - Clear personal ownership of the decision rather than a team narrative ### Follow-up Questions - Which piece of evidence, had it come out the other way, would have changed your decision? - Someone senior still disagreed after you decided. What did you do, and what happened to that working relationship? - If you faced the same call on a product built on a large language model, where quality is hard to measure, how would you back it up?