## Question This team sometimes works at high intensity. How do you maintain delivery quality, decide when extra effort is justified, and raise concerns when the pace is not sustainable? ### Constraints & Assumptions - Treat a real incident or fixed deadline differently from chronic understaffing. - Explain how you protect correctness and recovery even when time is short. - Address team health and prioritization, not only personal stamina. - Do not promise unlimited availability. ### Clarifying Questions to Ask - Does high intensity here mean incident response, launch deadlines, or a continuous workload? - What on-call and escalation support does the team have? - How are scope and deadlines renegotiated when risk changes? ```hint Separate a sprint from a system A temporary surge needs an exit condition and recovery plan; a recurring surge needs capacity, scope, or process changes. ``` ### What a Strong Answer Covers - Calm triage based on customer impact, reversibility, and deadlines. - Explicit cuts to scope rather than hidden cuts to testing or safety. - Clear ownership, escalation, handoffs, and recovery after a surge. - Early evidence-based communication when capacity is insufficient. - Healthy boundaries and a willingness to examine recurring causes. ### Follow-up Questions 1. Tell me about a time you pushed back on an unrealistic deadline. 2. Which engineering safeguards remain mandatory during an emergency? 3. How do you recognize that a temporary surge has become chronic?