Open app

Interview questions · Business analyst

Business analyst interview questions and how to answer them

Updated 3 November 2026

A business analyst interview checks whether you can understand what a business actually needs, turn it into clear requirements, and keep everyone aligned while it is built. Expect questions about requirements, stakeholders, process mapping, prioritisation and handling change. These are the questions that come up most, with what each one checks and an example answer you can adapt.

Reading answers helps, but saying them out loud is what makes them stick. When you are ready, run a free mock interview with these questions.

Try 3 questions now. No sign-up.

Answer out loud, like in the real interview, and get instant feedback on each answer.

The 12 questions

  1. Walk me through how you gather requirements.
  2. How do you handle stakeholders who want conflicting things?
  3. Tell me about a project where you improved a business process.
  4. What is the difference between functional and non-functional requirements?
  5. How do you prioritise requirements?
  6. Which tools and techniques do you use?
  7. How do you handle a change request in the middle of a project?
  8. How do you make sure developers understand the requirements?
  9. Tell me about a time a project did not go to plan.
  10. How would you explain a technical solution to a non-technical stakeholder?
  11. How do you know a project was successful?
  12. Do you have any questions for us?

1. Walk me through how you gather requirements.

What they are checking: Whether you have a structured approach.

How to answer: Explain the steps: understand the business goal, identify stakeholders, use interviews or workshops to find needs, write them down clearly, and confirm them with the people who asked.

Example answer: “I start with the business goal and who's affected. Then I run short interviews or a workshop with each group, document requirements as user stories with acceptance criteria, and play them back to stakeholders to confirm I've understood before anything gets built.”

2. How do you handle stakeholders who want conflicting things?

What they are checking: Whether you can manage people, not only documents.

How to answer: Show that you understand each side's real goal, make the trade-off visible, and get a decision from the right person rather than deciding yourself.

Example answer: “I find out what each side is actually trying to achieve, because often the conflict is about the solution, not the goal. If it's a real trade-off, I lay out the options and their impact and take it to the product owner or sponsor for a decision.”

3. Tell me about a project where you improved a business process.

What they are checking: Results, and whether you can explain them.

How to answer: Use the STAR order: situation, task, action, result. Include a before and after if you can.

Example answer: “Invoice approval was taking around two weeks because it went through four people by email. I mapped the process, found two approvals that added nothing, and worked with finance to automate the rest. Approval time dropped to a few days.”

4. What is the difference between functional and non-functional requirements?

What they are checking: Basic BA knowledge.

How to answer: Functional requirements describe what the system does. Non-functional requirements describe how well it does it: speed, security, availability, usability. Give an example of each.

Example answer: “Functional is what the system does, like "the user can reset their password by email." Non-functional is how well, like "the reset email arrives within one minute" or "the page meets accessibility standards."”

5. How do you prioritise requirements?

What they are checking: Whether you can say no and justify it.

How to answer: Mention a method such as MoSCoW (must, should, could, won't), and that you base priority on business value, risk and effort, agreed with stakeholders.

Example answer: “I usually use MoSCoW with stakeholders, but the real conversation is value against effort and risk. I make sure "must have" really means the release fails without it, otherwise everything ends up a must.”

6. Which tools and techniques do you use?

What they are checking: Whether your skills match their way of working.

How to answer: Be honest about tools (Jira, Confluence, Visio or similar, Excel, SQL) and techniques (process maps, user stories, use cases, wireframes).

Example answer: “Day to day I use Jira and Confluence for stories and documentation, and draw process maps in BPMN. I'm comfortable with Excel and basic SQL for checking data, and I sketch simple wireframes when a screen is easier to discuss than text.”

7. How do you handle a change request in the middle of a project?

What they are checking: Whether you control scope without blocking the business.

How to answer: Explain that you assess the impact on time, cost and other requirements, document it, and get a decision from the sponsor before it is added.

Example answer: “I assess what it affects: timeline, cost, and other requirements. Then I write it up with options and take it to whoever owns the budget or scope. Nothing gets added quietly, because that's how projects slip.”

8. How do you make sure developers understand the requirements?

What they are checking: Whether your work actually gets built correctly.

How to answer: Talk about clear acceptance criteria, walking the team through stories, being available for questions, and reviewing what was built.

Example answer: “I write acceptance criteria that can be tested, walk the team through new stories in refinement, and stay available while they build. Before a story is closed, I check it against the criteria with the tester.”

9. Tell me about a time a project did not go to plan.

What they are checking: Honesty, and what you learn.

How to answer: Pick a real example, say what went wrong, what you did about it, and what you do differently now.

Example answer: “On one project we discovered late that the warehouse team hadn't been consulted, and the new process didn't work for them. We had to rework part of it. Since then I do a stakeholder map at the start, so nobody affected is missed.”

10. How would you explain a technical solution to a non-technical stakeholder?

What they are checking: Communication, which is most of the job.

How to answer: Lead with the business outcome, avoid jargon, use a simple picture or example, and check understanding.

Example answer: “I start with what changes for them: what they'll be able to do and when. I use a simple diagram or a before-and-after example, skip the jargon, and ask them to tell me back how they'd use it.”

11. How do you know a project was successful?

What they are checking: Whether you think about outcomes, not just delivery.

How to answer: Talk about agreeing success measures at the start and checking them after launch, not only whether the project shipped on time.

Example answer: “I agree measures with the sponsor at the start, like processing time or error rate, and check them a few weeks after launch. Shipping on time is good, but it only counts if the problem we set out to fix is actually fixed.”

12. Do you have any questions for us?

What they are checking: Interest in how the team works.

How to answer: Ask how BAs work with product and development, what the biggest current project is, and how requirements are documented today.

Example answer: “How do business analysts work with the product and development teams here? And what's the biggest project the team is working on right now?”

Practise these out loud. Enter the company and the role, paste your CV, and Nail My Interview plays the interviewer: it asks questions like these, listens to your answers and scores them afterwards. Your first full mock interview is free.

Start a free mock interview

More interview questions