Tell me about a time you were given a deadline you believed was unrealistic.
answer
- name the date and who set it
- the estimate that exposed the gap
- raised it early, not at the end
- options offered: scope, time, people
- what I committed to, and hit
basics
~20 sTests whether you surface schedule risk early and negotiate with options instead of nodding and missing. Answer with the estimate that exposed the gap, a scope-time-people counter-proposal, and the date you actually committed to and hit.
how to answer
6 beats- the date, and where it came fromTwo or three sentences: what was being asked, who set the date, and why it mattered to them. Keep setup and task to about a fifth of your airtime — the interviewer does not need the org chart.
- the estimate that made the gap concreteState your own number against the ask, and say how you got it. A spike, a benchmark, a shadow run or a dependency lead time all work; a gut feeling does not. This is the sentence that turns an opinion into an argument.
- when and how I raised itGive the timing explicitly — day two, the same week — because early is the signal. Say who you took it to and how you opened, ideally with the risk first rather than a long preamble.
- the options I put on the tableThis beat plus the previous two carry roughly sixty percent of the answer. Offer at least two named alternatives across scope, time and staffing, price them honestly, and say which one you recommended.
- what we committed to and what shippedClose the loop with a date and an outcome, including the parts that landed later. Result and reflection together are about a quarter of the answer; a story with no ending reads as unfinished work.
- what I do earlier nowOne or two sentences on the habit that changed — estimating before agreeing, checking dependency lead times, publishing a confidence signal. Avoid working-harder as the lesson.
your answer
5 story prompts- Pick a date you were handed and privately doubted, ideally within the last two years.
- Find the moment you had a number that made the gap arguable rather than a feeling.
- Write down the exact options you offered and which one was chosen.
- Note what actually shipped and when, even if part of it landed late.
- This can be your prioritisation story re-angled onto the date instead of the scope.
draft and rehearse your own answer in a learn session
go deeper
This probes judgement under commitment pressure and honesty about capacity. Interviewers want to know whether you convert a schedule disagreement into options a decision-maker can act on, or whether you capitulate and miss quietly, or refuse with no alternative. A strong answer shows an early signal, a defensible estimate, and a commitment that actually held.
On an enterprise data platform team, I owned adding a new order-events source to our ingestion pipeline. My lead told me the finance group wanted it feeding the daily revenue dashboard by the end of the reporting cycle, which was nine working days out. I spent the first day and a half estimating properly instead of starting to code, and two things blew the number up. The source emitted events out of order, and about 4.3 percent of them arrived after our daily cutoff, so a naive load would have made the dashboard quietly wrong. Handling that late-arriving share needed a reprocessing window we did not have. My honest estimate was fifteen to seventeen days. I took it to my lead on day two with a written breakdown and three choices: load without late-event handling and label the dashboard provisional, ship on the date for only the two entities finance actually reviewed daily and follow with the rest, or keep full scope and move into the next cycle. I said plainly that I could commit to the second, not to the first date at full scope. We went with the second. I delivered the two entities on day eight, with a reconciliation check that alerted when the late-arriving share went above two percent, and the remaining sources landed eleven days later. Since then I estimate before I say yes to a date, even when the work looks obvious.
The signal here is the day-two escalation: the estimate came before the yes, and the three choices were concrete enough for someone else to pick between. Stopping at telling the lead it felt tight, with no number and no alternative date, would downlevel this immediately.
I was the engineer on point for moving one business unit's reporting off a nightly batch job and onto our streaming warehouse tables. The date came from a director who had already told his analysts the old reports would disappear at the end of the quarter, two sprints away. I did not argue it in the meeting. I spent two days building a throwaway shadow run against real traffic, and it gave me the number I needed: under the streaming model 6.1 percent of events landed after the watermark, against 0.4 percent in the batch job. Matching the old figures meant a late-arrival buffer plus a correction job, and nobody had scoped either. Then I went back with the evidence and a written option set. One: hold the date, cut over the seven reports whose numbers tolerate a same-day correction, and keep the batch job alive for the three financial ones. Two: cut everything over one sprint later. I recommended the first and named its cost out loud, which was running both systems for about five weeks with me owning reconciliation. He took the first. The seven landed on the quarter date, the three financial reports followed six weeks after, and once the buffer was tuned the late-arriving share settled at 0.9 percent. The habit I kept is measuring before negotiating. Arguing about whether a date is realistic goes nowhere; a two-day shadow run ends it.
The shadow run is the beat to copy — two days of evidence bought a decision that weeks of debate would not — plus naming the cost of the recommended option instead of selling it. Dropping the recommendation and presenting only a menu would downlevel this to a status report.
Own-task scope is expected and fine. Show that you estimated before you agreed, raised the gap within days rather than at the end, and named the smaller thing you could genuinely commit to.
Work at feature or peer-coordinated scope. The move that reads as mid-level is gathering evidence that makes the gap arguable, then handing over a written option set someone else can choose from rather than a complaint.
You are negotiating on behalf of people whose plans depend on yours, so name the cost of each option out loud and say who absorbs it. Close with the prevention: an earlier signal, a changed estimation habit, not extra hours.
Talk about how dates get set in the first place, not only this one. The strong answer describes a mechanism — estimate review, confidence reporting, a scope buffer convention — that stopped the organisation committing to fiction repeatedly.
saying these in an interview costs you the question
- Accepting the date silently, then missing it with no warning
- Refusing the date without offering a single alternative
- Blaming the manager or the stakeholder for setting an impossible date
- Pushing back on a feeling, with no estimate or evidence behind it
- Raising the risk only once the deadline had already passed
- Never saying what actually shipped, or when
- What if your manager had told you the date was not negotiable?Do not treat this as a trap. Say what you would trade instead: scope first, quality bar and staffing second, and be explicit that a fixed date with fixed scope means you are choosing which risk to carry. Name the risk you would accept and the one you would refuse, and say how you would make that visible in writing.
- How early did you know, and could you have known sooner?Interviewers are testing self-awareness more than the answer. Give the actual gap in days between the first bad signal and the moment you raised it, and be honest if you sat on it. Then say what would have surfaced it earlier — a spike, a benchmark, a dependency check before agreeing.
- Who decided what got cut, and how did you influence that?Show that you framed the choice rather than made it alone. Explain how you presented the options, what you recommended and why, and where the decision rights sat. Claiming you unilaterally cut a stakeholder's scope reads as poor judgement; presenting no recommendation at all reads as passive.
## The prompt has three common shapes and one answer You will hear it as: - a **story request** (a time you were given an unrealistic deadline), - a **hypothetical** (what do you do when you are handed a date you cannot meet), - or folded into a **work-style question** (how do you handle being over-committed). Prepare one episode and adapt the framing: for the hypothetical, tell the story anyway and generalise from it in the last sentence. That reads far better than an abstract process description, because the interviewer is trying to find out whether you have actually done this, not whether you can describe it. ## What is really being probed Two things sit under this question. 1. **The first** is whether you tell the truth about capacity early, when it is still cheap, or late, when it is only expensive. 2. **The second** is whether you argue like an engineer or like a complainant — with an estimate and a set of options, or with an assertion that the date is crazy. Almost every weak answer fails on one of those two axes, and they are independent: plenty of candidates raise the concern promptly and still bring nothing anyone can decide on. ## The triangle is the content, not the vocabulary Saying the words scope, time and quality proves nothing. What proves something is offering **concrete instances** of each: - which two of the seven deliverables ship on the date, - how much extra time buys the whole thing, - what a second person could take off the critical path and what onboarding them costs, - and which quality property you would deliberately relax — manual verification instead of automated, a provisional label on a number, a rollback plan instead of a migration. Give at least two named options and say which one you recommend. A **recommendation** is what separates a partner from a ticket-taker. ## Evidence beats conviction The single strongest device in this answer is a small piece of measurement that ended the argument: - a timed spike, - a shadow run against real traffic, - a benchmark on the slowest case, - a dependency whose lead time you looked up rather than guessed. Two days spent producing a number is almost always cheaper than two weeks spent debating a feeling, and describing that trade is itself a signal. ## Commit to something Answers that end with pushback and no commitment leave the interviewer thinking you avoid dates rather than negotiate them. The ending you want is: 1. here is what I said I would deliver, 2. here is what I delivered, 3. here is the gap if there was one. Hitting a smaller commitment beats missing a larger one, and saying so out loud is the point of the story. ## Weak versus strong, compressed - **Weak:** the date was set without asking us, I said it was not possible, we ended up late. There is no estimate, no option, no result and an implied grievance. - **Strong:** I estimated it at roughly twice the ask within two days, took three options to my lead the same week, we shipped the reduced scope on the original date, and the rest followed in the next cycle. Same situation, same constraints; one shows judgement and one shows resentment. ## How the bar moves - **Early-career**, the interviewer wants to see you raise your hand at all — many people do not. - **Mid-level**, they want the option set and the evidence. - **Senior**, they want you to have priced the options for other teams too, and to have changed something so the next commitment is better calibrated. - **Principal**, the episode is almost incidental; what matters is the system you built for how commitments get made.