On this page
Questions to practise
How do you gather requirements on a new project?
They want to see that you have a clear method and do not guess what people need.
Name your steps in order. Say who you talk to, for example each user group. Say what you ask, like their daily tasks. Then say how you check, for example by sharing your notes with them.
How do you prioritise requirements when there are too many?
Time and money are limited. They want to see how you decide what matters most.
Explain how you decide. For example, you look at business value, risk and effort, and you agree the order with the people involved. Give one short example of a choice you helped make.
What do you do when requirements change in the middle of a project?
Changes are common. They want to know you can manage them calmly and keep the project clear.
Say how you record the change, check its impact on time and cost, and share it with the right people. Explain who decides. Give a small real example if you can.
Tell me about a time a team and the business misunderstood each other. What happened?
They want a real story that shows how you notice and clear up a communication gap.
Say what went wrong, how you noticed it, and what you did yourself. Use 'I', not only 'we'. For example: one team meant monthly reports, the other weekly, and you showed a sample so they could agree.
Tell me about a mistake you made in your work. What did you do?
They want honesty and to see how you take responsibility and learn.
Choose a real, small mistake that was your own. Say how you found it, how you fixed it, and who you told. End with what you do differently now.
Describe a process you improved. What was the result?
They want proof that you can make work faster, simpler or clearer, with a real result.
Say what was slow or broken, what you changed, and the result. A number helps, like five days to two. A clear before and after in words is also fine, like fewer errors or less email.
How do you write down and share requirements?
Clear documents help teams build the right thing. They want to know your tools and habits.
Name the tools you use, such as user stories, process maps or simple requirement lists. Say how you keep them short and clear, and how people review and agree to them.
Think of a time two people in the business wanted opposite things. What did you do, step by step?
Analysts often stand between groups. They want to see how you keep different teams on side.
Go step by step: you listened to both sides, found the real need behind each request, shared options, and helped them agree. Say the final decision and how people felt.
How do you work with technical teams and business teams?
They want to know you can explain needs clearly to people with different skills.
Say how you change your language for each group. Mention simple tools, like short notes, examples or diagrams. Give one small example of a meeting where this helped.
What was your own role in a recent project?
They want to know your personal part, not only what the team did.
Name the project in one sentence. Then use 'I' and give two or three of your own actions, like 'I ran the workshops' or 'I wrote the new form'. You can also say how you supported the team.
First, I find out who uses the process, and I talk to them.
Clara
AI coach
Leo
AI coach
Lines to try
First, I find out who uses the process, and I talk to them.
I checked my notes with them to make sure I understood.
I noticed that we meant different things, so I showed them a sample.
I listened to both sides and found what each group really needed.
I explained it in simple words and used a diagram.
Before the change, it took five days. After the change, it took two.
Common questions
What if my example is from a small job or another country?
That is fine. The interviewer wants to hear how you work. A small, real example with clear steps and a result is better than a big, general one. Explain the situation in one or two sentences, then focus on your actions.
I do not have numbers for my results. Is that a problem?
No. A number helps, but it is not required. You can describe a clear before and after in words. For example: 'Before, people sent emails back and forth. After, everyone used one shared form, and there was less confusion.'
What should I do if I do not understand a question?
It is normal and polite to ask. You can say: 'Could you say that again, please?' or 'Do you mean a project at work or any project?' Take a short pause to think. A calm, clear answer is better than a fast one.