Dana Kessler

Senior Backend Engineer @ (fictional session)

You interviewed as Engineering Manager

Your decision: Hire

Overall

Your interviewing score across six areas.

Red Flag Detection 3/10 — the headline.

Red Flag

Questions

Coverage

Depth

Time

Conduct

The Tell

Dana Kessler was running The Blame Shifter: competent and personable, but in every setback the fault lands on someone or something else, never on them. They're not lying, exactly; the stories are real. What's missing is a single moment of "here's what I got wrong." Where it was on the table (all three went by): 1. The payments outage: "the platform team pushed a config change that took us down." You asked what they changed, not what Dana could have caught. 2. The missed launch: "the spec kept moving and we never got runway." True, maybe, but no reflection on their own estimate or pushback. 3. The teammate who "just wasn't pulling their weight." Delivered warmly, which is what made it land as candor instead of a flag. The three questions that would have popped it: - "What was your part in that outage?" - "Tell me about a failure that was genuinely yours, and what you changed after." - (Later, re-asked) "If your manager described that launch, what would they say you could have done differently?" Decision vs. truth: You said Hire. The Blame Shifter often is hireable, but on a team, unowned failures compound. Knowing the pattern, you'd calibrate onboarding and feedback expectations from day one instead of month three.

Scorecard detail

Red Flag Detection

3/10

The pattern surfaced three times and went unchallenged each time. When the payments outage came up, Dana said "the platform team pushed a config change that took us down" and the interviewer moved on. Accountability was never tested with a direct 'what was your part in that?'

Question Quality

7/10

Strong, open opener ("walk me through the hardest system you've owned") and good scenario framing. A few questions were leading ("so that was out of your control, right?"), which handed Dana the exact exit they were looking for.

Topic Coverage

6/10

Solid on architecture and scaling; light on collaboration and on ownership of failure. No question asked Dana to describe a mistake that was theirs.

Depth Balance

5/10

Went three follow-ups deep on the sharding design, but accepted the first answer on the outage postmortem, the one place depth would have surfaced the tell.

Time Management

7/10

Well paced across 34 minutes; left room for candidate questions. Spent a little long on the résumé recap that could have gone to probing.

Interviewer Conduct

9/10

Professional and warm throughout; no leading personal questions, nothing out of bounds. Built genuine rapport, which is exactly why the softballs slipped by.

What you did well

Opened with a specific, open-ended prompt that got Dana talking concretely instead of in generalities.
Took notes and circled back to an earlier answer, a good signal you were listening.
Kept the room professional and easy; Dana clearly felt comfortable, which surfaces more real behavior.

To work on next time

When a candidate names an external culprit ("the platform team", "the spec changed"), always follow with "what was your part in that?". You had three chances.
Ask for a failure the candidate personally owned and what they'd do differently. Dana never had to.
Re-ask the accountability question a second way later in the interview; consistency (or its absence) is the tell.

Coach's notes

You ran a clean, likable interview and got Dana talking; that's the hard part, and you did it well. The technical thread was genuinely strong: you pushed three follow-ups deep on the sharding design and got a clear picture of the architecture. The gap was accountability. Every failure story in this transcript had a villain, and it was never Dana: the platform team, a changing spec, "not enough runway." Each of those is plausible on its own, which is exactly why the pattern is easy to miss. The fix isn't suspicion; it's one reflex: when the blame points outward, ask where the candidate's own part was, and don't accept the first deflection. You called it a Hire on the strength of the technical answers. That may still be the right call, but you'd have made it knowing what you were signing up for, instead of finding out in the first postmortem.

Now find out what you'd miss.

Your first practice interview is free. One of our candidates sits down across from you, and you won't know which.

Run your first interview, free