OfferDrill.

Interview questions

The hard ones

Tell me about a time you missed a deadline.

This page shows you how to talk about a real missed deadline without sounding careless or defensive. You'll get the structure, the traps, three sample answers for different situations, and the follow-ups that come next.

Why they ask it

They already know you've missed a deadline. Everyone has. Nobody asks this question hoping you'll say it never happened — they ask it to see what you do when something goes wrong.

Three things are being measured. Whether you noticed the deadline was slipping before it hit, or only after. Whether you told someone, and how early. And whether you changed anything afterward, or just felt bad for a week and moved on.

There's a fourth thing, quieter. They want to know if you're the kind of person who can say "that one was on me" in a normal voice. Because the person who can't do it in an interview usually can't do it on a project either, and that's expensive for the people around them.

What not to say

"I've never missed a deadline."

It reads as either untrue or as a sign you've never owned anything with real risk in it. Either way the interviewer stops learning about you and starts wondering what else you'd smooth over. If you genuinely can't think of one, talk about a deadline that nearly slipped and what you did to save it — but say that's what you're doing.

Picking a miss where someone else caused everything.

The vendor was late, the client changed the spec, the other team never delivered. All of that can be true and still lose you the point, because the question was about you. You need at least one sentence that starts with "what I'd do differently." Without it, you sound like someone who's never the problem — and nobody believes that person.

Choosing something so small it isn't a real answer.

"I turned in a status report a day late." The interviewer hears you dodging. They'll either ask again, which wastes your goodwill, or they'll assume the real story is worse than it is. Pick something with actual stakes that you can discuss calmly.

Over-apologizing, or telling the story like a confession.

Long guilt, self-criticism piled on self-criticism, a voice that drops at the end. It makes the miss sound bigger than it was and makes the interviewer uncomfortable. Own it in one clear sentence and spend the rest of your time on what you did about it.

How to build a strong answer

  1. Pick a miss that's over and has a visible repair.
    The best story is one where the deadline slipped, you flagged it, something got fixed, and the work eventually landed. Avoid anything still unresolved, anything involving a firing or a lawsuit, and anything where you'd have to trash a former manager to explain it. If the only strong example is your current job, that's fine — just don't name clients or share confidential numbers.
  2. Set it up in two sentences, then say the miss plainly.
    What the work was, what the deadline was, why it mattered. Then: "We delivered [the actual amount of time] late." Say the date or the number. Don't drift into background. If an outside factor was genuinely part of it, give it one clause — "the data came to us two weeks later than planned" — and keep moving. One clause reads as context. Three reads as an excuse.
  3. Say what you should have caught, in your own words.
    This is the sentence the whole answer rests on. Something like: "I saw the schedule getting tight about ten days out and I told myself I could make it up. I should have raised it right then." Be specific about the moment you had information and didn't act on it. Vague ownership — "I could have communicated better" — doesn't count because anyone can say it about anything.
  4. End with the escalation and the change you kept.
    Two parts. What you did once you knew — who you told, what you offered, whether you gave them a revised date they could rely on. Then what's different now. A habit, a check, a threshold. "Now if anything slips more than two days, I flag it that week instead of waiting to see." Then stop. Don't restate the lesson twice.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career, a project that ran late because you underestimated it.

I owned a [system migration] with a hard date tied to [a contract renewal]. I scoped it at eight weeks. Around week five I could see we were behind — the testing was turning up more than I'd planned for. I told myself we'd catch up with a hard push. We didn't. We delivered about three weeks late. The real mistake wasn't the estimate, it was week five. I had the information and I sat on it because I wanted to fix it before I reported it. Once I did raise it, my director and I went to [the stakeholder] together with a new date and a shorter scope for phase one, and we hit that. What changed is that I don't wait for certainty anymore. If my own timeline slips past about ten percent, that goes in the status update that week, with what I plan to do about it. It's an uncomfortable email to send once instead of a bad conversation later.

It names the exact moment of failure — week five, not the estimate — which is more honest and more useful than blaming the scope. The repair is concrete and the new habit has a trigger you can actually describe.

Early career, where the miss came from not asking for help.

During my internship at [company] I was given [an analysis] due on a Friday. I'd never done that kind of work start to finish. By Wednesday I was stuck on [the data step] and I kept thinking I'd figure it out that night. I turned it in the following Monday. What I'd do differently is obvious to me now — I had a manager sitting twelve feet away who would have unstuck me in fifteen minutes. I didn't ask because I thought asking would look like I couldn't handle it. Being late looked a lot worse. Since then I use a rule: if I'm stuck on the same thing for more than half a day, I go ask, and I bring what I've already tried so the conversation is short. I used it three times on [the next project] and none of that work was late.

Being new isn't an excuse here, it's the actual cause, and naming the real reason — not wanting to look incapable — is more credible than a process explanation. The fix is small, specific, and repeatable.

The deadline was mostly missed by others, but you still owned your part.

I was coordinating [a launch] that depended on three teams. Two hit their dates. The third was two weeks behind and I didn't find that out until they were already late, because I was reading their status reports instead of talking to anyone. We shipped about two weeks after the announced date. I can point at the other team, but the coordination was my job, and I'd built a process that only told me things were fine. Once I knew, I called the launch date myself rather than waiting for it to slip publicly, and we moved the external announcement before customers saw anything. Now on cross-team work I set up a short standing check-in with each dependency owner, fifteen minutes, and I ask what would make them late rather than whether they're on track. People tell you very different things depending on which one you ask.

It gives the outside factor one clause and then turns straight back to what the speaker controlled. The closing detail about how you phrase the question shows real learning, not a slogan.

What comes next

Answer this one well and the interviewer usually goes here:

  • What did your manager say when you told them?
  • Was there a point earlier where you could have seen it coming?
  • How did the client or stakeholder react?
  • Have you missed a deadline since then?
  • How do you decide when something is worth escalating versus handling yourself?
  • How do you estimate timelines now?
  • Tell me about a deadline you were at risk of missing and saved.

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

Missing a deadline isn't the interesting part of the story — what you did in the days around it is, and if you can tell that part calmly, you've answered the question they were really asking.