Reading an assessment scorecard

Every profile we send carries the scorecard from the person's assessment. It is one page and it is the fastest way to decide who to interview.

What the columns mean

Each row is a criterion from the rubric for that role. The score is out of five and the note beside it is the reviewer's reason, written while they were reviewing rather than afterwards. The last column is the weight: a criterion weighted three matters three times as much to that role as a criterion weighted one.

The total at the bottom is weighted, so a four on something that matters beats a five on something that does not.

Why you see the low marks

Because you would find them in month two anyway, and then you would wonder what else we hid. A senior developer who scored two on written communication is still a good hire for a team with a strong tech lead and a bad hire for a team that needs someone client-facing. That is your call to make, not ours to hide.

Comparing two candidates

Read the weighted total first, then read the notes on the two highest-weighted rows. Ignore the gap between a 4.1 and a 4.3; it is inside the noise of two different reviewers. A gap of a full point on a heavily weighted row is real.