Tell me about a time you had far more work than you could deliver. How did you handle it?

Overload questions test triage, not stamina

The trap sits in the phrasing. "How did you handle it" sounds like an invitation to describe your work ethic, and a large share of candidates answer by describing effort: long hours, weekends, a very good task list, staying late until it was all done. That answer is scored badly by most interviewers, and for a reason that is worth internalising. If you delivered everything, either the demands were not genuinely in conflict or you absorbed the conflict privately, and both readings suggest that the next time capacity runs out, nobody upstream will find out until it is too late to reorder anything.

What the question is really probing is whether you can make a resource decision and put it in front of other people. That has three visible parts: the criterion you chose by, what you stopped doing, and who you told. An answer missing the middle part is an answer about being busy.

Say what the demands actually were

Start by making the conflict real. Three or four named claims on the same period, each with an owner and a consequence: a regulatory date that could not move, a customer commitment made by sales, a migration whose window was shared with another team, an on-call week, and a colleague's handover that had landed on you. The interviewer needs to believe that no ordering of effort delivered all of it, because otherwise the rest of your answer is a story about time management.

Then name the criterion. This is the sentence that separates good answers from average ones, and it should be explicit rather than implied. Irreversibility is one — do the thing that cannot be done later. Blast radius is another: which failure hurts customers rather than internal convenience. External commitment against internal preference is a third. Unblocking other people's work is a fourth, and often the most senior-sounding, because it treats your own throughput as less important than the team's. Any of these is fine. Having no criterion, and prioritising by whoever asked most recently or most loudly, is the thing being screened out.

The sentence candidates will not say

The hard move in an overload is telling someone their work is not happening. Most candidates in interviews describe having "managed expectations", which is a phrase that means nothing and usually conceals a message that was never clearly sent.

Vague, and probably never said	A message someone can plan around
"I managed stakeholder expectations."	"I told the product lead that the reporting change would not land this sprint, and asked her to decide between it and the migration."
"I flagged that things were tight."	"I sent the three items with dates and said I could commit to two, and asked which one to drop."
"I pushed back where I could."	"I said no to the dashboard request and told him I would revisit it after the audit date."
"I kept everyone informed."	"I told the other team on the Monday that their dependency would arrive a week late, so they could reorder their own work."

The right-hand column shares two features: a decision is stated as a decision, and it is handed to whoever owns the trade-off. That second part matters. Deciding alone which of your stakeholders loses is what junior candidates do; escalating the choice with a recommendation is what senior ones do, and it is also what protects you if the choice turns out to be wrong.

Timing is the part interviewers weigh most heavily. Telling someone on the Monday that a Friday date will slip is a functioning engineer. Telling them on the Friday is the failure mode, and it is the one nobody volunteers. If your story involves late notice, say so and say why, because the alternative is an answer where every conversation happened conveniently early and the interviewer has heard that version too many times to believe it.

Where the story quietly loses its credit

Two things weaken otherwise sound answers. The first is a resolution with no loser. If everything shipped, on time, and nobody was disappointed, the interviewer concludes either that the overload was ordinary or that you are smoothing the account. Name what was cut, deferred, delivered thinner than intended, or done manually for a month because automating it could wait. A specific casualty makes the whole story believable.

The second is asking for nothing. Candidates often narrate an overload in which they never requested more time, more people, a reduction in scope or the temporary suspension of something else. Interviewers read that as either poor judgement or a reluctance to be seen struggling, and neither is a good look at senior level. Say what you asked for and what the answer was, including when the answer was no. An answer of "no" that you then worked within is a stronger story than never having asked.

What the interviewer does with your answer

Behind this question is usually a real situation in the team you are joining: too much work, a date somebody has committed to, and a manager who wants to know whether you will tell them the truth about capacity in week three or in month three. Everything about how you tell the story is read through that lens, which is why the concrete, slightly uncomfortable version wins. A candidate who says they told a stakeholder something the stakeholder did not want to hear, on a specific day, and then describes the consequence, is answering the question the manager is actually asking.

Keep the personal cost brief if you mention it. Working two heavy weeks to protect a genuine deadline is normal and worth one sentence. A story in which the resolution is entirely your own exhaustion tells the interviewer what will happen the next time the team is short-handed, and it is not a reassuring forecast.

Overload is not a test of how much you can carry. It is a test of whether the person who owns the trade-off hears about it from you, early enough to choose.