Most applicants never get past the resume review, and most of them never hear a word. This candidate rejection email template is for that moment: you've reviewed an application and won't be interviewing the person. It's free to copy and edit, and the page also covers a closed-role version, a note for internal applicants and a text version for hourly hiring.
Candidate rejection email template
After the application review
When the role closed before you reviewed everyone
When to use it
Send the first version once a person has clearly failed a requirement that's written in the job posting, or once you've filled your interview slate with stronger matches. Aim to send it within a week or two of the application. A rejection that lands two months later reads as an afterthought.
Use the closed-role version when a req is filled, frozen or cancelled while applications are still sitting unreviewed. It's honest about why the person is hearing back, and it doesn't pretend you looked at a resume you didn't.
How to customize it
- Put the job title in the subject line. Candidates often apply to several roles, and a bare "Your application" leaves them guessing which one.
- Keep the reason at the level of "the requirements for this job." Specific reasons belong in a conversation with someone you've interviewed, not in a mass email.
- Only offer the talent community or "we'll keep you on file" line if someone will actually search it later. Otherwise delete it.
- Sign it with a real person's name. A no-reply address on a rejection feels colder than the rejection itself.
- Match your tone to your employer brand, but don't add jokes or exclamation points. Plain and warm works for every audience.
- Use the same wording for every applicant rejected at this stage, so the message itself never varies by who receives it.
Variations
Internal applicant
Text message for hourly roles
Text only applicants who gave their number for updates about their application.
Mistakes to avoid
- Silence. Applicants who never hear back remember the company, and the fix is one short email.
- Listing personal reasons, such as "overqualified" or "not a culture fit." They're vague, they invite argument, and they can read as code for things the law protects.
- Inviting a reapplication in three months when your team has no plan to reopen the role.
- Sending from a no-reply address and then ignoring replies that ask a simple question.
- Rejecting someone in your system but forgetting to send the email, or sending it twice from two tools.
Keep the decision clean
Rejections are where your hiring process meets the law most directly, so the email should be the last, simplest step of a fair decision. A few basics from EEOC guidance:
- Federal law forbids rejecting applicants because of race, color, religion, sex (including pregnancy, transgender status and sexual orientation), national origin, age (40 or older), disability or genetic information.
- A neutral screen that screens out a protected group more often can still be unlawful if it isn't job-related and necessary to the business. Check that your knockout criteria trace back to the job.
- EEOC rules require employers to keep personnel and employment records for one year, which generally includes applications and the records of hiring decisions.
- It's unlawful to treat an applicant worse because they complained about discrimination or took part in an investigation.
State and local rules can add more. This is not legal advice.
Automating this with Carolina
Carolina, the NTRVSTA agent, scores and ranks every resume against the job and explains why, so each decline has a job-related reason your team can review. It then sends candidate messages and updates by email, SMS or WhatsApp. Ask Carolina in plain English which applicants are still waiting on an answer, or check the morning digest in Slack or Microsoft Teams.
You set the guardrail per action. Keeping rejections on "ask first" means a recruiter approves each batch before anything goes out. Offers and compensation changes always wait for a person. See plans, including a free Starter tier, on our pricing section.
Questions
Should I give a reason when rejecting an applicant?
Keep it general at the application stage. A line saying you compared applications with the job's requirements is honest and enough. Detailed reasons in a mass email are easy to misread, and specifics are better saved for candidates you've interviewed. This is not legal advice.
How quickly should I send a rejection email after someone applies?
Within one to two weeks of the application is a good target. If your review takes longer, send a short status note first so the applicant isn't left waiting with no information at all.
Is it okay to send rejection emails in bulk?
Yes, as long as each email uses the person's name and the right job title and comes from an address someone reads. Use the same approved wording for everyone rejected at the same stage, and double-check that the list matches the decisions in your system before sending.
Want declines, updates and screening handled with a human approving each step? Book a 20-minute demo. Related templates: the rejection email after an interview, the candidate status update and the silver medalist email. Background reading: knockout questions and candidate experience.
