# Business analyst interview questions and how to answer them

Business analyst interviews test whether you can find out what people actually need, settle conflicting requests, document how work really happens and turn a vague ask like "we need a dashboard" into requirements a team can build. Answer by naming the questions you asked, the people you spoke to, the document you produced and how you confirmed it was right.

By the Speaking Coach team at Sodhera Intelligence. Updated 2026-10-22. Source: https://www.orecci.com/speaking-coach/interview-questions-by-role/business-analyst/

## What a business analyst interview is really about

A BA sits between the people who have a problem and the people who will build the fix. So the interview checks two things: can you get the truth out of busy, sometimes contradictory people, and can you write it down so nobody has to guess? Most questions are behavioral ("tell me about a time") with a scenario or two thrown in.

Your best evidence is the artifacts you made and the questions you asked. Name them.

## Gathering requirements

Interviewers want to hear more than "I hold workshops." Say which technique you choose and why.

| Technique | When you'd use it |
| --- | --- |
| One-to-one interviews | Senior stakeholders, sensitive topics, or early discovery |
| Workshops | Several teams need to agree on one process |
| Job shadowing | People say one thing and do another, or can't describe their own steps |
| Document and data review | Before meeting anyone, to ask better questions |
| Prototypes or mockups | Users struggle to react to written requirements |

Example answer (made-up details):

> "For a new claims intake system, I started by reading three months of complaint emails so I knew the pain points. Then I interviewed the two team leads separately and sat with four claims handlers for half a day each. Shadowing was where the real requirements came from: they kept a personal spreadsheet the leads didn't know about, because the old system couldn't flag duplicate claims. Duplicate detection became our top requirement."

## Turning a vague ask into specs

This often comes as a scenario: "The director says, 'We need a dashboard.' What do you do?" Show that you ask about decisions before data.

1. **What decision will this help you make?** "Whether to hire more staff in Q3."
2. **Who will use it, and how often?** "Me and three managers, every Monday."
3. **What do you look at today?** "A spreadsheet that takes a day to build."
4. **What would make you trust it?** "Matching the finance numbers."
5. **What's the smallest useful version?** "Weekly volume by team, against target."

Then write it back as specific requirements and acceptance criteria, and confirm them with the director before anyone builds anything.

> "As a regional manager, I want to see weekly ticket volume per team against target, so that I can decide on overtime by Monday noon. Accepted when: numbers match the finance report within 1%, data is refreshed by 8 a.m. Monday."

Saying a user story out loud like that, in the interview, shows you can do the job. Open questions are the core tool here; see [what an open-ended question is](/speaking-coach/glossary/open-ended-question/).

## Conflicting stakeholder needs

Show that you surface the conflict early, trace it back to goals and get a decision from the right person.

> "Sales wanted the order form to have as few fields as possible; compliance wanted six extra checks. Rather than negotiate field by field, I mapped each compliance check to the rule it covered. Two were legally required, four were habit. I took that one-page map to both heads together. We kept the two required checks, moved one to after the order and dropped three. Both signed the updated requirements."

If you couldn't resolve it, say who owned the decision and how you laid out the options.

## Documenting processes

Be specific about the format and the level of detail.

- **As-is first, to-be second.** Map how work happens today, including workarounds, before designing the new process.
- **Swimlane diagrams** for processes that cross teams, so hand-offs are visible.
- **Plain language next to the diagram.** Not everyone reads process notation.
- **A walkthrough with the people who do the work.** If they say "that's not what happens," the diagram is wrong.

Name the tools you've used, such as Visio, Lucidchart, Confluence or Jira, but tie each to something you produced.

## Mistakes to avoid

- **Treating stakeholders' first request as the requirement.** Show the question that found the real need.
- **No artifact in the story.** Mention the document, story or diagram you produced.
- **Taking sides in conflicts.** You lay out options; the owner decides.
- **Jargon without explanation.** If you say "BPMN" or "MoSCoW," explain it in a few words.

The "we need a dashboard" scenario is worth practicing out loud with someone playing the stakeholder. Speaking Coach can play that director and respond to the questions you actually ask.

## Questions people ask

### How is a business analyst different from a data analyst?

A business analyst defines what a process or system needs to do. A data analyst analyzes data to answer questions. There's overlap, especially in reporting projects. See [data analyst interview questions](/speaking-coach/interview-questions-by-role/data-analyst/).

### Do BA interviews include technical questions?

Sometimes: basic SQL, how APIs or databases work, or how you'd test a requirement. Depth depends on the role, so check the job post.

### How do I answer if I've never had the BA title?

Use times you clarified what someone needed and wrote it down for others: a process you documented, a system change you specified, a form you redesigned.

### What if requirements change halfway through?

Say how you captured the change, assessed its impact with the team and got the owner to approve it. Changing requirements are normal; unmanaged changes are the problem.

---
Speaking Coach on the App Store: https://apps.apple.com/app/id6767124039
Speaking Coach on Google Play: https://play.google.com/store/apps/details?id=com.sodhera.speakingcoach