situational Medium GeneralSoftware Engineer

One week into a four-week project, you discover your estimate was far too optimistic and the work will likely take seven. How would you handle it?

This is a hypothetical scenario question — the interviewer wants your decision framework, not a war story. Here is a model answer, the mistakes to avoid, and the follow-ups to expect.

A strong example answer

Speak up the day you discover it — an estimate correction is cheapest then. Before raising it, though, I would diagnose why the estimate missed. Once, I had assumed a legacy module had clean interfaces; a week in, it clearly needed serious refactoring before any new work could sit on top. That diagnosis matters, because it tells you whether the miss is a one-time surprise or a sign the rest of the plan is shaky too.

Then I would bring my manager options, not just bad news. On that project I offered three paths: move the date and keep the scope, hold the date and cut the weakest features, or borrow help and land in between — with a recommendation for the scope cut, since those features had the weakest usage projections. We shipped the reduced version slightly late, and usage data later confirmed the cut features were barely missed. Since then, I timebox a short technical spike before estimating anything on unfamiliar code. Bad estimates happen to everyone. Hiding them is the actual failure.

A framework for your own answer

  • Situation: Explain what you estimated and what you discovered in week one.
  • Task: State your obligation to correct the plan before others build on it.
  • Action: Show how you diagnosed the miss and brought options, not just bad news.
  • Result: Give the shipped outcome and the estimation habit you changed.

Common mistakes to avoid

  • Silence for weeks while you hope to catch up converts a small slip into a missed deadline.
  • Don't blame the legacy code or its previous owner — the estimate was yours.
  • Candidates often report the slip with no revised plan, which forces the manager to do their job.
  • Can weekends really close a three-week gap, or do they just burn you out before the same failure?

Follow-up questions to prepare for

Interviewers use follow-ups to verify your story is real. If you get this question in a real interview, expect probes like:

  • How has your estimation process changed since that experience?
  • What would you do if your manager refused all three options?
  • How do you estimate work in a codebase you have never touched?

Related practice questions

Keep drilling with these, or browse the complete question bank.

Next up

Practice this question on the clock

Reading an answer and delivering one are different skills. Run a timed round and rate yourself.

Start a practice round

Next up

Interview coming up?

Have your post-interview follow-up email ready before you need it.

Follow-up email generator