KNOWLEDGE HUB

Business Analyst interview prep guide

What BA interviews cover, how to structure your answers, and the questions that come up most often, with an outline answer for each.

How BA interviews are usually run

Most UK employers use three or four stages. Each one tests something different.

1

Screening

A recruiter call or, increasingly, an automated video or chatbot screen. Expect "tell me about yourself", why this role, notice period and salary. Keep answers short and specific.

2

Technical / competency

How you gather, document and prioritise requirements. For technical BA roles, expect SQL, reporting tools, APIs and how data moves between systems.

3

Scenario or panel

A business problem to talk through, often with several interviewers. They're testing how you think: the questions you ask, the assumptions you check and how you structure the answer.

4

Final / HR

Motivation, team fit and practical details. Have two or three good questions ready for them.

Junior vs senior: what they ask

Prepare for the level you're applying for. Senior interviews go much deeper into tools and real project detail.

Junior and mid-level roles

Senior and lead roles

  • Data: SQL, Power BI or Tableau, and how you've used them
  • End-to-end data flow on a project you've worked on: source, transformation, output
  • Wireframes, Excel modelling and API testing for technical BA roles
  • Leading workshops, managing senior stakeholders, budgets and forecasting
  • How you use AI tools to draft and check requirements

"Tell me about yourself"

The first answer sets the tone. Aim for about 90 seconds, in three parts.

Structure

  • Now: your current role or most recent focus, in one sentence
  • Before: two or three relevant experiences, each with a result
  • Next: why this role and this company, specifically

Tips

  • Lead with what makes you relevant to this job, not your whole history
  • No experience as a BA yet? Lead with your education, training and transferable work, such as testing, data or customer-facing roles
  • Include one number: projects delivered, time saved, stakeholders supported
  • Practise it out loud until it sounds natural, not memorised

Answer experience questions with STAR

For any "tell me about a time..." question, this keeps your answer focused.

S

Situation

The context, in one or two sentences. Which organisation, which project.

T

Task

What you were responsible for. The problem you had to solve.

A

Action

What you did, step by step. Say "I", not "we". This is most of your answer.

R

Result

What changed, with a number if you have one: time saved, errors reduced, delivered early.

Common questions, with answer outlines

Use these as a structure, then fill them with your own examples. Tap a question to open it.

Core business analysis

How do you gather requirements?
Start with preparation: understand the goal, read existing documents and identify the stakeholders. Then choose techniques to suit them: one-to-one interviews, workshops, observation, surveys. Document, review with stakeholders and get sign-off. Finish with a short example from your own work.
What is the requirements life cycle?
Plan the analysis, elicit requirements, analyse and document them, validate them with stakeholders, get sign-off, then manage changes and trace each requirement through to testing and delivery.
What's the difference between a BRD and an FRD?
A BRD says what the business needs and why. An FRD says how the system should behave to meet those needs, in enough detail for developers and testers.
Functional versus non-functional requirements?
Functional requirements describe what the system does ("users can reset their password"). Non-functional requirements describe how well it does it: speed, security, availability, accessibility.
How do you prioritise requirements?
Name a technique and show you'd use it with stakeholders, not alone. MoSCoW is the usual answer: agree the Must haves first, and challenge a list where everything is a Must.
Which documents have you produced?
List them and say who used each: BRDs, FRDs, user stories, process maps, traceability matrices, UAT scripts. Interviewers care more about the purpose than the template.

Agile and delivery

Write a user story for a login feature.
As a registered customer, I want to log in with my email and password so that I can see my orders. Then add acceptance criteria: Given a valid email and password, when I log in, then I see my account page. Cover the error cases too: wrong password, locked account.
Agile or Waterfall: which do you prefer?
Avoid picking a side. Explain that Waterfall suits fixed scope and regulated work, Agile suits changing requirements, and give an example of each from your experience.
What does a BA do in a Scrum team?
Works with the product owner on the backlog, writes and refines stories, clarifies requirements during the sprint, supports testing and checks that what's built meets the need.
How do you handle scope creep?
Check every new request against the agreed scope. Log it as a change request, assess the impact on time, cost and quality, and let the sponsor decide. Show you protect the delivery without just saying no.
How do you support UAT?
Write UAT scenarios from the acceptance criteria, prepare test data, support business users while they test, triage defects with the team and get formal sign-off.

Stakeholders

Two stakeholders want conflicting things. What do you do?
Meet them separately to understand the reason behind each request. Go back to the business objective, lay out the options and their impact, and bring them together to agree. Escalate to the sponsor only if they can't.
How do you deal with a stakeholder who won't engage?
Find out why: time, priorities or doubts about the project. Adapt: shorter sessions, async questions, showing them what's in it for them. Use stakeholder analysis to plan it.
How do you explain technical detail to a non-technical audience?
Start from the business impact, use their language and a visual such as a process map or a prototype. Check understanding by asking them to describe it back.

Data and technical (often for technical BA roles)

How have you used SQL?
Give a real example: the question you needed to answer, the tables you joined, what you found and what happened next. Basics to know: SELECT, WHERE, JOIN, GROUP BY. See SQL.
Walk me through the data flow on a project.
Source systems, how data is extracted, any transformation and validation, where it's stored and who uses the output. Draw it if you can. This is where invented project experience falls apart, so use a project you really know.
How do you use AI tools in your BA work?
Name the tool and the task: drafting user stories, summarising workshop notes, generating test cases. Then say how you check the output. Interviewers want to hear that you review everything, not that AI writes your requirements.
What's an API, and how would you test one?
An API lets two systems exchange data. You'd send requests with a tool such as Postman and check the responses against the requirement, including the error responses, not just the happy path.

Scenario questions: clarify before you answer

Scenario questions often sound odd on purpose: "I'm at your door asking for a spoon. What do you do?" The interviewer wants to see whether you ask before you act. What is it for? What size? How many? By when? Ask clarifying questions, state your assumptions, then answer. That is the BA job.

Questions to ask them

Good questions show you're thinking about the job, not just getting it.

  • What does success look like for this role in the first six months?
  • How do BAs work with product owners and developers here?
  • Which methodology do the teams use, and how strictly?
  • What's the biggest challenge the team is facing right now?

Before the interview

  • Read the job description and match each requirement to an example from your experience
  • Prepare a 90-second "tell me about yourself"
  • Prepare four or five STAR stories you can adapt: a conflict, a scope change, a delivery under pressure, a process improvement, a mistake you learned from
  • Revise the core terms in the BA glossary
  • Know every tool on your CV well enough to answer follow-up questions
  • Research the company: what they do, recent news, who their customers are
  • Have two or three questions ready for them

Hiring a Business Analyst?

I’d be glad to talk about the role and how I can help your team.

Scroll to Top