Free template
Structured interview plan
Most early-stage processes are a sequence of conversations with the same shape. This template forces each stage to test something the previous one did not, names an owner, and fixes what the candidate is told at every step.
Who fills it in
Hiring manager, with whoever schedules and whoever runs each stage.
How long it takes
About an hour once per role type, then reusable.
Reviewed by
Joseph Edney, 29 October 2026
When to use it
Use it when
- You are about to open a role and the process is “we will chat and see”.
- Different candidates in the same search have had noticeably different processes.
- Interviewers keep covering the same ground and nobody tests the hard part.
What good looks like
- Every stage has one owner and one primary thing it tests, written down before the first candidate.
- No two stages test the same thing; the hardest question about the role is tested somewhere explicitly.
- Each stage states what the candidate is told beforehand, so the process is fair and repeatable.
- The number of stages matches the seniority of the role, not the number of people who want to be involved.
Common mistakes
- Adding a stage because someone wants to meet the candidate. Meeting the team is legitimate — label it as that, not as an assessment.
- Running a take-home exercise with no agreed time limit or feedback path.
- Leaving the scheduling owner unnamed, which is where most days are lost.
- Designing five stages you cannot service. A shorter process you can run this month beats a perfect one you cannot.
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.
Process basics
Set it as a commitment to the candidate, not an aspiration.
Whichever stage tests this is the one that matters most.
The stages
Fill a row per stage. If two rows test the same thing, merge them or change one.
| Row | Owner | What it uniquely tests | Format and length | Told in advance |
|---|---|---|---|---|
| Stage 1 | ||||
| Stage 2 | ||||
| Stage 3 | ||||
| Stage 4 (optional) | ||||
| Stage 5 (optional) |
Before the first candidate
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. The same fictional seed-stage clinic-software company as the role scorecard example, now planning the interviews for its first platform engineer. The CTO runs the process with help from one product engineer and the CEO.
Process basics
- Role
- Platform engineer (first infrastructure hire)
- Process owner (scheduling and candidate comms)
- The CTO owns the process. The operations lead books every slot and sends every candidate message.
- Target elapsed time from first conversation to decision
- Three weeks from first call to decision, said to each candidate on the first call.
- The hardest thing to get right about this hire
- Telling someone who has operated production systems from someone who has only used a platform another team built. Stage 3 exists to test this.
The stages
| Row | Owner | What it uniquely tests | Format and length | Told in advance |
|---|---|---|---|---|
| Stage 1 | CTO | Motivation and fit with the scorecard's must-haves: has this person owned production systems, and do they want this much ownership? | Video call, thirty minutes | The scorecard outcomes, the stages ahead and the three-week timeline. |
| Stage 2 | Product engineer | Working with product engineers: explaining a technical change to people who will use it, and taking their objections seriously. | Video call, forty-five minutes, a real pipeline change from our backlog discussed together | That it is a conversation about a real change, with no coding and no right answer, followed by a short written note they can send within a few days. |
| Stage 3 | CTO | Operating experience: walking through a past incident in order, then reasoning about a failure in our own setup. | In person or video, ninety minutes, no preparation needed | The format, that they will be asked to describe an incident they handled, and that a whiteboard is optional. |
| Stage 4 (optional) | CEO | Meeting the team and asking their own questions. Labelled as not an assessment. | Video call, thirty minutes | That this stage is for their questions and will not be scored. |
| Stage 5 (optional) | CTO | References on the operating experience claimed in stage 3. | Two reference calls, with the candidate's permission | Which claims we will check, and that we only call referees they name. |
Before the first candidate
- Done: Interview slots blocked in every interviewer's diary
- Done: Scorecard agreed and shared with every interviewer
- Done: Each stage has its questions written, not improvised
- Done: Agreed turnaround for feedback after each stage
- Done: Named decision-maker, and who else has a veto
- Done: Adjustments offered to every candidate in writing
- Done: Any exercise is time-boxed, paid or short, and relevant
- Not yet: Agreed how and how quickly candidates are told no