Perimattic
Interview questions

Business analyst interview questions: 26 questions with answers

Requirements elicitation, user stories and acceptance criteria, BPMN process maps, MoSCoW, stakeholder management and SQL: the questions BA interviewers ask and how to structure your answers.

26 questionsIncludes SQLEntry to senior

Last updated 22 October 2026

Hand drawing a flowchart diagram on a whiteboard
Overview

What do business analyst interviews test?

Business analyst interviews test whether you can draw out the real need behind a request, write clear requirements and user stories with testable acceptance criteria, map processes, manage competing stakeholders and prioritize scope. Many also include basic SQL or data questions, and behavioral questions about conflicting requirements and missed requirements.

What gets tested

What skills do business analyst interviewers assess?

Business analyst interviews for IT, banking, consulting and product teams cover a similar set of skills. Entry level interviews focus on fundamentals such as requirement types and user stories; senior interviews dig into stakeholder conflict, scope control and how you shape the solution.

Skill areaWhat interviewers want to seeTypical format
Requirements elicitationThe right technique for the situation, and the need behind the request“How would you” questions
User stories and acceptance criteriaClear stories with testable Given/When/Then criteriaWrite one live
Process modelingReadable as-is and to-be maps using BPMN basicsWhiteboard exercise
PrioritizationMoSCoW or value versus effort, applied with disciplineScenario questions
Stakeholder managementHandling conflict and disengagement without losing trustBehavioral questions
Data and SQLJoins, aggregation and a sense of data qualityShort SQL test or verbal query

The top 26 business analyst interview questions below cover each area, grouped by type. SQL answers use standard SQL and note where syntax differs between databases. Use the STAR structure (situation, task, action, result) for the behavioral ones.

Core BA practice

Which core business analysis questions should you expect?

6 questions in this group.

1. What does a business analyst do, and how is the role different from a product manager’s?

Entry level

What the interviewer looks for: A clear view of the BA as the bridge between business need and solution, and an honest note that boundaries vary by company.

How to answer:

  • A BA understands the business problem, elicits and documents requirements, models processes and checks the solution meets the need.
  • A product manager usually owns the product’s direction, priorities and outcomes over time.
  • In many teams the roles overlap; say how you would agree responsibilities with the PM.

2. Which requirements elicitation techniques do you use, and how do you choose between them?

Entry level

What the interviewer looks for: Several techniques and a reason for each choice, rather than "I just talk to the users".

How to answer:

  • Interviews for depth with key stakeholders; workshops to resolve views across groups quickly.
  • Observation or job shadowing when users find it hard to describe what they do.
  • Document analysis, surveys for large groups, and prototypes or wireframes to test understanding.
  • Choose based on the number of stakeholders, how well the process is understood and the time available.

3. How do you carry out a gap analysis between the current and future state of a process?

Mid level

What the interviewer looks for: A structured as-is to to-be comparison that ends in actionable changes.

How to answer:

  • Map the as-is process with the people who do it, including workarounds.
  • Define the to-be state from the business goals.
  • List the gaps in process, people, data and systems, then size and prioritize the changes to close them.

4. How do you plan and run user acceptance testing?

Mid level

What the interviewer looks for: UAT seen as business users confirming the solution meets their needs, with clear entry and exit criteria.

How to answer:

  • Write scenarios from the acceptance criteria and real business cases, with test data.
  • Pick business testers, agree the schedule and the entry criteria (for example system testing complete).
  • Log defects with severity, triage them daily and agree the exit criteria for sign-off.

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

Mid level

What the interviewer looks for: Impact analysis and a decision by the right people, not silently absorbing the change or refusing it.

How to answer:

  • Capture the request and the reason behind it.
  • Analyze the impact on scope, timeline, cost and other requirements with the team.
  • Take it to the decision maker or change board with options, then update the backlog and documents.

6. How would you measure whether a process improvement you recommended worked?

Mid level

What the interviewer looks for: A baseline taken before the change and metrics tied to the original goal.

How to answer:

  • Agree the goal and the metric before the change, such as cycle time or error rate.
  • Capture a baseline and measure over a comparable period after the change.
  • Watch for side effects on other metrics and report honestly if the gain is small.
Technical

Which requirements, modeling and SQL questions come up?

10 questions in this group.

7. What is the difference between functional and non-functional requirements? Give an example of each.

Entry level

What the interviewer looks for: Correct definitions and testable examples, especially for non-functional requirements.

How to answer:

  • Functional: what the system must do, such as "the user can download an invoice as PDF".
  • Non-functional: how well it must do it, such as performance, security, availability, usability.
  • Make non-functional requirements measurable, for example "search returns results within 2 seconds for 95% of requests".

8. Write a user story with acceptance criteria for resetting a forgotten password.

Entry level

What the interviewer looks for: The standard story format, a clear user benefit and testable criteria that cover the unhappy paths.

How to answer:

  • Story: "As a registered user, I want to reset my password by email so that I can get back into my account."
  • Given I request a reset for a registered email, when I submit, then a single-use link is sent that expires after a set time.
  • Given the link has expired or was already used, when I open it, then I see an error and can request a new one.
  • Add criteria for password rules and for not revealing whether an email is registered.

9. How do you know a user story is ready for development?

Mid level

What the interviewer looks for: Knowledge of INVEST and a practical definition of ready.

How to answer:

  • INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable.
  • Acceptance criteria are agreed, dependencies and open questions are resolved, and designs are attached if needed.
  • The team has discussed and estimated it, for example in backlog refinement.

10. Explain MoSCoW prioritization. What are its weaknesses?

Entry level

What the interviewer looks for: An accurate definition and awareness that everything tends to become a Must without discipline.

How to answer:

  • Must have (the release fails without it), Should have (important but has a workaround), Could have (desirable), Won’t have this time.
  • Weakness: stakeholders push items into Must; agree in advance a cap or criteria for Musts.
  • It does not rank items within a category, so pair it with value and effort when ordering work.

11. How would you model a loan approval process in BPMN? Name the main elements you would use.

Mid level

What the interviewer looks for: Correct use of BPMN basics and a readable model of a real process.

How to answer:

  • Pools for organizations and lanes for roles, such as applicant, loan officer and credit team.
  • Start and end events, tasks for the work steps, and sequence flows between them.
  • An exclusive gateway for the approve or reject decision; message flows between pools.
  • Model the happy path first, then add exceptions such as missing documents.

12. What is a requirements traceability matrix and why is it useful?

Mid level

What the interviewer looks for: Understanding that traceability links requirements forward to design and tests and back to business goals.

How to answer:

  • A table linking each requirement to its source, design items, test cases and status.
  • It shows whether every requirement is built and tested and whether anything built has no requirement.
  • It speeds up impact analysis when a requirement changes.

13. What goes into a business requirements document versus a functional specification?

Mid level

What the interviewer looks for: Knowing the audience and level of each document, and that agile teams often use lighter artifacts.

How to answer:

  • BRD: the business problem, objectives, scope, stakeholders, high-level requirements and success measures.
  • Functional spec: detailed system behavior, rules, data, screens and interfaces for the delivery team.
  • In agile teams the same content may live in epics, stories and a wiki; the format matters less than clarity.

14. Write a SQL query to list customers who have placed no orders in the last 90 days.

Mid level

What the interviewer looks for: A correct anti-join and awareness of NULL pitfalls and dialect differences in date arithmetic.

How to answer:

  • SELECT c.customer_id, c.name FROM customers c WHERE NOT EXISTS (SELECT 1 FROM orders o WHERE o.customer_id = c.customer_id AND o.order_date >= CURRENT_DATE - INTERVAL '90' DAY);
  • Date syntax varies by database: for example DATEADD(day, -90, GETDATE()) in SQL Server.
  • A LEFT JOIN with WHERE o.order_id IS NULL also works; avoid NOT IN on a column that can be NULL, because one NULL makes it return no rows.

15. What is the difference between WHERE and HAVING in SQL?

Entry level

What the interviewer looks for: Correct order of evaluation and a simple example.

How to answer:

  • WHERE filters rows before grouping; HAVING filters groups after GROUP BY and aggregation.
  • Example: WHERE order_date >= '2026-01-01' … GROUP BY customer_id HAVING COUNT(*) > 5.
  • Filter in WHERE whenever you can, because it reduces the rows that are grouped.

16. How would you count distinct active customers per month from an orders table?

Mid level

What the interviewer looks for: Grouping by a truncated date and using COUNT(DISTINCT …), with a clear definition of "active".

How to answer:

  • Agree the definition first: one or more orders in the calendar month.
  • Group by the month, for example DATE_TRUNC('month', order_date) in PostgreSQL, and select COUNT(DISTINCT customer_id).
  • Check edge cases such as cancelled orders and time zones before sharing the numbers.
Behavioral

Which behavioral questions do BA interviewers ask?

6 questions in this group.

17. Tell me about a time two stakeholders wanted conflicting things. What did you do?

Mid level

What the interviewer looks for: Getting to the underlying needs and using shared goals or a decision maker to resolve it.

How to answer:

  • Situation: who the stakeholders were and what each wanted.
  • Action: how you uncovered the reason behind each request and found what they agreed on.
  • Result: the decision, who made it and how you documented it.

18. Describe a time a key stakeholder would not make time for requirements sessions.

Mid level

What the interviewer looks for: Persistence and creativity in getting input, and escalation when the risk was real.

How to answer:

  • Explain why their input mattered.
  • Describe what you tried: shorter sessions, a written draft to react to, a delegate.
  • Share the result and whether you had to raise the risk with the sponsor.

19. Tell me about a requirement you missed or got wrong. What happened?

Mid level

What the interviewer looks for: Ownership and a concrete change to how you elicit or validate requirements.

How to answer:

  • Describe the requirement and how the gap was found.
  • Explain how you helped fix it and limit the impact.
  • Say what you now do differently, such as walking through examples or prototypes with users.

20. Give an example of when you used data to change a stakeholder’s mind.

Mid level

What the interviewer looks for: Sound analysis presented simply and respectfully.

How to answer:

  • The belief or plan you questioned and why.
  • The data you gathered and how you checked it.
  • How you presented it and what decision followed.

21. Tell me about a time you explained a technical constraint to non-technical stakeholders.

Entry level

What the interviewer looks for: Translating technical detail into business impact and options.

How to answer:

  • What the constraint was and who needed to understand it.
  • How you explained it in terms of impact, using an analogy or visual if helpful.
  • The options you offered and what was decided.

22. Describe a project where requirements were unclear and the deadline was fixed.

Senior

What the interviewer looks for: Reducing ambiguity fast, making assumptions explicit and protecting the deadline with scope choices.

How to answer:

  • The context and what was unclear.
  • How you documented assumptions, got quick decisions and cut scope to essentials.
  • What was delivered and what you learned.
Scenarios

How would you handle these business analysis situations?

4 questions in this group.

23. Customer complaints about late deliveries have doubled. How would you find the root cause?

Mid level

What the interviewer looks for: Use of data and structured techniques before jumping to a solution.

How to answer:

  • Clarify the problem with data: which regions, products, carriers and time period.
  • Use techniques such as the 5 whys or a fishbone diagram with the operations team.
  • Test the likely causes against the data, then propose fixes with an owner and a metric to watch.

24. A department head says "we need a dashboard". What do you do next?

Mid level

What the interviewer looks for: Moving from a requested solution to the underlying problem and decision.

How to answer:

  • Ask what decisions the dashboard would support and who would use it, how often.
  • Find out what data exists and how those decisions are made today.
  • Confirm the need, then propose the simplest solution, which may be a report or an alert rather than a dashboard.

25. Developers say a story is too big to finish in one sprint. How do you split it?

Mid level

What the interviewer looks for: Splitting by user value (vertical slices), not by technical layer.

How to answer:

  • Split by workflow step, business rule, data variation or happy path first, then exceptions.
  • Make sure each smaller story still delivers something a user can test.
  • Avoid splitting into front-end and back-end stories that deliver nothing on their own.

26. Halfway through a project, a senior stakeholder keeps adding "small" requests. How do you respond?

Senior

What the interviewer looks for: Protecting the agreed scope politely while keeping the stakeholder on side.

How to answer:

  • Log every request and assess its impact, however small it seems.
  • Show the cumulative effect on timeline and cost.
  • Offer options: swap with lower-value items, defer to a later release, or extend the timeline with the sponsor’s approval.
Preparation

How should you prepare for a business analyst interview?

WhenWhat to do
1 week beforeRead the job description and note the domain, methodology (agile or waterfall) and tools. Prepare three or four STAR stories on stakeholder conflict, a missed requirement and a process you improved. Practice joins, GROUP BY and HAVING on a sample database.
1 day beforeWrite one user story with acceptance criteria and sketch one process map from your experience so you can draw it from memory. Prepare questions about how the team handles requirements and change.
During the interviewAsk clarifying questions before solving any case, think aloud on SQL and modeling tasks, and tie every answer back to the business problem and how you would measure success.

To rehearse, open the mock interview practice tool set to business analyst and answer timed questions, or use the interview question generator for business analysts to build a fresh set by level and question type.

AI Interview

How does Perimattic AI Interview help with business analyst interviews?

Perimattic AI Interview is a product from Perimattic for candidates and hiring teams. For business analyst roles, it offers:

  • Conversational mock interviews by role and level, with spoken or typed answers.
  • Feedback on each answer against a rubric covering structure, relevance and depth, plus a summary report.
  • Role-based question banks, including the questions on this page, and MCQ skill tests.
  • For employers: structured first-round interviews with the same questions for every candidate, recorded answers, transcripts and reports for human reviewers.
  • Human review stays in control: the AI does not make hiring decisions.

Get started: Sign up and our team will walk you through Perimattic AI Interview for the way you prepare for or run interviews.

Two colleagues discussing a diagram on a whiteboard in an office
FAQs

Business analyst interviews, answered

How much SQL does a business analyst interview need?

It varies by company, but many expect you to filter, join and aggregate: SELECT with WHERE, JOINs including LEFT JOIN, GROUP BY with HAVING, COUNT(DISTINCT) and simple subqueries. Data-heavy BA roles may add window functions. Ask the recruiter whether there is a SQL test, and practice on a sample database rather than only reading syntax.

Do I need a certification such as ECBA or CBAP to get a business analyst job?

Usually not. Certifications from IIBA, such as ECBA or CBAP, can help show structured knowledge, particularly if you are switching careers, but interviewers mostly judge how you elicit requirements, write stories and handle stakeholders. Check the job description; some employers and consulting firms list a certification as preferred.

How do I answer business analyst questions if I have no BA job experience?

Draw on projects where you did BA work under another title: gathering requirements for a college project, improving a process at work, or building a report for a team. Use the STAR structure, name the techniques you used, and bring a short sample, such as a user story with acceptance criteria or a simple process map.

Talk to our team

Want to rehearse a business analyst interview out loud?

Sign up to tell us how you prepare for or run interviews, and our team will get in touch to walk you through Perimattic AI Interview.

Sign up