How to Write Interview Feedback That Is Specific, Not Vague
Good interview feedback names what the candidate said or did, links it to a competency, and states what it means for the role. Fill in your interview feedback form with a quote or example for every score, avoid labels such as great fit, and finish with a recommendation and the reason in one sentence.
Why vague feedback costs you good hires
A debrief runs on the notes people bring to it. If the notes say nice person, strong communicator, not sure about culture fit, the group has nothing to weigh except tone and seniority. The most confident interviewer wins, and the decision follows a feeling that nobody can check. Vague feedback also hurts after the decision. When a candidate asks why they were rejected, you cannot say anything useful. When a new hire struggles, you cannot see which warning signs were in the notes. And when you try to improve your process, there is no data to learn from. The fix is not longer notes. It is notes that point at evidence. A short comment that says she walked through the budget variance step by step and caught the error unprompted is worth more than a page of adjectives. This guide shows what weak and strong comments look like, gives you a sentence frame you can reuse, and walks through an example. If you need the form itself, our page on an /interview-feedback-form has the structure to start from.
What specific feedback contains
Specific feedback has four parts. The first is the observation, which is something the candidate said, did or produced in the interview. The second is the competency it relates to, such as problem solving or ownership. The third is the meaning, a short judgment about whether the observation meets the bar for this role. The fourth is the confidence, which says how sure you are and what you could not test. You do not need all four in every line, but a comment with none of them is noise. Notice what is missing from this list: personality labels, guesses about motivation and comparisons to people you used to work with. Those feel like insight but they come from you, not from the candidate. A good test is to ask whether a colleague who was not in the room could read your comment and see what you saw. If they cannot, it is an opinion, not feedback. Keep opinions in the recommendation line, where they belong, and keep the rest as evidence.
Weak versus strong comments
The table below shows common weak comments next to stronger versions. The examples are illustrative, so adapt the wording to your role.
| Weak comment | Why it fails | Stronger version |
|---|---|---|
| Great communicator | No evidence, and communication means many things | Explained the pricing change in two sentences and checked that I understood before moving on |
| Not a culture fit | Cannot be checked and invites bias | Said she prefers to work alone on tasks; our role needs daily handoffs. Asked about handoffs and gave one example from a past team |
| Seems senior | Based on impression | Led a team of four on the migration, set the priorities and described how she handled a missed deadline |
| Lacks experience | No detail about what is missing | Has not run a budget above the example given. Described forecasting for a single team but not across teams |
| Very confident | Confidence is not skill | Answered quickly but the example did not include a result. Could not say what she would change |
| Good energy | Style, not substance | Asked three follow-up questions about customer segments before answering |
| Not sure about him | Feeling with no reason | Gave a clear plan for week one but could not explain how he would measure success |
Notice that stronger versions are not harsher or kinder. They are just checkable. A reader can disagree with them, and that is exactly what makes them useful in a debrief.
A sentence frame you can reuse
A frame saves time and keeps comments consistent. Use this one for each competency: In [competency], the candidate [did or said something specific]. This [meets, falls below or exceeds] the bar for [reason]. I could not test [gap], so my confidence is [high, medium or low].
Here is the frame filled in. In problem solving, the candidate asked about the data source before suggesting a fix, then proposed checking one customer segment first. This meets the bar because it narrows the question before spending effort. I could not test how she handles a conflicting dataset, so my confidence is medium.
And a second one for a weaker result. In ownership, the candidate described a missed launch and said the vendor was late, but could not name what she changed afterward. This falls below the bar because the example has no learning in it. I did not ask about other projects, so my confidence is low.
Notice that the frame forces a gap statement. That one clause is the most valuable habit you can teach. It tells the group where to probe next, and it stops a single interview from being treated as complete evidence.
Write it close to the interview, in this order
Timing and order change the quality of feedback. Write your notes within a few hours, while the conversation is fresh, and before you speak to anyone else about the candidate. Once you have heard a colleague call someone brilliant, your own memory shifts toward that view, and you will not notice it happening. During the interview, take short notes of facts and quotes only. Right after, convert them into scores and comments using the frame above. Score each competency first, then write the recommendation last, because recommendations written first tend to pull the scores up or down to match. Keep it to ten minutes. If you cannot write a specific comment for a competency, say so plainly, for example I did not cover this. A blank is more honest than a guess, and the group can fill the gap in a later round. Finally, read your comments once as if you were the candidate. If anything would embarrass you if read aloud, it probably does not belong, and it may be a sign of bias you want to look at.
A worked example
Here is a short, invented example for a marketing manager role. The interviewer used the form with three competencies and a recommendation.
| Competency | Score | Comment |
|---|---|---|
| Campaign planning | 4 | Described a launch for a product with a small budget. Chose two channels and explained why, using last quarter's data. Could name what she would drop if the budget fell by half |
| Analytics | 3 | Reads results well but relied on the team for attribution. Did not mention how she checks that numbers are right. I did not test spreadsheets in depth, confidence medium |
| Ownership | 2 | The example about a missed deadline blamed an agency and had no change afterward. I would test this again in a second round |
| Recommendation | Yes, with a follow-up | Strong planning and a clear ability to explain choices. Ownership is the concern and should be probed |
A reader who was not in the room can follow this. They know what the candidate did, where the evidence is thin and what to ask next. Compare that with the weak version, which would say strong marketer, good ideas, some concerns about ownership. The same facts, but nothing to act on.
Common mistakes to avoid
These are the patterns that turn feedback into noise, with a quick fix for each.
| Mistake | What it looks like | Fix |
|---|---|---|
| Labels instead of evidence | Smart, polished, sharp | Replace with what they said or did |
| Comparing to a person | Reminds me of our old lead | Compare to the written bar instead |
| Mind reading | I think she wants to leave in a year | Ask the question in the interview, or leave it out |
| Judging style | Too quiet, too loud | Score the answer, not the delivery |
| Skipping the gap | Treating one hour as full proof | State what you could not test |
| Writing after the debrief | Copying the group view | Submit before discussion |
| Burying the recommendation | A long story with no verdict | End with yes or no and one reason |
One more mistake deserves care: mentioning protected characteristics such as age, family plans, health, religion or origin. Do not record guesses about them. Rules about what you can ask and record differ by country, so check local law.
A checklist for reviewing feedback before the debrief
If you are the recruiter or hiring manager, check each submitted form against this list. It takes a minute per form and saves a long argument later.
| Check | Question | Pass? |
|---|---|---|
| Evidence | Does every score have a quote or example? | |
| Competency link | Is each comment tied to a listed competency? | |
| Gaps | Does the writer say what they could not test? | |
| Independence | Was it written before the debrief? | |
| Neutral language | Is it free of personality labels and guesses? | |
| Recommendation | Is there a clear verdict and one reason? | |
| Detail balance | Is it long enough to be useful and short enough to read? |
Send forms that fail back with a specific question, such as What did she say that made you give a 4? Most interviewers improve quickly once they see that vague comments get asked about. Over a few rounds the quality of the whole team rises without any training session.
Who this approach is not for
Writing detailed feedback is not worth the effort in every case. For a very informal chat, such as a coffee conversation with a possible future candidate, a form is overkill, and a two-line note is enough. It is also not a fix for a poor interview. If the questions were random or the interviewer did all the talking, there will be nothing specific to record, and the answer is better questions, not better notes. And it should not be used to build a case against a candidate you already decided to reject. Feedback should come from the conversation, not the other way round. Finally, be careful where the law treats interview notes as records candidates can request. Rules differ by country, so check local law before you decide what to store and for how long, and keep comments you would be happy to see read back.
Where Rezumz fits
Rezumz is an AI hiring workspace for small and mid-size hiring teams. For feedback, it lets you add interview rounds to a candidate, such as HR screen, Tech round or Final, with one or more interviewers per round. Each interviewer gets a private link by email and confirms a one-time code before opening a short, factual brief of the candidate and the form: scored points, an overall recommendation of strong yes, yes, no or strong no, and a summary comment, with the option to add a transcript. Submitted feedback is locked. If an interviewer changes their mind, they submit a new version and say why, and you can see every version. Rezumz flags feedback that looks copied between interviewers, and once two or more candidates have feedback it can rank them from the written evidence with names hidden, showing its reasons. People make the decision. It suits small and mid-size teams, with the Team plan for 4 or more recruiters. It does not suit large enterprises needing deep HRIS or payroll connections, and it does not do one-click multiposting to job boards. Prices: a free plan with 2 free candidate analyses, $29 a month, $199 a year, or a limited $499 lifetime option. Team is $79 a month or $699 a year for up to 10 teammates. See /pricing and try it in the live demo at /demo.
Frequently asked questions
How long should interview feedback be?
Long enough to carry evidence, short enough to be read. A good form has one or two sentences per competency, each with an example or quote, and a final recommendation with one reason. Ten minutes is usually enough. If feedback runs to a page, the writer is usually retelling the interview instead of judging it.
What is a good sentence frame for interview feedback?
Try this: in the competency, the candidate did or said something specific, which meets, falls below or exceeds the bar for a stated reason, and I could not test a named gap, so my confidence is high, medium or low. It forces evidence and an honest statement of what was not covered.
Should interviewers see each other's feedback before submitting?
No. Ask each interviewer to submit before the debrief so early opinions do not pull everyone along. Compare forms together afterward. Independent scoring is one of the simplest ways to get more honest results, and it costs nothing. It also makes disagreements visible, which is where the best discussion starts.
Can feedback be changed after it is submitted?
That depends on your process. A good practice is to keep the original and add a new version with the reason for the change, so the record shows how thinking moved. In Rezumz, submitted feedback is locked and changes are saved as new versions that must include a reason.
How do I avoid bias in interview comments?
Stick to what the candidate said or did, tie it to a listed competency, and leave out guesses about age, family, health, origin or personality. Compare to the written bar, not to people you know. Rules on what you may record differ by country, so check local law.