Business Analyst interview scorecard template
A structured scorecard for interviewing a Business Analyst: six weighted competencies, what a 1 and a 5 actually look like, and questions that surface evidence instead of opinions. Print it, or copy it into your ATS.
The Business Analyst scorecard
| Competency | Weight | Score 1 — what it looks like | Score 5 — what it looks like |
|---|---|---|---|
| Requirements elicitation and disambiguation Whether the candidate gets past what stakeholders ask for to what the work has to accomplish, before anyone starts building. | 20% | Transcribes stakeholder requests into a document and treats a signed list of features as a completed requirements phase. | Names a request they reframed after asking what problem it solved, and the requirement that changed once the real constraint surfaced. |
| Current-state process mapping Whether the candidate documents how work is actually done, including the workarounds people use, rather than the official procedure. | 18% | Maps the process from the manual or from one manager interview and misses the spreadsheet the team really runs on. | Describes sitting with the people doing the work, the undocumented step they found, and how that discovery changed the proposed solution. |
| Specification quality and acceptance criteria Whether what the candidate writes can be built and tested without a follow-up meeting, which governs how much rework the delivery team absorbs. | 18% | Writes requirements as capability statements with no acceptance criteria, edge cases, or definition of what a correct result looks like. | Shows criteria written so a tester could verify them, including the edge case and the error path, and cites an ambiguity a developer caught. |
| Stakeholder alignment and sign-off How disagreement between areas gets resolved before build starts, which determines whether a project stalls at user acceptance testing. | 16% | Reports that all stakeholders agreed, and cannot describe a conflict between two areas over the same process. | Names two areas that wanted different outcomes, what each stood to lose, and how the decision was made and recorded before build began. |
| Scope arbitration and trade-off framing Whether the candidate can present options with costs attached, instead of passing every scope question upward as a decision for someone else. | 16% | Escalates each scope question to a sponsor without a recommendation, or accepts additions without naming what they displace. | Describes a scope cut they proposed, the workaround the business accepted in the interim, and who signed off on carrying that gap. |
| Post-implementation validation Whether the candidate checks that the delivered change produced the intended effect, or considers the work finished at go-live. | 12% | Ends involvement at deployment and measures success by whether the release went out on the planned date. | Names the measure they checked weeks after launch, what it showed, and the follow-up change they requested because of the result. |
Weights sum to 100. Agree them before the first interview, not after — adjusting weights once you have scores is how a panel rationalises a favourite.
Questions that surface evidence
Each one asks for something that already happened, in enough detail to verify. Hypotheticals reward rehearsal, not track record.
- Tell me about a request you reframed. What did the stakeholder ask for, what did you find they actually needed, and how did the scope change?
- Describe a process you mapped. What step did you find that was not in any documentation, and how did it change the solution you proposed?
- Show me how you wrote acceptance criteria for one requirement. What edge case did you include, and what ambiguity did a developer still find?
- When did two areas want different things from the same process? What did each stand to lose, and how was the decision made and recorded?
- Take a project you delivered. What did you measure weeks after go-live, what did it show, and what did you ask to change because of it?
Red flags
- Describes requirements work as writing down what stakeholders asked for, with no example of a request challenged.
- Cannot name a project where the delivered solution differed from the original request.
- Every stakeholder group is described as aligned, with no conflict ever surfacing between areas.
- Treats go-live as the end of the work and never checked whether the change worked.
How to use this scorecard
- Agree the weights with the panel before anyone interviews, and write them down.
- Every interviewer scores every competency independently, adding a note that quotes what the candidate actually said.
- Compare scores before discussing them. Discussing first anchors the panel on whoever speaks loudest.
Build a custom scorecard → · Boolean string to source a Business Analyst →
Frequently asked questions
What should a business analyst interview scorecard include?
Weighted competencies tied to where projects fail: requirements elicitation and disambiguation, current-state process mapping, specification quality with acceptance criteria, stakeholder alignment, scope arbitration, and post-implementation validation. Weight elicitation and specification highest, since ambiguity written down early becomes rework paid for later. Anchors matter because every candidate will describe themselves as a good communicator.
How do you test business analysis skills in an interview?
Ask the candidate to show real work: the acceptance criteria they wrote for one requirement, the process map that revealed an undocumented step, the request they pushed back on. You can also hand them a deliberately vague request and listen to the questions they ask. The questions reveal more than any answer they could prepare.
What is the difference between a business analyst and a product manager?
A business analyst is accountable for a change being specified correctly and adopted by the affected areas; a product manager is accountable for choosing what gets built at all. The competencies overlap around stakeholders and scope, but the decision rights differ. Decide which accountability your team is missing before you write the scorecard, or you will interview for one and hire the other.
When the stakes are a real hire, use evidence
These tools are quick heuristics. Verdict reads the CV against your job description and scores six dimensions with verbatim quotes as evidence — a hiring document you can defend.