Business Analyst Interview Questions

1.1What business analysts do - bridging business and technology and why the role exists

1.2The BA in different contexts - waterfall, agile, large enterprise, and start-up and how the role changes

1.3Business analysis competencies - requirements, stakeholder management, process analysis, and solution assessment

1.4The BA career path - from junior analyst through to principal BA and business architecture

2.1Requirements elicitation techniques - interviews, workshops, observation, document analysis, and prototyping

2.2Functional vs non-functional requirements - the distinction and why NFRs get missed so often

2.3Requirements documentation - user stories, use cases, BRDs, and choosing the right format

2.4Requirements management - versioning, traceability, change control, and managing scope creep

3.1Process mapping - as-is process documentation, BPMN, swimlane diagrams, and process inventory

3.2Process improvement - identifying waste, bottlenecks, and root causes in the current state

3.3To-be process design - designing improved processes and defining the target operating model

3.4Process governance - how to ensure processes are followed, measured, and continuously improved

4.1Stakeholder analysis - identifying, mapping, and understanding the interests and influence of each stakeholder

4.2Facilitating workshops - planning, running, and getting genuine decisions from a group of stakeholders

4.3Managing conflicting requirements - techniques for resolving stakeholder disagreements professionally

4.4Influencing without authority - how BAs drive decisions when they have no formal power

5.1Data analysis for BAs - understanding data, interpreting reports, and using data to support requirements

5.2Data modelling basics - entity-relationship diagrams, data dictionaries, and understanding the data landscape

5.3Reporting requirements - defining what the business needs from reports and dashboards

5.4SQL basics for BAs - enough querying to explore data, validate requirements, and test solutions independently

6.1The BA in agile - working in sprints, maintaining the backlog, and continuous requirements discovery

6.2Writing effective user stories - format, acceptance criteria, the definition of ready, and common mistakes

6.3Backlog refinement - grooming sessions, estimation support, and keeping the backlog healthy

6.4Agile artefacts - epics, stories, tasks, and how BAs use them to manage scope and track progress

7.1Systems thinking - understanding how software systems work without being a developer

7.2API understanding - what APIs are, how they work, and the BA role in integration requirements

7.3Data integration and migration - the BA role in defining what moves, how, and what the acceptance criteria are

7.4Understanding technical constraints - how to work with architects and developers on what is feasible

8.1The BA role in testing - writing acceptance criteria, reviewing test cases, and supporting UAT

8.2User acceptance testing - planning UAT, managing testers, and obtaining sign-off

8.3Defect triage - the BA role in determining whether a defect is a bug or a change request

8.4Solution assessment - evaluating whether the delivered solution meets the original requirements

9.1Business change management - the BA role in preparing the organisation for a new system or process

9.2Training needs analysis - identifying who needs what training and what the content should cover

9.3Implementation planning - the go-live approach, cutover activities, and managing the transition

9.4Post-implementation review - measuring benefits realisation and identifying further improvements

10.1Technical questions - requirements, process modelling, stakeholder management, and agile BA

10.2Case study questions - analysing a process, eliciting requirements, or designing a solution under interview conditions

10.3Behavioural questions - managing difficult stakeholders, ambiguous requirements, and scope changes

10.4Salary negotiation for BA roles, evaluating a project or programme environment, and questions that reveal the real BA culture in an organisation