How to answer the failed project interview question
The short answer
Interview Coach asks this question in these words:
Tell me about a project or a decision that did not go to plan. What was your part in it?
Pick a project or a decision that really did not go to plan, where part of the cause was yours. Say what was at stake and what went wrong. Own your part in one plain sentence, without blaming others. Then say what you did once you saw the problem, how it ended, and what you do differently since, with one example. Spoken, that is about one to two minutes.
Check your own answer in Claude with Interview Coach, free
What the interviewer is checking
The question is not a trap about failure. It checks whether you can see your own part in a problem, and whether you changed anything because of it. The bank lists three things a strong answer does:
- It owns your part of what went wrong, without blaming others. A vendor can be late and a sponsor can change scope; the question asks about your part. "I planned the migration from the vendor's estimate and did not test it" is ownership. "The vendor delivered late" is not.
- It describes what you did once you saw the problem. Who you told, how fast, what you proposed and what you stopped.
- It names what you do differently since, with one example. A habit you can point to, and a later project where it helped.
A failure that is really a strength in disguise ("I worked too hard") skips the question. So does a failure that was nobody's fault. Choose one where your decision mattered.
A structure that works
Interview Coach describes a setback answer in four parts:
- Situation. What was at stake and what went wrong.
- Ownership. Your own part in it, without blaming others.
- Action. What you did once you saw the problem.
- Learning. What you do differently since, with one example.
The answer check looks for a situation, at least two actions said with I, a result near the end and a learning. It also reads the balance between "we" and "I", the length of a spoken answer, and words that weaken an answer: filler, hedges, weak ownership ("was responsible for", "tried to") and vague claims ("a lot", "significantly").
Answers as written, and what the check says
Illustrative, not a real client. Each answer below was sent on its own through the answer check of Interview Coach. All of them are also marked short for a spoken answer, because each is one or two sentences; the table shows the other finding, word for word, and one way to fix it.
| Answer as written | What the check says | What to change |
|---|---|---|
| The vendor delivered late and the business kept changing the scope, so the migration slipped by a quarter and the sponsor was unhappy. | No sentence says what you did yourself, with I. | Keep the causes short, then say your own part and your own steps, with I. |
| When the data migration slipped, I rebuilt the cutover plan and I moved the go-live by six weeks, and the migration closed in June. | No learning is named. Say what you do differently since. | Add the habit you changed and one later project where it showed. |
| I was responsible for the reporting rollout and I tried to keep it on track, but the go-live slipped and I learned a lot from it. | Hedging or weak ownership words found. | Replace "was responsible for" and "tried to" with what you decided and did. |
| When the rollout slipped, the team worked weekends and we fixed the data and we went live in June. Since then I check data earlier. | Mostly we and the team. The interviewer cannot tell which part was yours. | Keep the team's effort, and add the decisions that were yours. |
| I stopped the cutover, I told the sponsor the same day, and the new date was approved. Since then I run a trial load first. | No context is set before the action. Add what was at stake. | Open with the project, the date at stake and what went wrong. |
| When the trial load failed, I stopped the cutover and I told the sponsor the same day. I now run a trial load before I commit to a date. | No result is named. Say what changed. | Say how it ended: the new date, what was delivered and what it cost. |
| So basically I, um, underestimated the data work, and actually the cutover slipped by six weeks, and since then I test the data first. | Filler words found. | Drop the filler, and say the same thing in plain sentences. |
| I underestimated the data migration, and the go-live slipped by six weeks, which taught me to test real data earlier. | Only one first person action found. Say what you did yourself. | Add the steps you took once you saw the problem. |
The check never writes a figure or a lesson for you. If you have no record of how it ended, say what you saw, and say plainly that it was not measured.
An illustrative answer
Illustrative, not a real client. Every figure is invented. This answer gets all nine marks of the setback check: length, situation, own action, team versus me, result, learning, and no vague words, filler or hedges.
I led the move of a home goods retailer's order system to a new platform in 2023, and the go-live date was fixed by the end of the old contract. I planned the data migration from the vendor's estimate and did not run a trial load with real order history. That was my call, and it was wrong. At the first cutover rehearsal, a third of the open orders failed to load. I stopped the cutover, I told the sponsor the same day, and I asked for four more weeks. I set up two more trial loads with the warehouse team and I tracked every failed record in the cutover log until the count reached zero. The new platform went live four weeks late, with every open order loaded and no lost shipments in the first month. The sponsor accepted the new date, but the delay cost the business a second month of license fees on the old system. Since then I run a trial load with real data before I commit to a cutover date, and on my next migration that trial found a date format problem in the first week.
Why it works. The ownership is one plain sentence: "That was my call, and it was wrong." The vendor is part of the story, not the excuse. The result includes the cost. The learning is a habit with a later example, not a slogan.
What the check cannot see
The answer check reads the words of your answer. It does not judge whether you owned anything real. This answer, sent on its own, gets every mark except length:
The launch went badly and it was a disaster for the business, but I stayed calm and since then I plan better.
It has a situation, two actions said with I, a result word and a learning cue, so the structure looks complete. An interviewer would still ask: what went badly, what was your part, and what does "plan better" mean on your next project? Use the marks to find what is missing, then read your answer the way an interviewer would.
Choosing your story
- Pick a real miss. A date, a budget, a decision that turned out wrong. Not a near miss you saved at the last minute.
- Pick one where your decision was part of the cause. That is what makes ownership possible.
- Pick one that is over. You need an ending and something you have done differently since.
- Pick one you can talk about calmly. If the story still makes you angry at someone, choose another.
Your resume is where an interviewer looks for these stories, and a line that overstates a project makes this question harder. Get a free AI review of your resume and see which lines Reed flags first.
Prepare the follow-up questions
- What would you do in the first week if you ran that project again?
- How did your sponsor or manager react, and what did you say to them?
- Where else have you used what you learned?
Run the free review on your own resume lines.
Check your answer with Interview Coach in Claude
This question is in the shared part of the Interview Coach question bank, not tied to one role. Write your answer the way you would say it and ask for a check.
- It reads the answer for a situation, your own action said with I, a result, and a before and after figure or a named record.
- It flags filler, hedging, weak ownership and vague claims, and says when the answer is short or long for a spoken answer.
- It does not judge whether the story is true or good, and it never adds a figure you did not give.
Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.
Free in Claude, no account. We do not store the text you send through it.
Questions
Can I talk about a failure that was not my fault?
You can mention causes outside your control, briefly. The question asks for your part, so choose a story where you had one, and say it in one plain sentence. An answer that is only about other people's mistakes does not answer it.
How big should the failure be?
Big enough that something real was at stake: a date, money, a customer. Not so big that the story is only damage. A project that slipped or a decision that had to be reversed is enough. What matters more is what you did once you saw it.
Does Interview Coach know whether my story is true?
No. Interview Coach runs in Claude and checks the structure of an answer by fixed rules: a situation, your own action, a result, a learning. It does not judge whether the story is true or good. You decide what to say.
Keep going
- Interview questions: Project manager interview questions
- Interview questions: IT manager interview questions
- Interview questions: Program manager interview questions
- Guide: How to answer the stakeholder conflict question
- Guide: How to answer the influence without authority question
- Guide: How to answer the hardest deadline question
- Guide: How to answer the scope change question
- Guide: How to answer the project risk question
- Guide: How to answer the product metric question
Last updated: October 13, 2026