Internal interview feedback examples: 18 weak vs strong, by competency
On this page
- What makes internal feedback strong
- Problem solving and judgment
- Communication and collaboration
- Ownership and execution
- Technical and functional depth
- Leadership and people management
- Motivation, working style and learning
- Full write-ups: a hire, a no-hire, and a yes with a named risk
- A write-up structure to copy
- Questions people ask
Internal interview feedback is what an interviewer writes for the hiring team after an interview: a rating for each competency they covered, the evidence behind it, and a recommendation. Strong internal feedback describes what the candidate said or did, ties it to a competency, names what was missing, and makes sense to someone who was not in the room. Weak feedback is a list of adjectives.
Below are 18 weak and strong pairs grouped by competency, three complete write-ups (a hire, a no-hire, and a yes with a named risk), and a structure you can paste into your ATS. Every candidate and detail is invented.
What makes internal feedback strong
Run each line of feedback through four checks before you submit it:
- Observable. It says what the candidate said or did, not what kind of person they are.
- Rated. It names the competency and the score on your agreed scale.
- Honest about gaps. It says what was missing or what the follow-up question did not resolve.
- Readable cold. Someone who was not there understands the context: the question, the numbers, the candidate's role in the story.
The reasoning behind these checks, and how to get from notes to a rating, is the method in evidence-based interview feedback. This page is the examples. The form they go into is the interview scorecard template, which uses a 1–4 scale: 4 strong evidence, 3 meets the bar, 2 below the bar, 1 no evidence or the opposite.
Problem solving and judgment
| Weak | Strong | What changed |
|---|---|---|
| 1. "Very smart, thinks on their feet." | Problem solving: 3. On the pricing case, asked which customer segment was churning before proposing anything, then suggested a two-tier test with one success metric (trial-to-paid conversion). When asked, could not size the revenue effect; said they would need the data. | A sequence of actions, a concrete output, and the gap |
| 2. "Didn't really get the case." | Problem solving: 2. Went straight to "lower the price" without asking about the segment or the cause of churn. When I asked what else could explain the drop, named onboarding but kept the same recommendation. | Describes what they did and did not do, instead of a verdict on intelligence |
| 3. "Good judgment." | Judgment: 4. Turned down a large customer's request for a custom build: estimated it at a quarter of the team's time, took the estimate to their VP, and offered an integration instead. The customer renewed. Named the risk they accepted: "we might have lost them." | A real decision, the trade-off, the result, and the risk they saw |
Communication and collaboration
| Weak | Strong | What changed |
|---|---|---|
| 4. "Great communicator." | Communication: 3. Explained their data pipeline to me, a non-engineer, in about two minutes and checked twice that I was following. On the second question, spent most of the answer on background and needed a prompt to get to the result. | What good looked like, and where it fell short |
| 5. "Seemed a bit arrogant." | Collaboration: 2. Asked about a disagreement with a peer, described the peer as "not technical enough to get it" and said they went to their manager without talking to the peer first. Could not say what the peer's concern had been. | Replaces a personality label with what the candidate said |
| 6. "Would get along well with the team." | Cross-functional work: 3. Runs a weekly review with sales and support; gave an example of moving a release date after support showed ticket volume from the previous launch. The decision was the product lead's; their part was bringing the data. | "Get along" measures similarity; this names a behavior the role needs |
Ownership and execution
| Weak | Strong | What changed |
|---|---|---|
| 7. "Strong ownership." | Ownership: 4. Raised a failure before I asked about one: shipped a billing bug that double-charged some customers, "my code, and I missed it in review." Led the refund process and added the test that would have caught it. | An example the candidate volunteered, with what they did next |
| 8. "Not sure how much they actually did." | Execution: 2. Every example used "we." When asked "what was your part?" on the warehouse rollout, described attending planning meetings and updating the tracker. Could not name a decision they made. | Turns a doubt into the question asked and the answer given |
| 9. "Gets things done." | Execution: 3. Delivered a vendor switch in the planned eight weeks; described the weekly checklist they ran and a data-export slip they caught in week five. No example of a project spanning more than one team. | Scope, method, a problem caught, and the limit of the evidence |
Technical and functional depth
| Weak | Strong | What changed |
|---|---|---|
| 10. "Knows SQL." | SQL: 3. Wrote the retention query in the exercise with a correct join and window function. The date filter dropped users who signed up on the last day; fixed it when I pointed at the row count. | What they produced, the error, and how they responded |
| 11. "Technical depth lacking." | System design: 2. Chose a single database for the event log without asking about write volume. When I gave an example load, said they would "add caching" but could not say where it would sit or what it would solve. | Shows exactly where the depth ran out |
| 12. "Solid accountant." | Month-end close: 4. Walked through shortening their close from nine working days to six: a shared accruals schedule, a hard cutoff for expense reports, weekly bank reconciliations. Named the step that still slows it (intercompany). | Numbers the candidate stated, the changes they made, and what remains |
Leadership and people management
| Weak | Strong | What changed |
|---|---|---|
| 13. "Natural leader." | Managing performance: 3. A direct report was missing deadlines: raised it within a week of noticing, agreed two goals in writing, checked in weekly, and the report improved. Has not yet had to manage someone out. | A sequence of management actions, and the experience not yet shown |
| 14. "Probably too soft to manage." | Managing performance: 2. For the underperformance example, waited "about two quarters" before raising it and described the conversation as "hinting." No written expectations. Said they would act faster now but gave no example of having done so. | Speculation about temperament becomes what they described doing |
| 15. "Good at hiring." | Building a team: 4. Hired six people last year; described the scorecard they wrote with their recruiter, one hire that did not work out, and what they changed afterwards (added a work sample). | Volume, method, a mistake, and the change it led to |
Motivation, working style and learning
| Weak | Strong | What changed |
|---|---|---|
| 16. "Seems passionate." | Motivation for this role: 3. Named two parts of the job description they want more of, "owning the roadmap, not just the backlog," and one they expect to find hard (less hands-on coding). Reason for leaving fits: their team moved to maintenance work. | What they said about this job, not how enthusiastic they sounded |
| 17. "Not a culture fit." | Written communication: 2. The role depends on written updates across time zones. Said they "prefer to jump on a call" for most decisions and could not give an example of a written proposal they had authored. | An unanchored label becomes a named requirement of the job |
| 18. "Fast learner." | Learning: 4. Moved from support to QA with no testing background: took a course, wrote their first test suite in their first quarter, and described the class of bug it caught that support had been escalating. | A before, an after, and the evidence in between |
Two of the weak examples, "seemed a bit arrogant" and "not a culture fit", are more than vague. They are the kind of line that reads badly if interview records are ever reviewed. The full list of what to keep out, with rewrites, is in what not to write in interview notes.
Full write-ups: a hire, a no-hire, and a yes with a named risk
Hire
Candidate: Elena Voss · Role: Senior Financial Analyst · Interviewer: hiring manager, round 2
Recommendation: Yes. Both must-haves at 3 or above with first-hand examples, and the forecasting answer was the most specific I have heard in this search.
- Forecasting (must-have): 4. Rebuilt the quarterly revenue forecast after two misses: split it by product line, added a pipeline-weighted view, and reported variance monthly. Said the next two quarters landed within the range they had given; I did not verify the figures.
- Business partnering (must-have): 3. Meets the sales VP every week; example of pushing back on a hiring plan with a cost model, which was cut from eight roles to five. Her part was the model; the VP made the call.
- Systems: 3. Daily in Excel and their planning tool; built the forecast model herself. No experience with our ERP.
Gaps: no direct experience presenting to a board. For the offer stage: she asked twice about the close calendar; worth covering before she decides.
No-hire
Candidate: Tom Adeyemi · Role: Engineering Manager · Interviewer: round 3, people leadership
Recommendation: No. Managing performance is a must-have for this role and the evidence was below the bar after two separate questions.
- Managing performance (must-have): 2. For the underperformance question, described waiting "about two quarters" and "hinting" before a direct conversation; no written expectations. On the follow-up about a harder case, described handing it to HR.
- Delivery: 3. Ran quarterly planning for a team of seven; clear example of cutting scope to hit a launch date.
- Technical judgment: 4. The migration trade-off answer was one of the strongest in this loop.
What would change my recommendation: a specific example of setting expectations with a report and following through to an outcome. This is not a judgment of his engineering, which was strong.
Yes, with a named risk
Candidate: Rosa Lindqvist · Role: Account Executive, mid-market · Interviewer: round 2, sales process
Recommendation: Yes, if the reference or a pipeline review confirms the attainment numbers.
- Pipeline management (must-have): 3. Walked through her current pipeline by stage without notes; knew conversion from demo to proposal on her own deals.
- Quota attainment (must-have): 3, stated. Said she finished at 112% and 96% of quota over the last two years. Could not say how her quota compared with the team's; this is the risk.
- Discovery: 4. In the role play, asked about budget owner and timeline before pitching, and summarized the buyer's problem back in one sentence.
Risk: attainment is self-reported and quota size is unknown. Suggested check: ask for the numbers in writing or confirm through a reference the candidate provides.
A write-up structure to copy
Paste this into your ATS feedback field or scorecard summary. Fill in the ratings first and the recommendation last.
Recommendation: [Strong yes / Yes / No / Strong no]
Main reason: [one or two sentences that point to the ratings below]
Ratings
- [Competency] ([must-have / nice-to-have]): [1-4 or not assessed]
Evidence: [what they said or did; quotation marks only if exact]
Gap: [what was missing, or "none found"]
- [repeat for each competency you covered]
Must-haves: [met / not met / not assessed, for each]
What would change my recommendation: [a specific piece of evidence]
For the next interviewer or the offer stage: [probe, or an open question]
Not assessed: [competency, and why]Submit it before the debrief and before reading anyone else's. How the write-ups are then compared in the room, and what to do when they disagree, is in the interview debrief template. If Interview Signal ran on the call, each score on the scorecard already carries evidence quotes checked against the transcript, and your job is to read them against the anchors before you submit.
Questions people ask
How long should internal interview feedback be?
Two to four sentences per competency and a short summary; for a one-hour interview, aim for roughly 150 to 300 words. Length is not the goal; every rating needs at least one observation and a reason, and anything beyond that should earn its place.
Is internal feedback the same as the feedback given to the candidate?
No. Internal feedback is written for the hiring team and includes ratings, evidence and concerns. What a candidate hears is shorter, usually delivered by the recruiter, and follows your company's policy on what to share.
When should interviewers submit their feedback?
The same day, ideally within an hour of the interview, and always before the debrief or before reading anyone else's feedback. Details fade quickly, and feedback written after a group discussion tends to echo it.
What should I write if I did not get to one of my questions?
Write 'not assessed' for that competency and say why, for example that the earlier question ran long. Do not rate it from general impression; flag it so another interviewer or a follow-up conversation can cover it.