Role preparation
Business Analyst interview questions and answers.
Processes, stakeholder alignment, and prioritised requirements.
Questions
Technical questions to practise out loud
- 01
How do you write user stories and acceptance criteria?
A user story states the user, need, and value; acceptance criteria make the boundary testable with concrete rules, examples, permissions, errors, and outcomes. They clarify intent without turning into implementation tasks.
Read the full breakdown - 02
How do you map as-is and to-be processes?
Map the as-is process from observed actors, steps, handoffs, systems, delays, exceptions, volume, and pain points; design the to-be around measurable outcomes, changed responsibilities, controls, and transition gaps.
Read the full breakdown - 03
How do you prioritize requirements?
Prioritize requirements using value, urgency, risk reduction, compliance, dependencies, effort, and evidence; make capacity and trade-offs visible, define what is not included, and revisit priorities when assumptions change.
Read the full breakdown - 04
How do you run stakeholder interviews?
Prepare hypotheses and open questions, interview stakeholders separately when power dynamics matter, probe goals, decisions, exceptions and evidence, play back your understanding, and validate contradictions with artifacts or data.
Read the full breakdown - 05
How do you find process bottlenecks?
Measure demand, cycle time, wait time, work in progress, rework, handoffs, and capacity by step; the bottleneck is the constraint limiting throughput, not merely the step people complain about most.
Read the full breakdown - 06
How do you build a business case?
A business case compares a credible baseline with options using benefits, costs, risks, dependencies, timing, assumptions, and sensitivity. Recommend the option with measurable outcomes and a plan to validate them.
Read the full breakdown - 07
How do you manage changing scope?
Control changing scope through a visible baseline, impact analysis on value, time, cost and risk, an accountable decision maker, recorded decisions, and reprioritization rather than silently adding work.
Read the full breakdown - 08
How do you facilitate a requirements workshop?
Set a decision-focused objective, invite the necessary roles, share context, use a timed agenda and neutral facilitation, surface dissent, document assumptions and parking items, and finish with owners and deadlines.
Read the full breakdown - 09
How do you resolve conflicting requirements?
Trace each requirement to stakeholder goals, evidence, constraints, and business impact; expose the conflict, generate options, quantify trade-offs, and have the accountable owner decide against agreed principles.
Read the full breakdown - 10
How do you define success metrics for a change?
Define success from the intended behavior change: choose an outcome metric, baseline, target, time window, population, guardrails, data source, owner, and decision rule before implementation changes the measurement.
Read the full breakdown