Business Analysis interview questions
BA interviews — requirements, stakeholders, process modelling, and the evidence that a change was worth making.
22 questions, and for 18 of them what a good answer has to cover. This is the bank Answers Ready practises you against — the same questions, marked on the same points.
introduction
Tell me about yourself.
What a good answer covers
- A shape, not a history: what they analyse now, one thing they are good at, why this role.
- Under two minutes.
- Ends pointed at the job rather than trailing off.
the role
What does a business analyst actually do?
What a good answer covers
- Bridges a business problem and a delivered change — not 'writes documents'.
- Names the two directions: understanding the need, and making it buildable.
- Distinguishes the BA from the product owner and the project manager rather than blurring them.
elicitation
How do you gather requirements?
What a good answer covers
- Names more than one technique: interviews, workshops, observation, document analysis, prototyping.
- Chooses between them for a situation rather than reciting all of them.
- Mentions going to watch the work happen, not only asking people about it — the gap between what people say they do and what they do is the point.
A stakeholder tells you exactly what they want built. How do you handle it?
What a good answer covers
- Recognises a solution presented as a requirement.
- Works back to the problem — what would be true if this were solved — without making the stakeholder feel corrected.
- Often the stated solution is right; the point is knowing why, so the alternatives can be weighed.
- Names the risk: build the stated thing and the underlying problem remains.
requirements
What is the difference between a functional and a non-functional requirement?
What a good answer covers
- Functional is what it must do; non-functional is how well — performance, security, availability, accessibility.
- A concrete non-functional example, since this is where vague answers show.
- Non-functionals are the ones that get missed and the ones that sink a release.
How do you write a good user story?
What a good answer covers
- Role, goal, reason — and that the reason is the part that carries the value.
- Acceptance criteria that are testable, not restatements of the story.
- INVEST, or the substance of it: small, independent, valuable, verifiable.
- A story is a placeholder for a conversation, not a specification handed over.
How do you prioritise requirements?
What a good answer covers
- Names a method — MoSCoW, weighted scoring, cost of delay — and that the method matters less than the conversation it forces.
- Prioritisation is a business decision the BA facilitates, not one the BA makes alone.
- The failure mode: everything is a Must. How they handle that.
What is requirements traceability and why would you bother?
What a good answer covers
- Links a business need to a requirement to a test to a delivered change.
- What it buys: impact analysis when something changes, and evidence at sign-off.
- Proportionate — a full matrix on a two-week change is overhead nobody reads.
- Regulated environments where it is not optional.
stakeholders
Two stakeholders want incompatible things and both are senior. What do you do?
What a good answer covers
- Goes to the underlying need rather than adjudicating between the two stated solutions.
- Makes the trade-off visible with evidence — cost, impact, who is affected — rather than arguing.
- Escalates to the sponsor or a named decision-maker when it is genuinely a business decision, and says so without sounding like passing the buck.
- Records the decision and who made it.
The sponsor keeps adding to the scope. How do you handle it?
Senior. Marked against your own answer in the app.
Tell me about a stakeholder who would not engage.
What a good answer covers
- Diagnoses why rather than labelling them difficult — too busy, burnt before, threatened by the change.
- Something specific they tried: shorter sessions, going to them, finding what they cared about.
- The outcome, including if it stayed imperfect.
modelling
Walk me through how you would map an as-is process.
What a good answer covers
- Talks to the people who do the work, not only the manager who describes it.
- Walks the process end to end including the exceptions and workarounds — the workarounds are where the real problems are.
- Validates the map back with the participants before using it.
- Says what the map is for: finding the waste, the handoffs, the duplicated effort.
When would you use BPMN rather than a simpler flowchart?
What a good answer covers
- BPMN when several parties or systems are involved and the handoffs matter — swimlanes make ownership visible.
- A simpler diagram when the audience will not read notation.
- The real answer is audience: a model nobody reads has failed however correct it is.
analysis
How do you carry out a gap analysis?
What a good answer covers
- Current state, target state, and the difference expressed as work rather than as a list of complaints.
- Where the target state comes from — strategy, a regulation, a competitor, a business case.
- Prioritises the gaps; not all of them are worth closing.
What goes into a business case?
What a good answer covers
- The problem and its cost, the options considered including doing nothing, the recommendation and why.
- Costs and benefits, with the benefits stated in a way someone can check later.
- Risks and assumptions.
- Doing nothing as a genuine option is the part most candidates omit.
How do you decide what goes in an MVP?
Senior. Marked against your own answer in the app.
delivery
Tell me about a time a requirement was missed and what happened.
What a good answer covers
- A real situation with a consequence, not a hypothetical.
- What they changed afterwards — a checklist, a review step, involving someone earlier.
- Owns their part in it without theatrical self-blame.
How do you support UAT?
What a good answer covers
- Plans it against the acceptance criteria and the original business need, not against the build.
- Real users doing realistic tasks, with data that resembles theirs.
- Their role in triage: deciding what is a defect, what is a change, and what was always out of scope.
- Sign-off and who gives it.
How do you know a change actually delivered the benefit?
Senior. Marked against your own answer in the app.
agile
What is the BA's role on an agile team?
What a good answer covers
- Refinement: making stories ready, which is most of the job.
- Works with the product owner rather than replacing them — and can say what the difference is.
- Present through delivery, not finished when the story is written: questions arrive mid-sprint.
- Avoids the answer that agile means no documentation.
data
How comfortable are you with SQL, and what do you use it for?
What a good answer covers
- Honest about level — joins and aggregates is a fine answer, claiming optimisation when they mean SELECT is not.
- What they use it for: checking a claim, sizing an impact, finding how many records are actually affected.
- Going to the data instead of accepting an assertion is the behaviour being tested.
A report says the change worked. You think the numbers do not support that. What do you do?
Senior. Marked against your own answer in the app.