Examples of Interview Feedback: 15 Phrases That Work

Most interview feedback is useless. It is either too vague to act on ("not a culture fit") or too harsh to send ("weak answers"). Good feedback sits in the middle: specific, evidence-based, and tied to the role. These examples of interview feedback show you exactly how to write it, whether you are scoring a candidate internally or replying to someone you rejected.

I have written hundreds of interview scorecards and sat in enough debriefs to know where they fall apart. The pattern is always the same: someone writes a one-word verdict, the panel argues from memory, and the candidate gets a templated "we went another direction." Below are the phrases that actually work, split by who reads them.

What good interview feedback looks like

Useful feedback answers three questions: what did the candidate do, what did it mean for the role, and what should happen next. That is the observation-impact-recommendation pattern, and it forces you off lazy labels.

Compare these two notes for the same moment. Weak: "Seemed nervous." Strong: "Paused often on system-design questions and asked to restart twice, which suggests limited hands-on experience with the scale this role requires."

The second one is defensible. It points to behavior the whole panel saw, not a feeling. That is the difference between feedback you can stand behind and feedback that gets you into trouble.

This discipline also protects your hiring process. Structured, evidence-based notes are one of the clearest signals of a healthy, low-risk system, because they reduce the bias that creeps in when reviewers rely on gut feel.

Examples of interview feedback for internal scorecards

Internal feedback is the raw assessment your panel writes after each round. It is blunter than anything the candidate sees, but it still needs evidence. Here are phrases that score real competencies.

Notice that each note ends with a recommendation. A scorecard that just describes is half-finished. The hiring manager needs your verdict and your reasoning, not a transcript.

If you cannot point to the moment in the interview that justifies your rating, you do not have feedback. You have a feeling.

Examples of feedback to give candidates after rejection

Candidate-facing feedback is a different document. It is shorter, kinder, and stripped of anything that could read as bias or a legal risk. You are not giving a full debrief. You are giving one or two honest, useful points.

A strong rejection note sounds like this: "Thank you for the time you put in. The panel was impressed with your product sense. We chose a candidate with more direct experience scaling a paid-acquisition channel, which is the immediate priority for this role."

That message does three things. It thanks them, it gives one genuine positive, and it names a concrete, role-specific reason. No personality talk, no vague "culture" excuse that invites a follow-up.

Here are three more candidate-facing examples you can adapt:

• "Your portfolio was strong. We needed someone who had already managed agency relationships at this budget level, which came up in the final comparison."
• "You answered the case study well. The deciding factor was depth of experience with our specific tech stack, where another candidate was further along."
• "We enjoyed the conversation. For this round we prioritized people-management experience, and we would genuinely welcome a future application for an individual-contributor role."

If a candidate left feeling the process was unfair or rushed, that experience travels. Knowing the early signs of a broken or unfair setup helps you avoid sending feedback that reads as a setup rather than an honest no.

Phrases and mistakes to avoid

Some language does more harm than good. The most common interview feedback mistake is using subjective labels that no one can verify and that can expose you legally.

Avoid anything that touches a protected characteristic, even indirectly. "Too old-school," "wouldn't fit our young team," or "hard to understand his accent" are not feedback. They are liabilities. Under guidance from bodies like the Society for Human Resource Management, feedback should map only to job-related competencies.

Also drop the empty positives. "Great energy" and "really likeable" tell the next reviewer nothing. If energy matters, say what it produced: "kept the panel engaged and asked sharper questions than we did."

The deeper principle here is feedback as a feedback loop. A clear, specific signal sent back into a system is how that system corrects itself, which is the same idea behind re-inserting a useful checkpoint into a process that had gone too loose.

A simple template you can reuse

You do not need a complex form. The best structured interview scorecards use one repeatable block per competency, which keeps every reviewer honest and comparable.

Use this structure for each skill you test:

• Competency: the exact skill (for example, stakeholder management).
• Evidence: the specific moment or answer you observed.
• Rating: a clear scale, such as strong yes, yes, no, strong no.
• Recommendation: advance, probe further, or pass, with one line of reasoning.

If you are early in your career and writing your first self-assessment or interview prep notes, the same logic applies. A tight, evidence-led self-introduction that names concrete projects beats a generic summary, for the same reason specific feedback beats vague praise.

Related guides

Frequently asked questions

What are good examples of interview feedback?

Good examples of interview feedback are specific, evidence-based, and tied to the role, such as "explained the trade-offs of two technical approaches without prompting." They name a behavior, its impact on the job, and a recommendation, rather than using vague labels like "smart" or "not a fit."

How do you write feedback after an interview?

Use the observation-impact-recommendation structure. Describe what the candidate did, explain why it matters for the role, then state whether to advance, probe further, or pass. Anchor every point to a competency you tested and a moment you actually observed.

How do you give negative interview feedback to a candidate?

Keep it short, fast, and role-specific. Thank them, share one genuine positive, then name one concrete, job-related reason another candidate was chosen. Avoid personality comments and anything touching a protected characteristic, which can create legal risk.

Should you give feedback to rejected candidates?

Yes, when it is brief and specific. A short, honest reason protects your employer brand and helps the candidate improve. Decline only when company policy forbids it, and never send feedback that references age, gender, accent, or other protected traits.

What interview feedback should you never write?

Never write subjective labels or anything tied to a protected class, such as "too old," "wrong cultural background," or "hard accent." Avoid empty praise like "great energy" with no evidence. Stick strictly to job-related competencies you can defend.