← Back to the blog

Interviewing

How to build an interview scorecard with behavioral anchors

Turn broad hiring criteria into observable behaviors, consistent questions, and evidence-based ratings for a startup interview process.

InterviewingTemplates

An anchored interview scorecard explains what evidence supports each rating. Start with the work the person must perform, define observable behavior, and give interviewers a way to distinguish a concern from missing information.

A scorecard should help people reason consistently. It should not turn a complex decision into an unexplained average.

Select a small set of essential responsibilities from the role brief. Replace vague criteria such as “impressive” or “culture fit” with work-related behaviors.

For example, a customer-facing engineer may need to clarify requirements, make implementation tradeoffs, and coordinate a supported release.

OPM's structured interview guidance recommends consistent questions and rating standards. The scorecard below applies that principle to an illustrative startup assessment.

Write anchors before interviewing

Illustrative dimension: clarifies ambiguous requirements

RatingBehavioral anchor
ConcernCommits to a solution while important requirements remain unresolved
Meets the role's needIdentifies missing information and uses it to narrow the problem
Strong evidenceAlso explains competing needs and a sensible way to resolve them
Not assessedThe interview did not provide enough relevant evidence

These labels are a template. Define the required level for your role before seeing candidates.

Attach evidence to the rating

Ask interviewers to record the question, the relevant response or behavior, their interpretation, and remaining uncertainty.

“Asked who would maintain the integration before proposing an approach” is evidence. “Seems strategic” is an interpretation that needs support.

Do not include unrelated personal details in the scorecard.

Keep requirements distinct

A polished communicator may still have an untested technical skill. Strong technical execution may coexist with a specific collaboration concern.

Record the dimensions separately so one positive impression does not silently fill every box. Define which requirements are essential and which gaps the team can support.

Do not mechanically compensate for an essential missing skill with high ratings elsewhere.

Calibrate the interviewers

Before the process begins, discuss a fictional response and compare ratings. If interviewers interpret an anchor differently, refine the wording.

After interviews begin, investigate recurring uncertainty in the assessment design. Avoid rewriting the bar to fit a preferred candidate.

Use the scorecard in the decision

Collect independent notes before the debrief, then discuss evidence and unresolved questions. The final decision should explain how the candidate meets the role's requirements.

Use the interview evidence map to assign each dimension to an assessment and the debrief guide to handle differing conclusions.

Put this guide to work

Hire people who build like founders.

Share the role, the outcomes this person should own, and your hiring constraints. Refery brings specialist recruiters and trusted referrals behind one brief.