Anthropic's IPO has to land before the midterms. The deadline question, and what makes one real.
On September 5, 2026, CNBC reported — citing Reuters — that Anthropic is expected to begin marketing its IPO "in mid-October at the earliest and complete the listing days before the U.S. midterm elections in November." The prospectus, once expected within the week, is now not expected until late September. CNBC notes what investors have said this could be: "a $2 trillion listing, one of the largest IPOs ever attempted."
Notice the shape of that schedule. Almost every date in it is soft — the prospectus slipped a fortnight, and CNBC is careful to say plans are "subject to change," and that companies adjust IPO timing routinely. One date is not soft. The midterms happen when they happen. Everything else in the plan is being arranged around the one thing that cannot be moved.
That distinction — between the dates that can flex and the one that cannot — is the whole substance of a question interviewers ask constantly and candidates almost always answer poorly.
Why they ask it
Because "tight deadline" is where you find out whether someone understands what a deadline is.
Most deadlines in most companies are estimates wearing a costume. They were set by someone who wanted the thing sooner, and they will move if the work demands it. A few are genuinely immovable: a regulatory filing, a contractual date, a conference keynote, an election. The skill being tested is not endurance. It is whether you can tell the two apart, and whether you behave differently depending on the answer.
The candidate who treats every date as immovable burns their team out on deadlines that would have moved for the asking. The candidate who treats every date as soft eventually misses the one that wasn't. Interviewers have been on teams run by both, and they are listening for which one you are.
The trap
The heroic all-nighter is the classic wrong answer. "We worked three weekends straight and shipped on time." It invites exactly one follow-up — why was that necessary? — and the honest answers are all unflattering: the estimate was wrong, the scope was never cut, nobody escalated. Heroism is usually the visible symptom of a planning failure upstream, and at senior levels you are being evaluated on the upstream.
The subtler trap is the answer with no casualties. If you hit an aggressive date and nothing gave — not scope, not quality, not another project, not a person's weekend — then either the deadline was never tight, or something gave and you have not noticed what. Interviewers probe for the casualty because its absence means the story has not been examined.
Applying STAR-T
Situation. Establish immovability first, in one sentence, with the reason attached. "The date was set by the conference, not by us." Without that, the interviewer spends your entire answer wondering why you did not just move it — and any answer that leaves that question open cannot be graded.
Task. Name what you were accountable for delivering by that date, and how big the gap was when you first measured it honestly. "Six weeks of work, four weeks of calendar" is a story. "It was tight" is not.
Action. The move that separates senior from mid-level is that you closed the gap on purpose and early, rather than absorbing it with hours. Cut scope to a defensible core and say who agreed to the cut. Parallelize what could be parallelized and name what that cost elsewhere. Escalate before the slip, not during it. And state your own tripwire: "I told my director in week one that if the vendor integration wasn't done by the 14th, we'd ship without it — and we agreed that then, not later." Renegotiating a deadline in week one is competence. Announcing a slip in the final week is a different story, and interviewers grade it differently.
Result. Say what shipped, and say what did not. "We hit the keynote with the core flow. Bulk import slipped to November, which we had agreed in week one and told customers about in week two."
Trade-off. Name the casualty plainly. "We shipped without bulk import, and the two customers who needed it got a manual workaround from our support team for six weeks." That is what a real tight deadline costs, and naming it is the difference between a candidate who managed a constraint and one who survived it.
The follow-up that breaks weak answers
Expect "what would you have done with two more weeks?" It is diagnostic, and most candidates answer it wrong by saying they would have finished everything — which reveals that the scope cut was never a judgment, just a casualty of the clock.
The answer that lands is specific about what it would not have changed: "I'd have done the same cut. Bulk import was the right thing to drop even with the extra time, because the keynote demo never touched it. What I'd have bought is the migration tests, which we ran manually and which cost us a weekend." Now the interviewer can see a person who made choices under pressure, not one who was merely shaped by it.
Score your answer against the director’s bar
Q: Tell me about a time when you had to meet a tight deadline.
Bank a deadline story where you can name the date's source and what you dropped, and rehearse it in L8 Loop until the trade-off arrives before the interviewer asks. Try it free →