How to give candidate interview feedback

The shape of good feedback

1. The decision, stated plainly in the first line.
2. The requirement that was not met.
3. One specific observation from the process.
4. Thanks, and whether you would welcome a future application.

Lead with the decision

Do not bury it under three paragraphs of appreciation. Candidates scan for the answer and resent having to hunt for it. “We have decided not to move forward” in the first line, then the reason. This reads as respectful rather than blunt, because it treats the candidate as someone whose time matters.

Make it specific and job-related

• Good: “The role needs someone who has run migrations on a live system; the examples you gave were from staging environments.” Specific, checkable, actionable.
• Bad: “We went with someone more experienced.” Tells them nothing and invites a comparison argument.
• Bad: “You seemed nervous.” Personality, not requirement, and closer to legal risk than most people realise.
• Bad: “Not quite the right fit.” The phrase candidates most dislike, because it sounds like a decision about them as a person.

Stay away from these

• Comparisons to other candidates. You are explaining a decision about them, not running a league table.
• Anything touching a protected characteristic, including well-meant comments about career breaks, age or accent. See interview questions you cannot legally ask.
• Promises about the future you do not control — “we will keep you in mind” when nobody will.
• Negotiating the decision. Feedback explains a decision; it does not reopen it.

How much to give, and to whom

Scale it to how far they got. A candidate rejected at resume review gets a prompt, courteous no. Someone who did a screen gets a line about the requirement. Someone who spent a day in a loop has earned several sentences and, if they ask, a short call. The implicit rule candidates apply is proportionality: the more of their time you took, the more you owe them in return.

Speed matters more than polish

A short rejection within three days is received far better than a thoughtful one after three weeks. Silence is the thing candidates actually complain about publicly, and it is the cheapest problem on this list to fix. Decide at the debrief who sends it and by when, and treat that as part of the loop rather than as admin to do later.

When to say less

• When the decision was close and arbitrary. Say it was close and that there was no gap in their performance, rather than inventing a shortfall.
• When your own process failed. If an interviewer was unprepared, that is not the candidate's deficiency to carry.
• When local practice or counsel restricts it. Some jurisdictions and employers limit written feedback; a brief courteous decline is better than a vague invented reason.

A template you can adapt

“Hi [name] — we have decided not to move forward with your application for [role]. The main gap was [requirement]: in the [stage], we were looking for [specific thing], and the examples you described were [specific observation]. Everything else in the process was positive, particularly [one genuine strength]. Thank you for the time you put in, and we would welcome an application for [adjacent role or future opening] if that interests you.” Four sentences, specific, nothing about personality, and defensible because every claim is tied to something recorded at the time.

Handling the reply

• If they ask for more detail, give one more level and then stop. You are not obliged to justify a decision indefinitely.
• If they disagree, acknowledge it without reopening. “I understand it looked different from your side; the decision is final.”
• If they are angry, do not respond in kind or at length. A short, calm reply ends it; a defensive one escalates it publicly.
• If they ask to reapply, give a real timeframe or say no. “In six months, if you have run a migration on a live system” is useful; “anytime!” is not.

Base it on the scorecard

Feedback drawn from evidence recorded at the time is both more useful and more defensible than feedback reconstructed from memory a week later. This is a side benefit of evidence-based scorecards: the feedback almost writes itself from what was already recorded. See how to write an interview scorecard.

Where Interviewer Mode fits

Disclosure: we make CoPilot Interview, which includes Interviewer Mode for the hiring side and a real-time assistant used by candidates. We have an interest in you using the first, and our view of the second is that interviews should be designed to measure something an assistant cannot fake. Weigh the advice below accordingly.

Frequently asked questions

Should you give feedback to rejected candidates?

Yes, scaled to how far they got. A prompt courteous no at resume stage; a line about the requirement after a screen; several sentences after a full loop. Speed matters more than length — three days beats a thoughtful note after three weeks.

What should you say in interview rejection feedback?

State the decision in the first line, name the job requirement that was not met, give one specific observation from the process, and close. Avoid comparisons to other candidates, comments on personality, and vague phrases like “not the right fit”.

Is it risky to give interview feedback?

The risk comes from vague or personal wording, not from feedback itself. Keep it specific, job-related and tied to evidence recorded in the scorecard at the time, and avoid anything touching a protected characteristic.

What if the rejection decision was arbitrary?

Say so. “This was genuinely close and there was no gap in your performance” is more respectful and more honest than inventing a shortfall, and candidates can usually tell the difference.