Positive interview feedback is more useful when it explains why a strength matters for the role. I try not to write only “great candidate” or “I liked them.” Those comments may express enthusiasm, but they do not help the hiring team compare evidence or decide what to test next.
A simple structure for positive feedback
I use this pattern:
- Strength: What capability did the candidate demonstrate?
- Evidence: What specific answer, example, or exercise showed it?
- Role connection: Why does that capability matter here?
- Recommendation: What should the team do next?
For example: “The candidate showed strong stakeholder management by describing how they reset a missed launch expectation with a customer and internal product team. That judgment is relevant because this role handles changing priorities. Recommend advancing.”
The evidence should come from the interview, not assumptions based on a resume, school, employer, or communication style. If the candidate has not demonstrated a required competency, I mark it as untested rather than filling the gap with optimism.
Positive feedback examples by competency
Ownership
“The candidate took responsibility for a delayed project, explained the decisions that led to the delay, and described the changes they made afterward. This shows the ownership and learning mindset expected from the role.”
Problem solving
“The candidate clarified the problem before proposing a solution. They separated urgent symptoms from the underlying cause and described how they would validate the result. This approach fits the role's need for structured troubleshooting.”
Communication
“The candidate explained a technical tradeoff in terms a nontechnical partner could use. They checked for questions and adjusted the explanation when the audience needed more context. That is strong evidence for the role's cross-functional communication requirement.”
Collaboration
“The candidate described a disagreement with a teammate without assigning blame. They explained how the group compared options, made a decision, and maintained the working relationship. This supports the collaboration competency.”
Customer judgment
“The candidate balanced the customer's immediate request with the longer-term product impact. They explained when they would say no, what alternative they would offer, and how they would communicate the decision.”
Recommendation templates
Strong advance:
“The candidate provided clear evidence across [competencies]. Their experience with [relevant work] directly matches the main requirements for [role]. I recommend moving them to [next stage]. I would use the next interview to confirm [remaining question].”
Advance with a question to test:
“The candidate demonstrated [strength] through [evidence]. I recommend advancing, with the next stage focused on [specific area] because the current interview did not give us enough evidence there.”
Positive but not enough evidence yet:
“I had a positive conversation with the candidate and saw promising evidence of [strength]. I did not assess [required competency] in enough depth to make a recommendation. A follow-up focused on [area] would help us make a consistent decision.”
Keep enthusiasm disciplined
I separate confidence from likability. A warm conversation can be a good experience without proving the candidate can perform the work. I also avoid phrases such as “perfect fit,” “would get along with everyone,” or “more polished than the others.” They are vague and can introduce bias.
My final check is simple: could another interviewer understand the recommendation without being in the room? If the answer is no, I add the missing evidence, competency, or role connection before submitting the feedback.