Business analyst role-specific 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?

As asked

What is the difference between a functional and a non-functional requirement, and why does the distinction matter when you write a specification?

Sample answer outline

Functional requirements describe what the system must do, for example the actions, calculations, and data it must handle. Non-functional requirements describe how well it must do them, covering performance, availability, security, accessibility, and compliance. The distinction matters because non-functional needs are easy to omit yet drive architecture and cost, so a good analyst captures both explicitly and makes each testable.

Expect these follow-ups

• Give an example of a non-functional requirement that quietly drives the whole architecture.
• How do you make a vague requirement like the system must be fast measurable?
• Where do regulatory and data protection needs sit in this split?

As asked

On a project with many competing interests, how do you identify your stakeholders and decide how to engage each of them?

Sample answer outline

Build a stakeholder list, then plot each on a power and interest grid to decide engagement: manage closely, keep satisfied, keep informed, or monitor. Capture each stakeholder's goals, concerns, and preferred communication style, and set an engagement cadence. A strong answer treats the map as a living document that shifts as the project moves and names how they would convert a blocker into a supporter.

Expect these follow-ups

• What do you do with a high-power, low-interest stakeholder who suddenly becomes engaged late?
• How do you handle conflicting requirements from two equally senior sponsors?
• How does your engagement plan change for a sceptical stakeholder?

As asked

A stakeholder requests a change to how customer discounts are calculated mid-project. How do you assess the impact before agreeing to it?

Sample answer outline

Trace the change through everything it touches: upstream data, downstream reports, integrations, business rules, existing requirements, test cases, and affected teams. Assess the effort, risk, and schedule impact, and check whether it conflicts with other in-flight requirements. Present options with tradeoffs through the change control process so the decision is informed. A strong answer uses a requirements traceability matrix to find the ripple effects quickly.

Expect these follow-ups

• How does a traceability matrix speed up impact analysis?
• How do you handle a change the sponsor insists is tiny but actually is not?
• What goes into a change request so the decision is auditable?

As asked

Explain the difference between an inner join and a left join, using a business example where choosing the wrong one would give a misleading answer.

Sample answer outline

An inner join returns only rows that match in both tables, while a left join keeps every row from the left table and fills unmatched right-side columns with nulls. The business example: joining customers to orders with an inner join silently drops customers who never ordered, so a churn or signup analysis would undercount. A left join keeps them, which is why understanding the question decides the join. A strong answer warns that nulls then need careful handling in aggregates.

Expect these follow-ups

• How can a join accidentally inflate a sum or count?
• When would a full outer join be the right choice?
• How do you check a join did not duplicate rows unexpectedly?

As asked

Halfway through a project the requirements keep growing. How do you manage scope creep without becoming the person who always says no?

Sample answer outline

Anchor everything to the agreed business objective and a baselined scope, then route every new request through change control with an impact assessment so the cost is visible. Distinguish a genuine missed requirement from a nice-to-have, and trade new work against existing scope rather than simply adding it. A strong answer frames the analyst as an enabler who makes tradeoffs explicit, not a gatekeeper who blocks change.

Expect these follow-ups

• How do you tell a legitimate missed requirement from scope creep?
• How do you say no to a senior sponsor without damaging the relationship?
• What does a healthy change control process look like in practice?

As asked

Before a development team starts building, how do you validate that the requirements you captured are actually correct and complete?

Sample answer outline

Play requirements back to stakeholders through walkthroughs, prototypes, or wireframes so they react to something concrete rather than abstract text. Cross-check for completeness, consistency, and conflicts, confirm each is testable, and trace each back to a business objective. A strong answer favours showing over telling, because a clickable prototype surfaces misunderstandings that a document review never would, and it secures explicit sign-off.

Expect these follow-ups

• Why does a prototype catch errors a document review misses?
• How do you check a set of requirements has no internal contradictions?
• What do you do when sign-off is given but you suspect the stakeholder did not really read it?