Free template
Role scorecard template
Before you write an advert or speak to a recruiter, write the scorecard. It states what the person must achieve, what they must already be able to do, and what the team can teach. Everything downstream — the advert, the interview plan, the decision — should be traceable back to this page.
Who fills it in
Hiring manager, agreed with the founder or budget holder.
How long it takes
Half an hour with the hiring manager, then ten minutes with whoever signs the offer.
Reviewed by
Joseph Edney, 29 October 2026
When to use it
Use it when
- You have decided to open a role but nothing is written down beyond a title.
- Two people in the company would describe the job differently if asked separately.
- You are about to brief an internal recruiter, an agency or your own network.
What good looks like
- Outcomes are written as things that will be true by a date, not as duties. “CI pipeline runs in under ten minutes”, not “responsible for CI”.
- The must-have list is short enough that you could justify every item to a candidate who asked why it matters.
- Anything the team could reasonably teach in the first quarter sits under teachable, not must-have.
- The person who signs the offer has read it and agrees with it before the first interview.
Common mistakes
- Copying a job advert from a larger company. Their scorecard assumes a support structure you do not have yet.
- Listing tools instead of capability. A specific framework is rarely the thing that makes the hire work.
- Writing outcomes nobody could verify. If you cannot say how you would know it happened, it is not an outcome.
- Treating the scorecard as fixed. Revise it once real candidates show you what the market actually contains — but revise it deliberately, not silently.
The template
Anything you type stays in this browser tab, so reloading the page keeps it. It is not sent to us or added to the link, so it is safe to put real salary numbers and colleagues’ names in. Closing the tab clears it — copy or print before you go.
The role in one line
One or two sentences. If it takes a paragraph, the role is probably two roles.
What breaks, slows or does not happen if the seat stays empty.
Outcomes
Three to five outcomes, each with a date and a way of knowing it happened. Fewer, sharper outcomes beat a long list.
| Row | The outcome | By when | How you will know |
|---|---|---|---|
| Outcome 1 | |||
| Outcome 2 | |||
| Outcome 3 | |||
| Outcome 4 (optional) | |||
| Outcome 5 (optional) |
Must-have versus teachable
A must-have is something the person cannot do the job without on day one. Everything else belongs on the right.
| Row | Must have on day one | Teachable in the first quarter |
|---|---|---|
| Capability 1 | ||
| Capability 2 | ||
| Capability 3 | ||
| Capability 4 |
Evidence and boundaries
Work they have shipped, decisions they have owned, problems they have debugged. Not years of experience.
Naming these widens the search without lowering the bar.
Keep this short. Every item here removes candidates.
Record who approved it and when, so nobody rediscovers it at offer stage.
A worked example
Illustrative example. The company, role and answers are fictional, written to show a finished template. It is not a client, a quote or a result. A fictional seed-stage company of about a dozen people, selling scheduling software to clinics, is hiring its first platform engineer. Until now the two founding engineers have handled every release and every incident themselves.
The role in one line
- Working title
- Platform engineer (first infrastructure hire)
- Team and who they report to
- Engineering, five people today. Reports to the CTO, who is one of the two founding engineers.
- Mission: the problem this person owns
- Own how code gets from a merged pull request to customers, and keep it running, so the product engineers stop losing part of every week to releases and incidents.
- Why this hire, and why now
- Releases are manual and only the founders can run them, so we ship once a week at best. Customers noticed our last two outages before we did. A larger clinic group has sent a security questionnaire we cannot yet answer with evidence.
Outcomes
| Row | The outcome | By when | How you will know |
|---|---|---|---|
| Outcome 1 | Any engineer can release to production without a founder | End of month two | A product engineer runs a release from the written runbook with no founder involved. |
| Outcome 2 | We hear about outages before customers do | End of month three | Alerts reach the on-call engineer for the failures behind the last two outages, proved by rehearsing each one. |
| Outcome 3 | The security questionnaire is answered with evidence | End of month four | For every infrastructure question, the CTO can point to a setting, a log or a written procedure. |
| Outcome 4 (optional) | Cloud spend is understood and owned | End of month five | A short monthly cost note the CTO actually reads, with an owner named for each large line. |
| Outcome 5 (optional) | Process no longer sets the release pace | End of month six | Work ships when it is ready, not on a fixed weekly slot. |
Must-have versus teachable
| Row | Must have on day one | Teachable in the first quarter |
|---|---|---|
| Capability 1 | Has run production systems on a major cloud provider and been on call for them | Our particular provider, if they know another one well |
| Capability 2 | Has built or rebuilt a deployment pipeline that other engineers relied on | Our CI tool and repository conventions |
| Capability 3 | Can walk through an incident they debugged: what they saw, what they tried, what fixed it | How clinics use the product, and which failures hurt them most |
| Capability 4 | Writes procedures that someone else can follow without asking | Security questionnaire formats and the language buyers use |
Evidence and boundaries
- What evidence would convince you someone has the must-haves?
- A pipeline or platform change they led, explained end to end, including what they would now do differently. One real incident told in order. A runbook or design note they wrote, or a description of one if they cannot share it.
- Adjacent backgrounds you would genuinely consider
- A backend engineer at a small company who ended up owning deployments and on-call. A site reliability engineer at a larger company who wants broader ownership.
- Genuine dealbreakers
- Has never been responsible for a production system. Unwilling to join an on-call rota, which they would help design.
- Salary range and working pattern (signed off by)
- Range and hybrid pattern agreed by the CEO and CTO before the first interview, and recorded with the date. Your own figure goes here: it depends on your market and the seniority you need.
The thinking behind it
- Writing a technical hiring brief that gets resultsWhat a recruiter actually needs to run a technical search: the problem, the stack, the bar, the constraints and the trade-offs you are willing to make.
- Must-have versus learnable skills in early-stage technical hiringHow to split a requirements list into what must be true on day one and what can be learned after joining — and why that decision sets the size of your pool.