Tell me about a time requirements changed significantly mid-project. How did you adapt?

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

I was six weeks into an eight-week build of an internal reporting dashboard when leadership shifted the priority: instead of a historical reporting tool, they needed live operational metrics for an upcoming audit in five weeks. Roughly half of what I had built no longer fit the goal.

As the lead engineer, I first resisted the urge to defend the old plan. I scheduled one working session with the stakeholders to pin down what the audit actually required, and it turned out only three of the nine planned views needed real-time data. That reframing cut the new scope nearly in half.

I then audited the existing code and found the data ingestion layer was reusable as-is, which saved about two weeks. I rewrote the timeline with a checkpoint every Friday, flagged the two features we would drop, and got written sign-off so the scope would not drift again.

We delivered the real-time dashboard three days before the audit, which passed without findings. The dropped features shipped the following quarter. Afterward I instituted a lightweight requirements freeze at the midpoint of every project I lead — changes after that point need an explicit trade-off conversation. It has made mid-project pivots far less chaotic since.

How to structure your own answer

• Situation: Describe the project, the original requirements, and what changed.
• Task: Clarify how far along you were and what your ownership covered.
• Action: Explain how you re-planned, protected prior work, and communicated the change.
• Result: Share the outcome and what you changed in your process afterward.

Common mistakes to avoid

• Framing the story as resentment toward whoever changed the requirements.
• Claiming you absorbed the change with zero cost — interviewers know that is not real.
• Skipping how you re-scoped and re-negotiated, which is where the judgment shows.
• Forgetting to mention what happened to the original work and timeline.

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:

• How did you push back on any part of the new requirements?
• What did you do to keep your team motivated after losing half their work?
• How do you design systems so mid-project changes hurt less?

Related behavioral questions

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