Why this is worth doing properly
Every candidate you reject is someone who might apply again, refer someone, buy from you, or write about the experience publicly. In a small market, the people you turn down this year are often the people you want in two years.
There is also a more immediate reason. Rejection is the part of your process most candidates experience, since you reject far more people than you hire. If you want to know what your hiring reputation actually is, it is set here rather than in your job description.
The principle
Reject the fit, not the person. "We went with someone who has run this exact process before" is a fact about the role. "You were not strong enough" is a judgement about them, and it is both less useful and less true.
How fast, and by what channel
Speed matters more than eloquence. The waiting is the worst part for candidates, and it is entirely within your control.
| Stage they reached | When | How |
|---|---|---|
| Application only | Within a week | Short email, template is fine |
| Screening call | Within two days of deciding | Personal email, one specific reason |
| Full interview | Within two days | Personal email, or a call if they asked |
| Final stage or exercise | Within two days | A short call, then written confirmation |
Never leave a final-stage candidate waiting while you close your first choice. If you need time, say so honestly: "We are finalising a decision and will come back to you by Thursday." Candidates handle honest delay well. Silence is what they resent, and what they describe to others.
Match the effort to what you asked of them. Someone who spent four hours on an exercise has earned more than a template. Someone who applied and had no contact has not, and pretending otherwise wastes your time without helping them.
What to say
Four sentences is usually right.
Decide it clearly. "I am sorry, we are not taking your application further." No burying it after two paragraphs of praise, which makes people read twice to find the answer.
Give one specific reason where you can. "The role needs someone who has managed a support team through a tool migration, and that was the gap." Specific and factual.
Say something true about them. Not flattery. If their approach to a problem was genuinely good, say which one. If there is nothing specific, leave it out rather than inventing.
Say what happens to their details, and mean it. If you would consider them for something else, say so and be prepared to actually contact them. If not, do not imply it.
What to avoid: "we went with a stronger candidate" (unhelpful and slightly unkind), "we will keep you on file" when you will not, blaming a process ("HR decided") in a five-person company, and anything that sounds like it might be reversible if they push.
How much feedback to give
More than most companies give, and less than candidates sometimes ask for.
One concrete thing is the right amount. "The exercise answer covered the process but not what you would do when the customer disagreed" gives someone something to work on. "Be more confident" does not.
Stick to what was observable in the process. Comment on what they did or said, not on personality traits you inferred. This is better feedback and it is also the safer ground.
Do not negotiate. Give the feedback once, kindly. If a candidate argues, you are not obliged to defend it at length: "I understand you see it differently, and I have given you my honest read" is a complete answer.
A caution worth taking seriously
Discrimination law limits what you can say and how you record it, and candidates often have rights over the notes you hold about them. Keep feedback tied to the requirements of the role, write notes you would be comfortable being read back, and take advice for your jurisdiction on how much detail to give. Structured criteria, as covered in running a structured interview process, also make feedback both safer and more useful, because it is anchored to something written down.
Keeping the good ones warm
A small number of rejected candidates are people you actively want later. Treat that as a real list rather than a sentiment.
Say it explicitly, only when true. "This was close, and the thing that decided it was specific to this role. I would like to come back to you when we hire again."
Write down what they were strong at, not just that they were good. In eight months you will not remember, and a vague note produces a vague approach.
Actually contact them when the role appears. A candidate told they would hear from you and never contacted is worse off than one who received a clean no, and they know exactly what happened.
Handle the near-miss honestly if the first choice declines. "You were a very close second and the role is open again" is fine to say if it is true. Most people are pleased rather than insulted, provided you are not pretending they were first.
The same reasoning runs through all of this and through making an offer and handling the negotiation: hiring conversations are remembered far longer than they take, and the ones that end in a no are remembered most clearly of all.
Frequently asked questions
- How quickly should you reject a candidate?
- Within two working days of the decision. The waiting is the part candidates find hardest, and a fast no is treated as respect. Holding people as a backup while you close a first choice is the most resented practice in hiring.
- Should you give candidates feedback on why they were rejected?
- For anyone who interviewed, yes, briefly and about the role. One specific, factual reason is far more useful than encouragement. Take advice on how much detail to give, since discrimination law affects what is safe to say.
- Should rejections be a call or an email?
- Email for applications and early screens. A short call for anyone who reached a final stage or completed a substantial exercise. The effort should match what you asked of them.
- Can you tell a candidate they were second choice?
- Only if you mean it and would genuinely contact them. Saying it to soften a rejection, then never following up, is worse than a plain no because it leaves someone waiting.
- Is it acceptable to keep a candidate warm as a backup?
- Only if you tell them that is what is happening and give a date. Silent backups discover their status when the deadline passes, and they tell people about it.