How to Write a Rejection Email Candidates Won't Hate

Almost every rejection email says some version of the same six words: we've decided to move forward with other candidates. It's true, it's safe, and it's the reason candidates routinely describe rejections as the worst part of job searching — not because being rejected is pleasant, but because the form of it makes it clear no actual person is really behind the message.

A meaningfully better rejection email doesn't take much more effort. It just needs a few specific things the generic version skips.

What actually makes a rejection land better

• Say something true and specific about the conversation, even briefly — a real observation about the interview, not a generic compliment. It's the single biggest signal that someone actually read the notes rather than sending a template.
• Be direct about the outcome in the first sentence. Burying "unfortunately" in the third paragraph after two paragraphs of pleasantries reads as avoidant, not kind — most candidates would rather know immediately and read the context after.
• Don't leave a door open you don't mean to leave open. "We'll keep your resume on file for future opportunities" is fine when it's true and meaningless flattery when it isn't — candidates have learned to read it as the latter by default, so only include it if you actually mean it.
• Keep it short. A long rejection reads like it's trying to justify the decision at length, which usually makes it feel worse, not better. Two or three short paragraphs is enough.

A reasonable structure

A rejection email that follows this shape holds up well without requiring much extra time per candidate:

• Thank them for the specific conversation (name the role, maybe reference something concrete from it).
• State the outcome directly, without over-hedging.
• One honest, specific line about why — general enough to be legally safe, specific enough to not feel like a form letter.
• A genuine, not-obligatory closing line, only if you mean it.

Where the honest tension is: time

The advice above is easy to agree with and hard to actually execute across a full pipeline of candidates a recruiter is rejecting in a normal week. Writing one thoughtful, specific rejection takes real minutes; writing thirty of them, individually, on top of everything else in a hiring week, is where most recruiters quietly give up and fall back to the template — not because they don't care, but because the math doesn't work.

The practical fix isn't lowering the bar, it's removing the friction

The reason a specific rejection is slow to write by hand is that it requires remembering the details of a call that might have happened days earlier — which candidate said what, what stood out, what didn't. That's exactly the information a live notetaker already has captured, verbatim, from the interview itself.

It's also why we hold ourselves to a simple rule on every search: everyone hears back. Every candidate we speak to gets a real answer from a person, so your name stays good with the people you don't hire. Book a call if you'd like your next hire run that way.