Business analyst interview questions

As asked

A new project kicks off and the sponsor gives you a one-line brief. Walk me through how you would elicit detailed requirements from the stakeholders involved.

Sample answer outline

Start by identifying and mapping every stakeholder group, then choose elicitation techniques that fit each: interviews for depth, workshops for shared understanding, observation for tacit process knowledge, document analysis for the current state. Capture requirements in a structured backlog, separate business from functional from non-functional, and confirm understanding by playing it back. A strong answer stresses asking why repeatedly to reach the underlying need rather than the requested solution.

Expect these follow-ups

• How do you handle a stakeholder who only describes the solution, not the problem?
• Which technique do you reach for when stakeholders disagree on the current process?
• How do you elicit requirements when the subject matter expert has left the company?

As asked

You have been asked to redesign an order-to-cash process. Walk me through how you would document the as-is process and then design the to-be process.

Sample answer outline

Map the as-is by shadowing the people who do the work and modelling it in BPMN with swimlanes per role, capturing handoffs, decision gateways, systems touched, and cycle times. Identify pain points such as rework loops, manual reconciliations, and bottlenecks. Design the to-be by removing waste, automating where it pays off, and validating against the same swimlanes. A strong answer measures both states so the improvement is quantified, not just asserted.

Expect these follow-ups

• Which BPMN elements do you use to show a decision that can loop back?
• How do you keep the to-be map honest rather than an idealised fantasy?
• How do you handle a step that nobody can fully explain?

As asked

Take a feature like password reset and write it as a user story with acceptance criteria. What makes the criteria good?

Sample answer outline

Frame the story in the as a, I want, so that form to keep the user and the value explicit. Write acceptance criteria in given, when, then form so each is testable and unambiguous, covering the happy path, validation, error states, and edge cases such as an expired reset link. Good criteria are independent of implementation, verifiable by a tester, and small enough to fit a sprint, following INVEST.

Expect these follow-ups

• How do you split a story that is too big to fit one sprint?
• What goes in acceptance criteria versus the definition of done?
• How do you handle non-functional needs like the reset email arriving within a minute?

As asked

A finance director says they want better visibility of late payments. Walk me through how you turn that into something a development team can build.

Sample answer outline

Probe the underlying need to learn what visibility means, who consumes it, how often, and what decision it drives. Translate that into concrete requirements, for example a dashboard showing ageing debt by customer with a daily refresh and an alert above a threshold. Specify the data sources, the business rules for what counts as late, the calculations, and the acceptance criteria. A strong answer bridges business language and technical detail without losing either side.

Expect these follow-ups

• How do you avoid gold-plating the spec with features nobody asked for?
• How do you specify the business rule for what counts as a late payment?
• What do you do when the source data needed simply does not exist yet?

As asked

Without writing perfect syntax, talk me through how you would structure a SQL query to find the top ten customers by total revenue in the last quarter.

Sample answer outline

Describe selecting from the orders or sales table, filtering on the order date for the last quarter, grouping by customer, summing the line value, ordering by that sum descending, and limiting to ten. Mention joining to a customers table for names and being careful about whether revenue means gross, net of returns, or net of tax. A strong answer flags the date boundary and whether to count only completed orders.

Expect these follow-ups

• How would you also show each customer's share of total revenue?
• What changes if a customer can have orders in more than one currency?
• How do you handle returns and refunds in the revenue figure?

As asked

You have forty requirements and capacity for ten in the next release. How do you prioritise, and which framework would you use?

Sample answer outline

Choose a framework that fits the context: MoSCoW for a fixed-scope release to agree must, should, could, and won't, or RICE to score reach, impact, confidence, and effort when comparing competing items. Run the scoring with stakeholders so the ranking is shared, not imposed, and surface dependencies that force ordering. A strong answer treats the framework as a structured conversation tool rather than a precise formula, and revisits priorities as new information arrives.

Expect these follow-ups

• When would you prefer RICE over MoSCoW?
• How do you handle a stakeholder who marks everything as a must have?
• How do dependencies override a pure priority score?