How do you handle a change request late in a project?
Assesses fundamental understanding of Business Analysis conventions, runtime behavior, and memory/performance considerations.
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Late change requests are normal. Uncontrolled late change is the problem.
First I understand the request and why it is late. There may be a genuine regulatory deadline or a real missed requirement, in which case we need to act. I assess the impact on scope, schedule, cost, quality and risk, and I make that impact explicit rather than absorbing it silently.
Then I present options: swap it for something of lower priority within the same timeline, extend the timeline, add resource, or park it for the next release. This turns the conversation from yes or no into a trade off.
The decision goes through the agreed change process with the right authority, and I document it, including who approved and why.
If late changes recur, I look at the root cause, perhaps insufficient elicitation or unclear scope, and improve the front end rather than blaming the requester.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.