What is a hiring rubric? Definition, types and an example

A hiring rubric is a written guide that defines, for each criterion a candidate is assessed on, what weak, adequate and strong performance looks like, so that different interviewers give the same answer the same score. It turns a label such as "good communicator" into observable behavior at every point of the rating scale.

This page explains the parts of a rubric, the main types, how to build one, a filled example, and how a rubric differs from a scorecard or a rating scale. If you need ready-made anchors to paste in, the library of behavioral anchors covers nine common competencies.

What are the parts of a hiring rubric?

The anchors do most of the work. Without them, a rubric is only a list of criteria and a set of numbers, and each interviewer fills the gap with their own standard. Choosing an interview rating scale covers the number of points and the decision rules in more depth.

Why does a hiring rubric matter?

Interviewers rarely disagree about what a candidate said. They disagree about what it was worth. A rubric moves that argument to before the interviews, when nobody has a favorite yet.

The selection research treats this as one of the core parts of a well-built interview. OPM's guide calls a common rating scale for all candidates a key component of the structured interview, and its comparison of formats notes that unstructured interviews, which have no standard scale and no agreed acceptable answers, tend to show low agreement between interviewers. The review of interview structure by Campion, Palmer and Campion (1997) lists anchored rating scales among its fifteen components of structure. In practice, a rubric gives you three things: scores that mean the same across interviewers, a debrief that argues about evidence instead of taste, and a written reason for the decision that you can share with the hiring team.

What types of hiring rubric are there?

• Analytic rubric. Each criterion is rated separately, then the ratings are combined. This is the usual form for interviews, because it shows where a candidate is strong and where they are not.
• Holistic rubric. One overall rating with a description per level. Faster, but it hides trade-offs and invites halo effects, where one strength colors everything.
• Behaviorally anchored rating scale (BARS). Each level is described with examples of actual behavior. The method goes back to Smith and Kendall (1963, Journal of Applied Psychology), who set out a way to build unambiguous anchors for rating scales.
• General versus question-specific. The U.S. Office of Personnel Management's structured interview guide pairs a general five-level proficiency scale (Awareness, Basic, Intermediate, Advanced, Expert) with question-specific examples of what an answer at each level sounds like. The general scale keeps competencies comparable; the specific examples make each question scoreable.
• Work-sample rubric. The same idea applied to a take-home task, case study or trial shift, rating the output rather than an answer. See how to evaluate a take-home assignment.
• Knockout checklist. Pass or fail on hard requirements such as a license or shift availability. It belongs at the screen, not in place of a rubric.

How do you build a hiring rubric?

OPM's guide describes a process that small teams can scale down without losing what matters:

1. Start from the job. List the tasks and the competencies they need. Pick the four to six that the interview will assess.
2. Choose one scale for everything. OPM recommends at least three proficiency levels and suggests aiming for five to seven. Many teams settle on four so nobody can sit in the middle.
3. Ask people who know the job. For each question, have experienced employees or supervisors write how someone at each level would actually answer. Keep the examples they agree on.
4. Write anchors as behavior. What the candidate did, how often, with what result. Not adjectives.
5. Test it on real answers. Have two or three interviewers score the same recorded or written answers alone, compare, and rewrite anchors where scores split. That is an interview calibration session.
6. Treat anchors as a guide. OPM notes that candidates' answers will differ from the examples, so interviewers use them to judge level, not as a script to match word for word.

What does a hiring rubric look like?

An invented example for a project coordinator role:

Criterion: Stakeholder communication (must-have)
Definition: Keeps the people who depend on the work informed early
enough for them to act.
Question: "Tell me about a project where something you were responsible
for was going to be late. What did you do?"

4  Spotted the risk early, told affected people before the deadline
   with options and a recommendation, confirmed the new plan in
   writing, and followed up until it landed.
3  Told affected people before the deadline and agreed a new date;
   options or written follow-up missing.
2  Told people only when asked, or on the day it was due; little
   sense of who needed to know.
1  The deadline was missed before anyone was told, or the candidate
   describes someone else handling it.
Not assessed: no relevant example after two probes.
Threshold: 1 on this criterion ends the process.

Two interviewers who hear "I emailed the client the morning it was due and we pushed a week" should both land on a 2. If one gives a 3 because the candidate was likeable, the rubric has done its job by making the disagreement visible and discussable. Ratings like these are recorded, with evidence, on each interviewer's interview scorecard.

How is a rubric different from a scorecard, a rating scale or a job description?

What are the most common rubric mistakes?

• Adjective ladders. "Poor, fair, good, excellent" is a scale with labels, not a rubric. Each level needs behavior someone could observe.
• Describing traits instead of actions. "Confident" and "polished" reward presentation style. Describe what the person did.
• Levels nobody can tell apart. If the difference between a 6 and a 7 cannot be put into words, merge them.
• Writing it after the interviews. A rubric written once candidates are known tends to describe the favorite. Lock it before the first screen.
• Keyword matching. A rubric that awards points for saying "stakeholder" or "agile" scores vocabulary, and rehearsed or AI-written answers are full of the right words. Score the specifics: what happened, what the candidate did, what changed.
• Never training interviewers on it. A rubric in a shared folder that nobody has practiced with changes nothing. Run one calibration before a role opens.
• Never revising it. When the job changes, the anchors should too. Date each version.

When should you use a hiring rubric?

Use one for every scored stage: the phone screen's must-haves, each interview in the loop, and any work sample. It matters most when several people assess the same role, when candidates are compared over weeks, and when the decision may need to be explained later. A rubric is also what makes a structured interview structured: same questions are not enough if everyone scores them differently.

For a role you hire once with one interviewer, a lighter version still helps: three to five criteria with a one-line description of a strong and a weak answer for each. It takes half an hour and makes the decision easier to explain to the candidate, the team and yourself. For worked questions and anchors by competency, see behavioral interview questions with a scoring rubric and competency-based interviewing.