Tell me about a time requirements changed at the last minute before a delivery.

How to answer this behavioral interview question: a complete STAR example, the mistakes interviewers watch for, and the follow-ups you should expect.

A strong STAR example answer

Two days before a scheduled release of our payments service, legal flagged that a new data-retention rule applied to us, and we needed to mask certain fields in transaction logs before launch. The release had been in testing for two weeks and involved work from six engineers.

As the engineer owning the logging layer, I had to decide between delaying the release or absorbing the change safely. Delaying meant missing a contractual date with a platform partner. I spent the first hour scoping precisely: only two log pipelines carried the affected fields, and both flowed through a shared serializer I had written. That meant one change point instead of a dozen. I wrote the masking behind a feature flag, added tests asserting the masked output for every field on the legal list, and had a teammate review it that same afternoon. We ran the full regression suite overnight and deployed behind the flag, enabling it after 24 hours of clean monitoring.

The release shipped on the original date, legal signed off, and we had zero log-related incidents in the following month.

One careful hour up front made it a patch, not a crisis.

How to structure your own answer

• Situation: Set up what was about to ship when the change landed.
• Task: State your role and why the change could not simply be ignored.
• Action: Walk through how you scoped the safest, narrowest change.
• Result: Share the delivery outcome and your takeaway about change handling.

Common mistakes to avoid

• Treating the last-minute change as an annoyance to vent about rather than a problem you solved.
• Skipping the risk assessment — jumping straight to coding reads as reckless.
• Leaving out testing or safeguards, which are the whole point under time pressure.
• Failing to mention how you communicated the plan to stakeholders under the deadline.

Follow-up questions to prepare for

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

• When would you have chosen to delay the release instead?
• How do you keep last-minute requests from becoming a pattern?
• What would you have done if the change touched a dozen code paths?

Related behavioral questions

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