P
prepair.app
Start interview →
EnglishУкраїнськаРусскийDeutsch
📈

Middle Business AnalystBusiness analyst interview questions

Middle · 2–4 years of experience

Business analyst interviews test how you gather requirements, handle disagreeing stakeholders, and turn ambiguity into something a team can build. Below are the most common questions with model answers. Middle: deeper understanding, optimization, and real-world situations.

Try it — no account needed
Preparing your question…

Topics to prepare

Requirements gathering
User stories and acceptance criteria
UML and BPMN diagrams
Stakeholder management
Agile and Scrum
Prioritization (MoSCoW, RICE)

6 Middle-level questions with answers

1

How do you prioritise requirements when everyone says theirs is critical?

Answer

By making the trade-off visible rather than arguing about importance: what each delivers, what it costs, and what is given up by doing the other first. MoSCoW works when the categories are capped, otherwise everything becomes a Must. The question that ends most debates is what happens if this ships next quarter instead.

2

How do you handle a requirement that changes mid-development?

Answer

Assess the impact before agreeing or refusing — what else depends on it, what is already built, what the delay costs. Then it is a decision someone owns, not a favour. Silent scope creep, where each change is small and nobody tracks the total, is how a two-month project takes six.

3

What is a traceability matrix and when is it worth maintaining?

Answer

A map from requirements to the design, code and tests that satisfy them. It is worth maintaining when you must prove coverage — regulated industries, audits, safety — and it is bureaucracy elsewhere. The honest version is a link from the ticket to the test, not a spreadsheet nobody updates.

4

How do you model a process, and what do you actually get from it?

Answer

BPMN or a plain swimlane diagram showing who does what and where the handoffs are. What you get is not the picture — it is that drawing it exposes the steps nobody could name and the decisions with no owner. Most process problems are discovered while modelling rather than by reading the model.

5

What is the difference between validation and verification of requirements?

Answer

Verification asks whether the requirement is well-formed — clear, testable, consistent with the others. Validation asks whether it is the right requirement — whether it actually serves the business need. A document can pass verification completely and describe the wrong system.

6

How do you write requirements for an integration with an external system?

Answer

Start from the contract: what data crosses, in what shape, how often, and what happens when the other side is unavailable or wrong. The failure modes are the requirement — a spec that describes only the happy path will be discovered incomplete during testing, when it is expensive.

🦎

Reading answers is not enough

In a real interview you speak under pressure. Cam asks these same questions, scores every answer, and shows exactly what to fix.

Practice a Middle Business Analyst interview →
Free · 3 interviews per month

Other levels — Business Analyst

Junior Business AnalystSenior Business AnalystAll Business Analyst questions

Other specializations

🔍Middle Manual QA🤖Middle QA AutomationMiddle Java Backend🐍Middle Python Backend🐘Middle PHP Backend🦫Middle Go Backend🟢Middle Node.js Backend💎Middle Ruby on Rails🟣Middle .NET Backend Developer🔷Middle C++