Managing Delivery Dates When a Team Commitment Is at Risk

The interviewer asks how you, as an engineering manager, handle deadlines and due dates: how dates for your team's work get set, how you track them, and what you do when one is in danger. Then walk through a specific time a date your team had committed to was at risk: how you found out, what you did, and how it ended. ```hint Bring options, not only news Think about how early you raised the risk, and what choices you put in front of the people who owned the date. ``` ### Clarifying Questions - Are you more interested in externally fixed deadlines, internal targets, or both? - Should the example be one where the date was ultimately met, or is a well-managed slip acceptable? ### What a Strong Answer Covers - A repeatable way of setting dates: estimates as ranges, scope tiers and visible buffer - Tracking based on milestones and leading indicators of risk - Early escalation with concrete options across scope, staffing, competing work and the date itself - Clear stakeholder communication and clarity about who owns the decision - Protection of quality and of the team's sustainability, with no silent corner-cutting - A specific example with an outcome and a lasting change to how the team plans ### Follow-up Questions - A director commits your team to a date without consulting you. What do you do? - How do you handle an engineer who repeatedly misses their own estimates? - When is letting a deadline slip the right call?