Purpose
Good evaluations start with role clarity, not tooling. This page shows how to design evaluations that measure what actually matters for a role.Start with role clarity
Before you configure anything, answer four questions:What does the role actually require?
The skills and responsibilities that matter, not a generic job description.
What does 'strong' look like?
The bar a candidate needs to clear, stated in terms you can score against.
Which stages add real signal?
Every stage should justify itself, extra stages add drop-off, not insight.
Who owns the final call?
The hiring manager owns what “good” looks like; talent owns consistency.
What strong evaluation design looks like
Role-first, not tool-first
Start from what the role needs, not from what the platform can run.
Only as many stages as needed
Fewer, higher-signal stages beat a long funnel that adds drop-off.
Traceable to the rubric
Every report ties back to a defined dimension, not a black-box score.
You define what matters
Exterview evaluates consistently against your criteria, it doesn’t set them.
Map the evaluation
A clean evaluation traces a straight line from the role to the report: Each step should justify the next: skills come from the role, the rubric measures the skills, the session type collects the evidence, and the report reflects the rubric.FAQs
How many stages should an evaluation have?
How many stages should an evaluation have?
Only as many as add signal. Extra stages increase drop-off without improving the decision.
Who should design the evaluation?
Who should design the evaluation?
The hiring manager and talent lead together, the manager owns what “good”
looks like; talent owns consistency.
Does Exterview decide the criteria for us?
Does Exterview decide the criteria for us?
No. You define what matters; Exterview evaluates against it consistently and traceably.
Related
Scoring Quality
Keep scoring consistent once the evaluation is designed.
Operations Setup
Where rubrics, pipelines, and gating are actually configured.