Interview Rubric: How to Build One, With a Template
What goes in a rubric for each interview question, how to write levels your panel reads the same way, and how to test it before the first interview

An interview rubric is a scoring guide that describes what a weak, acceptable, and strong answer includes for each question. It gives every interviewer the same picture of each score, so two people who hear one answer can give it the same number.
Without one, a 1 to 5 scale leaves each interviewer to decide privately what a 4 means. That's how a debrief ends up with one person giving an answer a 2 and another giving it a 5. Writing down what each level contains before the interviews start closes that gap.
Say you're a recruiter working with a finance manager to fill an accounts payable specialist role at a regional distributor. The job requirements are catching invoice errors before payment, resolving payment disputes with vendors, and meeting month-end close deadlines. You can use those requirements to build a rubric that defines what a strong, acceptable, or weak response looks like for each interview question.
Key takeaways
- A scorecard is where ratings get recorded. An interview rubric describes what an answer at each score includes, question by question.
- Write each level from real examples of the work, and describe what the candidate says or did.
- Before the first interview, have two interviewers score one practice answer alone and rewrite any level they read differently.
- Score each answer on your own, write the evidence beside the score, and compare only after everyone has rated.
Interview rubric vs. scorecard: what each one does
A scorecard is the form where interviewers record ratings. An interview rubric is the guide that says what each rating means for a specific question. The interview scorecard holds the role's criteria and a general rating scale. The rubric sits behind each question and spells out what an answer scored 1, 3, or 5 includes.
That detail matters because labels like "strong problem solver" mean something different to each interviewer. When the levels describe behaviors instead, the rubric has a formal name. A behaviorally anchored rating scale ties each point on the scale to an example of what the candidate did or said. The template below works that way, even if you never use the term with a hiring manager or client.
Federal hiring guidance points in the same direction. The U.S. Office of Personnel Management (OPM) describes its most structured interviews as scored against "benchmarks of proficiency" in its structured interview guidance. OPM links more structure with higher validity, rater reliability, and rater agreement, along with less adverse impact. An interview rubric is a practical way to write those benchmarks down for your own openings.
What goes in an interview rubric template
Each question in the rubric covers the job requirement it tests, the question, the follow-up questions, and what an answer scored 1, 3, or 5 includes. Scores of 2 and 4 sit between the written levels. Interviewers use them when an answer has most of one level and part of the next.
The table shows the finished rubric for one question in the accounts payable example, after the practice test described further down.
| Job requirement | Question | Follow-up questions | 1 | 3 | 5 |
|---|---|---|---|---|---|
| Catches invoice errors before payment | Tell me about a time you found an error on an invoice that was already approved | How did you spot it? Who did you tell? What changed afterward? | Doesn't yet describe a specific invoice or says someone else found the error | Names a specific error and how they spotted it and held the payment until the invoice was corrected | Everything in a 3 and also found why the error happened and fixed the cause or told the person who could |
The job requirement goes first so every question has a clear reason to be in the interview. If you can't name the requirement a question tests, the question may not belong in the interview. A full interview scoring rubric is one of these tables per question. The follow-ups matter as much as the levels, since they're how an interviewer gets a thin answer to the point where it can be scored.
If you still need questions to build around, start with problem-solving questions. Each one comes with notes on strong answers that you can turn into levels. For manager roles, a set of leadership questions gives you the behaviors to write levels for.
How to write rubric levels interviewers read the same way
Write each level as what the candidate says or did, drawn from real examples of the work. That way, two interviewers reading a level picture the same answer.
Start from what people in the role did
Ask the hiring manager or client for two stories, one about a strong performer in the role and one about someone who struggled. Those stories set the ends of the scale in the manager's own words. In the accounts payable example, the finance manager described a specialist who caught a duplicate invoice before the payment run. The other story was about someone who paid invoices without checking them against the purchase order.
If the job requirements aren't settled yet, settle them first. The interview rubric can only be as clear as the job description it comes from.
Describe what the candidate did, not a label
A level should describe something you can hear in the answer. Interviewer trainers quoted in a 2026 SHRM article advise anchoring the scale to "observable, job-related behaviors or outcomes" instead of vague labels. They also suggest giving interviewers examples of poor, acceptable, and excellent answers for each competency.
"Good communicator" fails that test, because each interviewer fills it in differently. "Explained the disputed charge to the vendor and agreed on a corrected amount" works. You can tell from the answer whether it happened.
Define what the middle score means
Decide what a 3 means and write it into the rubric. The same SHRM article raises this exact point, asking whether a 3 on a five-point scale means acceptable performance, average performance, or something else. In the accounts payable rubric, a 3 means the candidate meets the job requirement as the role needs it today. So a 3 is a hireable answer, and the panel won't treat it as a polite way of saying weak.
Check that the levels don't reward the wrong things
Cut anything from a level that the job doesn't need. Polish, a well-told story, and credentials the role doesn't require can creep in because they're what interviewers notice first. Say a candidate gives a plain, halting account of catching a duplicate payment. That candidate has still shown the skill, so the 5 level shouldn't ask for confident delivery.
Search on the same job requirements
Book a demoTest the interview rubric with a practice answer
Before the first interview, have two or more interviewers score the same practice answer on their own, then compare. You can write a realistic answer yourself or adapt one from a past search with the details removed. Any level that produced different scores gets rewritten. A level that two people read differently in practice is likely to split them again with real candidates.
In the accounts payable example, the practice answer described a specialist who spotted a wrong unit price on an approved invoice. The specialist held the payment and got a corrected invoice from the vendor. The finance manager scored it a 5, and you scored it a 3. The first draft of the 5 level said only "fixed the error," which the finance manager read as met.
You expected a strong answer to explain why the price was wrong in the first place. So the two of you rewrote the 5 level to say the candidate also found the cause. That's the version in the table above.
Agreement between interviewers can also slip after the first round, as a 2022 residency study of one U.S. surgery residency program with 45 interviewers suggests. The program added interviewer training and structured interviews with behaviorally anchored scales. Agreement between interviewers then rose from a range the authors called "poor" to "fair" up to the "good" level. The share of applicants with ratings more than 2 points apart fell from 59% to 47%.
Training and structure changed at the same time, so the study can't say which one made the difference. The authors also note that refresher training may be needed to keep agreement up. Plan one when the panel changes or after a few hiring rounds on the same rubric, and have the new panel score a practice answer alone first.
Use the rubric during and after the interview
Score each answer against the written levels as soon as it ends, or right after the interview. Write the evidence beside the score, as a short note on what the candidate said. A note like "held the payment and called the approver" next to a 3 shows the debrief why it's a 3. When an answer lands at a 1, note what it doesn't yet show and which follow-up might draw it out.
The SHRM trainers also advise rating each candidate independently against the job's requirements. In a panel interview, everyone records scores before anyone shares theirs. That way the first opinion voiced doesn't set the number for the room. Anyone new to the panel will also need broader interviewer preparation than the rubric gives them.
Final ratings go on the scorecard. The evidence notes help later when you write candidate feedback, since they describe what the answer showed. A rubric score is one piece of evidence for the hiring decision. Even a strong score doesn't prove how someone will perform in the job.
Start with one question before you build the rest
An interview rubric does its job when every interviewer reads a level and pictures the same answer. That comes from writing levels as things candidates did, then checking them before the stakes are real. You don't need every question finished to see whether it's working. Write the rubric for the question tied to your most important job requirement, and score one practice answer with a second interviewer this week.
Know which requirements to ask about
Book a demoFrequently asked questions
Can you reuse an interview rubric for another opening?
You can reuse the format and any question that tests the same job requirement. Check each level against the new role first, though. A 3 for an entry-level accounts payable role may be too low a bar for a senior one. Run the practice-answer test again whenever the levels change.
What if a candidate's answer doesn't fit any level?
Score the parts of the answer that match a level, and note what it doesn't yet show. If the candidate skipped something the levels need, ask a follow-up before scoring instead of guessing. When several candidates give answers the rubric doesn't cover, revise the levels between interview rounds.
Should interviewers see the rubric before the interview?
Yes. Share it with each interviewer ahead of time, not at the start of the interview. Interviewers who have read the levels know which follow-ups to use. They can get an answer to a scorable point while the candidate is still in the room.
About the author

Founder & CEO of Rotto, building tools that help tech recruiters source better candidates, faster.





