21 interview questions
Business analyst interview questions and answers
Business analyst interviews check whether you can find the real problem behind a request and turn it into requirements a team can build and test. Expect questions on elicitation techniques, documentation, process modelling and basic data skills, plus scenarios about conflicting stakeholders and changing requirements.
Updated
Requirements
01How do you gather requirements from stakeholders?
What they want to hear: A range of elicitation techniques and the judgment to pick the right one.
Answer outline
- Start with the business goal and identify who is affected.
- Use a mix of techniques: interviews, workshops, observation, document analysis, surveys.
- Ask why behind each request to reach the underlying need.
- Write it up, play it back and get confirmation.
02What is the difference between functional and non-functional requirements?
What they want to hear: A core concept, and whether you remember non-functional requirements in practice.
Answer outline
- Functional: what the system must do, such as 'the user can export a report as CSV'.
- Non-functional: how well it must do it, such as performance, security, availability, usability and compliance.
- Non-functional requirements are often missed and expensive to add later.
- Make both measurable, for example 'the report loads in under three seconds for 95 percent of requests'.
03How do you write a good user story?
What they want to hear: Whether your stories are clear, small and testable.
Answer outline
- Use the form 'As a [user], I want [goal], so that [benefit]'.
- Add acceptance criteria, for example in Given-When-Then form.
- Check it against INVEST: independent, negotiable, valuable, estimable, small, testable.
- Refine it with the team before it enters a sprint.
04How do you handle vague or changing requirements?
What they want to hear: Comfort with ambiguity and a controlled way to manage change.
Answer outline
- Ask clarifying questions and use examples or prototypes to make ideas concrete.
- Record assumptions and confirm them.
- Route changes through an agreed process with impact assessed.
- Keep traceability so everyone knows what changed and why.
05How do you prioritise requirements?
What they want to hear: A method plus the ability to facilitate the decision rather than make it alone.
Answer outline
- Tie each requirement to a business objective.
- Use a technique such as MoSCoW (must, should, could, won't) with stakeholders.
- Consider value, cost, risk and dependencies.
- Confirm priorities with the product owner or sponsor who has the final say.
Analysis and modelling
06How would you map and improve a business process?
What they want to hear: Practical process analysis, from current state to measured improvement.
Answer outline
- Document the current state with the people who do the work, using a flowchart or BPMN.
- Measure it: time, cost, errors, handoffs.
- Find the causes of waste or delay, such as rework, waiting or manual steps.
- Design the future state, agree it, and define how improvement will be measured.
07What is a gap analysis?
What they want to hear: That you can compare where a business is with where it wants to be and turn that into actions.
Answer outline
- Describe the current state and the desired future state.
- Identify the gaps in process, people, technology or data.
- Prioritise the gaps and propose actions to close them.
- Give an example from your work.
08Which diagrams or models do you use, and when?
What they want to hear: A practical toolkit used to communicate, not to impress.
Answer outline
- Process flows or BPMN for workflows.
- Use case diagrams or user journeys for how users interact with a system.
- Entity relationship diagrams for data, and context diagrams for system boundaries.
- Choose based on the audience and what needs to be understood.
09How do you perform a root cause analysis?
What they want to hear: Whether you fix causes or symptoms.
Answer outline
- Define the problem precisely, with data.
- Use techniques such as the five whys or a fishbone diagram with the people involved.
- Verify the suspected cause with evidence.
- Propose a fix and a way to confirm it worked.
Data and tools
10How comfortable are you with SQL? Give an example of a query you have written.
What they want to hear: Many BA roles need you to check data yourself rather than wait for someone else.
Answer outline
- Be honest about your level.
- Describe a real query: the question, the tables, the joins and the aggregation.
- Mention how you validated the result.
- Say how the result was used.
11How do you validate that the data behind a report is correct?
What they want to hear: Attention to data quality and healthy distrust of a single source.
Answer outline
- Understand where the data comes from and how it is transformed.
- Reconcile totals against a trusted source.
- Check edge cases: nulls, duplicates, time zones, filters.
- Document definitions so everyone reads the numbers the same way.
12Which tools do you use for documentation and tracking?
What they want to hear: Practical experience and adaptability.
Answer outline
- Name the tools you have used for requirements, diagrams, tracking and analysis.
- Describe how you kept documentation current and easy to find.
- Show you can work with the team's existing tools.
Stakeholders and delivery
13Two stakeholders give you conflicting requirements. What do you do?
What they want to hear: Facilitation and knowing when to escalate.
Answer outline
- Meet each to understand the goal behind their requirement.
- Bring them together with the facts and the impact of each option.
- Look for a solution that serves both goals.
- If they cannot agree, take it to the decision-maker and record the outcome.
14How do you work with developers and testers?
What they want to hear: Whether you stay involved after writing the requirements.
Answer outline
- Walk the team through requirements and answer questions early.
- Join refinement and clarify acceptance criteria.
- Support testers with scenarios and help triage defects.
- Keep requirements updated as decisions change.
15How do you make sure a delivered solution meets the business need?
What they want to hear: Focus on outcomes, not just sign-off.
Answer outline
- Trace requirements to test cases and confirm coverage.
- Support user acceptance testing with real users and scenarios.
- After go-live, measure against the original business objectives.
- Collect feedback and propose follow-up improvements.
16How do you explain a technical constraint to a business stakeholder?
What they want to hear: Translation is a core part of the role.
Answer outline
- Start with the impact on their goal, not the technical detail.
- Use a simple analogy or example.
- Offer options and the trade-offs of each.
- Check understanding and agree next steps.
Experience
17Tell me about a time you discovered the real requirement was different from what was asked.
What they want to hear: Your ability to dig beneath a stated solution to the actual need.
Answer outline (STAR)
- The original request.
- How you found the underlying need: questions, observation, data.
- How you raised it and changed the plan.
- The result compared with what would have happened otherwise.
18Describe a time your analysis saved time or money.
What they want to hear: Measurable business impact.
Answer outline (STAR)
- The problem and how it was costing the business.
- Your analysis and recommendation.
- How it was implemented.
- The saving, with a number if you can honestly give one.
19Tell me about a time a requirement you wrote was misunderstood.
What they want to hear: Ownership and better habits afterwards.
Answer outline (STAR)
- What was misunderstood and how it came to light.
- Your part in the misunderstanding.
- How you fixed it with the team.
- What you changed in how you write and confirm requirements.
20Tell me about a time you had to get buy-in for a change people resisted.
What they want to hear: Change management and persuasion skills.
Answer outline (STAR)
- The change and who resisted it.
- How you understood their concerns.
- How you involved them and adjusted the plan.
- The result and the level of adoption.
21How do you get up to speed in a new business domain?
What they want to hear: Learning speed and method, since BAs often move between domains.
Answer outline
- Read existing documentation and process maps.
- Spend time with the people who do the work.
- Build a glossary and check it with experts.
- Ask questions early, before assumptions settle in.
How to prepare
- Prepare one example document you can describe in detail: a set of user stories, a process map or a requirements specification, with confidential details removed.
- Practise turning a vague request into clear requirements out loud. Scenario questions often work this way.
- Refresh basic SQL and spreadsheet skills; many interviews include a short data exercise.
- Have stories ready about conflicting stakeholders, a misunderstood requirement and an improvement you measured.
- Learn the business of the company you are interviewing with, so your examples and questions fit their domain.
Practice these questions out loud with NORDON
Reading answers is not the same as saying them. NORDON's interview practice asks you questions written for the role, listens to your spoken answer and shows you how to make it stronger.
- Upload your CV in the Knowledge base, so questions and feedback use your real background.
- Open Practice, enter the role (for example business analyst), paste the job ad if you have it, and choose 3, 5, 8 or 10 questions and the answer language.
- Listen to each question and answer out loud, as you would in the room. You can also type an answer.
- Get a score from 1 to 10, what worked, what to improve and a stronger answer to rehearse. It uses only what you said and your documents, and leaves a [placeholder] where a fact about you is missing.
- Try the question again, or move on. For a dress rehearsal, run a mock call where an interviewer voice asks the questions out loud.
The free plan includes 10 scored practice answers a month and mock calls of up to 10 minutes, no card needed. Paid plans include more practice and mock calls of up to 30 minutes. How practice works
Practice is for preparing. Use live help in a real interview only where the interviewer allows AI assistance, never in an interview, test or assessment whose rules forbid it.
Preparing for your business analyst interview
What does a business analyst interview usually include?
Often a screening call, an interview with the hiring manager and team, and sometimes a case study or exercise such as writing user stories or mapping a process. The exact format varies by company and industry.
Do business analysts need technical skills?
It depends on the role. Many BA roles expect basic SQL, comfortable spreadsheet work and an understanding of how software is built. Some IT-focused roles go further into data or system integration.
How do I prepare for a business analyst case study?
Practise with a simple scenario: identify stakeholders, ask clarifying questions, map the current process, find the problems and write a few requirements with acceptance criteria. Explain your reasoning as you go.