What Good Interview Feedback Looks Like
Good interview feedback is specific, evidence-based, and job-related. Interview feedback examples for hiring managers typically share three traits: they quote or paraphrase what the candidate actually said, they connect that evidence to a job requirement, and they avoid personal opinions or protected-characteristic references. Vague notes like "not a culture fit" are the opposite of useful feedback.
Interview feedback is the written evaluation an interviewer produces after meeting a candidate, summarizing what the candidate demonstrated against the role's requirements. It exists to help the hiring team compare candidates on evidence rather than impressions, and to create a defensible record of why each decision was made. When feedback is written well, debriefs take minutes instead of hours, and the team can explain any decision if it is ever questioned.
Think of your notes as a mini evidence file. Every claim should trace back to something the candidate said or did in the interview. If you cannot point to a moment, a project, or an answer that supports your judgment, the judgment does not belong in the write-up.
What Should Interview Feedback Include?
A complete candidate evaluation write up covers five elements:the competency assessedinterviewer. A useful structure looks like this:
- Competency: which skill or requirement you were probing.
- Evidence: what the candidate actually said or did.
- Assessment: how that evidence compares to the bar for the role.
- Recommendation: hire, no hire, or lean either way.
- Follow-up: a question the next interviewer should ask.
This structure keeps constructive interviewer notes anchored to the job. It also makes life easier when you are juggling five candidates in one week and cannot rely on memory alone.
Why Evidence-Based Feedback Protects Your Company
Evidence-based feedback is not just good practice; it is a legal safeguard. Hiring decisions can be challenged, and the written record is often the only documentation that exists. Notes that reference personality traits"fit" concerns create risk, while notes that document job-related evidence create protection. The EEOC's guidance on interview selection makes clear that all selection criteria must be job-related and consistent across candidates. If your notes could not be read aloud in front of a judge without embarrassment, rewrite them.
Example Feedback for a Strong Candidate
Here is a filled-in example of interview evaluation comments for a strong candidate applying for a senior marketing manager role. Notice how every claim is tied to something specific the candidate said, and how the recommendation is justified rather than asserted.
Competency assessed: Campaign ownership and cross-functional leadership.
Evidence: Candidate walked through a Q4 product launch end to end: owned the messaging brief, coordinated design and paid channels, and reported results weekly to the VP. When asked about a failure, she described a campaign that missed its lead target, diagnosed the cause (wrong audience segment), and described the fix she shipped the following quarter.
Assessment: Exceeds the bar. She demonstrated structured thinking, ownership of outcomes rather than tasks, and comfort with numbers. Her explanation of the failed campaign showed low defensiveness and high learning velocity.
Recommendation: Strong hire. I would move her to the final round.
Follow-up: Probe her experience managing external agencies; we did not cover that.
This example works because a reader who was not in the room can still evaluate the reasoning. That is the test for every piece of feedback you write: could a colleague act on this note without asking you a single clarifying question?
How to Write Feedback That Champions a Candidate Without Overselling
Even for a candidate you love, resist the urge to write pure praise. Strong feedback after interviews still documents gaps and open questions, because the next interviewer needs a complete picture. Oversold feedback also weakens your credibility in the debrief; panels discount reviewers who rate everyone a ten. Keep the same evidence-based format for every candidate, favorable or not, and let the evidence carry the enthusiasm.
Example Feedback for a Weak Candidate
Writing feedback about a weak candidate is where most hiring managers get into trouble. The goal is a factual, respectful candidate evaluation write up that explains the no-hire decision in job-related terms. Here is an example for the same senior marketing manager role.
Competency assessed: Analytical rigor and budget management.
Evidence: When asked how he measured campaign success, he listed metrics (impressions, clicks) but could not explain how he calculated return on ad spend or how he allocated budget across channels. Asked about a time a campaign underperformed, he attributed it to the market and did not describe any analysis or corrective action.
Assessment: Below the bar for a senior role. The role requires independent budget ownership and the ability to defend spend decisions with data; his answers suggested he relied on others for analysis.
Recommendation: No hire for this role. He presented well and communicated clearly, which may suit roles with less analytical demand.
Follow-up: None needed; competency gap is central to the role.
Notice what this note does not do. It does not speculate about the candidate's personality, age, or energy level. It does not use words like "unimpressive" or "not sharp." It documents what was asked, what was answered, and why the answer fell short of the stated requirement. That is legally safe feedback.
Should You Share Feedback With Rejected Candidates?
Sharing interview feedback with rejected candidates is optional and situational. The written notes you keep internally should always be professional and factual, in part because candidates in some jurisdictions can request access to their records, and in the EU and UK, GDPR-style data rules give candidates rights over data held about them. Keep internal notes as if the candidate might one day read them, because in some places they legally can.
Example Feedback for a Borderline Candidate
Borderline candidates produce the least useful feedback in most organizations, because interviewers default to hedged language like "mixed signals" or "hard to read." Good interview feedback examples for hiring managers in this scenario pick a side on each competency individually, then let the overall recommendation reflect the pattern. Here is an example.
Competency assessed: Stakeholder management and technical depth (product manager role).
Evidence: Strong on stakeholder management: described mediating a dispute between engineering and sales over a delayed feature, with a concrete process for aligning priorities. Weaker on technical depth: could not describe how she would evaluate trade-offs on API rate limiting, and her answers on prioritization frameworks were generic.
Assessment: Split. Stakeholder skills clearly exceed the bar; technical depth is uncertain, possibly because she has worked with strong technical partners who filled that gap.
Recommendation: Lean hire, contingent on a focused technical interview.
Follow-up: Next interviewer should test technical judgment directly with a scenario-based question, not a knowledge quiz.
The value of this format is precision. "Lean hire, contingent on X" is actionable; "mixed" is not. When every interviewer on a panel writes this way, the debrief becomes a short conversation about the one or two genuinely contested competencies instead of a re-litigation of the whole interview.
How to Handle Disagreement Between Interviewers
When interviewers disagree about a borderline candidate, resolve it with evidence, not seniority. In the debrief, have each reviewer state their rating and the single strongest piece of evidence behind it. If the disagreement is about the same competency, one of you likely probed it more deeply; weight that observation. If the disagreement is about different competencies, check the role's actual priorities, which should be defined before interviews begin, not negotiated afterward.
Words and Phrases to Avoid in Feedback
Certain words in interview feedback create legal risk, signal bias, or simply convey no information. The problem with phrases like "not a culture fit" is that they are unfalsifiable and can mask bias; interviewers should replace them with descriptions of specific behaviors measured against specific role requirements. Here are common offenders and what to write instead.
| Avoid | Why | Write instead |
|---|---|---|
| "Not a culture fit" | Unfalsifiable; can mask bias | "Did not show evidence of X behavior the role requires" |
| "Too junior / too senior" | Can read as age-based | "Has led teams of Y size; role requires Z" |
| "Wouldn't fit in with the team" | Vague, personality-based | "Working style example vs. role's collaboration demands" |
| "Low energy" | Subjective, disability-adjacent risk | "Gave short answers; could not elaborate on examples" |
| "Not confident enough" | Gendered and cultural bias risk | "Did not provide evidence for claims when probed" |
| "Poor communication" | Too vague to act on | "Struggled to structure answers; see note on Q3" |
A simple rule: never write anything about a candidate that references a protected characteristic, a physical impression, or a personality judgment detached from behavior. Everything else is fair game if it is tied to evidence.
Turning Feedback Into a Structured Debrief
A hiring debrief is a short, structured meeting where interviewers share evaluations and reach a decision. The debrief fails when it becomes an unstructured opinion exchange; it succeeds when the feedback notes do most of the work beforehand. If everyone submits written notes before the meeting, the discussion can focus only on disagreements and open questions.
A Hiring Debrief Template You Can Use Today
Here is a step-by-step hiring debrief template that keeps the meeting under 30 minutes:
- Before the meeting: every interviewer submits written feedback within 24 hours of the interview.
- Open (2 min): the hiring manager restates the role's top three requirements.
- Ratings round (5 min): each interviewer states hire / no hire / lean and their single strongest piece of evidence.
- Contested competencies (15 min): discuss only the competencies where ratings diverge.
- Decision (5 min): hiring manager decides and states the rationale aloud.
- Documentation (3 min): the hiring manager records the decision and rationale in the hiring system.
This sequence prevents the two classic debrief failures: the loudest voice winning, and the panel re-debating an interview nobody remembers clearly. The written record created in step six is also what protects the company if the decision is later questioned.
How to Write Interview Feedback Faster Without Cutting Quality
How to write interview feedback efficiently comes down to preparation, not speed-typing. Define your competencies and question set before interviews begin, take short verbatim notes during the conversation, and write the full evaluation within a few hours while details are fresh. Interviewers who batch feedback three days later consistently produce vaguer notes, because memory degrades quickly and impressions fill the gaps where evidence used to be. Fifteen focused minutes right after the interview beats an hour of reconstruction later.
Frequently Asked Questions
What should interview feedback include?
Interview feedback should include the competency assessed, the specific evidence you observed, your assessment against the role's bar, a clear recommendation, and any follow-up question for the next interviewer. Every claim should trace back to something the candidate actually said or did.
How long should interview feedback be?
Aim for 100 to 200 words per competency, or roughly half a page for a typical hour-long interview. Long enough to include evidence and reasoning, short enough that the panel will actually read it before the debrief.
Is it legal to keep notes on interview candidates?
Yes, keeping interview notes is legal and standard practice characteristics or personality judgments. In some jurisdictions candidates can request access to records held about them, so write notes as if the candidate may read them.
What do you write for a candidate with no red flags but no strengths?
Document the competencies where answers were adequate but unremarkable, note the absence of standout evidence, and recommend either a targeted follow-up interview or a no-hire with a factual rationale. "Fine but not differentiated" is a legitimate, defensible conclusion when stated with evidence.
Should interview feedback be shared with the candidate?
Generally no in the US, where companies typically share only a brief decision; in the UK and EU, candidates may have rights to access data held about them. Keep internal notes professional and factual regardless, and route any candidate-facing feedback through your HR or legal team.
Conclusion
Useful interview feedback is a skill, not a personality trait, and it improves fast once you adopt a consistent evidence-based format. Copy the three examples above, strip the risky phrases from your vocabulary, and run your next debrief with the template provided. If you are hiring through the GoWithFund Hiring & Jobs board, you can keep your interview rubricsructured, fair evaluation. Post your next role and try the workflow end to end.







