Business analyst interview questions
Business analyst interviews test how you turn unclear business needs into clear requirements, how you work with stakeholders who disagree, and whether you can back your recommendations with data.
The questions below are grouped by level, with what a strong answer includes.
What interviewers assess
- Requirements: elicitation, documentation, user stories and acceptance criteria
- Stakeholder management and communication
- Process modelling and analysis techniques
- Data skills and structured problem solving
Basic questions
What does a business analyst do?
What a good answer covers: Understands the business problem, gathers and clarifies requirements, works between the business and delivery teams, and checks that the solution delivers value.
What is the difference between functional and non-functional requirements?
What a good answer covers: What the system does versus how well it does it (performance, security, usability), with an example of each.
How do you write a good user story?
What a good answer covers: "As a [user], I want [goal] so that [benefit]" with clear acceptance criteria; mention INVEST and keeping stories small.
Which techniques do you use to gather requirements?
What a good answer covers: Interviews, workshops, observation, document analysis, surveys and prototypes, and choosing among them by situation.
What is a gap analysis?
What a good answer covers: Compare the current state with the desired state, identify the gaps and plan how to close them.
Intermediate questions
Two stakeholders want conflicting features. What do you do?
What a good answer covers: Understand each underlying need, bring data, go back to business goals, propose options, and escalate to the decision-maker if needed. Give a real example.
How do you prioritise requirements?
What a good answer covers: MoSCoW, value against effort, risk and dependencies, agreed with stakeholders and revisited regularly.
Walk me through modelling a business process.
What a good answer covers: Map the current process (for example in BPMN or a swimlane diagram), find delays and handoffs, design the improved process and agree on it.
How do you handle a requirement change late in a project?
What a good answer covers: Assess impact on scope, time and cost, discuss with stakeholders, follow change control and update the documents and the team.
What SQL or data skills do you use as a BA?
What a good answer covers: Querying data to check assumptions, sizing problems and measuring results. Give an example where data changed a decision.
Advanced questions
Customer complaints have doubled. How would you approach this?
What a good answer covers: Clarify the scope, check the data, segment by product, channel and reason, find root causes, propose and prioritise fixes, and define how to measure success.
How do you define success metrics for a new feature?
What a good answer covers: Link to a business goal, choose leading and lagging indicators, set a baseline and target, and agree how and when to measure.
How do you work as a BA in an agile team?
What a good answer covers: Refining the backlog with the product owner, writing stories just in time, joining ceremonies and validating increments with users.
Describe a time your analysis changed a decision.
What a good answer covers: A structured story with the situation, your analysis, how you presented it and the measurable outcome.
How would you build a business case for a new system?
What a good answer covers: The problem, options including doing nothing, costs, benefits, risks, recommendation and a high-level plan.
Common mistakes
- Describing yourself as someone who simply writes down what stakeholders ask for.
- Answering stakeholder questions without a real example.
- Not mentioning how you measured whether a change worked.
- Using frameworks by name without showing how you applied them.
How to prepare
- Prepare three stories: a stakeholder conflict, a requirement you clarified, and a data-driven recommendation.
- Practise writing user stories with acceptance criteria for a familiar app.
- Revise basic SQL and Excel, which many BA roles test.
- Practise structuring a case question aloud.
Reading questions only goes so far: the real test is answering them aloud, under follow-up questions. Career Scan builds a mock interview from your own resume and the job, then shows exactly which answers need work.
Frequently asked questions
Is coding needed for business analyst roles?
Usually not, but SQL and strong Excel skills are often expected, and some roles ask for Power BI or Tableau.
Are BA interviews mostly behavioural?
A large part is behavioural and scenario-based, often combined with a case study or a requirements exercise.
Do certifications like CBAP help?
They can help experienced candidates. For most roles, clear examples from real projects matter more.