Handling a Deadline You Will Miss, and Why Adding Engineers Late Backfires

You own a task, and partway through you realize it cannot be delivered by its deadline. What do you do? This question came up in two behavioral rounds, and in one of them it was followed by a probe about one specific remedy: adding more people close to the delivery date. ### Clarifying Questions - Do you want a specific past example, or the approach I would take in general? - Is the deadline tied to an external commitment, such as a release or a team that depends on the work, or is it an internal target? - How large is the slip: a few days on a long project, or an at-risk date this week? ### Part 1 — A deadline you will miss You realize that a task you own will not be delivered by its deadline. Walk through what you do, from the moment you notice until the work ships. Anchor the answer in a real example if you have one. ```hint What the news should carry Think about what your manager or a dependent team needs from you to make a decision, beyond hearing that the work is late, and how long before the deadline they need it. ``` #### What This Part Should Cover - How and how early the risk was detected, with an honest estimate of the gap and its cause - Who was told, when, and with what options and costs - The decision taken, who made it, and how it was carried out - The outcome and what changed afterward in how you estimate or track work ### Part 2 — Adding people near delivery Close to the delivery date, adding more people to the work is one possible solution. What is wrong with that approach? Are there cases where it does help? ```hint Count the hidden costs Think about what newcomers need before they produce anything, who has to give it to them, and how the amount of coordination grows with team size. ``` #### What This Part Should Cover - The ramp-up cost and who on the team pays it - Coordination overhead as the team grows, and work that cannot be split - The conditions under which more people can still help, and better levers near a deadline ### What a Strong Answer Covers - Raising the risk early instead of surprising people on the due date - Concrete options with trade-offs, not only a request for more time - Ownership of the slip without blaming teammates or other teams - A mechanism-level explanation of why late staffing slows work down, with nuance about when it does not - A specific lesson that changed later planning ### Follow-up Questions - Your manager insists on both the full scope and the original date. What do you do next? - How do you tell a dependent team that your piece will be late when their own release relies on it? - What would you change in how you estimate and track work so that this risk shows up earlier?