Business Analyst Mock Interview Guide
How to prepare for business analyst interviews: unclear requests, conflicting stakeholders, requirements and process questions, with worked examples.
HotSeat team
Updated November 2026 3 min read
‘We need a dashboard.’ That sentence is the business analyst's whole job in miniature. Who needs it? What will they do with it? What are they doing today? Often the answer turns out to be something other than a dashboard.
Expect your interview to test that instinct. They want to see you find the need behind the request, get people to agree, and show that something improved. Naming the documents you produced won't be enough.
In this article
When they ask how you'd handle an unclear request
- Find the person and the problem. Who needs this, what are they trying to do, and what's failing now?
- Agree what success looks like. What should improve, and how will you all know?
- Learn how it works today. Map the real steps, including the exceptions, handoffs and spreadsheets nobody mentioned in the meeting.
- Compare options. Include changes to process, policy and data. Software isn't always the answer, and saying so tends to go down well.
- Check you've understood. Use an example, a model or a small prototype to surface disagreement before anyone pays to build the wrong thing.
Show that you can sharpen a requirement
You may be handed a vague requirement and asked what you'd do with it. These are the sort of questions to ask, and the sort of answer you're after:
| Vague | Ask | Sharper |
|---|---|---|
| The dashboard must be easy to use | Easy for whom, doing what? | A support manager can find overdue cases within two clicks |
| The system must be fast | Which action, under what load? | Search results appear within two seconds for 95% of normal requests |
| Users need export | What will they do with the file? | Finance can export monthly totals in the format their reporting tool needs |
| Automate the process | Which step causes the delay or error? | Remove manual copying between approval and payment records |
‘Two teams want opposite things’
This question is close to guaranteed. Here's an invented answer that finds the need behind each request:
“Sales wanted every lead field required, while support wanted a shorter form. I talked to both teams and found only four fields actually affected lead routing. We made those four required, moved the rest to a later step, and tracked incomplete records for a month. Form completion improved by 18%, and routing errors didn't increase.”
Neither team got exactly what it asked for, and both got what they needed. It also ends with a check on whether it worked.
Others to prepare
Tell me about a process you improved.
Why they ask: They want evidence your analysis changed something measurable.
- Explain the original pain and the starting number
- Show how you found the cause
- Describe the new process and the result
Likely follow-up: Which part of your recommendation was rejected?
What do you do when a requested feature creates little value?
Why they ask: They want to see whether you can challenge a solution without dismissing the person asking.
- Explore the need behind the request
- Use evidence to compare options
- Offer a smaller or different solution
Likely follow-up: What if the requester is a senior leader?
What if neither team agrees on the requirement?
Why they ask: You usually won't be the one who decides, so they want to know that you can get a decision made.
- Bring out the shared goal
- Lay out the trade-off plainly
- Make it clear who owns the decision
Likely follow-up: How do you handle the team that lost?
Bring a before and after
Weak BA stories end with ‘and the requirements were signed off’. Strong ones say what happened to the business. Before your interview, look back through your projects for a starting number and an ending number: processing time, error rate, rework, tickets. If you never measured it, say what you'd measure now. That's more credible than guessing.
Practise turning a vague request into a useful change
Try requirements, process, conflict and value questions in a business analyst mock interview.
Start a business analyst interviewSources and further reading
- A model for effective analysis (International Institute of Business Analysis)
- Understanding requirements and designs (International Institute of Business Analysis)