Free template
Candidate briefing checklist
Early-stage companies are usually unknown to the person you want. This checklist covers what to tell candidates at each point: the honest version of the company, the process, the money, and what happens next. It is the same information whoever is speaking to them.
Who fills it in
Whoever speaks to candidates first — founder, hiring manager or recruiter.
How long it takes
Thirty minutes to write once per role, then reused verbatim.
Reviewed by
Joseph Edney, 29 October 2026
When to use it
Use it when
- You are about to approach people directly, or brief someone who will.
- Candidates keep asking the same question late in the process.
- Two people in the company describe the company differently to candidates.
What good looks like
- The company story is specific and checkable: what you build, who for, what stage you are at.
- The salary range is shared early and matches what you can actually approve.
- The full process is described up front, including how long it takes and how many stages.
- Every candidate hears the same things, whether they came through a founder, an employee or a recruiter.
Common mistakes
- Overselling the stage. Candidates who join on a false picture leave, and leavers cost more than a slower search.
- Withholding the salary range until the end, which wastes both sides' time.
- Describing the role differently to different candidates as the search drifts.
- Going quiet between stages. Silence is read as rejection by exactly the people you want.
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 honest company story
A sentence a candidate outside your sector would understand.
Say only what is true and shareable.
Saying these early filters out the wrong people and earns trust with the right ones.
Before the first conversation
During and after the process
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 fictional clinic-scheduling startup from the earlier examples, writing the one briefing that the CTO, the product engineer and the CEO will all use with platform engineer candidates. Three items are honestly not done yet.
The honest company story
- What the company does, in plain language
- We make the booking and scheduling software that clinics use to run their day: appointments, rotas and reminders, used by front-desk staff rather than by patients.
- Stage, funding position and what that means day to day
- Seed-funded, about a dozen people, with paying clinic customers. The runway figure and what the next funding step depends on are said on the first call, in the same words every time, and only once the CEO has confirmed them for that week.
- The genuinely hard or unglamorous parts of the job
- You would be the only infrastructure person, so you will be on call from the start, with the CTO sharing the rota at first. Much of the first months is unglamorous: runbooks, alerts and a security questionnaire that a customer is waiting on.
- Why a strong person would choose this over a bigger salary elsewhere
- You would own how the product gets to customers and stays up, with no platform team to wait for, and your decisions would shape the next engineers we hire. The problem is real: clinics feel every outage.
Before the first conversation
- Done: Salary range shared, and it matches what is approved
- Done: Location, work model and any travel expectations stated
- Done: Number of stages, format and expected elapsed time
- Done: Who they will meet and what each person does
- Not yet: How equity, if any, is described accurately rather than aspirationally
- Done: Adjustments and accessibility needs invited
During and after the process
- Done: Each stage's purpose and format sent in advance
- Done: Any exercise is time-boxed and its use explained
- Done: Feedback given within the promised window, every time
- Not yet: Nobody is left without an answer, including early rejections
- Not yet: Offer explained in writing: salary, start date, terms, notice
- Done: Agreed contact between offer and start date
The thinking behind it
- When not to hireThe cases where a permanent hire is the wrong answer, the alternatives worth testing first, and the signals that a role is genuinely ready.
- A founder's checklist for choosing a technical recruitment partnerWhat to test before instructing a recruiter for a technical role: briefing depth, market honesty, process, candidate experience and commercial terms.
- What a strong candidate will ask a Seed-stage startup, and how to answer honestlyThe seven risk questions a good candidate puts to a company before Series A, what a founder can truthfully say to each, and what not to promise.