Describe a time when a project you were responsible for didn't go as planned. What was your role in the failure and what did you learn?

behavioral · Mid level · general

What the interviewer is really asking

Assess accountability, self-reflection, and ability to extract actionable lessons from setbacks.

What to say

• Own your specific part in what went wrong — don't spread blame evenly to avoid accountability.
• Walk through the cascade: what went wrong, what your decisions contributed, what the impact was.
• Name two specific things you changed in how you work as a result.

What to avoid

• Don't frame the failure as primarily someone else's fault.
• Avoid picking a failure so trivial it signals you're playing it safe.
• Don't end without a genuine lesson — 'we learned to communicate better' is too vague.

Example answers

Strong: We missed a release date on a payment integration by three weeks. My role: I underestimated the third-party API's documentation quality and didn't build in buffer for integration surprises. I also didn't flag the schedule risk early enough when I first felt the timeline was tight. I now build a mandatory 'integration spike' into any third-party estimates and speak up about risk by the second day of uncertainty, not the second week.

Weak: The requirements kept changing so it wasn't really our fault.