How to prepare for a business analyst interview
Last updated:
The short answer
To prepare for a business analyst interview, first read the posting for the type of analyst the team needs. Then prepare four work samples to talk through: a process map, a user story, a requirement tied to its test and a test cycle. Ready five stories with I, and practice one live exercise out loud.
Key points
- Decide which type of analyst the posting wants before you choose your stories.
- Bring work samples you can describe without showing anything confidential.
- Ready stories on elicitation, a process change, testing, a disagreement and a requirement you got wrong.
- Expect a live exercise, such as writing user stories or mapping a process in the room.
Practice your answers in Claude with Interview Coach, free
Read the posting for the type of analyst
"Business analyst" covers several jobs. The posting tells you which one, and your preparation should follow it.
| Type of analyst | What the posting says | What to prepare |
|---|---|---|
| Systems or IT analyst | Requirements, integrations, user acceptance testing | A requirement tied to its test, and a test cycle |
| Process analyst | Current and future state, process improvement | A process map and the change it led to |
| Data-facing analyst | Reports, queries, dashboards | A query you wrote and the decision it supported |
| Product-facing analyst | Backlog, user stories, acceptance criteria | Stories you wrote and how the team used them |
| Domain analyst | Lending, claims, clinical or another field | The rules of the field that shaped a requirement |
Many roles mix two types. Pick the two that appear most often in the posting and weight your preparation toward them.
Prepare four work samples to talk through
Analyst interviews often ask "show me how you would" rather than "tell me about a time." Have four samples ready in your head, rebuilt from memory with invented names.
- A process map. The steps, the roles, the handoffs and the one step you changed.
- A user story with acceptance criteria. One story, three criteria, and how the tester used them.
- A requirement tied to its test. From the stakeholder's words to the test that proved it.
- A test cycle. How many scenarios, how defects were triaged and what decided go-live.
Never bring a real client's documents. Describe the shape of the work instead, and keep the real details for your own notes.
Ready five analyst stories
Each story needs your own actions with I, a result and the record that shows it. The table maps each story to the questions it can answer.
| Story to ready | What it proves | Questions it can answer |
|---|---|---|
| Two groups who described one process differently | You can elicit and reconcile | Elicitation, conflicting requirements, stakeholders |
| A process change you proposed | You improve, not only document | Process, efficiency, influence |
| A test cycle before a go-live | You protect quality | Testing, defects, readiness |
| A stakeholder who rejected your analysis | You hold a position with evidence | Conflict, influence, pressure |
| A requirement you got wrong | You own your part | Failure, learning, feedback |
Questions to rehearse
- How do you run an elicitation session? They listen for preparation, who attends and how you check what you heard.
- Tell me about two stakeholders with conflicting requirements. They want how you found the real need behind each one.
- Walk me through a process you mapped. They listen for the step you changed and why.
- How do you write acceptance criteria? They want testable conditions, not restated features.
- How do you prioritize requirements? They listen for a method and who makes the final call.
- Tell me about a defect found late. They want how it was missed and what you changed.
- How do you work with developers who disagree with a requirement? They listen for evidence and openness.
- What tools have you used for requirements and diagrams? They want depth in a few, not a list.
- How do you know a delivered change worked? They listen for a measure agreed before go-live.
- Why business analysis? They want a reason grounded in work you enjoyed.
Practice a live exercise
Some panels hand you a short scenario and ask you to work on it in the room. It might be "write the user stories for a password reset" or "map how a refund is approved." The panel scores how you ask and structure, not a perfect answer.
- Ask who the users are and what problem the change solves.
- Say your assumptions out loud before you write.
- Start with the main path, then add the exceptions.
- Write acceptance criteria a tester could follow.
- End by naming what you would confirm with the business next.
Answer examples
Each answer below gets every mark of its rubric in the answer check of Interview Coach.
Two groups who described one process differently (story rubric):
When a hospital asked for a new referral form, the clinic managers and the nurses described two different processes. I ran separate sessions with each group and I wrote down every step they used. I mapped both versions side by side and I showed the managers where the nurses skipped a step to save time. They agreed to one process with the shorter path. The form went live in March and referral rework fell from thirty cases a month to eight, per the referral queue report.
A process change you proposed (change rubric):
When the claims queue at an insurer grew every month, the cause was a rule that sent every large claim to a manager's inbox for sign-off. I mapped the current process with the claims team and I found that most approvals were never changed by the manager. I proposed a rule that let senior adjusters approve claims under a higher limit. I tested it with one team for a month and I reported the results to the claims director. She approved the rule for all teams. Average approval time fell from five days to two, per the claims system report.
A test cycle before go-live (story rubric):
Before a billing system went live, the business testers had a script but no clear pass rule. I wrote acceptance criteria for each of the forty scenarios with the billing lead. I ran a daily triage with the testers and the developers and I logged each defect against a scenario. I held the go-live review until the last high defect was closed. The system went live on the approved date with open high defects down from twelve to zero, per the test summary report.
Illustrative, not a real client.
Mistakes in business analyst preparation
- Tool lists instead of work. Naming six diagram tools says less than one process you changed.
- Documents as the result. A requirements document is an output. The result is what changed for the business.
- No data at all. Even a process analyst is asked how a change was measured. Have one figure with its source.
- Skipping the domain. For a lending, claims or clinical role, refresh the rules of the field that shape requirements.
Practice before the interview
Say each story out loud, then check one with the free STAR answer check. It marks a missing result, a missing record or an answer told only with we. Your resume will be read before the interview, and the business analyst resume guide shows the lines an interviewer may ask about.
Practice with Interview Coach in Claude
Interview Coach reads your resume and the business analyst posting, then asks about the requirements, processes and testing on your own resume. Write your answer the way you would say it and ask for a check.
- 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.
Questions
Do I need SQL for a business analyst interview?
It depends on the type of analyst the posting describes. Data-facing roles often include a short query exercise. Process and product-facing roles may only ask how you used data to support a decision.
How do I prepare for a business analyst interview with no analyst title?
Use the analysis you have done under another title, such as mapping a process at work or testing a system change. Say plainly what your title was and what you did. Prepare the live exercise with extra care, because it shows the skill directly.
What should I bring to a business analyst interview?
Bring the posting, your resume, your story list and a short list of questions for the panel. Do not bring a past client's documents. Be ready to sketch a process or a user story on paper or a shared screen.
