Katkat
Back

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

MicrosoftSoftware Engineer · Onsite
EasySoftware EngineerOnsiteBehavioral & Leadership

Last updated

A behavioral question about realizing that a task you own will miss its deadline and what you do next, followed by a probe on why adding more people close to delivery tends to backfire. It tests early escalation, framing options and trade-offs, ownership, and an understanding of ramp-up and coordination costs.

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.

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?

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

Part 3 — A task you could not complete

Describe a task you were given and could not complete. This time the work did not simply ship late: it never got delivered as assigned, because it was left unfinished, cut back, handed to someone else, or cancelled. What happened, and how did you handle it?

What This Part Should Cover

  • A genuine shortfall with clear stakes, and the signal that showed the task would not be finished
  • Who you told, how early, and the options you put forward: cut the scope, hand it off, pause it or stop it
  • Your own share of the cause, stated plainly, alongside the factors you did not control
  • What you salvaged, and the state you left the work in for whoever picked it up
  • A specific lesson and evidence that it changed how you take on or track work

Hints

Hint 1

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.

Hint 2

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.

Hint 3

Choose a genuine miss: Pick a case where the assigned work really did not get done, not one that landed a little late and not a success dressed up as a failure. Be ready to name the moment you realized it would not land.

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?