Courses › Behavioral Interviews › Question Themes

Failure & Feedback

Talking about mistakes and criticism without hurting yourself.

"Tell me about a time you failed" makes candidates nervous, and many dodge it with a disguised strength ("I worked too hard"). Interviewers see through that instantly. These questions test self-awareness, accountability and growth — and a genuinely good failure story is one of the most persuasive answers you can give.

Typical questions

• Tell me about a time you failed.
• Tell me about a mistake you made and how you handled it.
• Tell me about a project that didn't go as planned.
• Tell me about a time you received critical feedback.
• What's a weakness you're working on?

Choosing a failure story

Good failure stories:

• Are real, with real consequences (a missed deadline, an outage, a wrong technical bet)
• Are owned — you were a meaningful cause, not a bystander
• Are not catastrophic or ongoing — you've clearly moved past it
• Lead to a concrete change in how you work

Avoid failures that raise serious questions about judgment or ethics, and very old stories.

Structure: STAR with a heavier R

Spend about a third of your answer on what happened *after*:

• What happened — briefly and honestly, including your part.
• How you responded — contained the damage, communicated, fixed it.
• Root cause — what about your approach led to it.
• What changed — the specific habit, process or tool you introduced.
• Evidence it stuck — a later situation where the change made a difference.

[!EXAMPLE] Outline I estimated a database migration at three weeks without investigating the long tail of legacy queries; it took ten weeks and delayed a launch. I told stakeholders as soon as I saw the slip, re-planned in phases, and shipped the critical path first. The root cause was committing to an estimate before a spike. Now I timebox a discovery phase on any migration before estimating, and I give ranges. On the next migration, the spike surfaced two blockers early and we delivered within the range.

Feedback questions

Show that you can receive feedback without defensiveness and act on it:

• Describe the feedback specifically ("my design docs were too long for reviewers to act on")
• Be honest about your first reaction
• Show how you sought to understand it (asked for examples)
• Describe the concrete change and its result

Weakness questions

Pick a real, non-disqualifying weakness, and focus on how you're managing it: "I tend to go deep into implementation before aligning stakeholders. I now share a one-page proposal before I start building anything that touches other teams."

[!WARNING] Red flags - Blaming teammates, managers or circumstances - A failure with no lesson, or a lesson with no behavior change - "I can't think of a failure" — this reads as low self-awareness