Interview scorecard for business analysts, with anchors for each competency
On this page
- Which competencies should a business analyst scorecard cover?
- The scorecard: weights and what a 1, 3 and 5 look like
- Copy-ready business analyst scorecard
- What should each interviewer ask, and what counts as evidence?
- Which work samples produce scoreable evidence?
- A filled example
- How do you adjust it for the seat and the level?
- Mistakes specific to scoring business analysts
- Where does this scorecard fit in the hiring process?
- Questions people ask
A business analyst interview scorecard should score six lines separately: eliciting the real need, writing requirements that can be tested, analyzing processes and data, facilitating decisions when stakeholders disagree, supporting delivery through testing and change, and clear written communication. Weight elicitation, requirements quality and analysis highest, and score them from two short work samples, because every business analyst can name BRDs, user stories and process maps, and only an exercise shows who asks the question that changes the solution. A CBAP or CCBA is background to verify, not points.
The scale is the 1–5 interview rating scale and the layout follows the interview scorecard template. The seat questions, domain fit and logistics knockouts are in business analyst phone screen questions; this scorecard is for the panel: the hiring manager, a stakeholder from the business and a developer or tester who will work from the analyst's requirements.
Which competencies should a business analyst scorecard cover?
- Elicitation. Prepares, interviews, observes and runs workshops to find the need behind the request, and confirms what was heard.
- Requirements quality. Writes requirements and acceptance criteria a developer can build from and a tester can test, including exceptions and error cases.
- Process and data analysis. Maps the current and future state with volumes, handoffs and exceptions; on data seats, checks claims with their own query.
- Facilitation and stakeholder alignment. Makes trade-offs visible, finds the decision owner and records the decision.
- Delivery support and solution evaluation. Answers build questions, manages changes, supports user acceptance testing and checks after go-live whether the need was met.
- Written and visual communication. Documents and diagrams that the business and IT both read the same way, and a one-paragraph summary an executive can act on.
These lines track IIBA's body of knowledge, which names six knowledge areas: business analysis planning and monitoring, elicitation and collaboration, requirements life cycle management, strategy analysis, requirements analysis and design definition, and solution evaluation (IIBA, business analysis knowledge areas, as of November 2026). An interview can observe the last five directly; planning shows up in how the candidate prepares for elicitation.
The scorecard: weights and what a 1, 3 and 5 look like
Example weights for an IT business analyst on a systems change team. Adjust them for the seat and lock them before the first candidate.
| Competency | Weight | 1 looks like | 3 looks like | 5 looks like |
|---|---|---|---|---|
| Elicitation | 20% | "I ask what they want and write it down"; one stakeholder, one meeting | Prepares questions, talks to the people who do the work as well as the requester, plays back what they heard | Found a need nobody had stated (a downstream team, a regulatory step) that changed the solution, and can show how |
| Requirements quality | 20% | Vague statements ("the system should be fast"); no acceptance criteria | Specific requirements with testable acceptance criteria, including the main exceptions | Requirements a tester used unchanged; traced each to a business need and caught a gap before build |
| Process and data analysis | 20% | Draws the happy path only; no volumes | Maps current and future state with handoffs, volumes and the costly exception; checks a number before relying on it | Quantified the problem (volumes, rework, cycle time) and used it to rank options |
| Facilitation and stakeholder alignment | 15% | Sides with the most senior person, or claims there was never conflict | Lays out the trade-off, gets the decision owner to decide, records the decision | Brought opposed departments to a recorded decision that held through delivery |
| Delivery support and solution evaluation | 15% | Hands over the document and moves on | Answers developer questions, runs changes through an agreed process, supports UAT | Checked after go-live whether the need was met and fed the gap back as a new requirement |
| Written and visual communication | 10% | Long documents nobody reads; jargon for the business | Clear documents and diagrams at the right level for each reader | Created a template or standard the team adopted |
A 2 shows part of the 3 behavior, or only after prompting; a 4 shows the 3 behavior and part of the 5. Mark a line "not assessed" if it never came up. Score the substance of the answers, not polish or accent.
Copy-ready business analyst scorecard
Candidate: [name] Seat: [IT systems / process / agile team / data-leaning] Domain: [ ]
Interviewer: [name] Stage: [hiring manager / stakeholder role-play / developer or tester]
Competency Weight Score (1-5 or N/A) Evidence (their words or the work sample)
Elicitation 20% [ ] [questions asked; who they would talk to]
Requirements quality 20% [ ] [user stories; acceptance criteria; exceptions]
Process and data analysis 20% [ ] [current/future state; volumes; checks]
Facilitation and stakeholder alignment 15% [ ] [decision owner named; decision recorded]
Delivery support and solution evaluation 15% [ ] [change process; UAT; after go-live]
Written and visual communication 10% [ ] [the written exercise; the summary]
Requirements (pass/fail, not scored): [domain or system experience if a true must-have]
[certification only if the job requires it, verified]
Weighted score: [ ] Open questions: [ ] Recommendation: [Strong yes / Yes / No / Strong no]
What should each interviewer ask, and what counts as evidence?
Elicitation
Run the stakeholder role-play below. Then ask: "Tell me about a need you found that the requester never mentioned." Evidence: they talked to the people doing the work, not only the sponsor, and confirmed what they heard. See interview questions for active listening for probes.
Requirements quality
Score the user stories from the written exercise. Give them to the developer or tester on the panel: could they build and test from them without coming back with questions? Then ask: "Pick a requirement you wrote that turned out wrong. How did you find out?"
Process and data analysis
Ask: "Describe a process you mapped. What was the exception that caused the most trouble, and how many cases a month was it?" On data-leaning seats, add one query question from the data analyst scorecard rather than a full SQL test.
Facilitation and stakeholder alignment
Ask: "Two departments wanted opposite things from the same system. What did you do?" A 3 made the trade-off visible, got the person who owned the decision to make it and wrote it down. A candidate who "made the call" themselves may be describing a product owner's job; ask who had the authority. See interview questions for stakeholder management.
Delivery support and solution evaluation
Ask: "What happened between handing over the requirements and go-live on your last project? What did you check afterward?" Evidence: specific developer questions answered, a change handled through the team's process, test cases or UAT support, and a look at whether the result met the original need.
Written and visual communication
Score the written exercise and one more task: "Summarize your recommendation for the returns process in three sentences for the COO." Evidence: the decision needed, the reason and the cost of waiting, in plain words.
Which work samples produce scoreable evidence?
The messy request (30 minutes, written). Hand over a made-up email from an operations director: "We need the returns process automated. Customers complain it takes too long, and finance says refunds are coming out wrong. Can you get requirements to IT by Friday?" Ask the candidate to list the questions they would ask and whom they would ask, then write two user stories with acceptance criteria for one part of the process.
What to look for: seeing two problems (cycle time and refund accuracy) rather than one; questions about volumes, the current steps, the kind of refund error and who decides; and acceptance criteria a tester could pass or fail, including at least one exception (a partial return, a return past the window). Give every candidate the same email and time; see what is a work sample test for keeping it fair.
The stakeholder role-play (20 minutes). An interviewer plays the warehouse returns supervisor, briefed with a script. Early on, the supervisor says "every return gets inspected before restocking." Ten minutes later, in passing: "anything under twenty-five dollars we just put back on the shelf."
What to listen for: open questions, then specifics (how many returns a day, who inspects, what happens to damaged items); catching the contradiction and asking about the under-$25 rule; and a playback summary at the end that includes the exception. A candidate who pitches a solution in the first five minutes scores 2 at most on elicitation.
A filled example
A made-up candidate for an IT business analyst seat at a retailer:
Elicitation: 4 (20%). Caught the under-$25 exception and asked how many returns it covered; planned to sit with the returns team for a morning.
Requirements quality: 3 (20%). Two clear user stories with testable criteria; covered partial returns but not returns past the window.
Process and data analysis: 3 (20%). Mapped the current state with handoffs; did not ask for volumes until probed.
Facilitation and stakeholder alignment: 4 (15%). Described getting finance and the warehouse to agree a refund rule and recording it in the decision log the sponsor signed.
Delivery support and solution evaluation: 2 (15%). Supported UAT on the last project but had not checked results after go-live.
Written and visual communication: 3 (10%). The COO summary was clear but did not state the decision needed.
Weighted score: 3.2 of 5. (0.2 x 4 + 0.2 x 3 + 0.2 x 3 + 0.15 x 4 + 0.15 x 2 + 0.1 x 3.) Recommendation: Yes, with a post-go-live review of their first change as a 90-day goal.
How do you adjust it for the seat and the level?
| Seat or level | What changes |
|---|---|
| IT or systems analyst | Add data mapping and integration questions to analysis; the developer on the panel scores requirements quality. |
| Process improvement analyst | Raise process analysis to 30%; replace the user stories with a current-and-future-state map. |
| Analyst in an agile team | Score backlog refinement and acceptance criteria under requirements quality; compare the product manager scorecard if the seat owns priorities. |
| Data-leaning analyst | Add a data line (own queries, checks against a known total) at 15–20%. |
| Junior analyst | Accept school, internship or operations examples; a 3 means sound questions and criteria with some prompting. |
| Lead or senior analyst | Add planning the analysis approach and coaching other analysts; a 5 in facilitation means decisions across senior leaders. |
Mistakes specific to scoring business analysts
| Mistake | Why it fails | Fix |
|---|---|---|
| Scoring vocabulary (BPMN, BRD, MoSCoW) as skill | Anyone can name artifacts; few write ones a tester can use | Score the work sample, read by the developer or tester |
| Rewarding the candidate who talks most in the role-play | Elicitation is asking and listening, not presenting | Count the questions asked and the exception caught |
| Crediting "I decided" on stakeholder conflicts | The decision usually belongs to a product or business owner | Ask who had authority and score how the analyst got the decision made |
| Adding points for certification | Double counts background and favors tenure over evidence | Verify it if listed; score the exercises |
| Long unpaid take-home projects | Strong candidates with jobs drop out; you score free time, not skill | Keep the exercise to 30 minutes, the same for everyone |
If a candidate lists an IIBA certification, check it through IIBA's directory or the digital badge the candidate shares. IIBA says its certifications and membership "can be verified at any time," but holders build their own directory profiles and can set a badge to private, so a missing listing is a reason to ask for the badge link, not proof of anything (IIBA, digital badge program and directory, as of November 2026).
Where does this scorecard fit in the hiring process?
Write the rows from the must-haves in the business analyst job description template, screen for seat and domain fit on the first call, then run the panel and the two work samples with this scorecard, each interviewer scoring alone before the debrief. Offer the same accommodations for the written exercise you would for any test (see ADA accommodations in interviews). Carry the lowest line of the person you hire into their 30-60-90 day plan.
If you hold the interviews on a video call with Interview Signal, our desktop app, you can enter these competencies as the role's scorecard areas: it scores each area from 1 to 10 during the call with the candidate's own quotes as evidence, deletes any quote not found word for word in the transcript, and caps an area with no surviving quote at 5, marked "Probe further" (see how the verified-quote scorecard works). The written exercise is still scored by the person reading it.
Questions people ask
What should a business analyst interview scorecard include?
Score six lines: eliciting the real need from stakeholders, writing requirements that can be tested, analyzing processes and data, facilitating decisions when stakeholders disagree, supporting delivery through testing and change, and clear written communication. Weight elicitation, requirements quality and analysis highest, and score them from a short work sample rather than from the candidate's description of their methods.
What work sample should I use to interview a business analyst?
Use two short exercises given the same way to every candidate: a messy request email they turn into questions and two user stories with acceptance criteria, and a 20-minute role-play where an interviewer plays a stakeholder with one planted contradiction. Together they show whether the candidate finds the real problem, writes criteria a tester could use and catches the exception a stakeholder mentions in passing.
Should a CBAP or CCBA certification raise a business analyst's interview score?
No. Verify an IIBA certification if the candidate lists it, through IIBA's directory or the digital badge the candidate shares, and treat it as background. Score the elicitation, requirements and analysis evidence from the interview and work sample so certified and uncertified candidates are compared on the same terms.
How is a business analyst scorecard different from a product manager or data analyst scorecard?
A business analyst scorecard weights eliciting and documenting what stakeholders need and helping the decision owner choose, while a product manager scorecard weights deciding what to build and owning the trade-offs. A data analyst scorecard weights SQL and analytical rigor. If your seat is really one of those, use that scorecard, or add its strongest line to this one.