8 role-specific questions
Business Analyst Interview Questions & Answers
Business analyst interviews test how you elicit and document requirements, analyse processes, write user stories, handle conflicting stakeholders and use data to build a case.
Free, no sign-up. 71 questions in this role's practice pool, including behavioural, HR and situational questions.
Business analysis interview questions
Requirements elicitation, process modelling, user stories, stakeholder management and data.
1.
How do you gather requirements from stakeholders?
BeginnerRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Elicitation skills: getting to real needs from the right people, and confirming them.
Key points a strong answer covers
- Stakeholder identification. Identify the right stakeholders.
- Techniques. Interviews, workshops, observation, document analysis, prototypes.
- Ask why. Get to the underlying need, not just the requested solution.
- Document & confirm. Document and confirm back with stakeholders.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Writing down solutions instead of needs.
- Talking only to managers, not end users.
Likely follow-up questions
- How do you handle a stakeholder who doesn't know what they want?
- How do you prioritise requirements?
Example strong answer
I start by identifying stakeholders — not just the sponsor, but the people who'll use the system day to day and those affected downstream. Then I choose techniques to fit: one-to-one interviews for depth, workshops to resolve differences, observing people at work to see what they actually do, and reviewing existing documents and data. I keep asking why, because requests often come as solutions — 'we need a new report' — when the need is 'I can't see which invoices are overdue'. I document requirements as user stories or use cases with acceptance criteria, play them back to stakeholders to confirm, and use prototypes when words aren't enough.
2.
How do you analyse and improve a business process?
IntermediateRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Process analysis: measuring how work really flows and fixing causes, not symptoms.
Key points a strong answer covers
- Map current state. Map the as-is process (BPMN, swimlanes).
- Find problems. Find bottlenecks, waste, rework and root causes.
- Data. Measure with data: volumes, cycle times, error rates.
- Future state. Design a to-be process.
- Change & validate. Plan the change, pilot and measure benefits.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Jumping to automation without fixing the process.
- Mapping how the process should work, not how it does.
Likely follow-up questions
- Which modelling notation do you use and why?
- How do you get buy-in for a new process?
Example strong answer
I start by mapping the current, as-is process as it really happens — not as the procedure manual says — by walking through it with the people who do it, usually as a swimlane or BPMN diagram showing who does what and where handoffs happen. Then I measure it: volumes, cycle time per step, error and rework rates. That shows where the waste is — waiting between handoffs, duplicate data entry, approvals that add nothing. I find root causes, then design the to-be process with the team, simplifying first and automating second. Finally I plan the change — training, a pilot, updated documentation — and measure whether cycle time and errors actually improved.
3.
What makes a good user story and good acceptance criteria?
BeginnerRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Agile requirements quality.
Key points a strong answer covers
- Story format. As a [user], I want [goal], so that [benefit].
- INVEST. INVEST: independent, negotiable, valuable, estimable, small, testable.
- Acceptance criteria. Clear, testable acceptance criteria (often Given/When/Then).
- Edge cases. Cover edge cases and errors.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Stories that describe technical tasks with no user value.
- Vague criteria like 'should be fast'.
Likely follow-up questions
- How do you split a story that's too big?
- Who writes acceptance criteria?
Example strong answer
A good user story describes value from a user's point of view: 'As an accounts clerk, I want to filter invoices by overdue status, so that I can chase late payments first.' It follows INVEST — independent, negotiable, valuable, estimable, small enough for a sprint and testable. Acceptance criteria make it testable and remove ambiguity, often in Given/When/Then form: 'Given invoices with past due dates, when I select Overdue, then only unpaid invoices past their due date are listed, sorted by oldest first.' They should include edge cases and errors — no overdue invoices, a partially paid invoice. I write them collaboratively with the product owner, developers and testers.
4.
Two departments give you conflicting requirements. What do you do?
IntermediateSituationalPractise this question and get feedbackWhat the interviewer is evaluating
Facilitation and negotiation.
Key points a strong answer covers
- Understand each side. Understand the need behind each requirement.
- Bring together. Facilitate a joint discussion.
- Use objectives & data. Evaluate against business objectives and data.
- Escalate & document. Escalate to the sponsor if needed; document the decision.
Suggested answer structure
- Clarify the situation and what's at stake.
- Say what you'd do first, and why.
- Explain who you'd involve and how you'd communicate.
- Describe how you'd check the outcome and prevent a repeat.
Common mistakes
- Picking the side of the more senior stakeholder.
- Trying to satisfy both with a complicated compromise.
Likely follow-up questions
- What if the sponsor is in one of the departments?
- How do you keep relationships intact afterwards?
Example strong answer
I'd meet each department separately to understand the need behind its requirement — for example, finance wants every discount approved, sales wants to quote instantly. Often the underlying needs aren't actually in conflict: here, automatic approval for discounts below a threshold and fast-track approval above it could satisfy both. I'd bring them together in a workshop with the data — how many quotes, how many discounts, the cost of delays — and the project's objectives. If we still can't agree, I'd take the options and their impact to the sponsor for a decision, document it and its rationale, and make sure both sides understand why.
5.
What is a gap analysis, and how do you run one?
IntermediateRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Analytical frameworks.
Key points a strong answer covers
- Current vs desired. Compare the current state with the desired future state.
- Identify gaps. Identify the gaps in process, people, technology and data.
- Prioritise. Prioritise gaps by impact and effort.
- Action plan. Turn them into an action plan.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Listing gaps without prioritising them.
- Describing the future state vaguely.
Likely follow-up questions
- Give an example from your experience.
- How would you present a gap analysis to executives?
Example strong answer
A gap analysis compares where an organisation is now with where it wants to be, and identifies what's missing to get there. I define the desired future state concretely first — say, 'customers can track their order status online without calling'. Then I document the current state across process, people, technology and data: today status lives in three systems and agents look it up by phone. The gaps follow: no single order status data source, no customer-facing portal, no process for updating delayed orders. I prioritise gaps by impact and effort, and turn them into recommendations and a roadmap with owners and costs.
6.
How do you use data in your business analysis work?
IntermediateTechnicalPractise this question and get feedbackWhat the interviewer is evaluating
Analytical capability.
Key points a strong answer covers
- Quantify problems. Quantify problems and set baselines.
- SQL / Excel / BI. SQL, Excel or BI tools to analyse data.
- Data requirements. Define data requirements, mappings and models.
- Validate solutions. Measure benefits after delivery.
Suggested answer structure
- Define it in one sentence.
- Explain how it works underneath.
- Give a practical example from code or a project.
- Close with a trade-off, pitfall or when you'd use it.
Common mistakes
- Relying only on stakeholder opinions.
- Never checking data quality.
Likely follow-up questions
- Give an example where data changed a stakeholder's view.
- How do you write a data mapping document?
Example strong answer
Data makes requirements and business cases credible. Early on I use it to quantify the problem — querying the ticketing system with SQL to show that 30% of support tickets are 'where is my order', which sized the opportunity. I use Excel or Power BI to analyse trends and set baselines. In projects with integrations or migrations I write data requirements: source-to-target mappings, field definitions, validation rules and data-quality checks, often finding issues like duplicate customer records before they cause problems. After delivery I compare the same measures with the baseline to confirm benefits were realised.
7.
Which business analysis documents do you produce, and how do you keep them useful?
BeginnerRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Practical documentation habits.
Key points a strong answer covers
- Documents. Business case, BRD/FRD or user stories, process maps, use cases.
- Fit to methodology. Match depth to the methodology — just enough documentation.
- Traceability. Trace requirements to design and tests.
- Living & accessible. Keep them in one accessible, versioned place.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Writing 80-page documents nobody reads.
- Documents that go stale after sign-off.
Likely follow-up questions
- What's a traceability matrix used for?
- How do you document requirements in an agile team?
Example strong answer
It depends on the methodology. On waterfall or regulated projects I write a business case, a business requirements document and a functional specification, with process maps and use cases, plus a traceability matrix linking each requirement to design and test cases, so nothing is lost. In agile teams it's lighter: a product backlog of user stories with acceptance criteria, process diagrams and decision logs in Confluence. Either way I aim for 'just enough': clear, visual where possible, written for the reader, kept in one versioned place and updated when decisions change — a document that's out of date is worse than none.
8.
How would you build a business case for a new system?
IntermediateRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Commercial thinking: options, evidence-based costs and benefits, risks and a clear recommendation.
Key points a strong answer covers
- Problem & objectives. The problem and strategic objectives.
- Options. Options, including do nothing.
- Costs & benefits. Costs and quantified benefits: ROI, payback, total cost of ownership.
- Risks & assumptions. Risks, assumptions and sensitivity.
- Recommendation. A clear recommendation and plan.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Only presenting one option.
- Overstating benefits without evidence.
Likely follow-up questions
- How do you quantify intangible benefits?
- What's a sensitivity analysis?
Example strong answer
I'd start with the problem and how it links to strategy — for example, manual invoice processing costs us 2,000 staff hours a month and causes late-payment penalties. Then the options, always including 'do nothing' as a baseline, plus build, buy, or improve the current process. For each: total cost of ownership over three to five years — licences, implementation, training, support — and benefits quantified with evidence: hours saved times cost, penalties avoided, fewer errors. I'd show ROI and payback, list risks and assumptions, and run a sensitivity analysis — what if adoption is only half what we expect? Then a clear recommendation with an implementation plan and how benefits will be measured.
Ready to answer them out loud?
Run a timed business analyst mock interview, type or speak your answers, and get a score breakdown with what to improve.