Explain a Change in Project Requirements in an Inter­view

You may be asked about a time the requirements of a project changed. This guide helps you describe one real change in a clear order: the original requirement, the later request, what you clarified, what was approved, what you did and where things stand now. The focus is how the agreed work changed, rather than a general account of project success or failure. The project does not have to be finished. If your story is mostly about competing deadlines, see our guide to explaining competing deadlines.

Separate the request from the approved change

Do not assume that every suggestion became an approved change. A request from someone with authority may itself confirm a change; describe how it worked in your actual example. Say what was asked, who asked and what was approved, and by whom. The approved version can be narrower than the request, or only part of it may have been agreed. If you cannot say who approved it, say so.

Tell it in six steps

• Before: the original requirement, and what you had already done.
• Request: what was asked, as it was asked.
• Clarification: what you asked, and what you learned. If you did not ask, say so.
• Approved revision: what was agreed, and who agreed it.
• Your execution: what you did, separate from what others did. Our guide to explaining your contribution to a team achievement covers that distinction.
• Where things stand: what you know now, and what you do not know.

Keep blame out

Describe the request as it was made. Sample wording such as "The committee asked for descriptions" is fictional, and suits an answer only if that request really was made. If there were several changes, name them rather than guessing why people made them. A changed requirement alone does not establish that anyone made a mistake.

Keep names, internal documents and confidential project details out of your interview and practice notes. This is an account of your experience, not advice on technical, legal or safety-critical change procedures.

It does not need to be finished

A project that is still running, was handed on or ended before the change took effect can still make a clear answer. Say what you know. National Careers Service STAR guidance describes the result as what happened and what you learned, and advises preparing for follow-up questions. If you learned nothing new, say so. Do not invent a lesson or a tidy ending.

Prepare for follow-up questions

You may be asked how you knew what had been approved, what you did when something was unclear or how you told other people. Answer from what happened, and say so if you do not know.

A fictional example

This example is invented. Do not present it as your own experience.

Fictional example:

• Before: "I maintained the events page on a club website. It listed event names and dates."
• Request: "A committee member asked whether the page could show a description for every event."
• Clarification: "I asked who would write the descriptions and how long they should be."
• Approved revision: "The committee agreed to short descriptions, written by the organisers, for upcoming events only."
• Execution: "I added a description field and updated the layout. I asked the organisers for text, and I did not write the descriptions myself. I did not add descriptions to past events, because that had not been approved."
• Where things stand: "Some organisers have sent text and others have not. I don't know whether the descriptions have changed how many people read the page."

Fictional wording, only if it is true for you: "The request was wider than the change that was approved, so I built only what had been approved."

Practice your answer

Say your answer aloud if you wish. If you practice with another person, agree with them before recording or sharing any recording. In a real interview or assessment, do not use any tool to generate answers unless the organiser has explicitly allowed it.

This guide is published by Muqabala. If you would like to rehearse your answer, you can visit our interview practice page. Do not paste confidential employer, client or personal information into any practice tool.