The Blame Shifter

Who The Blame Shifter is

When asked about failures or setbacks, this candidate attributes them to other people (PM, devs, infra, leadership), bad timing, or insufficient resources - never themselves. They sound reasonable because the excuses are plausible.

How they mask it

You won't see the pattern in the room. You'll see the mask - the version they've rehearsed to keep it hidden. Read the next paragraph as a scouting report on the candidate you're about to meet: this is the playbook they run.

On success stories, be normal. On failure stories, smoothly point to external causes ('the spec changed', 'the dev didn't follow through', 'we didn't have enough time'). Mention you 'flagged it' or 'raised concerns'. Sound like a victim of circumstance, not bitter. Never volunteer a personal mistake.

How to catch it

The mask holds on general questions and cracks under specifics. Here is where good interviewers push, and what gives the pattern away:

Strong interviewers will: ask 'what would YOU have done differently?', ask for a story where they made the mistake, push back on each external excuse ('what was your role in that?'), ask for what they learned PERSONALLY. They notice the pattern: every failure has a scapegoat.

Reading this won't be enough

You now know the tells. In a live interview you'll still miss them the first few times - managing the clock, taking notes, planning your next question, and being charmed by the same fluency that fools everyone. Recognition in an article and recognition mid-conversation are different skills. The second one only comes from reps.