How to Write a Candidate Rejection Email (Templates for 2026)
Every hiring process ends with far more "no"s than "yes"es, and most of those "no"s never get sent. The candidate who made it to a final interview, took an afternoon off work to be there, and then hears nothing for three weeks isn't wondering if they got the job anymore — they're wondering if your company just doesn't bother replying. A short, clear rejection email costs you two minutes and protects something that took years to build: how candidates, and the people they talk to, describe your hiring process.
Below is the structure that makes a rejection land well, templates for the two moments that matter most, and the mistakes that quietly do more damage than staying silent.
Why the rejection email matters more than it feels like it should
Candidates remember how they were let go, not just that they were. A rejection sent within a reasonable window, written like a human wrote it, leaves someone thinking "that was a well-run process, I'd apply there again." A generic three-week-late auto-reject leaves them leaving a review, warning a friend, or quietly deprioritizing your product as a customer. The rejection is the last touchpoint most candidates ever have with your company — it's disproportionately what they remember.
Silence isn't neutral — it reads as disrespect. A candidate who interviewed and then heard nothing doesn't assume you're busy; they assume they didn't matter enough to get a reply. That's true even when the real reason is mundane, like a frozen req or a slow approval chain. From the outside, silence and indifference look identical.
Boomerang candidates are common, and a bad rejection burns that bridge. Someone rejected today for "not quite right for this role" is often a strong fit for a different one six months later — but only if the door was left open respectfully. A cold or thoughtless rejection makes that person unlikely to ever apply again, even when your next opening is exactly what they wanted.
Why most rejection emails never get sent
It's rarely malice — it's admin load. A recruiter who ran fifteen phone screens has fifteen "no" emails to personalize, on top of everything else on their plate, and the easiest thing to deprioritize is the message to people who already didn't get the job. That's how "I'll get to it" quietly becomes "I never did."
The fix isn't asking recruiters to care more. It's shrinking the number of live conversations that generate an awkward, personal rejection later, and building the "no" into the workflow at the moment you already have every candidate's status in front of you — right after you finish reviewing a batch, not as a separate task you have to remember.
The three-part structure that works
A good rejection email is short — four to six sentences — and does three things in order:
- State the decision clearly, in the first line. Don't bury it under three paragraphs of preamble; a candidate scanning their inbox should know the outcome immediately, not have to hunt for it.
- Thank them for something specific. Their time, a detail from the conversation, the effort in their application — specific beats generic ("thanks for your interest") because it signals a real person read their file.
- Leave the door open, briefly and honestly. Invite them to apply again for a future fit, or offer one genuine piece of feedback if you have time to give it — but only promise what you'll actually deliver.
Template: rejecting after a resume or video screen
This is the highest-volume rejection you'll send, so it should be fast to personalize and still feel human:
Subject: Update on your application — [Role]
Hi [Name],
Thanks for taking the time to apply for [Role] and for sharing your [video answer / application] — we appreciate you putting yourself forward. After reviewing the field, we've decided to move forward with other candidates whose experience lines up more closely with what this specific role needs.
This isn't a reflection of your ability, and we'd genuinely welcome an application from you for future roles that match your background. Thanks again, and best of luck with your search.
Template: rejecting after a live interview
Someone who made it to a real conversation deserves a slightly warmer, more specific note — and, where you can offer it, one honest piece of feedback:
Subject: Following up on your interview for [Role]
Hi [Name],
Thank you for the time you put into our conversation last week — I enjoyed hearing about [one specific detail from the interview]. After talking with the team, we've decided to move forward with another candidate for this particular role.
One thing that stood out positively was [specific strength]; where we ultimately felt the fit was closer for another candidate was [honest, brief reason, if you have one to give]. We'd like to keep your resume on file and would welcome hearing from you again for roles that match your background more closely. Thanks again for your time and interest.
What quietly makes a rejection worse than useful
Sending nothing at all. Silence past the timeline you promised is the single most common candidate-experience complaint there is, and the easiest one to fix — a short "not moving forward" email beats no email every time.
A subject line or opener so generic it reads as a mail-merge fail. "Regarding Your Application" with no name and no role feels like exactly what it is: a template nobody proofread before sending.
Promising feedback and then not giving any, or giving vague non-feedback. "We had a lot of strong candidates" isn't feedback — it's a placeholder that makes candidates trust the process less, not more. If you can't give a real reason, don't promise one.
Rejecting in a tone that contradicts how positive the interview felt. A warm, encouraging final round followed by a cold form-letter rejection is jarring, and candidates notice the mismatch. Match the tone you actually built during the process.
Where this fits with async video screening
Rejection admin piles up fastest when you're juggling a live interview calendar — every scheduled call is another status to track and another awkward email to eventually write. With Flash Interview, you review every candidate's recorded answer in one batch sitting rather than across a week of scattered calls, which means you already have the full list — advance, reject, maybe — in front of you at once. Sending the "no" emails right there, while the context is fresh, is far easier than reconstructing who said what three weeks after a string of separate live calls. For how that batch review actually works, see how to review and score one-way video responses.
The honest caveat
Templates make a rejection faster to send, not automatically warm — swap in the bracketed specifics every time, or a copy-pasted template becomes exactly the generic mail-merge candidates resent. And a good rejection email doesn't undo a slow or disorganized process before it; if candidates waited five weeks with no updates, a polished final email won't fully repair that impression. The email matters most as the last step of a process that was reasonably fast and communicative throughout, not as a substitute for one that wasn't.
Flash Interview lets hiring teams screen candidates with a 50-second recorded video answer instead of a scheduled call — review the whole batch in one sitting, close the loop with everyone at once. $39 per role, up to 50 candidates, no subscription.
Frequently asked questions
Should you always send a rejection email to candidates?
Yes — even a short, templated note beats silence. Candidates who hear nothing assume they were ignored, which does more brand damage than a brief, honest rejection ever does.
How long after an interview should you send a rejection?
Within the timeline you told the candidate, or within about a week if no date was given. The longer the gap between the interview and the "no," the more it reads as disorganization rather than a considered decision.
Should a rejection email include feedback?
Only if you can give something specific and honest. Vague filler like "we had many strong applicants" reads as an empty gesture — a brief, real reason is more useful, and it's fine to say you can't share detailed feedback if that's genuinely the case.
Is it okay to send the same rejection template to every early-stage candidate?
Yes, for resume or first-round rejections — high volume makes full personalization impractical. Just make sure the name and role are correctly filled in every time; an unpersonalized template with the wrong role name is worse than a generic one done right.
Does a good rejection email bring candidates back for future roles?
Often, yes. A respectful, specific rejection is one of the main reasons a "boomerang" candidate reapplies later — a cold or silent one is one of the main reasons they never do.