Business Analyst Interview Questions (and How to Answer Them)

A business analyst interview is harder to prepare for than a technical one, because there is rarely a single right answer. Interviewers are listening for how you think: whether you ask before you assume, whether you can hold a room of people who disagree, and whether you write things down clearly enough for someone else to build from them.

The questions below are drawn from the skills UK employers name most often in business analyst adverts: Agile, user stories, stakeholder management, requirements gathering, workshop facilitation and acceptance criteria (ITJobsWatch).

What a UK business analyst interview looks like

Most processes have three or four stages: a short screening call, a competency interview, a scenario or case exercise, and sometimes a practical task such as writing a user story or mapping a process. Public-sector roles use "Success Profiles", which score behaviours and technical skills separately, so read the advert's assessment section carefully.

Core business analysis questions

How do you gather requirements?

Describe a process, not a single technique. Start by understanding the problem and who it affects, then choose techniques to suit the people involved: interviews for detail, workshops for agreement, observation for how work really happens, and document analysis for the current rules. Finish by playing requirements back to stakeholders to confirm them.

How do you handle stakeholders who want conflicting things?

Show that you separate positions from needs. Bring the conflict into the open, trace each request back to the business objective it serves, and make the trade-off visible: cost, risk and benefit. If it still cannot be resolved, escalate it to the person who owns the decision. Never quietly pick a side.

What is the difference between functional and non-functional requirements?

A functional requirement describes what the system must do, such as "a customer can reset their password by email". A non-functional requirement describes how well it must do it: performance, security, availability or accessibility, such as "the reset email arrives within one minute". Good answers add that non-functional requirements are often forgotten until it is expensive to fix them.

How would you write a user story for this?

Use the standard form, "As a [user], I want [goal], so that [benefit]", then add acceptance criteria, ideally in Given/When/Then form. Interviewers want to see that the story is small enough to deliver in one sprint, testable, and written from the user's point of view rather than the system's.

Scenario questions

Expect at least one open scenario, such as "The operations director says the returns process is too slow. What would you do?" A strong answer has a shape:

1. Clarify. What does "too slow" mean, measured how, and compared with what?
2. Map the current state. Walk the process with the people who do it, and time each step.
3. Find where it breaks. Handoffs, rework and waiting time usually account for most of the delay.
4. Propose options with their costs and benefits, not one answer.
5. Agree how success will be measured before anything changes.

The most common mistake is jumping to a solution, such as "we should automate it", before establishing the problem.

Agile questions

What does a business analyst do in a Scrum team?

Scrum does not name a business analyst role, so the work is shared. In practice the business analyst helps the product owner refine the backlog: breaking work into user stories, writing acceptance criteria, clarifying questions with stakeholders, and making sure the team understands what "done" means for each story before the sprint starts.

What is the difference between a business analyst and a product owner?

The product owner is accountable for what gets built and in which order, and owns the backlog. The business analyst supports those decisions with analysis: understanding needs, modelling processes and writing clear requirements. In smaller teams one person may do both, but the accountability stays with the product owner.

Behavioural questions

Use the STAR structure (situation, task, action, result) and choose examples that show business analysis skills, even from jobs that were not called "business analyst". Common prompts:

• Tell me about a time you had to influence someone you had no authority over.
• Tell me about a requirement you got wrong, and what you changed afterwards.
• Describe a time you simplified something complicated for a non-technical audience.

Interviewers look for what you did, not what the team did, and for a result you can state plainly.

How to prepare in two weeks

• Days 1–3: reread the advert and list the skills it names. Write one STAR example for each.
• Days 4–7: practise writing three user stories with acceptance criteria, and map one process you know well in BPMN.
• Days 8–11: rehearse two scenario questions out loud, using the five-step shape above.
• Days 12–14: research the organisation's current change programmes, and prepare two questions about how business analysts work there.

Frequently asked questions

What are the most common business analyst interview questions? How you gather requirements, how you handle conflicting stakeholders, the difference between functional and non-functional requirements, and how you would write a user story. Expect at least one open scenario about improving a process, and behavioural questions about influence and communication.

Do business analyst interviews include a test? Often. Common tasks are writing user stories with acceptance criteria, mapping a process from a short description, or analysing a case study and presenting recommendations. Some data-focused business analyst roles add a basic SQL or Excel exercise.

How do I answer business analyst interview questions with no BA experience? Use examples from other work that show the same skills: improving a process, gathering what colleagues needed, testing a new system or explaining a change. Name the business analysis technique you were using, even if you did not call it that at the time.

Sources: ITJobsWatch, Business Analyst permanent jobs, skills appearing in adverts, six months to October 2026; Government Digital and Data Profession Capability Framework, business analyst role, updated 28 August 2026; Civil Service Success Profiles; The Scrum Guide (2020).

Read next

• Business analyst job description
• Business analyst salary UK
• How to become a BA with no experience
• Data analyst interview questions