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 release, legal told us a new data-retention rule meant certain fields in our transaction logs had to be masked before launch. The payments service had been in testing for weeks, with half the team's work riding on it.
Delaying would have broken a contractual date with a platform partner. Absorbing the change blindly would have been reckless. So I spent the first hour scoping instead of coding.
That hour paid off. Only a couple of log pipelines carried the affected fields, and both flowed through a shared serializer I had written — one change point instead of scattered edits. I put the masking behind a feature flag, wrote tests asserting the masked output for every field on legal's list, and had a teammate review it the same afternoon.
We ran the full regression suite overnight, deployed dark, and flipped the flag after a clean monitoring window.
The release shipped on the original date, legal signed off, and the following month brought no log-related incidents. The change felt like a crisis for about an hour. Careful scoping turned it into a patch.
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
- Venting about the last-minute change wastes the question — it should land as a problem you solved.
- Don't jump straight to coding; skipping the risk assessment reads as reckless.
- Under time pressure, testing and safeguards are the whole point, and answers without them collapse.
- Who heard the plan, and when? Communication under the deadline is part of the story.
Follow-up questions to prepare for
Interviewers use follow-ups to verify your story is real. If you get 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 practice questions
Keep drilling with these, or browse the complete question bank.
Next up
Practice this question on the clock
Reading an answer and delivering one are different skills. Run a timed round and rate yourself.
Start a practice roundNext up
Interview coming up?
Have your post-interview follow-up email ready before you need it.
Follow-up email generator