Business analyst interview questions
The short answer
A business analyst interview checks how you turn unclear or conflicting needs into requirements a team can build and test. Expect questions about requirements that were in conflict, a process you mapped and changed, a gap you caught before go-live and how you wrote acceptance criteria. Hiring managers listen for the decision your analysis made possible, not the number of documents you produced.
Practice these questions in Claude with Interview Coach, free
How to use these questions
Each question comes with what a hiring manager usually listens for. Prepare one story per question from your own record: the requirements document or backlog, the process maps, the test log, the sign-off. Tell it as the situation, what you did yourself, what changed and how you know. Bring one artifact you can describe in detail, such as a process map or a set of acceptance criteria, because the follow-up questions often go there.
Behavioral questions
Tell me about requirements that were unclear or in conflict. How did you get to agreement?
In the Interview Coach question bank
Listen for: who wanted what and why, the technique you used to get to agreement (a workshop, a prototype, data), who signed off, and what was built as a result.
Tell me about a defect or a gap you caught before go-live. How did you find it, and what happened next?
In the Interview Coach question bank
Listen for: how you found the gap (a test case, a data check, a walk through the process), who you told, and what was changed before go-live.
Tell me about a project or a decision that did not go to plan. What was your part in it?
In the Interview Coach question bank
Listen for: a requirement or analysis that turned out wrong, your part in it, and what you check now that you did not check then.
Tell me about a time your analysis changed a decision someone had already made.
Listen for: the decision, the evidence you brought, how you raised it, and what was decided in the end.
Situational questions
The sponsor asks for a feature, and you think it solves the wrong problem. What do you do?
Listen for: questions that get to the problem behind the request, evidence from users or data, and a recommendation that leaves the decision with the sponsor.
Developers say the user stories are too vague to estimate. What do you do?
Listen for: a refinement session with the people who will build it, examples and acceptance criteria added, and what you change in how you write the next stories.
A stakeholder adds new requirements during user acceptance testing. How do you respond?
Listen for: separating defects from new requests, the change route for new scope, and the impact on the go-live made clear to the person who decides.
You have a week to understand a process nobody has documented. Where do you start?
Listen for: talking to the people who do the work, watching it done, collecting real examples and exceptions, and checking your first map with them.
Business analysis questions
Walk me through a process you mapped and changed. What did the current state show, and what changed?
In the Interview Coach question bank
Listen for: what the current state showed, the change you proposed, who adopted it, and what was different afterwards.
How do you write acceptance criteria? Give me one from your last project.
Listen for: criteria a tester could check without asking you, written with the people who will build and test, and covering the main exceptions.
How do you keep requirements traceable from the original request to the test?
Listen for: the method or tool you used, how changes were handled, and one time traceability caught a gap.
Which modeling technique do you use most, and when did it change a decision?
Listen for: the technique (a process map, a data flow, use cases, a state diagram), why it fit that problem, and the decision it led to.
How do you decide what goes into the first release?
Listen for: the criteria (value, risk, dependency, effort), who decided, and what was left for later and why.
Stakeholder questions
How do you get time from busy subject matter experts?
Listen for: respect for their time, short focused sessions, coming prepared with examples, and showing them what their input changed.
Tell me about a time you disagreed with a senior stakeholder. What did you do, and how did it end?
In the Interview Coach question bank
Listen for: the disagreement, what you did to move it, and how it ended.
Tell me about a time you had to get people to act when they did not report to you.
In the Interview Coach question bank
Listen for: who had to act without reporting to you, the steps you took and what they did.
Metrics and evidence questions
How did you measure whether the process change worked?
Listen for: the measure, its value before the change, its value after, and where both came from.
Which data did you analyze yourself, with which tool, and what did it show?
Listen for: the data, the tool you used yourself, and the finding. Name only tools you can talk through in detail.
Which defects or change requests came from requirements gaps on your last project, and what did you change?
Listen for: an honest look at your own work, the pattern you found, and the change in how you work since.
Practice these with Interview Coach in Claude
Interview Coach has a business analyst track for business, process and systems analyst titles. The questions marked above as in its bank come from it, and it adds questions that quote your own resume lines and the requirements of the posting.
- Paste your resume and the job posting. Interview Coach returns the lines a hiring manager is likely to ask about, each as a question that quotes your own line, with the points a strong answer covers.
- It matches the requirements of the posting to your resume and turns the gaps into questions to prepare.
- Write one answer at a time and ask for a check. It looks for a situation, your own action, a result and a before and after figure or a named record. It does not judge whether the story is true.
Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.
Free in Claude, no account. We do not store the text you send through it.
Resources
Your answers start from your resume. The resume guide for this role shows how to write each line so you can back it up.
- Resume guide: Business analyst resume guide
Questions
What do hiring managers listen for in business analyst interview answers?
They listen for how you got from an unclear need to something a team could build and test: the people you talked to, the technique you used, the decision your analysis supported and how you checked the result. Lists of documents and tools tell them little on their own.
Should I bring examples of my work to a business analyst interview?
Describe them rather than share them if they belong to an employer or a client. You can walk through the structure of a process map or a set of acceptance criteria without showing confidential content. Ask before you share anything.
How technical should I be in a business analyst interview?
It depends on the posting. Some business analyst roles expect data work in SQL or a reporting tool, others focus on process and requirements. Name only the tools you have used yourself, and be ready to say what you did in each one.
Keep going
- Role hub: Business analyst resume and career help
- Related: Product owner interview questions
- Related: Project manager interview questions
- Guide: AI resume review: what Reed checks
Last updated: October 13, 2026