Missing a Deadline
Talk about a slipped deadline with honesty: when you saw the risk, who you told, what you traded, and what you changed so it happens less.
Overview
Every engineer misses a date sooner or later. Estimates are guesses, dependencies slip, and hidden work shows up late. So the interviewer is not asking whether you have ever been late. They want to know how you behave when a plan starts to fail.
The interviewer listens for three things. First, how early you saw the risk and said so. A delay announced two weeks ahead is a planning problem; a delay announced on the due date is a trust problem. Second, whether you came with options (cut scope, add help, move the date) instead of only bad news. Third, whether you fixed the cause, so your next estimate is better.
- Timing — raised the risk as soon as it was clear — told people on the due date
- Ownership — 'my estimate missed the migration work' — blames another team or bad luck
- Options — brought two or three choices with trade-offs — brought only the problem
- Quality — cut scope, kept the bar — shipped on time with serious known bugs, quietly
- Learning — changed how they estimate or track risk — 'I would work harder'
What you will be able to do
- Pick a missed-deadline story that shows judgment, not just effort.
- Explain when you saw the risk, who you told, and what options you offered.
- Describe a concrete change you made so the same miss is less likely.
- Answer follow-ups on estimation and scope trade-offs.
Interview questions
- Tell me about a time you missed a deadline.
- How do you tell stakeholders a deadline is at risk?
- What do you do to avoid missing deadlines?
- Would you rather ship late or ship with lower quality?
Sign up free to read the full topic
More Behavioral topics
Start free on Cariara · Coding problems · System design studio