## Prompt Tell me about a time you had to deliver an important engineering result under a tight deadline. Explain what made the deadline difficult, how you separated essential scope from optional scope, how you surfaced risk, and what actually shipped. ### Constraints & Assumptions - Use one real example in which your decisions materially affected the result. - State the deadline, the people or systems affected, and your own responsibility without revealing confidential details. - Do not present overtime as the primary strategy; explain prioritization, coordination, and quality controls. - Include the outcome and one lesson that changed how you plan later work. ### Clarifying Questions to Ask - Should the example emphasize an individual contribution or coordination across a team? - Is a partial delivery acceptable if the candidate negotiated the scope explicitly? - Which dimensions matter most: customer impact, operational safety, or speed? ```hint Make the trade-off visible Name one item you protected, one item you deferred, and the evidence used to make that choice. ``` ### What a Strong Answer Covers - A concise situation and an unambiguous deadline with real consequences. - The candidate's ownership rather than a vague account of what the team did. - Early identification of the critical path, dependencies, and failure risks. - Explicit scope negotiation and communication with affected stakeholders. - Proportionate tests, rollout controls, and monitoring despite the time pressure. - A measurable result plus a candid discussion of what was deferred or imperfect. ### Follow-up Questions 1. What did you refuse to cut, and why? 2. When did you first communicate that the original plan was at risk? 3. What would you do if the stakeholder rejected the smaller scope? 4. How did you prevent the compressed schedule from creating hidden operational debt?