Launch prices end Friday-d --h --m --s left

Business analyst interview questions

22 questions · 5 answer outlines · Updated Oct 6, 2026

Business analyst interviews test how you gather and document requirements, analyse processes and data, and connect business teams with developers. Expect scenario questions about vague or conflicting requirements, questions on techniques such as process mapping and user stories, and often a short case or data exercise.

Five questions to prepare first

These come up in most interviews for this role. For each one: what the interviewer is checking, and the points a strong answer covers, in order.

1

How do you gather requirements from stakeholders who aren't sure what they want?

What they're checking

Whether you can draw out real needs instead of just taking orders.

A strong answer covers

  1. Start from the problem and the goal, asking what is not working today and what success would look like.
  2. Use several techniques, such as interviews, workshops, observing the current process and reviewing documents.
  3. Make it concrete early with process maps, mock-ups or examples people can react to.
  4. Write requirements down, play them back for confirmation, and keep a record of open questions.
2

What makes a good user story?

What they're checking

Whether you can write requirements developers can build and test from.

A strong answer covers

  1. Describe the format, as a type of user, I want something, so that I get a benefit.
  2. Add clear acceptance criteria, often written as given, when, then scenarios.
  3. Keep stories small, independent and testable, and split anything too big for one iteration.
  4. Say how you check stories with the team before work starts, such as in refinement sessions.
3

Two departments want conflicting things. How do you handle it?

What they're checking

How you resolve conflict with facts and get a decision made.

A strong answer covers

  1. Understand each side's underlying goal, which is often less opposed than the requests are.
  2. Lay out the options and their impact on cost, time, risk and the business goal.
  3. Look for a solution that meets both goals, and if there isn't one, take it to the person who owns the decision.
  4. Record the decision and the reasoning so it doesn't reopen later.
4

How would you map and improve a slow business process?

What they're checking

Whether you can analyse a process and find improvements that matter.

A strong answer covers

  1. Map the current process with the people who do it, including the workarounds they actually use.
  2. Measure where time and errors build up, such as waiting, rework and handoffs.
  3. Find the root causes and propose changes, from simple process fixes to automation.
  4. Estimate the benefit, agree a target and check after the change that it was reached.
5

Tell me about a project where your analysis made a measurable difference.

What they're checking

Whether your work leads to outcomes, not just documents.

A strong answer covers

  1. Describe the business problem and what was at stake.
  2. Explain the analysis you did and the key insight it produced.
  3. Describe how you got the change accepted and delivered.
  4. Give the result in numbers, such as time saved, errors reduced or revenue gained.

Requirements

The core of the job. Show how you get from what people say they want to what they need.

  1. 1How do you gather requirements from stakeholders who aren't sure what they want?Answer outline
  2. 2What makes a good user story?Answer outline
  3. 3Two departments want conflicting things. How do you handle it?Answer outline
  4. 4What is the difference between functional and non-functional requirements?
  5. 5How do you make sure developers understood the requirements?
  6. 6How do you handle changes to requirements once development has started?

Analysis and techniques

Expect to name techniques and, more importantly, explain when you would use them.

  1. 7How would you map and improve a slow business process?Answer outline
  2. 8Which modelling techniques do you use, such as BPMN, use cases or data flow diagrams?
  3. 9How do you carry out a gap analysis?
  4. 10How do you prioritise requirements?
  5. 11What SQL or data analysis do you use in your work?
  6. 12How do you work out whether a proposed change is worth the cost?

Stakeholders and delivery

Business analysts sit between the business and the delivery team. Show you can work both ways.

  1. 13How do you work with a product owner and a development team?
  2. 14Tell me about a time a stakeholder rejected your recommendation.
  3. 15How do you run a requirements workshop?
  4. 16How do you support user acceptance testing?
  5. 17How do you explain a technical constraint to business users?

Behavioural

Bring examples where your analysis changed what was built or how work was done.

  1. 18Tell me about a project where your analysis made a measurable difference.Answer outline
  2. 19Tell me about a requirement you discovered late. What did you do?
  3. 20How do you handle working on several projects at once?
  4. 21Tell me about a time you had to learn a new business area quickly.
  5. 22Why business analysis rather than product or project management?

Business analyst interview tips

  • Bring a sample of your work if you can share it, such as an anonymised process map or a set of user stories.
  • Prepare a story about conflicting requirements. It is one of the most common business analyst questions.
  • Brush up on basic SQL or spreadsheet analysis; many roles include a short data exercise.
  • Learn the company's industry terms before the interview. Business analysts are expected to pick up a domain quickly.

Business analyst interview FAQ

Often. A typical case gives you a business problem or a process description and asks you to identify issues, ask questions and suggest requirements or improvements.

For many roles, basic SQL is expected or at least a plus, especially in data-heavy industries. Others focus on process and requirements and test spreadsheets instead.

Certifications from the International Institute of Business Analysis, such as the CBAP, are well known. They can help, but most interviews weigh examples of real work more heavily.

Related roles

All interview questionsHow a mock interview works

Say these answers out loud before the real interview.

A free mock interview for this role asks five questions you haven't seen, scores each answer and shows a stronger one.

Start with a free mock interview
Start a free mock interview