## Question Choose two projects from your experience and compare them through their hardest technical decisions. For each project, explain the problem, your ownership, one trade-off, implementation detail, validation, and lesson. Then explain why the second project demonstrates a different kind of engineering judgment from the first. ### Constraints & Assumptions - Do not spend most of the answer on business impact while leaving technical difficulty vague. - Pick projects you can defend under detailed follow-up. - Distinguish direct contribution from leadership or team outcome. - Avoid repeating the same architecture decision twice. ### Clarifying Questions to Ask - Should the two examples contrast scale, reliability, product ambiguity, or leadership scope? - How much time should I spend on each before follow-up? - Would a diagram help? ```hint Give the projects different jobs One may show deep implementation reasoning while the other shows cross-system or organizational judgment. State the contrast explicitly. ``` ### What a Strong Answer Covers - Two compact system maps with exact ownership. - A different consequential decision and rejected alternative for each. - Technical detail, evidence, and failure modes. - Honest outcomes and lessons. - A comparison that shows range rather than two versions of the same story. ### Follow-up Questions 1. Which project had the greater technical risk? 2. Which decision depended most on other teams? 3. What would you redesign in each? 4. Which project best represents your current level and why?