60 Business Analyst interview questions with detailed answers, sorted from basic to advanced. Free to practice, with progress saved automatically.
A Business Analyst bridges business needs and the development team by gathering, analysing and documenting software requirements. The questions cover needs versus requirements, requirement documents, use cases and modelling, GAP analysis, the BA role itself, Agile versus Waterfall, the skills and learning path, and situational cases such as conflicting stakeholders.
A BA sits between the business side and the technical side: turning business needs into requirements the delivery team can build, and making sure what gets built addresses the original problem. Responsibilities across the project lifecycle: - Before development — understand the business context, identify…
The two roles differ in the question each one must answer. Business Analyst answers "what should we build and why". The inputs are people and processes: interviewing stakeholders, modelling the current process, proposing a new one, writing requirements. The outputs are documents, process flows, user…
A business-side BA works at the organisational level: analyzing processes, structure, and cost, then proposing improvements. The recommended solution may have nothing to do with software — changing an approval process, reorganizing a team, renegotiating with a supplier. An IT BA works in the context…
The three differ in what each is ultimately accountable for. - Business Analyst owns requirement correctness and completeness. Central question: does this solution address the right business problem, and is the description clear enough to build? - Product Owner owns product value. They decide backlog…
It depends on the delivery model, but the common groups are: Need and scope - BRD (Business Requirement Document) — the business problem, objectives, scope, stakeholders. Written for decision makers. - SRS / FRD — a detailed specification of what the system must do, including…
Analytical skills — decomposing problems, separating symptoms from causes, modelling processes, and asking questions until the requirement stops being ambiguous. Communication and writing — interviewing stakeholders, facilitating meetings with conflicting views, and writing concisely without hedging. This is where candidates fail most often, not on…
The core strength is holding one shared version of the truth across groups with different concerns. Concretely: - Identify the right stakeholders early, including groups not in the meeting room — operations, customer support, finance. Missed requirements usually come from a forgotten group. - Adjust…
Four common directions branch off the BA role, differing in what you want to go deep on. 1. Deeper analysis — Junior BA → BA → Senior BA → Lead BA / BA Manager. The higher you go, the less document writing and the more…
This question checks whether you have actually researched the profession or simply noticed it hiring. An effective structure: 1. A concrete starting point — something you did and enjoyed: rewriting a process for a student club, running user surveys for a capstone project, building reports…
CBAP (Certified Business Analysis Professional) is the senior certification from IIBA, based on the BABOK framework. Eligibility requires accumulated business analysis hours, training hours, and references — meaning it targets experienced practitioners, not newcomers. IIBA also offers entry-level tiers for people new to the profession,…
Taking a generic project frame, the BA workload shifts phase by phase: 1. Initiation — clarify the business problem and objectives, identify stakeholders, do a first feasibility assessment, agree high-level scope. 2. Requirements analysis — interviews, surveys, observation of the current process; model the as-is…
This comes up often at outsourcing companies where the domain changes with every project. The interviewer wants a repeatable method, not "I will try hard to learn". A workable sequence: 1. Read the existing material before asking people — contracts, prior project documents, operating manuals,…
Name each difficulty with how you handled it — the question is testing experience, not pessimism. Ambiguous or conflicting requirements — every stakeholder describes it differently. Handling: reduce it to concrete examples and real data, then write acceptance criteria that force one shared reading. Scope…
A need is a business problem or desire, expressed in terms of an outcome. A requirement is what the system or solution must do to satisfy that need, expressed in verifiable terms. Example: - Need: "Customer support spends too long looking up orders." - Requirement:…
Functional requirements describe what the system does — behavior, inputs, outputs, business rules. "A user resets their password by email; the link expires after 15 minutes." Non-functional requirements describe how well the system must do it — quality attributes that cut across many functions. Categories…
Clients almost never volunteer performance or capacity expectations. The BA job is to draw them out with questions that produce numbers. How to probe each area: - Volume — "How many orders per day? How much bigger is a peak day? What do you expect…
The three documents differ by audience and level of detail. BRD — Business Requirement Document Answers why we are doing this and what it should achieve. Contents: business context, the problem, objectives and metrics, in-scope and out-of-scope, stakeholders, assumptions and constraints. Read by decision makers…
A typical SRS structure: 1. Introduction — purpose, product scope, intended readers, glossary and abbreviations, referenced documents. The glossary matters more than it looks: most late-project disputes trace back to one term read two ways. 2. Overall description — product context and its place in…
Elicitation is the work of drawing out information about needs and requirements from stakeholders and other sources. The word "draw out" rather than "collect" is deliberate: most requirements are not lying somewhere ready to be picked up — users state them only when asked the…
Nothing proves completeness absolutely, so a strong answer names layers of cross-checking instead of claiming certainty. 1. Cover every stakeholder — build the stakeholder list deliberately, including groups affected only indirectly: finance, customer support, operations, compliance. Missed requirements usually belong to the group that was…
General principle: prioritization is a business decision; the BA supplies the basis and facilitates rather than ranking on their behalf. Common techniques: MoSCoW — Must have, Should have, Could have, Will not have (this time). Easy to use, good for fixing the scope of a…
Scope creep is project scope growing during delivery without matching adjustments to time, cost, or resources. It differs from controlled scope change: an approved change is normal; the dangerous part is what slips in silently. Common causes: - Vague initial scope that never states what…
An RTM is a table linking each requirement to what derives from it: business objectives above, and design, development items, and test cases below. Example: Req ID Business objective Description Design doc Dev item Test cases Status --------------------- FR-012 Cut lookup time Order lookup by…
A strong answer describes a process, because the question tests whether you work systematically or by instinct. The steps: 1. Log through one entry point — every change request lands in the same place with requester, date, description, and business reason. A request that arrives…
The familiar template: As a [role], I want [capability], so that [value]. Example: As a support agent, I want to look up an order by phone number, so that I do not have to ask callers for an order code. The three parts of a…
A use case describes a sequence of interactions between an actor and the system to achieve a specific goal. It answers: who does what with the system, in what order, and what result it ends in. A fully written use case contains: - Name —…
A use case diagram is an overview showing which functions the system offers, who uses them, and where the system boundary sits. It deliberately avoids detail — its value is showing the whole scope on one page. When to use it: - Early in a…
An alternate flow is another route to the same successful goal. The use case still ends as intended, just by a different path. Placing an order: the main flow pays by card; an alternate pays by e-wallet or cash on delivery. The order is still…
Both relationships pull a piece of behavior out of a base use case, but they differ in whether it is mandatory and in the direction of dependency. include — always happens The base use case always invokes the included one; the extracted piece is a…
A sequence that works in practice: 1. Fix the system boundary — decide what is inside the system and what is outside. Getting this wrong invalidates everything after it. 2. List the actors — the roles using the system, plus external systems and scheduled events.…
An activity diagram describes the sequence of activities in a process, including conditional branches and parallel paths. It answers what happens first, what follows, and where the flow diverges. Main components: - Start node and end node. - Activity — a unit of work, named…
BPMN (Business Process Model and Notation) is an OMG standard notation for modelling business processes. Its strength is that each symbol has a defined meaning, so business, BA, and technical readers arrive at the same interpretation. Basic element groups: - Flow objects — events (start,…
This checks whether you pick diagrams by purpose or by habit. Common types and the problem each solves: - Use case diagram — fixing scope: who uses which function. - Activity diagram / BPMN — process flow, exposing handoffs and bottlenecks between departments. - Sequence…
These four sit on one axis of increasing fidelity, each answering a different question. Sketch — a hand drawing or rough outline, no scale required. Used during discussion to align on layout ideas. Its value is being drawn in minutes and discarded without regret. Wireframe…
A persona is a profile of a typical user group, built from real survey and interview data rather than imagination. It usually covers work context, goals when using the product, current pain points, technical proficiency, and usage environment (device, physical setting, timing). BAs use personas…
Waterfall runs sequentially: analysis, then design, then development, then testing, then deployment. Requirements are fixed and signed off up front; later changes go through a change request process. Agile works in short cycles, each producing something usable and gathering feedback to adjust. Requirements are clarified…
The Agile Manifesto states four value pairs, each in the form "we value the left more than the right" — not that the right is discarded: 1. Individuals and interactions over processes and tools. 2. Working software over comprehensive documentation. 3. Customer collaboration over contract…
INVEST is a six-criterion checklist for user story quality: - I — Independent: buildable on its own, not forced to wait behind another story. Tangled dependencies remove freedom in prioritization. - N — Negotiable: states what is needed and leaves room to discuss how. A…
Acceptance Criteria (AC) are the conditions a user story must satisfy to count as done. They hold the detail the short story sentence cannot carry. Why write them: - To lock in one shared interpretation among BA, developer, tester, and business before work starts. -…
Similarities: both describe a need from the user perspective, both tie to a role and a goal, and both feed the delivery team. Differences: User story Use case --------- Length One sentence, detail in the AC A structured, multi-step specification Focus The value the user…
What sets an Agile BA apart is clarifying requirements on an iterative rhythm, rather than handing over a sealed specification and stepping away. - Work to the rhythm — enough detail ready for the coming sprint, coarser items further out. Writing a full specification for…
GAP analysis compares the current state against the desired state to identify what is missing and what must be done to close it. Three steps: 1. Describe the current state with real data — how the process runs, how long it takes, its error rate,…
Pareto analysis rests on the observation that most effects come from a small share of causes — often quoted as the 80/20 ratio. The method: list the causes, measure the frequency or impact of each, sort descending, and focus on the leading group. BA uses:…
Assess feasibility across five dimensions, each with its own question and its own confirming authority — the BA consolidates rather than concluding all five alone. Technical — can existing technology do it, does the team have the capability, will it integrate with running systems, will…
They differ by timing: a risk has not happened yet; an issue already has. Risk — an event that may occur and would affect the project if it did. Described by probability and impact, and handled with preventive or contingency plans. "The payment gateway vendor…
After identifying and ranking risks by probability and impact, there are four response directions: Avoid — change the plan so the risk can no longer occur. Drop the feature that depends on an unreliable third-party system, or choose technology the team already knows instead of…
Group tools by the problem they solve, and mention only what you actually use — interviewers often follow up with a detail question. Requirements and work tracking — Jira, Azure DevOps, Trello: managing the backlog and linking user stories to development items and test cases.…
The level required is querying and verifying data, not tuning or database design. The goal is answering a business question yourself instead of waiting for a developer to run it. Commonly tested knowledge: - SELECT with WHERE, ORDER BY, LIMIT. - GROUP BY with aggregate…
Yes, but in the right role. A BA does not replace the test team; the BA contribution is reconciling the product against the requirements and the real business. What a BA can do in testing: - Review test cases — check coverage against acceptance criteria…
This is the most common situational question for BA roles. Answer with a sequence and a real example. The sequence: 1. Clarify where the conflict actually lies. Often two parties use the same word with different meanings, or describe two solutions to the same need.…
Do not accept it and worry later, and do not refuse flatly. The sequence: 1. Confirm with the technical team before saying anything to the client. Establish the degree of infeasibility: impossible with current technology, possible but over budget or schedule, or possible but breaking…
Start from the assumption that the pushback has a reason, because developers often see constraints the documentation has not captured. Step 1 — Hear the full reason and classify it. Three common kinds: - Technical — buildable but breaking the current design, risking data, or…
The interviewer is checking whether you keep the work moving, not whether you are agreeable. Before the session: - Prepare more thoroughly than usual: documents, numbers, questions in order. Most sharp reactions come from the feeling of wasted time. - Learn what they actually care…
This tests honesty and how you react when a plan slips, not whether you are flawless. "I have never missed a deadline" is the worst possible answer. A workable structure: 1. Brief context — what the work was, the deadline, and why that deadline existed.…
The goal of the first session is to turn a vague sentence into a measurable scope: who uses it, how attendance is captured, how working time is calculated and where the results go. Do not ask "which features do you want" — the client will…
A safe order is: clarify the prompt → agree on a measurable goal → break the problem down → form hypotheses and test them with data → recommend with priorities. Interviewers score structured thinking far more than the final answer. 1. Clarify (first 2–3 minutes):…
Do not jump to "it is the pandemic". Break revenue into a formula and find which component dropped: revenue = visitors × purchase rate × average order value, then split further by channel (physical store / online). Step by step: - Validate the number: fivefold…
