Interview Feedback Examples a Hiring Manager Can Act On

In August an internal alarm told us that about 15% of the quotes our AI was putting into its rejection notes were fabricated. If true, it meant hiring managers were reading feedback that said “the candidate said X” when the candidate had said no such thing.

It was not true. The checker behind the alarm had been comparing each quote with only the candidate’s last ten messages, roughly 20 seconds of speech. Checked against the full transcripts, 163 of the 166 quotes were really there. One was not, and that candidate’s rejection now goes to a human for review instead.

I tell that story because it is the whole point of interview feedback. A hiring manager acts on what you write. If the evidence behind it is not real, or not there at all, the feedback is just an opinion with a confident tone. The examples below are built the other way round.

What is interview feedback?

Interview feedback is the written record of what an interviewer saw and what they recommend. Good feedback leads with a decision (hire, hold or no hire), backs it with evidence from the interview tied to the job’s requirements, names the one thing that could make the decision wrong, and says what should happen next.

There are two audiences, and they need different documents. The hiring manager needs enough to decide. The candidate needs a short, fair reason. Most of this post is about the first. The section on candidates comes near the end.

What good interview feedback contains

The notes that actually help a hiring manager decide have five parts:

1. The decision, first. “Hire”, “Hold” or “No hire” in the first line. A hiring manager reading twenty notes between meetings should not have to reach the last paragraph to find out which way you lean.
2. The criterion. Which requirement of the role is this evidence about? “Communication” is too broad; “explains a technical problem to a non-technical customer” is a criterion.
3. The evidence. What the candidate said or did, close to their own words. A quote, a number they gave, a step they described. This is the part that makes feedback checkable.
4. The risk. The one thing that would change your mind, or that the next interviewer should probe. Strong feedback admits uncertainty instead of hiding it.
5. The next step. Who does what next: a second round focused on a gap, a reference check, an offer conversation, or a rejection email.

If a note is missing the evidence, the other four parts cannot carry it.

Interview feedback examples: vague vs usable

The fastest way to improve feedback is to see the same note written twice. Each pair below is the same judgment; only the second one helps a hiring manager decide.

Communication

• Vague: “Great communicator, very articulate.”
• Usable: “Explained why the billing migration failed in two minutes, in plain language, without being prompted for structure. Criterion met: explains technical issues to customers.”

Technical depth

• Vague: “Strong technical skills.”
• Usable: “Walked through how they would index the orders table and why a composite index beats two single ones for our query pattern. Missed caching entirely; worth probing in round two.”

Ownership

• Vague: “Shows ownership.”
• Usable: “Described finding the reconciliation error themselves, telling their manager the same day, and writing the fix. Named the first step without hesitation.”

Problem solving

• Vague: “Good problem solver.”
• Usable: “Given the scheduling case, asked two clarifying questions before answering, then proposed a plan with a fallback. Did not ask about cost, which matters in this role.”

Motivation

• Vague: “Seems very motivated.”
• Usable: “Could name three things about our product and why they want to work on support tooling specifically. Has applied for similar roles at two competitors, which they volunteered.”

A concern

• Vague: “Not sure about this one.”
• Usable: “Every answer described team results; when asked for their own part, gave the same answer twice. Hold: needs one more conversation focused on individual contribution.”

Seniority mismatch

• Vague: “Overqualified.”
• Usable: “Eight years of team leadership against a role with no reports. Said they want to return to hands-on work, but expects a salary above the band. Risk is retention, not ability.”

A rejection

• Vague: “Not a fit.”
• Usable: “No Hire. The role requires SQL daily; candidate could not write a basic join when asked and said they have not used SQL since college. Everything else was solid.”

Notice what the usable versions have in common: a criterion, something the candidate actually said, and a clear direction. None of them needs adjectives. If you want the questions that produce answers like these, our list of interview questions to ask candidates gives each one a follow-up.

Templates for each decision

Copy these into your ATS or a shared doc. Keep each to five or six lines.

Strong hire

• Decision: Strong hire.
• Evidence: [two criteria, each with what they said or did].
• Risk: [the one thing to confirm, or “none found”].
• Next: [offer conversation, references, or final round with whom].

Hold

• Decision: Hold.
• Met: [criteria with evidence].
• Unclear: [the specific gap, and why the interview could not settle it].
• Next: [one focused conversation or a work sample, by whom, by when].

No hire

• Decision: No hire.
• Reason: [the requirement not met, with the evidence].
• Also observed: [anything positive worth keeping for future roles].
• Next: [rejection email; consider for (other role) if relevant].

Split panel

• Votes: [two hire, one no hire].
• Where we agree: [criteria everyone saw met].
• Where we differ: [the specific criterion, and what each person saw].
• Next: [the hiring manager decides, or one tie-break question].

The split-panel template matters most. Disagreement is useful when it is about a specific criterion and a specific answer. It is useless when it is “I just didn’t get a good feeling”, because nobody can check a feeling.

How to give interview feedback to a hiring manager

A few habits make the same feedback land better:

• Send it the same day. Specific answers fade within hours. Late feedback drifts toward a general impression, which is where bias lives.
• Lead with the decision, then the evidence. Hiring managers skim. Put the verdict where they will see it.
• Score against the role, not against the last candidate. Comparing candidates is the hiring manager’s job; yours is to say whether this person meets the bar the role set. A shared structured scoring rubric keeps everyone measuring the same thing, which is also what the US Office of Personnel Management recommends for structured interviews: rate each answer against a written standard.
• Attach the evidence, not just your summary. If the interview was recorded or transcribed, point to the moment. “Minute 7, the billing question” lets a busy manager check you in thirty seconds.
• Separate what you saw from what you guess. “Did not mention testing” is an observation. “Probably doesn’t test” is a guess, and should be labeled as one or left out.

When a hiring manager disagrees with your recommendation, the evidence is what makes the conversation short. You are no longer arguing about impressions; you are both looking at the same answer.

Interview feedback for candidates

Many candidates never hear why they were turned down, and the ones who reached a late round remember whether they did. A short, honest note costs little and protects your employer brand.

Keep it to one or two job-related points they can act on:

• “We moved forward with candidates who had more hands-on experience with data pipelines in production. Your project work was strong; production experience would make you competitive for a role like this next time.”
• “The role needs daily client calls in English. Your answers were well organized, and more practice explaining technical detail aloud would help.”
• “We were impressed by your portfolio, but this role needs someone who can start leading a team now. We would like to keep you in mind for senior individual roles.”

What not to share: panel debate, scores, comparisons with other candidates, or anything you would not want quoted back to you.

That last point is not only courtesy. In the US, the EEOC requires employers to keep personnel and employment records for one year, and longer if a charge is filed. Interview notes are part of that record. Write every line as if the candidate might read it, and keep out anything about age, family plans, religion, health, accent or appearance. “Not a culture fit” is the phrase to retire first: it says nothing about the job, and it reads badly in a file.

How we write feedback for the first round

Most of what HireQwik does is first-round screening, and the output of a first round is feedback: a verdict and the reasons for it. We built it to follow the five parts above.

After a HireQwik AI interview, the evaluation scores each question against the role’s rubric and quotes the candidate’s answers as evidence. When a candidate fails a knock-out question, the rejection reason carries their words. And because of the alarm in August, every knock-out quote is checked against the candidate’s full transcript; if a quote cannot be found, the verdict becomes On Hold with a note telling the recruiter to review the call, rather than a rejection nobody can verify.

Hiring managers do not need an account to read it. A recruiter can share the scorecard as a link that opens the verdict, the scores, the notes and the transcript on a phone, and can revoke it later.

The last part is the one most teams skip: finding out whether the feedback was right. When a recruiter records the real outcome (hired, offered, not selected or withdrew), HireQwik compares it with the verdict for each role in a “Screener vs reality” view. The most important number on it is the candidate the screen rejected and the team hired anyway. That is the feedback on your feedback, and it is the only way the rubric gets better.

If you are setting up that first round, start with our guide to pre-screening interview questions, then write the feedback template before the first interview, not after the fifth.