A candidate screening rubric defines what you are assessing, what evidence supports each rating, and how the hiring team will use the results. Start with the work the person must do, then translate those responsibilities into a small set of observable criteria.
Write the rubric before reviewing applicants. Changing the standard after seeing a candidate makes comparison less consistent and can turn a scoring process into a justification for an existing preference.
1. Separate requirements from preferences
List the outcomes the role must deliver. For each outcome, identify the relevant skill or behavior and where you will assess it: application, short work sample, prescreen, or interview.
Distinguish genuine must-haves from skills that can be learned. If a license is required for the role, record that as a separate eligibility check. A missing eligibility requirement should not be disguised as a low communication score.
Choose four or five criteria that the screening stage can actually observe. Save competencies that require deeper evidence for later stages.
2. Define anchored ratings
A rating becomes useful when reviewers understand what distinguishes one level from another. Here is an illustrative four-point rubric for a short problem-solving exercise:
| Rating | Evidence standard |
|---|---|
| 4 — Strong | Identifies the core problem, evaluates alternatives, and checks the result against realistic constraints. |
| 3 — Sufficient | Uses a workable method, explains the main decisions, and performs an appropriate check. |
| 2 — Incomplete | Makes useful progress but leaves an important gap in the method or validation. |
| 1 — Insufficient | Does not demonstrate a workable approach to the essential task. |
| N/O — Not observed | The exercise did not provide enough evidence to rate this criterion. |
This is a design example, not a scientifically validated cutoff for every role. Replace its wording with behaviors relevant to your vacancy.
3. Match questions to criteria
Give each criterion a defined source of evidence. A question about troubleshooting should produce evidence about troubleshooting, rather than becoming a general impression of confidence.
Use job-related prescreening questions to cover the initial stage. When a resume does not provide enough skills evidence, short skills exercises without a take-home assignment can provide a more direct observation.
The OPM structured-interview guidance explains how consistent questions and evaluation procedures support comparison across candidates.
4. Set the decision rules in advance
Decide which criteria are essential, whether any ratings require follow-up, and how incomplete evidence will be handled. Do not convert “not observed” into a failure. If you use weights, document why the role requires them; numerical precision does not make an arbitrary weighting valid.
Review sample responses together before launch. Ask reviewers to score independently, compare their evidence notes, and resolve disagreements about the anchors. Keep notes such as “explained how they checked the error,” rather than “good culture fit.”
5. Keep the rubric connected to the workflow
Use the same core standards for comparable candidates and record changes when the job requirements change. Consistent candidate evaluation can support the assessment and scoring workflow, but software does not decide which requirements matter for your role.
Bottom line
A useful rubric connects job requirements to observable evidence and explicit ratings. Keep eligibility checks separate, define how missing evidence is handled, and calibrate reviewers before using the rubric to shortlist applicants.