## Question Tell me about a technical decision you made that later proved wrong. Why did it seem reasonable at the time, what evidence revealed the mistake, and how did you repair both the system and the decision process? ### Constraints & Assumptions - Choose a decision you influenced materially. - Avoid hindsight claims that the answer was obvious. - Explain impact without minimizing it or exaggerating blame. - Include remediation and a reusable process lesson. ### Clarifying Questions to Ask - Should I choose an architectural decision or a smaller implementation choice? - Is an example where the system still shipped acceptable? - Would you like more focus on recovery or on the original reasoning? ```hint Reconstruct the original evidence A credible answer shows what was known, which assumption failed, and which check would have surfaced it sooner. ``` ### What a Strong Answer Covers - The decision context, alternatives, and original rationale. - Personal accountability and the failed assumption. - Signals that exposed the problem. - A safe repair with stakeholder communication. - A proportional improvement to future decision making. ### Follow-up Questions 1. Who challenged the decision originally? 2. What did the mistake cost? 3. How do you avoid overcorrecting with excessive process?