How to Give Interview Feedback to Candidates:Examples, Templates, and Legal Guardrails
Most companies ghost candidates after rejections. The ones that give clear, specific feedback build stronger employer brands, fill future roles faster, and avoid the legal gray zone that vague rejections create. Here is how to do it right.
According to Talent Board's Candidate Experience research, 94% of candidates want feedback after an interview, but only 26% ever receive any. That gap is not a minor inconvenience. It is a reputational problem. Candidates who were ghosted after multiple interview rounds post about it on LinkedIn, Glassdoor, and in communities relevant to your industry. The people you rejected today are potential customers, referral sources, and future hires.
The hiring teams I have seen handle this well share one trait: they treat feedback as a system, not an afterthought. They decide in advance what to say at each stage, who delivers it, and how much specificity to offer. The result is candidates who leave your process thinking well of your company, even when you said no. That matters more than most hiring managers realize. My view is that giving honest, specific feedback is one of the lowest-cost, highest-return things a recruiting team can do.
This guide covers what good feedback looks like at each stage, real examples you can adapt, the legal language to avoid, and how to build a feedback process that does not drain your recruiters' time. For context on the broader hiring picture, see our guides on candidate experience and candidate rejection emails.
One note before going further: this guide is written for employers and hiring teams. It is about giving feedback to candidates you interviewed and chose not to hire. That is a different practice from the feedback managers give to employees, and it carries different legal considerations.
The Business Case
Why most companies skip feedback and what it actually costs them
The main reason companies skip candidate feedback is time. A recruiter managing 15 open roles and screening 200 candidates a month does not have hours to write personalized notes for everyone who did not make the cut. That is a real constraint, and I am not going to pretend it is not.
But the time argument usually conflates two things: feedback for phone screen rejections (which can be brief and templated) and feedback for final round rejections (which deserves more care). The cost of a three-sentence email to someone who spent four hours in your interview process is minimal. The cost of not sending it shows up in Glassdoor reviews, referral rates, and how quickly top candidates accept your offers.
The data is clear on this. LinkedIn research shows 57% of job seekers who had a poor candidate experience would share that experience publicly. Talent Board data shows candidates who received feedback after rejection were 4x more likely to apply again or refer others to open roles. This is not soft data. It directly affects your future pipeline quality.
There is also a secondary benefit: feedback forces your hiring team to articulate why decisions were made. When a recruiter has to write down why a candidate was rejected, it surfaces whether the decision was based on real criteria or gut instinct. That discipline improves the quality of your structured interview process over time.
The honest answer is that most companies skip feedback because it feels optional and takes effort. It is optional. But the companies that do it consistently build the kind of reputation that makes recruiting easier year over year.
Feedback by Stage
What to say at each stage of the process
Not every rejection warrants the same level of feedback. The depth should match how far the candidate got and how much time they invested in your process.
"We decided to move forward with candidates whose background more closely matches [X] requirement."
"Your experience is strong on the product side, but we need deeper expertise in enterprise sales cycles for this role."
"Your technical skills were excellent. The deciding factor was the other candidate's direct experience managing remote engineering teams at scale."
"You made it to our final round, which we do not say lightly. We would welcome a conversation if a more relevant role opens up."
Phone screen rejections happen at high volume. A templated response that includes one honest sentence about why the candidate was not advanced is enough. Trying to write personalized notes for 40 phone screens a week is not sustainable.
Final round rejections are a different situation. Someone who spent a day doing a case study, meeting your team, and preparing for a technical evaluation deserves a direct explanation. Not a form letter. This is where your interview scorecard data becomes your feedback source. If you documented why you preferred the candidate you hired, you already have the content of the rejection feedback for everyone else.
Structure
A four-part structure for useful interview feedback
Good candidate feedback does not need to be long. But it does need to follow a structure that gives the person something real. Vague reassurances are worse than silence because they waste the candidate's time while offering nothing actionable. Here is the structure that works:
One or two specific things the candidate did well. Not flattery. Something real that you observed in the interview.
"Your case study approach was methodical and you asked good clarifying questions before diving in."
The specific skill, experience, or behavioral pattern that caused you to pass. One or two items only. Tie it to the role requirements.
"We need someone who has led enterprise contract negotiations directly, and that was not evident from your examples."
If it was a close call, say so. If you hired internally, say so. Candidates appreciate honesty over corporate vagueness.
"This was a genuinely close decision. The candidate we selected had 3 years of direct team lead experience that tipped it."
Leave the door open if they were strong. Or give one specific suggestion if you want to be helpful. Skip it if neither applies.
"If you build out your experience managing distributed teams, you would be a strong fit for future roles here."
The key constraint is this: keep the named gap tied to observable evidence from the interview, not your impression of the person. You can say "the examples you gave during the system design interview did not demonstrate experience with distributed architectures." You cannot say "you seemed like you were not really a technical person." One is a statement about what happened in the conversation. The other is a characterization that creates legal risk.
This structure also works when the candidate was strong and the decision was close. In that case, the "gap" is often not a gap at all. It is that one candidate had something the other did not. Saying so clearly is more respectful than a generic "we found someone with more experience."
Real Examples
Weak vs. specific feedback: side-by-side comparisons
The difference between bad feedback and good feedback is almost always specificity. Here are four common rejection scenarios with examples of what weak feedback looks like versus what actually helps the candidate.
"You weren't a strong culture fit."
"Your communication style tends toward detailed, written processes. Our team operates with fast verbal decision-making and limited documentation. That mismatch would create friction in daily work."
"We went with someone with more experience."
"The candidate we selected had five years of direct P&L ownership in a similar ARR range. Your background is strong on execution, but we needed someone who has already owned the revenue number."
"Your interview performance was not what we expected."
"In the technical case study, your solution was creative but did not account for the data pipeline constraints we outlined in the brief. The top candidate walked through those tradeoffs in detail."
"We decided to move in a different direction."
"We filled the role internally after the interview process concluded. Your skills are genuinely strong, and I'd encourage you to apply again when we hire for a similar role."
Notice that the strong examples all name something specific: a skill gap, a missing experience, a measurable difference between candidates, or a factual circumstance like an internal hire. None of them speculate about the candidate's personality, potential, or what they might do in the future.
The "culture fit" example is worth examining in more detail. "Not a culture fit" is legally problematic because it is undefined. Courts and HR attorneys have flagged it repeatedly as a phrase that can mask discrimination. Replacing it with a specific description of the working style mismatch gives the candidate real information and protects your organization.
Legal Guardrails
What to say and what to avoid in written feedback
The legal exposure in candidate feedback comes from two sources: mentioning protected characteristics (age, race, gender, disability, national origin, religion, family status) and making statements that could be construed as promises or evaluations that contradict your decision. The EEOC guidelines are the starting point for understanding what you cannot ask in interviews. The same principles extend to what you write in feedback.
- Lacks experience with [specific skill or tool]
- Did not demonstrate [observable behavior] during the interview
- The selected candidate had [measurable advantage]
- The role requires [specific competency] we did not see evidence of
- Your answers on [topic] were general where we needed specifics
- We hired internally / filled from the existing team
- You seemed overqualified (implies age discrimination)
- You would not fit in with our team (vague, can imply bias)
- We need someone with more energy (can imply age or health)
- You are too junior for this culture (can imply race, gender)
- We want someone who can grow with us (can imply age or family)
- Your communication style was different from ours (too vague to be legal)
The word "overqualified" is worth special attention. Courts in the US have ruled that "overqualified" can be used as evidence of age discrimination under the Age Discrimination in Employment Act (ADEA). If your real concern is that a senior candidate will leave quickly, say that directly: "We were concerned that this role would not provide the scope of challenge you are looking for long-term." That is honest and defensible. "Overqualified" is not.
I would also flag "not a fit" as a phrase to avoid entirely. It tells the candidate nothing and provides no legal protection. If you felt strongly enough about the person to interview them multiple times, you should be able to name what specifically did not work. If you cannot name it, that is a signal to examine your hiring criteria, not a reason to write a vague rejection.
For more on structuring your hiring process to minimize bias and legal exposure, see our guide on reducing unconscious bias in hiring.
Templates
Ready-to-use feedback templates by scenario
Hi [Name], Thank you for the time you put into our process. You made it to our final round, which means you impressed our team significantly. The decision came down to one specific factor: the other candidate had [3 years of direct experience managing fully remote engineering teams / a stronger background in enterprise procurement cycles / etc.]. Your skills in [area] were genuinely strong. We would like to stay in touch. If a [similar role] opens up, I will reach out directly. Best, [Your name]
Hi [Name], Thank you for going through our interview process. I wanted to give you some honest feedback, since you invested real time with us. The primary reason we did not move forward was [the technical assessment showed limited experience with distributed system architecture / your examples in the revenue operations round did not demonstrate direct pipeline management / etc.]. This is a core requirement for this role, and we needed to see more evidence of it. Your strengths in [area] are real, and I think you would be a strong candidate for roles with a different emphasis. [Optional: If you build out [specific skill], I think you would be competitive for similar roles in the future.] Best, [Your name]
Hi [Name], Thank you for speaking with us about the [Role] position. After reviewing all candidates, we have decided to move forward with others whose background more closely matches the [specific requirement] we need for this stage of the role. We will keep your profile on file and will reach out if a more relevant opening comes up. Best, [Your name]
Hi [Name], I enjoyed our conversation about the [Role]. You asked thoughtful questions and clearly understand [relevant domain]. After the full panel review, we decided not to move to the next stage. The main feedback from the team was that [your answers on the go-to-market strategy questions stayed at a high level where we needed specific examples from past roles / etc.]. That made it harder for us to assess your direct experience with [specific area]. I think you are worth talking to for future openings. Are you open to staying connected? Best, [Your name]
These are starting points, not scripts. The bracketed sections are where real specificity goes. A template with blanks filled in with honest details is far more useful to a candidate than a polished generic letter.
Operations
How to scale feedback without burning out your recruiters
Build templates by rejection reason, not by stage
Most rejections fall into four or five categories: wrong skills, salary mismatch, hired internally, stronger competition, not enough experience in a specific area. Build a template for each. A recruiter who can pick the right template and fill in two blanks will send better feedback than one trying to write from scratch under time pressure.
Batch your feedback sends strategically
For phone screen rejections, wait until you have completed all screening for a role before sending feedback in batch. This protects you legally (you can reference that you moved forward with candidates who better matched the requirements, plural) and prevents premature feedback that you might need to walk back.
Use your ATS notes as feedback raw material
If your team is using a structured interview scorecard, the rejection feedback is already written. The interviewer notes saying 'limited enterprise sales experience, gave mostly SMB examples' become the feedback. Build a workflow where interviewers know their notes will be used as candidate feedback. It raises the quality of the notes.
Have legal or HR review your templates once
You do not need legal review on every feedback message. You need it once, when you build your templates. Get sign-off on the language before you build the system, not after a problem surfaces. This is especially important for feedback on protected class-adjacent situations like overqualification or culture mismatch.
Track feedback rate as a recruiting metric
Add candidate feedback rate to your recruiting team scorecard alongside time-to-fill and offer acceptance rate. Teams that track it treat it as real work. A target of 100% feedback for candidates past round two and 80% for phone screens is achievable without dramatic effort. It becomes a habit.
Train hiring managers to own the message, not the words
Recruiters usually send rejection feedback. But the content should come from the hiring manager. Build a step into your hiring debrief where the manager articulates one specific reason for each rejection. The recruiter translates that into the feedback message. This keeps the message accurate without requiring managers to write the email themselves.
The goal is a system where feedback happens automatically as part of your rejection workflow, not as an optional extra step a recruiter decides to take. For teams building that process from scratch, the interview training for hiring managers guide covers how to build debrief practices that generate the raw material feedback needs.
Handling Requests
When a candidate asks for feedback after rejection
Some candidates will follow up after a rejection and directly ask for feedback. This is more common for senior roles and late-stage rejections. The honest answer is you have two real options: give genuine feedback or decline politely. What you should not do is promise feedback and then send a vague non-answer.
If you have notes and the candidate was strong, give the feedback. Use the structure above. Keep it brief. Most candidates asking for feedback want to know one specific thing they can work on, not a performance review.
If you do not have useful notes, or if the decision involved sensitive internal factors (restructuring, budget cuts, a leadership disagreement about the role), it is fine to say so directly: "The decision was not based on your interview performance. There were internal factors that made the hire difficult to move forward. Your skills are genuine and I hope you find a strong fit elsewhere."
What candidates remember is whether you treated them honestly. A short, truthful response is better than a lengthy one that avoids saying anything real. This connects directly to the broader challenge of why candidates ghost employers: trust erodes when people feel they are being managed rather than talked to.
Employer Brand
How feedback builds your employer brand over time
Employer brand is built in the moments no one is paying attention to. A candidate who was rejected but received specific, respectful feedback will describe your company differently than one who was ghosted after four rounds. That description reaches people you will want to recruit in two years.
The benchmark data from Talent Board shows a direct correlation between candidate experience scores and offer acceptance rates. Teams ranked in the top quartile for candidate experience see 33% higher offer acceptance than those in the bottom quartile. Feedback is one of the cheapest inputs into that score.
There is also a practical referral effect. A candidate who was rejected but respected your process will refer friends to open roles. A candidate who was ghosted will not. Given that SHRM data shows employee referrals produce 55% faster hires and significantly higher retention rates, treating rejected candidates well has a direct return on your recruiting efficiency. For more on building a referral-friendly process, see our guide on employee referral programs.
I think the deeper shift is cultural. Teams that give real feedback treat their hiring process as something they take pride in, not just a function that produces headcount. That attitude shows up in the quality of interviews, the speed of decisions, and the respect candidates feel throughout the process. Feedback is not the cause of good hiring culture. It is a symptom of it.
Frequently Asked Questions
Are employers legally required to give interview feedback?
In most jurisdictions, no. Employers are not required to provide interview feedback. Some European countries have stronger candidate rights, but in the US, providing feedback is discretionary. The legal risk is not in giving feedback, it is in giving feedback that mentions protected characteristics. A clear, skills-based explanation of your decision is generally safer than silence.
Should you give feedback to every rejected candidate?
Not necessarily. Phone screen rejections can use brief, templated responses. Final round rejections deserve more personal feedback, especially if the candidate invested significant time. The practical threshold for detailed feedback is any candidate who completed more than two rounds of interviews. For high-volume sourcing, a short, honest template is better than nothing.
How do you give feedback to a candidate who performed poorly?
Focus on specific, observable gaps in the interview, not personality or attitude. 'Your answers to the system design questions lacked depth on scalability tradeoffs' is useful. 'You seemed unprepared' is not. Stick to things you can point to from the actual interview. Keep it brief. You are not obligated to write a detailed development plan for someone you are not hiring.
When should you send interview feedback?
Within 48 to 72 hours of the decision for later-stage rejections. Phone screen feedback can wait until the role is filled or until you have screened enough candidates to make a comparison. The worst timing is two weeks after the interview, when the candidate has moved on mentally and the delay itself feels disrespectful.
Can giving interview feedback expose you to legal liability?
It can, if the feedback references protected characteristics like age, race, gender, disability, or family status. The risk is low when feedback focuses on skills, experience, and specific interview performance. Vague language like 'not a fit' actually creates more legal exposure than specific, skills-based feedback because it leaves room for a discrimination inference.
What is the difference between candidate feedback and a rejection email?
A rejection email tells the candidate the outcome. Feedback explains why. Most rejection emails skip the why entirely. Good feedback includes at least one specific reason tied to role requirements, not just 'we found a stronger candidate.' The two can be combined in one message or delivered separately, but candidates who received a reason are significantly more likely to think positively of your employer brand.
Resources & Further Reading
Related Guides
- Candidate Rejection Email: Templates That Respect the Candidate
Templates for every stage of the rejection process
- Candidate Experience: How to Fix Your Hiring Funnel's Biggest Leak
The full picture on candidate experience optimization
- Interview Scorecard: Build One That Predicts Performance
Scorecards generate the data that makes feedback specific
- Structured Interviews: How to Build a Process That Scales
The interview architecture behind good candidate documentation
External Sources
- Talent Board Candidate Experience Research (CandE)
Annual benchmark on what candidates actually experience
- EEOC Pre-Employment Inquiry Guidelines
Legal foundation for what can and cannot inform hiring decisions
- HBR: How Companies Can Give Better Feedback to Rejected Candidates
Research on the employer brand impact of candidate feedback
- SHRM: Employee Referral Programs
Data on how referral rates connect to candidate treatment
Build a hiring process candidates remember
Prepzo helps hiring teams run structured interviews, document decisions, and move faster without cutting corners on candidate experience. Free to start.
Try Prepzo free