0 day streak

BEHAVIORAL · SPEED AND DELIVERY

Tell me about a time you delivered under a tight deadline: sample answer

Whether you deliver on time by making smart choices: cutting scope deliberately, removing blockers early and telling people the truth about risk. Heroics like working every night score lower than a plan that made the deadline safe.

Also asked as

  • Tell me about a time you missed a deadline.
  • Tell me about a decision you made without all the data you wanted.
  • Tell me about a time you delivered under a very tight deadline.
  • Describe a time you had to cut scope to ship. How did you choose?
  • Describe a time you had to choose between quality and speed.

The short version: Show a hard deadline met by cutting scope wisely, not by heroics alone.

Sample STAR answer

An invented example from typical software engineering work, about 260 words, around two minutes spoken. Use the structure, not the story: yours should be real.

Situation Our team had to support a new invoice format required by a regulation in one of our markets. The date was fixed by law, and we found out about the full requirements with five weeks left, when the original estimate was ten weeks.

Task I was the lead engineer for the change. I had to get something compliant out by the date without breaking invoicing for the rest of our customers.

Action In the first two days I went through the regulation with our compliance colleague and split the work into "required by the date" and "nice to have". Only about half was truly required: the new fields, the digital signature and storing invoices for the legal period. Automatic corrections, a nicer PDF layout and support for older invoice types could wait. I wrote this down and got product and compliance to sign off on it. The riskiest part was the signature service, which depended on an outside provider, so we built and tested that first, in week one, instead of last. I put the new format behind a flag for that market only, so other customers were untouched. I gave a short written status every Friday with what was done, what was at risk and what I needed.

Result We went live four days before the deadline. The later parts shipped over the next five weeks with no rush. Nobody on the team worked weekends, and there were no invoicing incidents during the switch. Agreeing the cut list in writing in week one was what made it possible.

Weak answer vs strong answer

Weak

"We had a really tight deadline, so the whole team worked late nights and weekends for a month. It was hard, but we pushed through and delivered on time."

Why it scores low: It shows effort, not judgment. There is no prioritisation, no handling of risk, and working everyone late is a warning sign about planning. It also gives no idea of your own role.

Strong

A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Show a hard deadline met by cutting scope wisely, not by heroics alone.

How the story changes with level

SDE 1

At SDE 1, a tight deadline on your own feature, where you asked early which parts mattered most and raised a risk in time, is a good answer.

Senior and staff

At senior or staff level, show that you planned across several engineers or teams, negotiated scope with stakeholders, and set up a delivery that did not depend on overtime.

SDE 1 interviews · Senior interviews · Staff interviews

Follow-up questions interviewers ask

  1. How did you decide what was required?Show you went to the source, the regulation, with an expert, not just opinions.
  2. What would you have done if the signature provider had been late?Describe the fallback you had prepared and when you would have raised it.
  3. How did you tell stakeholders about the cuts?In writing, early, with the reason and the date each cut item would come.
  4. Tell me about a deadline you missed.Have one ready; say when you raised the risk and what you changed after.

Amazon Leadership Principles that test this

Bias for Action · Tell me about a time you made a quick decision without all the information.

Move quickly, because speed matters and many decisions can be undone; take sensible risks rather than waiting for perfect information.

Situation I was on call when error rates on our search service started climbing on a Saturday evening. A deployment had gone out two hours earlier, but its changes looked unrelated to the errors.

Task I could spend time proving the deployment was the cause, or act. Errors were affecting about eight percent of searches and rising.

Action I asked myself whether a rollback could be undone easily, and it could; rolling back cost us nothing but a delayed feature. So I rolled back immediately and posted in the incident channel why, while I kept investigating. Errors dropped to normal within five minutes, which confirmed the link. I then found the cause: the deployment had updated a shared library that changed a default timeout. I wrote it up the next morning, and the feature was re-released on Monday with the timeout set explicitly.

Result Total impact was about 25 minutes instead of what could have been hours. I proposed and we adopted a simple rule: if errors rise within a few hours of a deploy, roll back first and investigate second.

Tip: Stress that the action was reversible, and that you explained it and followed up properly.

Deliver Results · Tell me about a time you delivered an important result despite a setback.

Focus on the inputs that matter most and deliver them with the right quality and on time; when setbacks hit, rise to the challenge and do not settle.

Situation Our team had to move 40 million customer records from an old database to a new one before the old database's support contract ended, eight weeks away.

Task I led the migration. Three weeks in, our test run showed the copy would take eleven days, far longer than the weekend window we had planned.

Action Instead of asking for a later date, I changed the approach. I split the migration into a background copy that could run for days while the old database stayed live, and a short final step that only copied changes made since. I wrote a checker that compared record counts and samples between the databases each night, so we would know the copy was correct before switching. I shared a revised plan with my manager the same week, including the one risk I could not remove: a slower final step if traffic was unusually high. We ran two full rehearsals on staging.

Result We switched over in a 40-minute window, two weeks before the deadline, with no data errors found by the checker or by customers. The two-step method became our standard for large data moves.

Tip: Show the setback, how you changed the plan instead of the date, and the result delivered on time.

All 16 Amazon Leadership Principles with sample answers

Companies that test this

Prepare your own

Write your story in the story bank and tag it "Speed and delivery"; it will show up against every company value that tests this theme.

Related: Failure and learning · Ambiguity and judgment · High standards

All behavioral themes · How the behavioral round is scored