.webp)
About 70% of rejected candidates say a clear reason for not being selected leaves them with a positive impression of the company, even though they didn't get the job. Most companies still send a generic rejection, or nothing at all, because writing individual feedback for every unsuccessful candidate feels like it doesn't scale. It doesn't have to be individual for every line. It has to be specific for the one or two lines that matter.
Here is how to write interview feedback for unsuccessful candidates that takes five minutes, doesn't expose the company to unnecessary risk, and actually helps your employer brand instead of just checking a box.
Why bother giving feedback at all
You are not required to give feedback to candidates you don't hire. But candidates talk, especially in tight technical talent markets, and a hiring process that ends in silence or a copy-paste rejection is one of the most common reasons candidates describe a company negatively to their network. A rejection with a specific, honest reason does the opposite: it signals that the process was fair, even to the people who didn't win.
It also has a direct pipeline benefit. Candidates who didn't get this role but were close often go on to apply for a different one, refer other candidates, or become customers later. None of that happens if their last interaction with your company was a form email that didn't tell them anything.
The structure that works
Good rejection feedback follows the same shape whether it's delivered by email, phone, or text.
1. Lead with something specific and true. Not a generic compliment. Reference an actual moment from the interview: a project they described well, a question they handled cleanly, a skill that was clearly strong.
2. Give one or two concrete reasons, not a list of everything. Pick the actual deciding factor, usually a skills gap relative to another candidate or the specific requirements of the role, and say it plainly. Vague feedback like "we went with someone who was a better fit" is worse than no feedback, because it gives the candidate nothing to act on and reads as evasive.
3. Keep it short. This is not the place for a full debrief of their performance. Two to four sentences of substance is enough. Long feedback emails read as either legal hedging or an attempt to soften bad news by burying it.
4. Decide delivery method by how far they got. A candidate rejected after a resume screen can get a templated email. A candidate rejected after a final-round or onsite interview, especially one who invested real time, deserves a personal note or a short call.
Four templates you can adapt
Rejected after a technical skills gap.
"Thanks for the time you put into the process. Your experience with [X] came through clearly. We ultimately moved forward with a candidate whose background more closely matched the [specific technical requirement] this role needs right now. We'd encourage you to apply again as you build more experience in that area."
Rejected in favor of a closer match on experience.
"It was a close decision. We were impressed with [specific strength], but chose a candidate whose experience with [specific tool or domain] aligned more directly with what this team needs immediately."
Strong candidate, wrong role.
"You have skills that don't fit this particular opening but would be a strong match for [other function]. We'd like to keep you in mind for that team, and would welcome you applying directly if a relevant role opens."
Rejected after an assessment or technical round, with a specific gap.
"Your problem-solving approach came through well in the discussion. The [specific test or round] showed a gap in [specific skill] relative to what this role requires day to day. That's a learnable area, and we'd be glad to see you apply again once you've had more hands-on time with it."
What to avoid
Don't compare the candidate to the person who got the job by name or by implication that invites debate. Keep the reason about the role's requirements, not a head-to-head comparison.
Don't invent a reason to soften the blow. If the real reason is compensation expectations, timeline mismatch, or a hiring freeze on the role, say that instead of manufacturing a skills gap that isn't true. Candidates can tell, and it undermines the credibility of the feedback.
Don't skip feedback for candidates you'd want to hire in the future. A generic "not moving forward" email is the fastest way to make sure a strong runner-up never reapplies.
Making this sustainable at scale
The reason most companies stop giving individual feedback isn't that they don't see the value. It's that recruiters are juggling dozens of open roles and writing personalized rejections for every candidate isn't realistic without some structure behind it. The fix isn't to skip feedback, it's to make the underlying evaluation specific enough that writing the feedback takes minutes instead of requiring a recruiter to reconstruct the interview from memory.
That's a direct benefit of interviews that produce a detailed, structured evaluation instead of a one-line verdict. When each interview report already documents the specific strengths and gaps against defined criteria, a recruiter can turn that into candidate-facing feedback without starting from a blank page.
FAQs
Should I always give feedback to unsuccessful candidates?
Not always, and it isn't legally required in most cases. But for anyone who reached a phone screen or later, a short, specific reason is worth the five minutes it takes and meaningfully improves how the candidate remembers the process.
Is it better to give feedback by email, phone, or text?
Email works for early-stage rejections. A short call is worth the extra effort for candidates who reached final rounds or an onsite, since it's easier to convey nuance and answer a follow-up question without it reading as cold.
What if the candidate pushes back on the feedback?
Acknowledge their perspective without re-opening the decision. Restate the specific reason once, calmly, and close the conversation. You don't owe a debate, only a clear and honest answer.
How specific is too specific?
Avoid anything that sounds like a legal risk, comments tied to a protected characteristic, health, family status, and so on, even if that's not what you meant. Stick to job-relevant skills and requirements.
The short version
Specific beats generic, short beats long, and honest beats softened. Candidates remember how a company treated them on the way out far more than most recruiters expect, and that memory shapes whether they apply again, refer someone else, or tell their network to avoid you.
See how Intervue's structured interview reports make it easier to turn every rejection into feedback candidates actually find useful.
Visit intervue.io
