01
Pick observable competencies
Prefer ownership, adaptability, customer empathy, and judgment over vague labels like “culture fit” or undefendable traits. If two trained reviewers cannot describe what the competency looks like at work, the model will not magically make it valid. Start from the job: which behaviors distinguish strong performers?
- Ownership, judgment, collaboration, customer empathy, execution, coachability
- Avoid vague culture-fit proxies that invite bias
- Weight competencies by role criticality
- Document why each competency is job-related
02
Write anchors, not vibes
A score of 5 should describe concrete behaviors: personal responsibility, actions taken, outcomes measured, prevention reflected. A score of 1 should describe avoidance, blame, or unrelated examples. Anchors should be specific enough that a new reviewer-and a scoring system-can apply them consistently.
- Describe observable actions, decisions, and outcomes
- Include what “missing evidence” looks like, not only what excellence looks like
- Call out common false positives (fluent but generic answers)
- Align anchors to the question prompts candidates will see
03
Design questions that can elicit the evidence
A brilliant rubric fails if the question cannot elicit the behaviors you want to score. Use structured behavioral and situational prompts that invite specifics: context, actions, constraints, outcomes, and reflection. Plan follow-ups for shallow answers. Freeze the approved set so candidates are comparable.
- Pair each competency with prompts designed to surface it
- Include consistency probes across the assessment
- Avoid leading questions that telegraph the “right” story
04
Calibrate with humans before you scale AI
Have hiring managers and trained raters score a sample of responses using the anchors. Measure agreement. Revise ambiguous anchors. Only then let automated scoring assist at volume. Calibration is how you keep AI tied to your standard instead of drifting into generic eloquence rewards.
- Double-score a calibration set
- Discuss disagreements and tighten language
- Track ongoing reviewer–model disagreement after launch
