Describe a project where requirements changed significantly mid-way. How did you adapt?

behavioral · Junior level · general

What the interviewer is really asking

Evaluate flexibility, re-prioritization skills, and communication under shifting requirements.

What to say

• Set the stage: what was the original plan and what changed, and when?
• Walk through how you assessed the impact and re-planned your work.
• Note what you communicated to stakeholders and what the final result was.

What to avoid

• Don't express frustration with the change as the central theme.
• Avoid a story where you ignored the new requirements and shipped the original plan.
• Don't skip the re-planning step — that's what the interviewer wants to see.

Example answers

Strong: Three weeks into a feature build, the product owner pivoted the core flow after user testing. I listed every completed task, marked what could be reused, and estimated re-work for what couldn't. I flagged to my lead that we'd need to cut two secondary features to hit the original deadline. We agreed, shipped the revised core on time, and deferred the cuts to the next sprint.

Weak: Requirements changed partway through, so I just kept coding what I'd originally planned and hoped the scope would settle down.