How to build a sales interview scorecard.

Start here

Start with the role, not the card.

The mistake is starting from a generic list of sales virtues. Start from the role instead. Break down the sales motion and work backward from what winning actually requires. An enterprise, multi-stakeholder motion rewards multi-threading, building a business case, and staying disciplined through a long cycle. A high-volume motion that lives or dies on prospecting rewards self-sourcing, activity, and resilience to rejection. A fast, inbound-heavy motion rewards speed and sharp qualification. What belongs on the card falls out of that question — not out of a template.

Then look at your team, not just the role. Two questions are worth asking before you finalize the card. One: do you want someone who mirrors what your best reps already do well — the same competencies, aimed at the same outcomes? That’s a proven, lower-risk profile. Two: is there something your team is missing — a strength no one has yet — that, if someone brought it, would resonate through the team and make it meaningfully better? Sometimes the highest-leverage hire covers a gap instead of cloning a strength, and deciding which you’re optimizing for changes what goes on the card. That’s the heart of context-aware hiring — cloning a strength or covering a gap on purpose.

Once you know what the role needs and what your team is missing, you translate it into the three things a scorecard scores — competencies, skills, and outcomes. The discipline is the same for all three: brainstorm wide, then cut hard to the 3–4 items that actually matter. It’s the “Scored” pillar of the 4 Pillars of Talent Selection, applied to a sales role; the full process lives on how to hire salespeople. And it pays off: structured interviews are the single best predictor of job performance among all selection methods (Sackett et al., 2022) — when the structure is disciplined rather than sprawling.

Part two · Skills

What you can’t teach fast — so check they already have it.

Skills are concrete technical, functional, or domain abilities — as opposed to the behavioral competencies above. But the filter that decides what actually earns a spot is sharper than “is it a skill”: put the ones a candidate has to already have, because you can’t teach them quickly. The reason to score a skill at all is to verify prior experience where ramping someone from zero would be too slow or too risky.

Run each candidate skill through one test: could a strong hire pick this up in their first few weeks? Your product, your tools, and your sales process almost always clear that bar — you teach them to everyone in onboarding — so don’t screen for prior mastery. Screen for the ability to learn them fast, which is a competency. Reserve the skills section for the selling motions that take years of reps to build and that onboarding can’t manufacture; for many roles that section stays nearly empty, and that’s fine.

One caution: relationships are usually overrated. Hiring for a rolodex — “they know everyone in the space” — is a classic way to make a bad hire; the contacts rarely transfer, and they mask whether the person can actually sell. The real exception is a genuinely tiny, named-account market, where trusted access to those specific accounts is the job itself. Outside that, score the selling motion, not the contact list.

Watch the line between a skill and an outcome, because the same theme can appear as both. “Has closed complex enterprise deals before” is a skill — have they done it. “Will close two or more competitive displacement deals in year one” is an outcome — will they do it here. Score the experience in the skills section and the target in the outcomes section; don’t let a résumé line stand in for the goal.

Scoring

Score 0–4 with an honest zero — and don’t let the number decide.

Score every item — competency, skill, or outcome — on a 0–4 behaviorally anchored scale: each number is tied to observable behavior, not a vibe, so a 4 on “resourcefulness” describes what a 4 actually did, and two interviewers reading the same evidence land near the same score. One anchor is worth stating outright — 0 means “not enough information,” not “bad” — so if something never came up, you score it 0 instead of guessing.

And don’t weight the criteria. Assigning “closing is 30%, coachability is 20%” feels rigorous, but it’s false precision — and false precision is dangerous because it tempts you to let the score decide. Once “anything over a 3.5 is a hire” takes over, you stop having the debrief conversation — and that conversation is the one place you’d discover a score was wrong, that one interviewer misread the evidence, or that the number hides a disqualifying gap.

So use the scores to make the conversation better, not to replace it: score independently before comparing notes, have the leader speak last so the room isn’t anchored, and treat the card as confirmation that everyone weighed the same evidence — then decide as a team. Where it pays off is the comparison: once every candidate is on one scale, you can lay them side by side with Yardstick’s candidate comparison — one scored grid across competencies, skills, and outcomes, with role-average baselines — and see the real differences instead of arguing from memory.

You can stand this whole card up in Yardstick — competencies, skills, outcomes, and the 0–4 scale — and score every candidate against it. Generate a first-draft sales scorecard and edit from there.

FAQ

Common questions about sales interview scorecards.