

In my work prepping BAs for interviews, I’ve seen AI business analyst interviews evolve rapidly. Traditional BA interviews tested elicitation, modelling, and stakeholder skills. The 2026 BA interview I see now tests those plus AI fluency, prompt design, and the ability to articulate when AI helps and when it does not. In this guide I share the 40 questions I see come up most often, with the structure strong candidates I’ve coached use to answer.
| Round | Focus |
| Fundamentals | Classic BA skills (elicitation, modelling, AC) |
| AI fluency | Prompt design, tool fluency, judgement on AI use |
| Strategic | Business case, options analysis, value realisation |
| Stakeholder | Influence, conflict, communication |
| Domain | Industry-specific knowledge |
Strong candidates prepare for all five.
Q1: Walk me through how you elicit requirements from a difficult stakeholder. > Approach: prep with role research, open-ended questions, listen actively, manage expectations explicitly, validate understanding.
Q2: How do you handle conflicting requirements? > Approach: surface the conflict, ground each in evidence, facilitate joint conversation, escalate if unresolved.
Q3: Describe a process modelling exercise you led. > Approach: STAR. Lead with business problem, your method, AI tools used, outcome.
Q4: How do you ensure traceability across requirements? > Approach: tool support (Jama, Modern Requirements), discipline of linking, regular audits.
Q5: Walk me through your approach to acceptance criteria. > Approach: Given/When/Then, cover happy path/edge cases/errors, AC must be testable, validate with team.
(Continue with Q6-Q10 covering: handling scope creep, INVEST checks, requirements prioritisation, BRD vs FRS distinction, requirements elicitation in remote settings.)
Q11: Walk me through your AI tool stack. > Approach: be specific. Name tools, use cases, costs, ROI seen.
Q12: How do you structure prompts for synthesis tasks? > Approach: role + goal + context + output format. Give an example.
Q13: When does AI not help? > Approach: stakeholder relationship building, novel domains, political dynamics, irreversible decisions.
Q14: How do you validate AI-generated output? > Approach: cross-check against source material, validate with stakeholders, manual review of 10% of synthesis.
Q15: How do you handle AI hallucination? > Approach: always validate facts, never let AI invent quotes, use enterprise tier, train team on the risk.
Q16: Describe a failure case from AI use. > Approach: be honest. Strong candidates have war stories.
(Continue with Q17-Q20 covering: privacy and PHI handling, tool selection criteria, cost management, training others on AI.)
Q21: Build me a business case for [hypothetical project]. > Approach: state the problem, options, expected value, costs, risks, recommendation. Show your reasoning.
Q22: How do you handle a project that the organisation wants but the business case is weak? > Approach: surface the weakness, propose adjustments, escalate if leadership insists.
Q23: Describe a strategic analysis you delivered. > Approach: STAR. Show the analysis structure, your judgement, the decision it informed.
(Continue with Q24-Q28 covering: SWOT and similar frameworks, options analysis, risk assessment, stakeholder buy-in, ROI calculation.)
Q29: Tell me about a difficult stakeholder. > Approach: STAR. Show empathy, specific actions, learnings.
Q30: How do you handle conflicting executive demands? > Approach: surface the conflict early, propose options, escalate appropriately, communicate trade-offs.
(Continue with Q31-Q34 covering: building credibility with senior stakeholders, managing up, distributed stakeholders, cultural sensitivity.)
Q35: What is unique about [industry] BA work? > Approach: industry-specific regulations, common project types, typical stakeholders, characteristic challenges.
Q36: How do you keep up with [industry] trends? > Approach: specific sources, networks, ongoing education.
(Continue with Q37-Q40 covering: industry-specific regulations, common methodologies, vendor landscape, customer behaviour patterns.)
Three frameworks cover most BA interview questions:
Practising these until they are second nature is the highest-leverage interview prep.
Week 1: review fundamentals. Refresh BABOK basics. Practice 5 STAR answers.
Week 2: AI fluency rehearsal. Walk through your prompt library. Practice describing 3 AI use cases with outcomes.
Week 3: strategic case practice. Work through 3 case studies with structure: frame, gather, analyse, recommend.
Week 4: mock interviews. 4-6 mocks with peers or coaches. Refine based on feedback.
This plan assumes existing BA experience. Career switchers should double the timeline.
Some interviewers ask intentionally difficult questions to test how you handle ambiguity:
“Tell me about a time AI gave you wrong output and you missed it.” Be honest. Show learning. Don’t pretend you’ve never been fooled.
“How would you analyse a problem you have no domain knowledge for?” Show structured thinking: research first, frame the problem, gather perspectives, propose options.
“What’s your view on AI replacing BAs?” Nuanced: AI compresses some BA work; the strategic and human parts remain. Demonstrate clear thinking.
“How would you handle a stakeholder who doesn’t believe in your analysis?” Empathy first, evidence second. Show specific behaviours you’d use.
To get the most from mocks:
8-12 mocks is the sweet spot for most candidates.
Logan Hutchinson has 25+ years of experience leading AI innovation at Cruise, Motorola, Siemens, and Drift, building Level 5 autonomous systems, enterprise AI platforms, and breakthrough healthcare automation products at scale.
QUICK FACTS
4-6 weeks of focused prep is typical. Career switchers may need 8-12 weeks.