Twenty minutes into an interview, everything is going well. Then they ask:
“Tell me about a time you dealt with a difficult stakeholder.”
And your mind goes blank.
You have handled situations like this before. But right now, you can’t remember a single one.
Sometimes the problem isn’t that you lack the experience. You just haven’t prepared to retrieve it when you need it. So how do you prepare before the interview, and what do you do if your mind still goes blank on the day?
What are interviewers really looking for?
As business analysts (BAs), we ask questions, listen, and make sense of unclear information. An interview isn’t that different. The interviewer is trying to see how you think, how you communicate, and how you approach problems.
So when they ask, “Tell me about a time a requirement changed late in a project,” they are not only interested in the requirement. They want to know how you handled the change. Did you ask why it changed? Did you understand the impact? Did you bring the right people together? Once you know what a question is really after, it’s much easier to answer.
If you are moving into business analysis from another field, don’t overlook your earlier experience. Noticing that customers keep complaining about the same issue is problem identification. Coordinating between teams is stakeholder management. You may not have had the title yet, but you may already have the experience. Your job is to make that connection clear.
Get two or three stories ready
Before the interview, prepare two or three real stories. They can come from work, school, volunteering, or personal projects. Try to cover a difficult stakeholder, a scope change, a problem you solved, a mistake you learned from, and something you are proud of. If you are going for a senior role, include one where you influenced a decision, not just delivered a task.
For each story, know what was happening, who was involved, what you personally did, and what happened afterwards. That’s the idea behind the STAR method (Situation, Task, Action, Result). Don’t memorize it word for word. Know it well enough to tell it naturally and adjust it to the question.
Here’s the difference. When asked about a difficult stakeholder, an unprepared answer might sound like:
“There was a project at my previous job where we had different teams involved. One of the managers kept changing what he wanted, so it was difficult. We eventually sorted it out.”
Nothing is wrong with that, but the interviewer still doesn’t know what you did. Compare it with:
“I was working on a customer onboarding project, and the sales manager kept bringing in new requests. By the third change, I realized we were at risk of missing the delivery date. I arranged a short discussion with him, walked him through how each request affected the timeline, and asked him to help prioritize what was most important. We agreed to move two of the requests to a later phase, and the team was able to meet the original deadline.”
Now they can see how you think. You spotted the risk, explained the impact, involved the stakeholder, and got a result.
Practice your answers out loud
Thinking through your answers in your head is not enough. Once you start speaking, you may realize you are going in three directions or taking five minutes to answer something that needs two. Practice with a friend, a mentor, or another BA, or record yourself and listen back. Check that you answered the question, explained what you did, and mentioned the outcome.
Three questions to be ready for
1. The scenario question
“How would you handle two stakeholders who disagree on priorities?”
Don’t rush to a solution. As a BA, you would ask questions first. You could say, “Before deciding how to handle it, I would like to understand the situation a bit more,” then ask who the stakeholders are, what they disagree about, and what the deadline is. It shows you understand a problem before trying to solve it, and it gives you a few seconds to think.
2. The question you can’t answer
You may be asked about a tool you have never used or an industry you have never worked in. Don’t bluff. Say something like:
“I haven’t worked directly with that tool, but I’ve used a similar one. Here’s how I would approach it…”
Being honest about a gap is better than getting caught halfway through a made-up answer.
3. The question you ask them
When they ask, “Do you have any questions for us?”, don’t say “No, I’m fine.” Ask how BAs work with product managers and developers, what you would be expected to achieve in the first six months, or what challenges the team is working through. You are also deciding whether the role suits you.
When your nerves take over
Some nerves are normal, even when you have prepared. Before the interview, don’t cram. Glance over the headlines of your stories, keep some water nearby, take a few slow breaths, and check your camera, connection, or route. Prepare a 30-second answer to “Tell me about yourself” so your first response comes easily.
If you go blank, you don’t have to answer immediately. Say:
“That’s a good question. Let me take a moment to think about it.”
You can also repeat the question back or ask for clarification. If you lose your thread halfway through an answer, don’t speed up. Say “Let me come back to the main point,” and continue. A short pause feels much longer to you than it does to the interviewer.
Afterwards, write down the questions you remember, which ones you answered well, and where you rambled. Your next interview shouldn’t be the same version of you as the last one.
Conclusion
You don’t need a perfect answer to every question. You need to know your own experiences well enough to talk about them. And if you blank out, it doesn’t mean you are not qualified. Take a breath, ask for a moment, and start from what you know.
Try this today. Pick one situation from work, a project, or school, and write down what happened, who was involved, what you did, and what happened afterwards. Then say it out loud. That’s one story ready for your next interview.
Monthly Webinar Reminder
