Autocoder

Business Analyst Interview Questions and Answers

Last updated 2026-11-19

Business analyst interviews test three things: whether you can turn a vague request into clear requirements, whether you can work with stakeholders and delivery teams, and whether you can back recommendations with data. Expect a mix of process questions (requirements, documents, Agile), a scenario or case, and basic SQL and Excel.

The answers below are written the way you would say them in an interview, with a small example in each. If your tools are the weak spot, read how to crack the data analyst interview and the SQL interview guide; the metric-heavy end of the role overlaps with product analyst interview questions.

Typical roundsRequirements and process questions, case study, SQL or Excel, stakeholder scenarios
Core skillsRequirements, documentation, SQL, Excel, stakeholder management
Questions here13 worked questions

What the role covers

A structure for scenario questions

Clarify the objective and the stakeholders, define the problem with data, find root causes, list options with cost, benefit and risk, recommend one with a rollout and success measure, and say what you would monitor. Naming each step aloud makes an average answer sound organised, and it keeps you from jumping straight to a solution.

Business Analyst Interview Questions and Answers: questions with worked answers

  1. 1

    What does a business analyst do, and how does the role differ from a data analyst?

    easy

    A business analyst defines what should be built or changed: gathering requirements, mapping processes, documenting them and ensuring the delivered solution meets the business need. A data analyst answers questions with data: querying, cleaning, analysing and visualising. The roles overlap in reporting and metrics, but the business analyst focuses on stakeholders, requirements and process change, and the data analyst on analysis and insight. Smaller teams combine them, so read the job description.

  2. 2

    What techniques do you use to elicit requirements?

    easy

    Interviews with stakeholders for depth, workshops to resolve conflicting needs quickly, observation of the real process, document and report analysis, surveys for large user groups and prototypes or wireframes to get concrete feedback. Use several, because people forget steps they do automatically and tell you what they want rather than what they need. Confirm what you heard by writing it back and getting sign-off.

  3. 3

    Differentiate BRD, FRD and SRS.

    medium

    A Business Requirements Document states the business goals, scope and high-level needs: why the project exists. A Functional Requirements Document describes what the system must do from the user's point of view: features, inputs, outputs and rules. A Software Requirements Specification is a more technical, complete description of functional and non-functional requirements, such as performance, security and constraints, used by developers and testers. Agile teams often replace much of this with a backlog of user stories and a lighter product document.

  4. 4

    Write a good user story with acceptance criteria.

    medium

    A user story follows the form: as a role, I want a capability, so that a benefit. It should be independent, small enough for a sprint, testable and valuable. Acceptance criteria state the conditions for done. Example story: as a customer, I want to reset my password by email so that I can regain access without calling support. Criteria: the link expires after 30 minutes; the link works once; a message appears for an unknown email without revealing whether the account exists; the new password must meet the policy.

  5. 5

    Explain MoSCoW prioritisation with an example.

    easy

    MoSCoW sorts requirements into Must have (the release fails without them), Should have (important but a workaround exists), Could have (nice if time allows) and Won't have this time (agreed out of scope). For an online ticket booking release: seat selection and payment are Must, email confirmation is Should, saved cards are Could, and loyalty points are Won't for now. Keep Musts to about 60 percent of effort so that there is room for risk. Other methods include RICE scoring and the Kano model.

  6. 6

    How do you analyse and manage stakeholders?

    medium

    List stakeholders and place them on a power and interest grid. High power and high interest stakeholders, such as the sponsor, are managed closely with regular updates and decisions. High power and low interest are kept satisfied with brief summaries. Low power and high interest, often end users, are kept informed and consulted for requirements. Low power and low interest are monitored. Agree a communication plan, identify conflicts early and escalate with options, not complaints.

  7. 7

    How do you handle conflicting requirements or scope creep?

    medium

    For conflicts, bring the stakeholders together, restate each need as a business objective, and use impact, cost and the project goals to decide, escalating to the sponsor if there is no agreement. For scope creep, use a change control process: record the request, assess its effect on cost, time and risk, and let the sponsor approve, defer or reject it. Small useful changes can be traded for lower-priority items rather than extending the deadline. Document every decision.

  8. 8

    What is a gap analysis and how is it done?

    medium

    It compares the current state with the desired state and identifies what is missing. Document the as-is process or system, define the to-be goals, list the differences in people, process, data and technology, estimate the effort and risk of closing each gap, and prioritise. For example, if orders are entered manually from email (as-is) and should arrive from a portal (to-be), the gaps include a portal, validation rules, a data migration and staff training.

  9. 9

    What is a Requirements Traceability Matrix and why is it used?

    easy

    An RTM links each requirement forward to design items, test cases and delivery status, and backward to the business objective it serves. It shows that every requirement is built and tested, and that nothing was built without a requirement. It also supports impact analysis: when a requirement changes, you can see which designs and tests are affected. A simple version is a table with requirement id, description, source, priority, test case id and status.

  10. 10

    Agile versus Waterfall: where does the business analyst fit?

    easy

    Waterfall completes phases in sequence (requirements, design, build, test, release), which suits stable, well-understood needs and fixed contracts, but feedback arrives late. Agile delivers in short iterations with continuous feedback, which suits changing needs. In Scrum, the analyst helps the product owner write and refine the backlog, writes stories and acceptance criteria, answers questions during the sprint, supports demos and acceptance testing, and keeps documentation light but sufficient.

  11. 11

    Write a SQL query for monthly revenue and top 3 categories by revenue in each month.

    medium

    Aggregate revenue by month and category, then rank categories inside each month with a window function and keep ranks 1 to 3. Ranking must happen after aggregation, so use a subquery or CTE. If categories tie, RANK keeps both, while ROW_NUMBER picks one arbitrarily.

    sql
    WITH monthly AS (
      SELECT DATE_TRUNC('month', o.order_date) AS month, p.category,
             SUM(oi.quantity * oi.unit_price) AS revenue
      FROM orders o
      JOIN order_items oi ON oi.order_id = o.order_id
      JOIN products p ON p.product_id = oi.product_id
      GROUP BY 1, 2
    )
    SELECT month, category, revenue
    FROM (SELECT m.*, DENSE_RANK() OVER (PARTITION BY month ORDER BY revenue DESC) AS rk
          FROM monthly m) t
    WHERE rk <= 3
    ORDER BY month, rk;
  12. 12

    A project costs 10 lakh and is expected to save 4 lakh a year. Compute ROI over 3 years and the payback period.

    easy

    Total benefit over 3 years is 3 x 4 = 12 lakh. ROI = (benefit - cost) / cost = (12 - 10) / 10 = 20 percent. Payback is cost divided by the annual benefit, 10 / 4 = 2.5 years. A fuller business case would discount the cash flows to a net present value and compare options, and would include running costs, risk and benefits that are hard to quantify, such as improved customer experience.

  13. 13

    Orders are being abandoned at checkout. How would you approach finding the root cause and a fix?

    hard

    Define the problem with data: the abandonment rate by step, device, payment method and new versus returning customers, compared with a baseline period. Look for where it concentrates. Combine this with qualitative input: session recordings, support tickets and short user interviews. Use a 5 whys or a fishbone diagram to separate causes, such as slow page load, forced registration, unexpected shipping cost or payment failures. List options with effort and expected impact, recommend the highest impact change, test it with an A/B test, and track the abandonment rate and revenue per visitor after launch.

Frequently asked questions

Do business analyst interviews include SQL?

Often yes, at a basic to intermediate level: joins, aggregation and sometimes window functions. Excel and a BI tool such as Power BI are also common.

Which certifications help?

Common ones include CBAP and CCBA from IIBA, and Agile or Scrum certifications. They are helpful but not required for most entry-level roles.

How do I answer behavioural questions without work experience?

Use academic projects, internships or volunteer work. Describe the stakeholders, your role, the action you took and the result, keeping to what actually happened.

What documents should I be ready to discuss?

BRD, user stories with acceptance criteria, process flow diagrams, an RTM and a simple business case. Bring one example you have worked on.

Related guides

More in Role-wise Interview Questions by Job and Tech Stack

See all in this section