Examples of Interview Feedback: 15 Templates 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 strong candidate internally or replying to someone after an unsuccessful interview.

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 decided to move forward with another candidate."

Below are the interview feedback examples that actually work, split by who reads them. Each one is something you can copy, adapt to your role, and use in the next debrief without rewriting from scratch.

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 observation-impact-recommendation pattern is the backbone of effective interview feedback, and it forces you off lazy labels.

Compare 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 detailed interview 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.

Good interview feedback shares four traits. It is specific, it is timely, it is honest, and it is actionable. Miss any one of those and the feedback provided stops being helpful interview feedback and starts being noise the next reviewer ignores.

That last word matters. Helpful feedback is the whole point: a note only earns its place if the person reading it, whether a colleague or the candidate, can actually do something with it. Anything else is decoration on a form nobody trusts.

One more test before you hit save. Could a colleague who was not in the room understand your note and reach the same conclusion? If yes, you have written specific feedback. If they would need you to explain it, you have written a private memory, not feedback.

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 specific examples that score real competencies and capture interview performance answer by answer.

Each note below rates the candidate's performance during the interview against a single competency, so the panel can compare like with like later.

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 of the job interview.

It also helps to score against the same interview questions every reviewer asked. When the panel rates the same prompts in every interview, the debrief compares like with like instead of arguing about which candidate got the easier conversation.

These examples for HR teams work because they are comparable. When every reviewer writes against the same competencies, the debrief stops being a popularity contest and becomes a calibrated hiring decision. Consistent scorecards are also where the best feedback comes from: structure beats memory every time.

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 positive interview feedback

Positive feedback is not the same as empty praise. The best positive interview feedback still cites evidence, it just happens to be evidence the candidate did well. It tells the panel why this person clears the bar.

Here is positive feedback that earns its place on a scorecard:

• "Strongest answer of the day on prioritization. Walked through a real trade-off where they killed their own pet project for the company's number."
• "Asked sharper questions about our roadmap than two of our interviewers did. Genuine curiosity, not rehearsed."
• "Handled the curveball question calmly, said 'I don't know, here is how I'd find out,' which is exactly the behavior we want."

Good comments for a job interview name a moment, not a mood. "Great energy" tells the next reader nothing. "Kept the panel engaged and reframed the problem better than we had" tells them everything. That is what thoughtful feedback looks like in practice, and it gives a strong candidate a clear reason to advance.

A positive interview note also helps later. When two finalists are close, the panel can reread who did well on which competency instead of relitigating the whole loop from memory. Positive feedback that cites a specific moment is the tiebreaker that holds up in a debrief.

Examples of interview feedback for unsuccessful candidates

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

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 to move forward with another candidate who had 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. This is honest feedback that still respects the person.

Here are three more examples of feedback to candidates you can adapt as interview feedback for unsuccessful candidates:

• "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."

Constructive interview feedback to unsuccessful candidates should help candidates understand the decision, not relitigate it. Give them one actionable point and a clear suggestion on how the candidate could strengthen a future application, then close the loop cleanly.

Keep those suggestions on how the candidate can improve concrete and within their control. "Bring a metric to every project story" is useful. "Be more senior" is not. The first one is something they can act on before the next job interview; the second just stings.

If a candidate left feeling the process was unfair or rushed, that interview 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.

Reasons to reject a candidate (and how to phrase them)

Most rejections trace back to a handful of reasons to reject a candidate: a skills gap for the level, a stronger competing candidate, weak evidence on a core competency, or a values mismatch you can actually point to. The reason is fine. The phrasing is where teams get sloppy.

Translate the internal reason into role-specific language before it reaches the candidate. "Not senior enough" becomes "we needed someone who had already owned a budget of this size." That keeps the negative interview feedback honest without making it personal, and it keeps your hiring decisions defensible.

One caution. Never invent a softer reason to spare feelings. If you tell a candidate the role needed more Python and they later see the same job reposted asking for SQL, your credibility is gone. The real reason, phrased kindly, always beats a comfortable fiction.

Giving interview feedback: best practices

Knowing what to write is half the job. How you deliver interview feedback decides whether it builds trust or burns it. These interview feedback best practices come from watching feedback delivery go right and wrong across dozens of hiring loops.

• Feedback promptly: write your notes within an hour of the interview, while the answers are fresh. Timely feedback is accurate feedback.
• Separate observation from judgment: record what happened first, rate it second. This single habit kills most bias in the feedback process.
• Balance positive and constructive feedback: name one thing the candidate did well alongside the gap. Honest does not mean harsh.
• Keep it actionable: if you would not know what to do with the comment, the candidate will not either.
• Stay job-related: every line maps to a competency, an interview question, or a requirement, full stop.

When you provide feedback this way, you give the candidate actionable feedback they can use, not a verdict they can only absorb. That is the line between feedback that helps and feedback that merely judges.

These feedback best practices apply at every stage of the interview process, from the first phone interview to the final on-site. A phone interview deserves the same written note as a panel round, even if it is shorter, because getting feedback in early is how a weak loop corrects itself fast. Treat every interview as a chance to sharpen both the candidate and your own interview skills.

One habit raises the quality of everything else: decide who will give feedback before the loop starts. When each interviewer owns a competency, nobody scores the same thing twice and no signal falls through the gap between rounds.

The debrief: turn feedback into a loop

Individual notes are inputs. The debrief is where they become a decision. Run it as a short, structured feedback loop: each interviewer reads their evidence first, gives a rating second, and only then does the panel discuss. Reversing that order is how the loudest voice hijacks the hiring decisions.

A simple feedback form keeps the debrief honest. List the competencies down one side, one rating column per interviewer, and a final recommendation row. When the internal feedback is laid out side by side, disagreement becomes visible and useful instead of vague.

Treat the whole thing as recruitment in miniature: a clear signal goes in, the next cycle improves. That feedback loop is also where you catch a flawed interview question. If three strong candidates all stumbled on the same prompt, the problem is your question, not them.

How feedback helps your candidate experience and employer brand

Feedback is not a favor you do at the end. It is part of the product candidates judge you on. A clear, respectful note after a rejection is one of the cheapest ways to improve the candidate experience and protect a positive employer brand.

Here is why this matters in plain numbers. Candidates who get useful feedback are far more likely to reapply, refer a friend, and leave a fair review, even when the answer was no. Silence does the opposite. Feedback builds trust; a black hole burns it.

This is the practical payoff of treating recruitment as a feedback loop. Getting feedback right at the candidate level mirrors how a healthy system corrects itself: a clear signal goes back in, and the next cycle improves. That is the same logic behind re-inserting a useful checkpoint into a process that had gone too loose.

So the case for good interview feedback is not only ethical, it is commercial. Every interview that ends with thoughtful, honest feedback strengthens your reputation in a market where candidates talk.

Where AI interview tools fit (and where they do not)

AI interview tools now transcribe calls, summarize answers, and even draft a first pass of candidate feedback. Used well, this kind of AI interview support saves the recruiter time and makes post-interview feedback more consistent. Used lazily, it produces confident nonsense.

My rule: let the AI interview assistant capture and structure, never decide. An AI summary is a starting draft a human edits, not the final feedback provided to a hiring manager. The evidence still has to be real, and the recommendation still has to be yours.

The deeper principle is feedback as a loop. A clear, specific signal sent back into a system is how that system corrects itself, which is the same idea that makes detailed feedback worth the effort in the first place.

A simple interview feedback template you can reuse

You do not need a complex feedback form. The best structured interview scorecards use one repeatable block per competency, which keeps every reviewer honest and comparable. These examples and templates turn a dreaded task into a habit.

Use this interview feedback template for each skill you test:

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

For candidate-facing notes, the template is even simpler: one line of thanks, one genuine positive, one role-specific reason, one open door. Feedback templates like these turn examples and best practices into a five-minute habit, and consistency is what builds a positive employer brand over time.

Guidance from bodies like the Society for Human Resource Management is clear that feedback should map only to job-related competencies. 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.

That legal caution sits inside a wider truth about every job interview: the feedback you write is a record. Treat each note as something a candidate, a colleague, or a court could one day read, and you will naturally write the kind of specific, fair, role-based feedback this whole guide is built on.

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 a specific example of feedback beats vague praise.

Related guides

Frequently asked questions

What is an example of good interview feedback?

An example of good interview feedback is specific, evidence-based, and tied to the role, such as "explained the trade-offs of two technical approaches without prompting." It names a behavior, its impact on the job, and a recommendation, rather than using vague labels like "smart" or "not a fit."

What are examples of good feedback comments?

Good feedback comments point to a moment, not a mood. Examples include "broke the ambiguous brief into three testable assumptions on the spot" or "owned a failed launch and named the exact decision they would change." Each one is specific, defensible, and mapped to a competency you tested.

What are some examples of positive feedback?

Examples of positive feedback name evidence the candidate did well: "asked sharper roadmap questions than our interviewers did" or "said 'I don't know, here is how I'd find out,' which is exactly the behavior we want." Positive feedback should still cite a concrete moment, not just praise energy.

What are some good comments for a job interview?

Good comments for a job interview balance honesty with usefulness, such as "strong on execution but gave no examples of leading without authority, recommend a follow-up." Deliver them promptly, keep them job-related, and pair one genuine positive with one clear area the candidate can improve.