Give me an example of a time when you were not able to meet a commitment.
Asked at:
Amazon
Meta
Snowflake
Anthropic
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess how you handle failure against expectations, especially when your work affects other people. They are usually less interested in the fact that you missed than in whether you recognized risk early, communicated responsibly, took ownership for the impact, and learned in a way that changed your future behavior. At higher levels, they also want to see whether your judgment about commitments themselves was sound and whether your response protected the team or organization.
“Tell me about a time you missed a deadline or target you had committed to.”
“Describe a situation where you told someone something would be done by a certain time, and it wasn't.”
“Have you ever had to go back on a commitment at work? What happened?”
“Walk me through a time when you realized you weren't going to deliver what you had promised.”
“What's an example of a project or task where you couldn't meet the expectation you had set?”
Key Insights
- You do not need a dramatic failure story, but the miss should be real and consequential enough that a commitment actually mattered to someone besides you.
- A strong answer usually starts before the miss: explain when you first saw risk, what you did to reduce it, and how proactively you communicated rather than waiting until the deadline had already passed.
- Do not make the story about why the commitment became impossible; make it about how you owned your part, managed the impact on others, and changed how you make commitments now.
What interviewers probe atlevel
Top Priority
Interviewers want to hear that you did not disappear with the problem; you raised it when you had evidence and asked for help appropriately.
Good examples
🟢Once I saw I was two days behind and still uncertain on the root cause, I flagged the risk in standup and asked for a quick review.
🟢I let my mentor know early that my estimate was slipping, along with what I had tried and what help I needed.
Bad examples
🔴I told my lead on the due date that it would take longer once I was sure I couldn't finish.
🔴I waited until I had fully diagnosed the issue before saying anything because I didn't want to bother anyone.
Strong answers show proactive communication while there was still time to adjust, not just a late status update.
You are not expected to control everything, but you are expected to clearly name what you misjudged or failed to do.
Good examples
🟢I should have asked for help earlier instead of spending too long trying to debug it alone.
🟢I assumed the existing code worked the way the documentation said and didn't validate that assumption early enough.
Bad examples
🔴I missed because the task ended up being more complicated than anyone would have expected.
🔴I was blocked by other people for most of the week, so there wasn't much I could really own there.
Strong answers distinguish external factors from the candidate's own decisions and explicitly own the part they could have handled better.
Valuable
After a miss, show what you did to recover the work or reduce impact, not just that you felt bad about it.
Good examples
🟢I broke the remaining work into smaller pieces, got a quick check on my approach, and delivered the most needed part first so testing could start.
🟢I paired with a teammate for an hour to unblock the core issue and moved a lower-priority piece to a follow-up task so we could still ship the essential functionality.
Bad examples
🔴I apologized and then kept working until it was done.
🔴I told the team it was delayed and waited for my lead to decide what to do next.
Strong answers show active recovery and impact reduction instead of passive regret.
Pick a real miss on a meaningful task, not a trivial scheduling slip or a disaster far beyond your actual responsibility.
Good examples
🟢I committed to delivering a testing tool another engineer needed that week, and my delay blocked part of their validation work.
🟢I owned a small feature for a sprint, underestimated the integration work, and had to tell my lead it would miss the sprint goal.
Bad examples
🔴I missed a personal to-do I had set for myself, but it wasn't a big deal because I just finished it the next day.
🔴The whole release was late because product kept changing requirements, so there wasn't really anything I could have done.
Strong answers choose a miss that was genuinely consequential within the candidate's scope and where the candidate had meaningful agency.
Example answers atlevel
Great answers
In my first few months at work, I committed to finishing a small internal dashboard update by the end of the sprint because another engineer needed the data view for testing. A couple of days in, I realized I had underestimated how messy the underlying data was, and I spent too long trying to fix it alone because I wanted to prove I could handle it. Once I saw I was slipping, I told my lead in our daily check-in, showed what I had tried, and asked for help validating the approach. We decided to cut one lower-priority filter so I could deliver the main view on time for testing, and I finished the rest a few days later. What I learned was to surface risk earlier and test my assumptions before committing on unfamiliar code, and since then I've been much more consistent about giving updates before something becomes a surprise.
At my last startup I committed to deliver an updated onboarding flow before a scheduled marketing campaign because the PM wanted users to see the new content. A few days in I realized I’d badly underestimated the time needed for cross-browser fixes and accessibility checks—things I hadn’t factored into my estimate as a junior developer. I told the PM immediately, showed a quick list of what would remain unfinished, and suggested shipping a simplified version that preserved the new visuals but deferred some interactive validation, while I worked with QA and a senior engineer to finish the accessibility items. The team agreed to use the simplified flow for the campaign, and I completed the remaining work the following week. I learned to always include testing and accessibility in my timelines and to flag cross-team dependencies as soon as possible.
Poor answers
I had a task where I expected to finish a bug fix by Friday, but it ended up taking longer because the codebase was more complicated than it looked. I kept working on it and finished it the following week. I don't think there was much else I could have done because sometimes estimates are just off, especially when you're new. Overall it worked out because the fix still went in.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early April, 2026
Amazon
Manager
Late February, 2026
Amazon
Mid-level
Mid December, 2025
Meta
Manager
Hello Interview Premium
Your account is free and you can post anonymously if you choose.