Hiring memo template: the written case for a hire, a no-hire or an exception
On this page
A hiring memo is a one-to-two-page document in which the hiring manager recommends a decision on a candidate, shows the evidence for it against the role's criteria, answers every concern interviewers raised, and names the risks being accepted. It is written for someone who was not in the debrief: an approver, a hiring committee, or whoever asks in a year why this person was hired. Write one when the panel was split, the hire is senior or first of its kind, the offer needs an exception, or the decision-maker was not in the room.
Below: when a memo is the right document and when the debrief record is enough, the standard template, four versions for the situations memos are usually written for, a filled example and the rules that make a memo persuasive to a skeptical reader.
When do you need a hiring memo, and when is the debrief record enough?
| Document | Written by | For | Use it when |
|---|---|---|---|
| Debrief decision record | Facilitator, in the meeting | The file | Every candidate who reaches a debrief |
| Hiring committee packet | Recruiter | A committee deciding from paper | Your process has a formal committee |
| Candidate assessment summary | Recruiter | Hiring manager | Summarizing a screen or loop for the decision-maker |
| Hiring memo | Hiring manager | Approver, committee, the record | Split panel, senior or novel hire, exception, absent approver |
The difference is authorship and argument. The packet and the summary collect evidence neutrally. The memo is the hiring manager taking a position and defending it, in writing, against the strongest objection.
Ashby's recruiting blog describes one version of this practice: when a live debrief cannot reach consensus in about 30 minutes, the hiring manager writes up the strengths and concerns, shares the memo for comments, and holds a smaller second debrief only on the points still open (Ashby, as of October 2026). The templates below extend the idea to the other situations where a written case helps.
What goes in a hiring memo?
- The recommendation, in the first line: hire, hire at a different level, no hire, or hire with a named exception.
- The criteria, linked rather than restated: the success profile or must-haves agreed before interviews began.
- Evidence by must-have, quoting what the candidate said or did, with the interview it came from.
- Every concern raised, each with the evidence for it, the evidence against it, and how much it matters for this role.
- Risks accepted and the plan to manage each one after the start date.
- What would change the recommendation: the evidence that would make you decide differently.
- The ask: who needs to approve what, by when.
The hiring memo template
HIRING MEMO
To: [approver / committee] From: [hiring manager]
Candidate: [name] Role / level: [title, level]
Req ID: [ ] Date: [date]
Decision needed by: [date]
RECOMMENDATION
[Hire / Hire at (level) / No hire / Hire with exception: (what)]
In one sentence: [why].
CRITERIA
Success profile: [link]. Must-haves: [1], [2], [3].
EVIDENCE BY MUST-HAVE
1. [Must-have]: [met / partly / not met]
"[Candidate's words, short]" ([interview, interviewer]).
[What it shows, one line.]
2. [Must-have]: [ ]
3. [Must-have]: [ ]
CONCERNS RAISED, AND MY ASSESSMENT
Concern: [as the interviewer stated it] ([who])
Evidence for: [ ]
Evidence against: [ ]
Weight for this role: [high / medium / low], because [ ]
RISKS ACCEPTED AND PLAN
[Risk] → [plan, owner, by when]
WHAT WOULD CHANGE MY MIND
[The evidence that would make me recommend otherwise.]
ASK
[Approve offer at $(amount) / approve level / confirm no hire] by [date].
Scorecards and debrief record: [links]
Four more versions
1. Split panel
Add a short table above "Concerns raised", so the reader sees the disagreement before your interpretation of it:
WHERE THE PANEL DISAGREED
Must-have Ratings Source of the difference
[ ] [A: 4, B: 2] [different evidence / same evidence,
different reading / one didn't test it]
Debrief outcome: [ratings changed? who, why]
Dissent still standing: [who, on what, their evidence]
Name the dissent and keep it in. A memo that erases the dissenting view is the one most likely to be challenged later, and the dissenter is more likely to support a decision they can see was weighed.
2. No-hire for a strong finalist
RECOMMENDATION: No hire for [Role].
Deciding factor: [the job-related reason, tied to a must-have].
Hireable for: [other roles or levels, if any].
What could change: [a gap that time or experience could close].
Keep in touch: [yes / no]. Candidate agreed: [date, channel].
This is the record that makes a silver medalist usable later. Without the deciding factor in writing, nobody remembers in six months why the candidate came second.
3. Exception: above range, different level or a missing must-have
EXCEPTION REQUESTED: [pay above range / level change / must-have not met]
Standard: [the range, level or must-have]
Proposed: [the exception]
Why this candidate justifies it: [evidence, not market anecdotes]
Effect on peers: [internal equity check, done by (name)]
If declined: [the next best option and its cost in time]
Attach the memo to the offer approval form, so the approver sees the reasoning and the numbers together.
4. Choosing between two finalists
FINALISTS: [Candidate A], [Candidate B]
Must-have A B
[ ] [rating, one line] [rating, one line]
[ ] [ ] [ ]
Where they differ most: [ ]
Recommendation: [A], because [the difference that matters most for the
first 12 months].
For [B]: [no hire / hold as silver medalist / other role].
Compare against the criteria, not against each other's personalities. The candidate comparison matrix is the working document behind this section.
A filled example
An invented candidate and team, showing a split-panel memo in short form:
Recommendation: Hire Priya Nair as Senior Data Engineer, level 4. She met all three must-haves with first-hand examples, and the one concern raised is real but manageable for this team.
Evidence:
- Pipeline reliability (met): "We had a nightly job failing silently about once a week, so I added row-count checks between each stage and paged on a mismatch." (System design, Marco.) Shows she designs for failure without being prompted.
- Data modeling (met): rebuilt a reporting model used by finance and could explain the trade-off she made on slowly changing dimensions. (Technical interview, Lee.)
- Working with analysts (met): runs a weekly office hour for analysts and described the request she turned down and why. (Hiring manager interview.)
Concern: "Light on streaming" (Lee, rated 2 on that question). Evidence for: she has used a streaming platform only in a side project. Evidence against: none of our roadmap for the next two quarters uses streaming. Weight: low for the first year.
Dissent: Lee still leans no, because streaming is likely in next year's plan.
Risk and plan: streaming gap; pair her with the platform team on the first streaming project and budget a course in her first six months.
What would change my mind: if the streaming migration moves into this year's plan, this hire should be someone with production streaming experience.
Ask: approve offer at the midpoint of the level 4 range by Thursday.
How do you write a memo a skeptic can follow?
- Lead with the strongest objection, not the strongest praise. The reader who disagrees will look for it first.
- Quote, then interpret. Keep what the candidate said separate from what you think it shows, so the reader can disagree with your reading without doubting your facts. The evidence-based feedback guide covers what counts.
- Check every quote against the notes. A paraphrase presented as a quote undermines the whole memo when someone checks. Interview Signal's scorecards carry the candidate's own words and remove any quote that is not in the transcript, which makes this step quicker; candidates should be told at the start of the interview when a transcription tool is in use.
- Stay on the job. No age, family, health, accent or appearance, and no "culture fit" without a named behavior.
- Keep it to two pages. Link the scorecards instead of pasting them.
How to use these templates
- Write the memo within one working day of the debrief, while the discussion is fresh.
- Choose the standard template and add the split-panel, no-hire, exception or two-finalist section that applies.
- Share it with the interviewers first, with a deadline for factual corrections (one working day is usually enough).
- Send it to the approver with the scorecards and debrief record linked, and a decision date.
- Store the final memo with the candidate's hiring record. In the US, employers covered by Title VII must generally keep hiring records for at least one year from when the record was made or the decision taken, whichever is later (29 CFR 1602.14, as of October 2026). That is a summary, not legal advice; check your own retention rules.
Memo mistakes and the fix
| Mistake | Fix |
|---|---|
| Recommendation buried on page two | First line, one sentence |
| Concerns left out because they were "resolved" | List every concern and show how it was weighed |
| New criteria introduced to justify the decision | Argue only from the criteria agreed before interviews |
| Adjectives instead of evidence | One quote or observed action per must-have |
| Written a week later from memory | Within a working day, from the scorecards |
| No ask or deadline | Name who approves what, by when |
Questions people ask
What is a hiring memo?
A hiring memo is a one-to-two-page document in which the hiring manager recommends a decision on a candidate, sets out the evidence against the role's criteria, answers every concern interviewers raised, and states the risks being accepted. It is written for a reader who was not in the debrief, such as an approver, a committee or a future auditor of the decision.
When should a hiring manager write a hiring memo?
When the debrief did not reach agreement, when the hire is senior or the first of its kind, when the offer needs an exception such as pay above range or a missing must-have, or when someone who was not in the room has to approve the decision. For a clear, unanimous decision on a routine hire, the debrief decision record is enough.
How long should a hiring memo be?
One page for most hires and two at most. If it runs longer, it is usually repeating scorecards rather than weighing them; link the scorecards and keep the memo to the argument, the evidence that decides it, and the risks.
What should not go in a hiring memo?
Anything unrelated to the job: age, family plans, health, accent, appearance, or vague judgments like "not a culture fit" without a named behavior. Leave out hearsay from back-channel references unless the candidate agreed to them, and anything you would not be comfortable having the candidate read.