For people stepping into BA roles

Interview prep, the way BAs actually get hired.

Common BA interview questions, each broken down into what the interviewer is testing, the points a strong answer must hit, a sample answer, and the red flags that weaken one. Use the bullet logic to think — don't memorise the script.

How to use this

1. Read the prompt. Try to answer in your head before opening the card.
2. Check the bullet logic. Did you hit those points? Order matters less than coverage.
3. Reveal the sample. Compare structure, not phrasing. The goal is your own answer, not theirs.

Deep dive · Junior BA interview frame + quiz

Deep learning module

A frame for answering BA questions confidently as a junior or career-changer: what interviewers are actually testing, the structure that wins, and the handful of stories you need ready before any interview.

Problem solved: Memorising answers to 50 questions is brittle and unconvincing. A small number of well-prepared stories plus a frame for shaping each answer beats a script every time.

Interview prep, the way BAs actually get hired.

1. Overview

2. Full breakdown

3. When to use

4. When NOT to use

5. Step-by-step usage

6. Worked example

8. Comparison with similar techniques

9. Common mistakes

10. BA perspective

11. Interview angle

12. Quick reference

Cross-links

Practice — quiz

What does a business analyst actually do?

What's the difference between a BA and a project manager?

What makes a good requirement?

How do you decide which elicitation technique to use?

How do you make sure you've identified the right stakeholders?

A key stakeholder won't engage — won't reply to emails, skips meetings. What do you do?

What's the difference between a functional and a non-functional requirement? Give an example.

A stakeholder tells you 'the system should be fast'. What do you do?

When would you use a user story versus a use case versus a process model?

How do you prioritise requirements when stakeholders disagree?

When would you use MoSCoW versus Kano?

Two senior stakeholders give you conflicting requirements. How do you handle it?

How do you explain a technical constraint to a non-technical stakeholder?

Tell me about a project where you made a real difference as the BA.

Your sponsor asks you to start eliciting requirements but there's no business case and no clear objective. What do you do?

What's a weakness you have as a BA, and what are you doing about it?

What are the BABOK perspectives, and why do they matter?

How do you tell a requirement from a design?

How do you decide between a predictive and an adaptive BA approach?

When would you reach for a process model, and how do you decide between BPMN, a state diagram, and DMN?