Chapter 8: Common Candidate Mistakes and How to Fix Them

Why this matters

Most behavioral interview failures aren't caused by a candidate lacking good experiences to draw on — they're caused by a small, recurring set of delivery mistakes that obscure genuinely good material. This chapter catalogs the most common ones precisely, each with a concrete fix, because naming a mistake exactly is the first step to noticing yourself making it in real time.

Mistake 1: Rambling

[BEGINNER] Already covered mechanically in Chapter 6 — rambling is answering without a clear internal structure, resulting in a long, hard-to-follow account with no clear signal about what mattered. The fix: internalize STAR's beats (Chapter 2) firmly enough that you can silently check off "have I covered Situation, Task, Action, Result" as you speak, catching yourself if you're still elaborating Situation after 20-30 seconds.

Mistake 2: Hiding behind "we" instead of "I"

[SENIOR INSIGHT] This is one of the most common, most damaging, and most fixable mistakes in behavioral interviewing. A candidate describing a team accomplishment entirely in "we" language ("we decided," "we built," "we figured it out") gives the interviewer no way to isolate the candidate's own individual contribution — which is specifically what the interview is trying to assess. This isn't about claiming excessive credit or erasing teammates; it's about precision: a strong answer uses "we" for genuinely collective actions and switches deliberately to "I" for the specific things the candidate personally did, thought, or decided.

Weak (all "we"): "We noticed the deployment process was slow, so we
                  looked into it, and we found a bottleneck in the
                  build step, and we fixed it, and now deploys are faster."
                  -- the interviewer has NO idea what THIS candidate
                     specifically contributed versus anyone else on the team.

Strong (precise "I" and "we"): "Our team noticed deployments were
                  getting slower [WE -- genuinely collective observation].
                  I volunteered to investigate and found the bottleneck
                  was in our build step's dependency resolution [I --
                  specific, individual action]. I proposed caching the
                  dependency layer and implemented it [I]. After I
                  rolled it out, the team's average deploy time dropped
                  from 12 minutes to 4 [result, tied back to the
                  individual's specific action]."

[INTERVIEWER'S VIEW] An interviewer hearing persistent "we" language will often explicitly probe for the individual contribution ("what did you specifically do?") — candidates should treat this follow-up as an expected, fair, and fixable moment, not a sign the story itself was weak; simply switching to specific "I" language in the follow-up response usually resolves it completely.

Mistake 3: Vague or unmeasured results

[BEGINNER] Already introduced in Chapters 1 and 2 — a result like "it went well" or "the team was happy" provides no verifiable evidence the effort mattered. The fix: for every story in your bank, force yourself to write down an actual number, percentage, timeframe, or specific, concrete outcome — if you genuinely can't find one, consider whether a different story in your bank has a more demonstrable result, even if this one intuitively feels more impressive.

Vague: "The new process really helped the team."
Specific: "Onboarding time dropped from two weeks to five days, and
           we had zero reported quality issues from new hires in the
           following two quarters, compared to three the prior year."

Mistake 4: Badmouthing past employers or colleagues

[SENIOR INSIGHT] Even when a candidate's criticism of a past employer or colleague is completely accurate and justified, voicing it in an interview creates a specific, negative inference that has nothing to do with whether the criticism was fair: the interviewer has no way to verify your account, and hearing sharp criticism of an absent third party makes them wonder how you'll describe them, similarly, in a future interview after you've left this company. This is true regardless of how legitimate the underlying grievance actually was — the interview is evaluating your judgment about what and how to share, not adjudicating the merits of the original dispute.

Risky: "My manager was honestly pretty incompetent and didn't understand
        the technical trade-offs, so I had to basically work around him
        the whole time."

Safer, equally honest about the substance: "My manager and I had
different views on the right technical approach for a key decision.
I made sure to document my reasoning clearly and proposed we pilot a
small version of my approach to test it empirically, which we did,
and it validated my concern -- we adjusted course based on the data."

Notice the safer version conveys the same underlying reality (a disagreement, a manager who wasn't initially persuaded) without editorializing about the manager's competence — it reports behavior and outcomes, not character judgments about an absent third party.

Mistake 5: Sounding overly scripted

[BEGINNER] Already covered in depth in Chapter 7 — the fix is rehearsing the skeleton, not the script, and practicing with real mock-interview follow-ups rather than a fixed, one-shot recitation.

Common mistakes (a meta-list, since this whole chapter is about mistakes)

1. Assuming these five mistakes are independent — in practice, they compound: a rambling answer (Mistake 1) often also hides individual contribution in "we" language (Mistake 2) simply because there's no clear structure forcing the candidate to isolate their own specific actions.
2. Fixing the symptom instead of the underlying habit — e.g., consciously trying to say "I" more without actually identifying which specific actions were genuinely individual, producing an artificial, uncomfortable-sounding overcorrection.
3. Not noticing these patterns in your own speech without external feedback — this is exactly why Chapter 7's mock-interview practice matters: these mistakes are often invisible to the person making them until a listener points them out.
4. Treating a single instance of badmouthing as harmless if the criticism feels justified — even one moment of sharp, personal criticism of an absent third party can color an interviewer's overall impression disproportionately to its brief duration.

Checklist: catching and fixing these mistakes

1. Silently check off STAR's beats as you speak, catching rambling before it consumes your Situation/Task budget (Chapter 6).
2. Deliberately audit your language for "we" versus "I" in every prepared story — mark the specific sentences where the action was genuinely yours, and make sure those specifically use "I."
3. Write down an actual number or concrete outcome for every story in your bank, and if you can't find one, weight that story lower in your rotation.
4. Practice describing any past conflict or negative situation in terms of behavior and outcomes, never character judgments about an absent person — rehearse this specifically for any story involving a difficult manager, colleague, or employer.

More sample questions on this theme

1. "Why are you looking to leave your current company?" The highest-risk question for Mistake 4 — rehearse a specific, neutral, forward-looking answer in advance rather than improvising in the moment when frustration might surface.
2. "Tell me about your role on your team's biggest project." A natural trap for Mistake 2 ("we") — practice this one specifically isolating your individual contribution.
3. "What's the impact of a project you led?" Directly tests Mistake 3 — if your answer doesn't include a number, that's the signal to dig for one before the actual interview, not during it.
4. "Tell me about a time you worked with a difficult stakeholder." Another high-risk prompt for Mistake 4 — practice describing the difficulty in terms of specific behaviors and how you adapted, not character judgments.
5. "Tell me about your proudest achievement." A prompt candidates often over-rehearse into Mistake 5's flat, scripted cadence — precisely because it's a predictable question — revisit Chapter 7's skeleton-not-script practice specifically for this one.

Chapter summary / cheat sheet

Mistake	Fix
Rambling	Internalize STAR's beats; silently check off Situation/Task/Action/Result as you speak
Hiding behind "we"	Audit language; use "we" for genuinely collective actions, switch to "I" for your specific contributions
Vague/unmeasured results	Force a real number or concrete outcome into every story; deprioritize stories that lack one
Badmouthing past employers/colleagues	Describe behavior and outcomes, never character judgments about an absent third party
Sounding overly scripted	Rehearse the skeleton, not a verbatim script (Chapter 7)

• These five mistakes compound rather than occurring independently — fixing structure (STAR) often incidentally fixes several of the others at once.
• Most of these mistakes are invisible to the person making them without external feedback — mock interviews (Chapter 7) are the most reliable way to catch them before the real interview.

---