Chapter 10: Handling Curveballs: No Story on Hand, Uncomfortable Questions, Stories That Reflect Poorly

Why this matters

Even a thoroughly prepared candidate with a rich story bank (Chapter 4) will eventually hit a question that doesn't map cleanly to anything they've prepared, or a question that requires sharing something genuinely uncomfortable. How a candidate handles these specific, harder moments is disproportionately memorable to interviewers — precisely because it's the moment furthest from anything that could have been scripted.

Curveball 1: no matching story comes to mind

[BEGINNER] Every candidate, no matter how well-prepared, will occasionally get a question that doesn't obviously match anything in their story bank. The single worst response is filling the silence by inventing or badly stretching an unrelated story to fit — interviewers can usually tell, and the resulting answer tends to be unconvincing on every dimension at once.

## A better process when nothing comes to mind immediately
1. Buy genuine time, honestly: "That's a good question, let me think
   of a specific example for a moment" -- and actually pause and think,
   don't just say the sentence and immediately continue.
2. If a partial match exists, offer it explicitly as a partial match:
   "I don't have an exact example of that specific situation, but I
   have one that's closely related -- would that be useful, or would
   you rather I keep thinking?" -- this respects the interviewer's
   actual intent rather than silently substituting a worse-fitting story.
3. If genuinely nothing comes to mind after real effort, it's better
   to say so honestly than to force a poor answer: "I'm having trouble
   thinking of a specific example of that right now -- can we come
   back to it, or would a related example be helpful?"

[INTERVIEWER'S VIEW] An interviewer who allows a candidate to return to a question later, or who accepts an honest "I don't have a great example of exactly that" is not doing the candidate a special favor — this is normal, expected interview behavior, and most interviewers would rather get an honest, if imperfect, answer than a stretched, unconvincing one. A candidate who visibly panics or who forces an obviously poor-fit story is remembered far more negatively than one who calmly, professionally worked through the moment.

Curveball 2: an uncomfortable or unexpected question

[SENIOR INSIGHT] Some questions are uncomfortable by design — "tell me about a time you failed," "why did you leave your last job," "tell me about a time you received harsh criticism" — and the discomfort itself is not a sign something has gone wrong; it's often the exact point of the question (probing self-awareness and composure under a mildly stressful, exposing prompt). The key distinction: discomfort about the topic is normal and expected; visible defensiveness or evasion in response to it is the actual, damaging signal.

Weak response to discomfort (visible defensiveness): "I don't really
have a good example of failure, I try to learn from things quickly
so I don't really think of it that way."

Strong response to the SAME discomfort (composed, honest): "This one's
a bit uncomfortable to talk about, but I think it's a good example.
[proceeds with a genuine, specific failure story]"

[IN PRACTICE] Naming the discomfort briefly and directly, as the strong example above does, often works for the candidate rather than against them — it signals self-awareness and comfort with vulnerability, which is precisely one of the traits many of these uncomfortable questions are designed to surface in the first place.

Curveball 3: the honest story reflects poorly on you

[SENIOR INSIGHT] The most delicate curveball: a genuinely honest answer to a question requires describing a real mistake, a real failure, or a real moment of poor judgment on the candidate's own part — and the instinct to soften, obscure, or shift blame in that moment is strong and understandable, but usually backfires. An interviewer evaluating a failure story is not primarily judging the failure itself — they're judging the honesty of the account and the quality of what was learned and changed afterward. A candidate who owns a real mistake clearly, without excessive self-flagellation or deflection, and who can point to a specific, credible change in behavior since, generally scores better than a candidate who tells a sanitized "failure" story that isn't really a failure at all (a extremely common, recognizable pattern interviewers see constantly — see below).

The recognizable "fake failure" pattern to avoid: "My biggest weakness
is that I care too much about quality, so sometimes I take longer than
others on a task." -- this is a disguised strength, not a genuine
weakness, and experienced interviewers recognize this pattern
IMMEDIATELY, which actively damages credibility rather than helping it.

A genuine, well-handled failure story instead: "Early in my career, I
pushed a database migration without adequately testing it against
production-scale data, and it caused a two-hour outage. I take full
ownership of that -- I didn't follow our own testing checklist because
I was under deadline pressure and assumed a smaller-scale test was
representative enough. Afterward, I proposed making the production-scale
test step mandatory and non-skippable in our deployment pipeline, which
prevented at least two similar issues I'm aware of since."

Common mistakes

1. Forcing a poorly-matching story onto a question rather than honestly buying time or acknowledging the mismatch — an unconvincing stretch is worse than a brief, honest pause.
2. Responding to an intentionally uncomfortable question with visible defensiveness or evasion rather than treating the discomfort as normal and simply proceeding with a genuine, composed answer.
3. Disguising a strength as a weakness ("I work too hard," "I care too much") when asked for a genuine failure or weakness — this is an extremely common, easily-recognized pattern that damages credibility specifically because it's so familiar to experienced interviewers.
4. Deflecting blame or minimizing a genuine mistake when telling a failure story, rather than owning it clearly and pairing it with a specific, credible change in behavior since.

Checklist: handling curveball questions

1. When no story comes to mind immediately, buy genuine time honestly rather than forcing an unconvincing, poorly-fitting answer — offer a partial match explicitly if one exists, or ask to return to the question if nothing does.
2. Expect certain questions to be uncomfortable by design, and treat the discomfort as normal — proceed with composure rather than visible defensiveness or evasion.
3. When describing a genuine failure or mistake, own it clearly and specifically — avoid both excessive self-flagellation and any deflection of responsibility.
4. Never disguise a strength as a weakness when asked for a genuine one — this specific pattern is extremely familiar to experienced interviewers and reliably damages credibility.

More sample questions on this theme

1. "Tell me about a time you were let go or asked to leave a role." A genuinely difficult question for candidates with this history — the strong approach is factual, non-defensive, and focused on what was learned, following this chapter's failure-story guidance directly.
2. "What's the biggest criticism you've received in a performance review?" A direct test of the fake-weakness pattern — a strong answer names something genuinely real and specific, with evidence of subsequent change.
3. "Tell me about a time you missed a deadline." Nearly every experienced candidate has one — the temptation to blame external factors entirely is high; a strong answer acknowledges the candidate's own specific contributing decisions, not just circumstances beyond their control.
4. "Have you ever disagreed with a company policy or decision you had to enforce anyway?" A values-adjacent question that can feel like a trap — a strong answer is honest about the disagreement while demonstrating professional judgment about how it was handled, without badmouthing (Chapter 8) the policy or the people behind it.
5. "Tell me about the last time you got really frustrated at work." An intentionally probing, slightly uncomfortable prompt — a strong answer names a genuine, specific source of frustration and, critically, a constructive way it was channeled, rather than either denying ever getting frustrated or venting uncontrolled irritation in the retelling.

Chapter summary / cheat sheet

• When no matching story comes to mind, buy genuine time honestly, offer a partial match explicitly, or ask to return to the question — never force an unconvincing, stretched answer.
• Discomfort in response to an intentionally probing question is normal and expected; visible defensiveness or evasion is the actual damaging signal, not the discomfort itself.
• A genuine, well-owned failure story with a credible behavior change since generally scores better than a disguised-strength "fake weakness" — experienced interviewers recognize the fake-weakness pattern immediately.
• Across all three curveball types, composure and honesty consistently outperform a polished-sounding but evasive or fabricated response.

---