Cohesyve · Practice for candidates
Going for a Business Analyst role? Find out how you'd actually score.
Run a Business Analyst simulation built the same way employers build theirs, and get a full report showing exactly where you lost marks — before it counts.
5
free assessments a month
$0
no card required
Full
scored report every run
Every
question type included
5 free assessments a month · No card required · Pro from $16/mo
Overview
Business analyst assessments test whether you can turn a vague business problem into something a team can build or decide on. Expect messy requirements, an ambiguous stakeholder request, and a dataset that does not quite answer the question. This page covers the common formats and how they are scored.
Why employers assess this role
The core BA skill — extracting a real requirement from what someone says they want — is invisible on a résumé and easy to claim in an interview. A practical task shows immediately whether a candidate asks the clarifying question or simply documents the request as stated.
What gets tested
The format
Duration
45–90 minutes
Question types
- Turn a vague request into documented requirements
- Analyse a small dataset and report findings
- Map or improve an existing process
- Write acceptance criteria for a described feature
Levels
Entry · Mid · Senior
What you'll be asked to do
Elicit the real requirement
A stakeholder asks for a solution. You are scored on whether you find the problem behind it rather than specifying what was requested.
- •A manager asks for "a dashboard" — determine what they actually need
- •A team requests a new field on a form; establish why
- •A request conflicts with an existing process; work out which should change
Document it usably
Requirements and acceptance criteria that a developer and a tester could both work from without follow-up.
- •Write user stories with acceptance criteria for a described workflow
- •Specify the validation rules for a data entry screen
- •Document the edge cases an approval workflow must handle
Analyse the data
A small dataset with a question attached. Scored on whether the conclusion is actually supported by what is there.
- •Explain what is driving a change in a monthly figure
- •Identify the data quality problems before drawing a conclusion
- •State what this dataset cannot tell you
Map and improve a process
An existing process with inefficiencies. You are asked to represent it and propose changes with a rationale.
- •Map an approval process and identify the bottleneck
- •Propose changes and state the risk each one introduces
- •Decide what to measure to know the change worked
Cohesyve for candidates
Practise a Business Analyst assessment before the real one
Run the same AI job simulations companies use to evaluate applicants. You get a scored report showing where you're strong and where you're not, plus what to work on.
Sample tasks — and what strong looks like
A department head says "we need a report that shows everything". Produce the requirements.
EntryWhat strong looks like: Establishes the decision the report is meant to support, who uses it and how often, and what action follows from it — then specifies something narrow and usable. Weak answers document the request literally.
Write acceptance criteria for a feature where a manager approves expense claims above a threshold.
MidWhat strong looks like: Covers the boundary at exactly the threshold, the absent-approver case, currency and rounding, resubmission after rejection, and the audit trail. Weak answers cover approve and reject only.
Here is three months of support ticket data. Explain what it shows.
MidWhat strong looks like: Checks completeness and categorisation quality before analysing, segments rather than reporting totals, and states explicitly what the data does not support concluding.
Two departments each believe they own a step in the same process. Resolve it.
SeniorWhat strong looks like: Separates the ownership question from the process question, proposes a decision rule rather than a compromise that satisfies neither, and names who signs off.
How to prepare
- #1
Practise turning a solution request into a problem statement. It is the single most-rewarded move in these assessments.
- #2
Write acceptance criteria for everyday workflows and check whether a tester could work from them unaided.
- #3
Rehearse stating what a dataset cannot tell you — candidates who name the limits consistently score higher.
- #4
Get quick at basic process mapping notation; you are marked on clarity rather than on tool proficiency.
- #5
Practise writing for two audiences, technical and executive, from the same underlying analysis.
- #6
Run a timed scored simulation so you know where your documentation is thin before it counts.
Common mistakes
Specifying the solution that was asked for without establishing the underlying need.
Writing acceptance criteria that cover only the successful path.
Drawing conclusions from data without checking its quality or completeness first.
Producing documentation so long that the decision points are buried.
Leaving ambiguity unresolved rather than flagging it explicitly.
Using the same register for an engineering audience and an executive one.
How it's scored
| Criterion | What strong looks like |
|---|---|
| Requirement quality | Requirements are unambiguous, testable, and traceable to a stated business need. |
| Clarifying instinct | Identifies what is missing or contradictory and raises it, rather than assuming silently. |
| Analytical soundness | Conclusions are supported by the data presented, with limitations stated. |
| Edge case coverage | Boundaries, exceptions and failure paths are documented, not just the intended flow. |
| Communication | Written at the right level for the stated audience, structured so the decision is easy to find. |
Frequently Asked Questions
Will I need SQL or Excel?
Frequently one or the other, at a basic level. The analysis is usually small enough that the tool matters less than whether your interpretation is supported by the data.
How detailed should requirements be?
Detailed enough to be testable, short enough to be read. Assessors look for unambiguous acceptance criteria rather than volume of documentation.
Do I need a specific methodology background?
Usually not. Agile and waterfall backgrounds both do well. What is marked is clarity of thinking, not familiarity with a particular ceremony.
What separates a strong submission?
Almost always the clarifying questions. Candidates who identify what the request leaves undefined score consistently higher than those who produce a polished specification of the wrong thing.
Can I practise one before the real thing?
Yes — Cohesyve gives you five free assessments a month with a scored report showing which criteria you fell short on.
Practise another role
Cohesyve · Practice for candidates
Practise a Business Analyst assessment now — free.
Five scored assessments a month, a full report on every run, and a learning pathway built from what you got wrong. No card required.
5
free assessments a month
$0
no card required
Full
scored report every run
Every
question type included
5 free assessments a month · No card required · Pro from $16/mo
For hiring teams
Hiring for a Business Analyst role? See how your applicants perform before you spend interview time.