How to Write a Candidate Rejection Email That Doesn't Burn a Bridge

Most rejection emails fall into one of two bad shapes. The first is the automated one line from the applicant tracking system: “We have decided to move forward with other candidates.” Nobody believes a human wrote it, and nobody who reads it forms a better opinion of the company. The second is the over-explained one, where a well-meaning hiring manager writes three paragraphs justifying the decision and accidentally invites an argument.

Neither version is doing the job the email actually needs to do. A candidate who applied, interviewed, and waited deserves a clear no, delivered with enough warmth that they would still apply again for a different role. That is a narrower target than it sounds, and it is easy to miss in either direction.

Say No In The First Two Sentences

The candidate is reading for one piece of information. Give it to them immediately, then close the loop.

Before:

Dear Applicant, Thank you for taking the time to apply to the Senior Analyst position at our company and for participating in our interview process. After careful consideration of all candidates, we have made the difficult decision to move forward with another candidate whose qualifications more closely align with our current needs at this time. We wish you the best of luck in your future endeavors and encourage you to apply again for future openings that may match your skill set.

After:

Hi Marcus,

Thanks for the time you put into interviewing for the Senior Analyst role. We’ve decided to move forward with another candidate.

This wasn’t close to an easy call. Your systems experience stood out, and I’d genuinely welcome an application if a data-heavy role opens here again.

Wishing you the best with the search, Priya

The second version names the person, says no without padding, and gives one specific, honest reason to reapply instead of a form letter’s blanket invitation nobody trusts. It is also shorter, which reads as respect for the candidate’s time rather than as coldness.

Give Feedback Only When You Mean It

Specific feedback is the single biggest lever for how a rejection lands, and also the easiest way to create a legal or interpersonal problem if you get it wrong.

Good feedback is about the work: “the case study leaned heavily on individual contribution and we were hiring for someone who had run a team of six or more.” That is verifiable, tied to the role, and not arguable in a way that invites a reply.

Feedback to avoid is anything evaluative about the person rather than the work: culture fit, communication style, or a vague sense that another candidate was “stronger overall.” These read as subjective, they are hard to defend if challenged, and they rarely help the candidate improve anything concrete. If you cannot point to a specific, job-related reason, it is safer to say the field was strong and leave it there.

A Wrivio Context for candidate rejection emails could say:

Rewrite this as a warm but direct rejection email to a job candidate. Say no in the first two sentences, thank them for their time without over-explaining, and keep any feedback specific to the work rather than the person. Keep every name, role title, and date exactly as written, and do not soften the “no” into something that could read as still under consideration.

Press Ctrl+Shift+Space, paste the draft, and check the diff for anywhere the rewrite made the outcome sound less final than you intended. That is the failure mode worth watching for in this particular message.

Keep A Record Without Writing A Legal Memo

There is a practical reason to keep the email itself factual rather than persuasive: in the United States, the EEOC’s recordkeeping rules require employers to retain application and hiring records, including rejected applications, for one year after the record was made or the personnel action taken, longer if a charge is filed. Similar record-retention expectations exist under employment law in most other jurisdictions. A short, factual email that matches your interview notes is easy to stand behind later. A long one written to make the candidate feel better in the moment can end up contradicting what your notes actually say, which is worse for everyone if the decision is ever questioned.

This is not a reason to sound legalistic. It is a reason to keep opinion out of the email and stick to what actually happened: the role, the process, the decision, and one genuine, job-related detail if you have one. That combination is both the kinder version to receive and the safer one to have sent.

What To Do When The Candidate Was Close

For a candidate who made it to a final round or lost out narrowly, a short call is worth the fifteen minutes before the email goes out at all. It costs you almost nothing, and hearing “no” from a person rather than an inbox changes how someone remembers the company, which matters if you are also the team writing the job description for the next opening and hoping strong candidates apply again. If a call genuinely is not possible, the email should do the same work: name what they did well, be honest that it came down to a close call, and mean it.

The same discipline applies on the other side of hiring, too. Whoever ends up checking references for the candidate you did hire should keep those notes just as factual, since they carry the same record-keeping weight a rejection email does.

Common Questions

Should I tell a candidate why they didn’t get the job?

Only if you have something specific and work-related to say. Vague or personality-based feedback creates more risk than it offers value, so it is better to keep the reason general if that is all you have.

How soon should I send a rejection after deciding?

As soon as the decision is final and the preferred candidate has verbally accepted, ideally within a few business days. Candidates who hear nothing for weeks assume the worst about the company, not just about their own chances.

Is a phone call better than an email for finalists?

Yes, for anyone who reached a final round or was told they were a strong contender. A short call before the follow-up email is the difference candidates remember, and it is worth the discomfort of making it.

Do I need to keep rejected applications on file?

In the United States, yes: the EEOC requires retaining hiring-related records, including applications from candidates who were not hired, for at least one year. Check the specific requirement in your jurisdiction, since some extend it further.

What if the candidate replies asking for more detail?

Answer with one more specific, job-related point if you have one, or say honestly that the field was strong and you are not able to go further into the comparison. Do not invent a new reason on the spot.

Download Wrivio for Windows to turn a blank rejection template into a short, specific email in the time it takes to name the role and the one thing the candidate did well.