Write the Scorecard Before You Meet Anyone

How to decide what a good hire looks like before the first interview: three to five requirements, the evidence that proves each one, and who checks what. Do it first and your interviewers measure the same job instead of their own idea of it.

By JobPost Team · Nov 7, 2026 · 4 min read

Most hiring teams decide what they were looking for after they have met the candidates. The person who interviewed well becomes the template, and the requirements quietly reshape themselves around them. Writing the scorecard first stops that. It is an hour of work, done before anyone books a call, and it changes what every interview after it is for.

Why "Good" Drifts Once Candidates Show Up

Ask four interviewers what the role needs and you will get four overlapping but different answers. One cares about technical depth. One wants someone who can talk to clients. One is quietly hiring for the person who left. One is mostly checking whether they would enjoy working with this person.

None of those are wrong. The problem is that they are never written down, so each interviewer runs a different test and reports a single verdict. When the verdicts disagree, nobody can tell whether the candidate was inconsistent or the interviewers were measuring different things.

Then the candidates themselves start to set the bar. A confident first interviewee makes the next one look hesitant. A candidate with an impressive previous employer makes the role suddenly seem to need that background. Without a fixed standard, the comparison becomes candidate against candidate instead of candidate against the job.

Pick Three to Five Things the Role Actually Needs

Start from the work, not the job description. Picture the person six months in. What are they doing every week, and what would make the hiring manager say it is going well?

From that picture, pull out the few capabilities that matter most. Three to five is the useful range. Fewer and you are probably hiring on one dimension; more and the list turns into the wish list that most job posts already are.

A scorecard for a customer success lead might look like this:

  • Can run a difficult renewal conversation with a frustrated client and keep the account
  • Can spot an at-risk account from usage data before the client says anything
  • Can write a clear escalation that engineering will act on
  • Can manage a book of accounts without someone checking their calendar

Notice what is missing: "great communicator", "team player", "passionate". Those are traits everyone claims and no interview can measure reliably. Each line on a good scorecard describes something the person does, in a situation they will actually face.

Separate the must-haves from the nice-to-haves while you are at it. If a candidate is strong on four items and weak on the fifth, the team should already know whether that fifth one is a dealbreaker or something you can train.

Define What Evidence Looks Like

A requirement is only half a scorecard. The other half is what would convince you the candidate has it.

For each line, write down what strong evidence sounds like and what weak evidence sounds like. For the renewal conversation, strong evidence might be a specific story: the client, what they were upset about, what the candidate said, and what happened to the account. Weak evidence is a general statement about valuing relationships, or a story where the outcome was decided by someone else.

This step matters most for the interviewers who are newest to hiring. Experienced interviewers often carry an informal version of this in their heads. Newer ones tend to score on fluency, and fluency is not the same as having done the work.

Write a rating scale with words attached, not just numbers. "3 out of 5" means different things to different people. "Gave one concrete example with a clear outcome" means the same thing to everyone.

Assign Each Interviewer Their Part

Once the requirements and evidence are written, split them up. Each interviewer owns one or two items and goes deep on those. The person checking escalation writing asks for a real escalation they wrote, or has the candidate draft one. The person checking account judgement walks through how the candidate prioritized a busy week.

This does two things. It stops five interviewers from asking the same "tell me about yourself" questions and reaching five shallow opinions. And it means each interviewer's notes answer a specific question, so their input carries weight on that item rather than on everything at once.

Ask interviewers to submit their written scores against the scorecard before they talk to each other. Independent notes, tied to named requirements, are what make the later discussion worth having.

What Changes When the Standard Comes First

The conversation after the interviews gets narrower and more useful. Instead of "I liked her" against "something felt off", the discussion becomes "she gave two strong renewal examples but nothing convincing on reading usage data". That is a disagreement you can resolve, or at least name.

Fairness improves too. Candidates are measured against the same written criteria, which makes it harder for a shared alma mater or a familiar accent to tip the outcome. It also gives you something to point to if you need to explain a decision later.

And sometimes the scorecard reveals that the team never agreed on the job in the first place. If the hiring manager and the team lead cannot settle on the top four items, finding that out before interviews costs an afternoon. Finding it out after three final-round candidates costs a month, and possibly a hire who was right for one version of the role and wrong for the other.

Write it down, share it with everyone on the panel, and do not change it halfway through the search unless you are willing to say out loud why.