How to assess · For hiring teams
How to Assess Business Analysis Skills When Hiring
The test formats that actually work for Business Analysis, what a strong answer looks like, sample questions and a scoring rubric you can use as-is.
The short answer
Assess Business Analysis with a task, not a conversation: requirements from a messy brief, process mapping exercise, ai-scored assessment (e.g. cohesyve) or stakeholder role-play. Score it against written criteria you fix before you see any submissions, and weight the criteria that the role actually depends on.
- Elicits needs, not solutions: asks why until the underlying problem is clear
- Writes requirements that are specific, testable and traceable to a goal
- Maps current and future processes and finds the gaps and the waste
- Identifies conflicts, ambiguities and missing cases before development starts
Paste a job description; Cohesyve generates a role-specific assessment and rubric. Ten candidates free, no card.
Business analysis is the discipline of finding out what is actually needed before anything is built, and it is the skill most projects are missing when they fail. A business analyst who documents what stakeholders say rather than what they need, who cannot spot a requirement that contradicts another, or who writes specifications developers cannot use, produces expensive rework. This page covers how to assess business analysis for BA, product analyst and systems analyst roles: elicitation, requirements quality, process understanding, and the judgement to challenge as well as capture.
Why Business Analysis is worth testing
Bad requirements are the most expensive defects, because they are discovered last. A BA who cannot elicit real needs, resolve conflicts between stakeholders, or write testable requirements sets a project up to build the wrong thing correctly. Testing shows whether a candidate can get from a vague ask to a precise, agreed specification, and that predicts whether what gets built is what was needed.
What strong Business Analysis looks like
- Elicits needs, not solutions: asks why until the underlying problem is clear
- Writes requirements that are specific, testable and traceable to a goal
- Maps current and future processes and finds the gaps and the waste
- Identifies conflicts, ambiguities and missing cases before development starts
- Manages stakeholders with different priorities and gets to an agreed scope
- Works with developers and testers so requirements are buildable and verifiable
- Prioritises scope by value and can say what to leave out
Ways to assess Business Analysis
Requirements from a messy brief
Provide stakeholder notes with contradictions, a proposed solution disguised as a need, and gaps. Ask for the clarifying questions, the requirements, and what is unresolved. Sixty minutes.
Pros
Cons
Best for Any BA role.
Process mapping exercise
Describe a process in prose with inefficiencies and ask for a map and the improvements.
Pros
Cons
Best for Process-focused roles.
AI-scored assessment (e.g. Cohesyve)
Generate a business analysis task from the job description — a requirements task, a stakeholder conflict, a process gap analysis — with a rubric. Each candidate receives a different variant; the reasoning is scored alongside the work.
Pros
Cons
Best for Screening an applicant pool fairly before interview time is spent.
Stakeholder role-play
Play a stakeholder who insists on a specific feature. Ask the candidate to uncover the need behind it.
Pros
Cons
Best for Stakeholder-facing roles.
Cohesyve
Run a Business Analysis assessment on your next opening
Cohesyve generates a unique Business Analysis task per candidate from your job description, with the scoring rubric attached. Questions are different for every applicant, so they cannot be shared or looked up.
What to test
Elicitation
Whether they find the real need.
Requirements quality
Whether specifications are usable.
Process analysis
Whether they understand how work flows.
Scope and judgement
Whether they shape what gets built.
Sample Business Analysis questions
A stakeholder asks for a button that exports to spreadsheet. What do you ask?
EntryLook for Why; what they do with it; who else needs it; whether a report or integration serves better.
What makes a requirement testable?
EntryLook for Specific, measurable, unambiguous, with acceptance criteria.
Two stakeholders give contradictory requirements. What do you do?
MidLook for Understand each need, find the underlying goal, facilitate agreement, escalate with a recommendation if needed.
Developers say the specification is unbuildable. What went wrong?
MidLook for Requirements written without technical input, missing constraints; involve engineering early.
Scope is twice what the timeline allows. How do you cut it?
SeniorLook for Prioritise by value and risk, define a coherent first release, agree with stakeholders, document what is deferred.
Red flags
- Documents solutions as requirements
- Requirements are vague or untestable
- Avoids stakeholder conflict
- Does not involve developers
- Cannot say what to leave out
Scoring rubric
| Criterion | Weight | What strong looks like |
|---|---|---|
| Elicitation | 30% | Finds needs behind requests; surfaces gaps. |
| Requirements quality | 30% | Specific, testable, traceable. |
| Process analysis | 15% | Flow understood; gaps identified. |
| Scope judgement | 25% | Prioritises and negotiates scope. |
Mistakes hiring teams make
- Testing documentation formats rather than analysis
- Not including contradictions in the brief
- Accepting requirements that restate the ask
- Ignoring scope judgement
- Assuming domain knowledge equals analysis skill
Roles that need Business Analysis
Common questions
Should the assessment use our domain?
A generic domain tests analysis skill more cleanly. Domain knowledge can be assessed separately if it matters.
What is the best single BA question?
Give a stakeholder's solution request and ask what they would ask. Elicitation instinct shows immediately.
How long should a BA assessment take?
Sixty minutes for a requirements exercise; thirty for a role-play.
How do I assess stakeholder management?
A role-play with a stakeholder who insists on a feature reveals whether they can uncover the need without alienating the person.
Cohesyve · Skill assessments for hiring
Test Business Analysis before the first interview
Generate a role-specific Business Analysis assessment from your job description and see who can do the work before you spend interview time on them.
1,500+
assessments completed
50%
faster time-to-hire
90%
completion rate
5 min
from JD to assessment
No credit card · 10 free candidates · Plans sized to your hiring volume
From the blog