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 interviews run
- Junior vs senior
- Tell me about yourself
- STAR answers
- Common questions
- Scenario questions
- Questions to ask
- Checklist
How BA interviews are usually run
Most UK employers use three or four stages. Each one tests something different.
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.
Technical / competency
How you gather, document and prioritise requirements. For technical BA roles, expect SQL, reporting tools, APIs and how data moves between systems.
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.
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
- The requirements life cycle, from elicitation to sign-off
- Core techniques: interviews, workshops, process mapping, MoSCoW
- User stories and acceptance criteria
- Agile versus Waterfall, and when each fits
- How you'd handle a simple stakeholder or scope scenario
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.
Situation
The context, in one or two sentences. Which organisation, which project.
Task
What you were responsible for. The problem you had to solve.
Action
What you did, step by step. Say "I", not "we". This is most of your answer.
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?
What is the requirements life cycle?
What's the difference between a BRD and an FRD?
Functional versus non-functional requirements?
How do you prioritise requirements?
Which documents have you produced?
Agile and delivery
Write a user story for a login feature.
Agile or Waterfall: which do you prefer?
What does a BA do in a Scrum team?
How do you handle scope creep?
How do you support UAT?
Stakeholders
Two stakeholders want conflicting things. What do you do?
How do you deal with a stakeholder who won't engage?
How do you explain technical detail to a non-technical audience?
Data and technical (often for technical BA roles)
How have you used SQL?
Walk me through the data flow on a project.
How do you use AI tools in your BA work?
What's an API, and how would you test one?
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.