Why does the same interview feedback matter more than a single comment?
Feedback after an interview is scarce, so two matching comments carry real weight. In Talent Board's 2023 research, only 17% of participating North American employers said hiring managers give approved, detailed feedback to external finalists who weren't selected (Talent Board). Most people get none.
A single comment can reflect one interviewer's taste or one awkward day. The same comment from two companies, scored by different people with different questions, is much harder to explain away. It usually points at a habit in how you answer, which is good news, because habits can be changed before the next round.
This page is about reading feedback across several interviews. If you only have one rejection to work through, start with why people are rejected after a final round instead.
Why would different companies give you the same feedback?
Many companies score interviews in similar ways, so the same weak spot shows up in the same place. Google says it uses the same questions for candidates applying for the same job and grades answers on an identical scale, with rubrics that define outstanding, solid, borderline and poor responses (Google re:Work).
The US Office of Personnel Management describes the same approach for structured interviews. Questions come from job analysis, answers are scored against proficiency benchmarks, and a panel usually rates each answer separately before discussing big differences (OPM).
When two employers use benchmarks like these, an answer with no result or no clear role for you scores low at both. The feedback sounds alike because the scoring was alike. The guide to how interview scorecards work explains what interviewers write down.
What does common interview feedback usually mean?
Feedback phrases are short and polite, so they need translating. Most of them point at one of a few gaps an interviewer could see: missing evidence, unclear ownership, answers that ran long, or a background that didn't match the level. The table below gives a likely reading and the place in your notes to check.
| Feedback you heard | What it often points to | Where to check in your notes | First fix to try |
|---|---|---|---|
| "We wanted more depth" or "more detail" | Answers stopped at the task and skipped the result | Answers with no number or outcome | Add one measurable result per story |
| "We weren't sure about your role" | "We" where "I" belonged | Every story told in the plural | Say what you did, in the first person |
| "Strong, but another candidate had more experience" | Level or background mismatch | The years and scope you described | Lead with your largest comparable project |
| "Communication could be clearer" | Long or drifting answers | Answers longer than about two minutes | Put the result in the first two sentences |
| "Not quite the right fit" | Unclear; often a polite catch-all | Little to check | Ask one follow-up question |
| "Needed stronger technical answers" | A gap in a skill the role requires | The questions you couldn't finish | Practice that topic before the next round |
The table is a starting point for your own check. A phrase can mean different things at different companies, and the only way to confirm a reading is to find the matching moment in your notes. "Fit" is the hardest one, and Google's guide itself warns interviewers against relying on vague cultural fit.
How do you find a pattern across several interviews?
Put your last three to five interviews side by side and mark the weakest answer in each. Write the question, what you said in one line, and what happened next, such as a follow-up, a quick change of topic, or a flat reply. Then look for the same kind of moment appearing at least twice.
You need notes for this to work. If you didn't write anything down at the time, rebuild what you can and leave gaps where the memory is gone. The post-interview notes template shows the format, and the free 10-minute debrief template gives you a printable page for each future interview.
Use a simple log with five columns: company, round, the weak question, why it was weak, and any feedback you received. Fill one row per interview. After three rows, read down the "why it was weak" column. A pattern usually shows up as the same reason written in slightly different words.
Here is an example of a filled-in log for three interviews:
- Company A, round 2: "Tell me about a hard deadline." Weak because the story ended with "it went fine." Feedback: "wanted more depth."
- Company B, round 1: "A project you led." Weak because the result had no number. No feedback given.
- Company C, round 3: "A time you disagreed with your manager." Weak because I never said what changed afterward. Feedback: "strong, but more detail would help."
In that example, three different questions failed in the same way. Every story stopped before the result.
How do you tell a real pattern from coincidence?
A real pattern repeats across different questions, different interviewers and different companies. If the weak moment always comes from one story, the story is the problem. If it comes from many stories, the habit is the problem. Two matches is a signal, and three is a pattern you should act on.
Be careful with feedback that only describes the result, such as "we went with someone else." It tells you nothing about your answers. Also be careful with a pattern that matches what you already feared. Check it against the notes before you accept it, so you fix the habit the evidence supports.
Feedback you asked for usually beats feedback that arrived unprompted, since you could ask a specific question. The guide to asking for feedback after a rejection shows how to ask for one concrete thing.
What should you fix first once you see a pattern?
Fix the habit behind the most repeated weak moment, and fix it in one story first. Rebuild that answer so it has a clear role for you, a number in the result, and a length under two minutes. Then apply the same change to your other stories, since the pattern means the habit will show up again.
Debriefing yourself this way has evidence behind it. A 2013 meta-analysis of 46 samples found that debriefs improved performance by about 25% on average over control groups, with similar effects for individuals and teams (Tannenbaum and Cerasoli). Reviewing across interviews is the same habit, run over a longer period.
Specific fixes have their own guides. The STAR method guide shows where the result goes. If your answers run long, see how to shorten an answer that drifted. If your figures changed between companies or rounds, check whether your story changed.
What if your interviews keep failing at the same stage?
Look at the stage as part of the pattern. Failing at the phone screen points to basics such as pay, requirements and your summary. Failing after the hiring manager round points to depth and ownership in your examples. Failing at the final round points to comparison with other finalists, where evidence and consistency matter most.
Each stage has its own guide. See rejected after a phone screen, rejected after the hiring manager round and why you keep getting rejected after interviews.
If you recorded your interviews with everyone's consent, Prept can debrief each one after the call, quoting the moment you lost the room and the words to say instead. Reading several debriefs side by side makes a repeated weak spot easier to see. The first interview hour is free with no card.