rolekit
Interviews

March 2026 · 5 min read

The Candidate Scorecard Template Every Tech Hiring Manager Needs

Gut-feel hiring is why you keep making the wrong call. A structured scorecard fixes that. Here's the exact template we use for senior tech roles.

You've interviewed four candidates. Two of them were "really strong." One "just had something about them." The fourth was technically solid but you weren't sure about the culture fit.

Three weeks later, you've hired someone and you're not entirely sure why you picked them over the others. Six months later, you're not sure it was the right call.

This is what hiring without a scorecard looks like. And it's how most companies hire.

Why gut feel fails

Human beings are pattern-matching machines. We make decisions in the first five minutes of an interview and spend the rest of the time confirming them. We confuse confidence with competence. We hire people who remind us of ourselves. We penalise candidates who are nervous and reward those who are polished — regardless of actual ability.

A scorecard doesn't eliminate human judgment. It structures it. Instead of "strong overall feeling," you have "Technical Depth: High — explained distributed caching trade-offs clearly, gave specific example from production incident." That's useful. That's defensible. That's something you can compare across candidates.

The template

Every criterion needs three things: a weight (High/Medium/Low), what good looks like, and specific red flags. Here's a template for a senior software engineer role:

Technical DepthHigh

What good looks like

Can explain trade-offs, not just implementations. Discusses past decisions with nuance — "we chose X because Y, but it had the downside of Z." Knows what they don't know.

🚩 Red flags

Gives textbook answers without real examples. Can't explain why they made a technical choice. Claims expertise in everything.

Problem SolvingHigh

What good looks like

Breaks down ambiguous problems systematically. Asks clarifying questions before diving in. Considers edge cases. Thinks aloud without prompting.

🚩 Red flags

Jumps to solution immediately. Gets stuck and stops. Needs hand-holding through structured problems.

CommunicationHigh

What good looks like

Explains complex things simply. Adapts language for the audience. Concise without being terse. Asks good questions.

🚩 Red flags

Vague or circular answers. Uses jargon as a shield. Can't explain their own work clearly. Talks over the interviewer.

Ownership & AccountabilityMedium

What good looks like

Uses "I" not "we" when describing their contributions. Talks about failures honestly. Has examples of going beyond the brief.

🚩 Red flags

Always "we did this" — unclear what their actual role was. Blames others for failures. No examples of taking initiative.

CollaborationMedium

What good looks like

Specific examples of working through disagreements. Mentions other people's contributions positively. Understands that code review is about the code, not the person.

🚩 Red flags

Dismissive of others' approaches. "I prefer to work alone." No examples of changing their mind based on feedback.

Culture FitLow

What good looks like

Asks thoughtful questions about how the team works. Seems genuinely interested in the problem, not just the role. Values align with how your team operates.

🚩 Red flags

Only asks about salary and benefits. Seems to have rehearsed answers to culture questions. Values clearly misaligned.

How to use it

Share the scorecard with every interviewer before they meet the candidate. Not after. If they fill it in retrospectively, they're just rationalising the gut feeling they already had.

Each interviewer scores independently, then you compare. Disagreements are valuable — they surface different perspectives and force a real conversation about what you're actually hiring for.

Weight matters. If two candidates tie on Medium and Low criteria but one clearly wins on all three High criteria, you know what to do.

The fast way to get a scorecard for any role

The template above works for a generic senior engineer. But every role is different — a Staff Engineer scorecard looks different from a mid-level backend developer. The weights shift, the technical criteria change, the red flags are specific to the stack.

RoleKit generates a tailored scorecard for every role in 30 seconds — just paste in your job brief and get back a complete hiring pack including a scorecard built specifically for that position.

Get a tailored scorecard for your next hire

Paste a job brief, get a complete scorecard in 30 seconds. Free to try.

Try RoleKit free →