Tell Me About a Project That Failed: How to Answer

“Tell Me About a Project That Failed” is one of the most dreaded interview questions, yet most candidates handle it badly by either dodging the question or drowning in self-criticism. This guide shows you exactly how to structure a strong, honest answer that turns a past failure into proof of your professional maturity.

Key Takeaways

• Interviewers ask this question to assess self-awareness, accountability, and your ability to learn under pressure.
• A strong answer follows a clear structure: context, what went wrong, your role, and what you changed as a result.
• Avoid blaming colleagues, clients, or external circumstances as the sole cause of the failure.
• Choose a real example that had genuine consequences but was not catastrophic or illegal.
• Practising out loud before your interview reduces the risk of rambling or becoming defensive on the day.

Why do interviewers ask you to tell them about a project that failed?

Interviewers ask this question because they want to see how you respond when things go wrong, not just how you perform when everything runs smoothly. A candidate who can reflect honestly on failure and explain what they did differently afterwards is far more valuable than one who claims they have never made a significant mistake. The question is a direct test of self-awareness and professional growth.

Hiring managers use behavioural interview questions like this one to predict future performance based on past behaviour. According to the CIPD, behavioural interviewing is one of the most widely used selection methods in the UK, with over 70% of employers incorporating it into their hiring process. When they ask about failure specifically, they are checking whether you take ownership of outcomes rather than deflecting responsibility onto others.

For example, a project manager interviewing for a senior role might be asked this question to reveal whether they can identify systemic issues, not just surface-level problems. An interviewer is listening for genuine reflection, not a rehearsed story that conveniently makes the candidate look faultless. The answer you give tells them far more about your character than a straightforward question about your strengths ever could.

What interviewers are really evaluating

Beyond the story itself, interviewers are scoring you on three specific qualities: accountability, adaptability, and communication. They want to hear that you understood your contribution to the failure, that you adjusted your approach, and that you can explain all of this clearly under mild pressure. If your answer ticks all three boxes, it works in your favour regardless of how significant the failure was.

What makes a good example of a failed project for an interview?

A good example is one where you played a meaningful role, the failure had real consequences, and you can clearly explain what you learned. It does not need to be dramatic or large-scale. A missed deadline, a product launch that underperformed, or a client relationship that broke down can all work well if you frame them honestly.

The best examples sit in a middle ground: serious enough to show the stakes were real, but not so severe that they raise concerns about your judgement or conduct. You should avoid examples that involve legal or ethical violations, or that require you to disclose confidential information about a former employer. Equally, avoid trivial examples like a minor spelling error in an email, as these signal poor self-awareness about what actually constitutes failure.

For example, an account manager who lost a key client after missing several follow-up calls has a strong example to work with. They can explain the cause, acknowledge their specific lapse in communication, and describe the new system they put in place to prevent the same outcome. That narrative arc, from problem to learning to change, is exactly what interviewers are looking for.

How recent does the example need to be?

There is no strict rule on recency, but examples from the last three to five years tend to land better because they feel more relevant to your current working style. According to HBR research on interview performance, candidates who draw on recent examples are perceived as more self-aware because the detail is sharper and the learning is more likely to have influenced their present behaviour. If you are a recent graduate with limited work history, an academic or voluntary project failure is entirely acceptable to use.

How should you structure your answer to this interview question?

The most reliable structure for answering this question is a modified version of the STAR method: Situation, Task, Action, Result, with an additional step for Learning. This gives your answer a clear beginning, middle, and end, and ensures you do not skip the reflection that interviewers most want to hear. A well-structured answer typically runs between 90 seconds and two minutes when spoken aloud.

Start by briefly setting the scene so the interviewer understands the context without unnecessary detail. Move quickly to your specific role and what went wrong, taking ownership of your part in the failure rather than describing it as something that happened to you. Close the answer with a concrete description of what you changed, whether that is a process, a habit, or a way of communicating with stakeholders.

For example, a software developer might say: “We were building a client portal with a four-week deadline. I underestimated the complexity of one integration and did not flag the risk early enough, which meant we delivered two weeks late. After that, I introduced a weekly risk log into every project I led, and we have not missed a client deadline since.” That answer is clear, honest, and forward-looking.

Breaking down the STAR-L structure

The STAR-L approach works well because each element serves a specific purpose in your answer. The Situation and Task establish credibility and context. The Action section is where you take accountability, which is the part most candidates rush or avoid. The Result shows consequence, and the Learning is the part that converts a story about failure into a story about growth.

How long should each part of the answer be?

Keep the Situation and Task sections short, no more than two or three sentences combined. Spend the most time on the Action and Learning sections, as these are where interviewers focus their attention. According to research published by the British Psychological Society, structured answers in competency-based interviews are rated significantly higher by trained assessors than unstructured narratives, so the time you invest in planning your response directly improves your score.

What should you avoid saying when answering this question?

The biggest mistake candidates make is answering the question without actually describing a genuine failure. Phrases like “I work too hard” or “I care too much about quality” are not failures, and experienced interviewers will view them as evasive. Attempting to reframe a strength as a weakness in response to a failure question damages your credibility immediately.

You should also avoid placing the entire blame on other people, even if colleagues did contribute to the problem. Saying “the project failed because my manager gave us an unrealistic timeline” may be accurate, but it signals to the interviewer that you struggle to take personal accountability. A stronger approach acknowledges external factors briefly before redirecting to your own role and what you could have done differently.

For example, if a project genuinely failed partly because of poor leadership above you, you might say: “The timeline was very tight, and I also did not push back early enough when I could see we were at risk of missing it.” That framing is honest and shows maturity without eliminating your accountability from the story. Avoid any language that positions you as a passive observer of your own career.

Common phrases to cut from your answer

Certain phrases consistently weaken failure answers in interview settings. Avoid “it wasn’t really my fault”, “everyone agreed it was the right call at the time”, and “I wouldn’t change anything, to be honest.” These signals suggest you have not genuinely reflected on the experience. Replace them with specific, direct language that names the error and the lesson in plain terms.

How should you practise answering this interview question?

Practising out loud is the most effective way to prepare, because failure is an emotionally charged topic and your delivery matters as much as your content. Many candidates who have a good answer in their head still sound defensive or apologetic when they say it for the first time. Rehearsing the answer several times builds the neutral, confident tone that interviewers respond to positively.

Record yourself on your phone and play it back, paying attention to whether your answer sounds like a genuine reflection or a rehearsed defence. According to ONS data on employment trends, interview preparation is consistently cited by successful job seekers as one of the most impactful steps they took before securing a new role. If you can, ask a trusted colleague or friend to listen and tell you whether your tone sounds accountable or deflective.

For example, try delivering the answer to a mirror first, then to another person, and finally under mild time pressure by setting a two-minute timer. Each stage of practice reveals something different about how your answer lands. The goal is not to memorise a script but to internalise the structure so the answer feels natural even if the wording changes slightly on the day.

Should you prepare more than one failure example?

Yes, preparing two distinct examples is a sensible approach. Different roles call for different types of failure stories, and having a second option means you can adapt if your first example does not quite fit the context of the question. One example might focus on a technical or process failure, while the other could centre on a communication or stakeholder management breakdown.

Can you use a team failure rather than a personal one?

You can use a team failure, but only if you clearly explain your specific contribution to it rather than describing what the team did collectively. Interviewers ask this question to understand your individual judgement and behaviour, so an answer that stays at team level without zooming in on your role will feel incomplete. The key is to use “I” more than “we” when describing actions and decisions.

Team failures are actually strong examples when handled well, because they also let you demonstrate your understanding of collaboration, communication, and shared accountability. According to CIPD research on workplace performance, project failures in UK organisations most commonly stem from poor communication between team members rather than individual technical errors. Choosing a team-based failure can therefore feel highly relevant and credible to a hiring manager, provided you anchor it in your own actions.

For example, if your team missed a product launch date, you might explain that you were responsible for coordinating testing timelines and that you did not escalate a known delay early enough to allow the team to adjust. That framing makes the failure shared but your accountability personal. It also gives you a natural learning to close with, such as introducing a clearer escalation process or a more regular check-in rhythm with the wider team.

How to shift from “we” to “I” without sounding like you are blaming teammates

The simplest technique is to describe what the team experienced, then immediately pivot to what you specifically did or did not do within that situation. Phrases like “my responsibility in that project was…” or “where I fell short was…” signal personal ownership without throwing colleagues under the bus. This approach keeps the answer honest and protects your professional relationships at the same time.

How Long Should Your Answer Be and What Structure Works Best?

Your answer to “tell me about a project that failed” should last between ninety seconds and two and a half minutes when spoken aloud, which translates to roughly two hundred and fifty to four hundred words in written form. The STAR method — Situation, Task, Action, Result — gives you a reliable skeleton that keeps the answer focused and easy for the interviewer to follow.

Many candidates either rush through the failure in ten seconds and spend the rest of the time on the recovery, or they do the opposite and dwell so long on what went wrong that they never arrive at a clear lesson. Neither approach lands well. A balanced structure signals emotional maturity and genuine reflection, both of which hiring managers actively look for when they ask this question.

Breaking Down the STAR Structure for This Specific Question

When applying STAR to a failure question, each stage carries slightly different weight than it would for a success story. The Situation and Task sections should be brief — two or three sentences each — because they exist only to give context. The Action section is where you need to be specific about your individual choices, including the ones that contributed to the failure. The Result section must include the concrete outcome, the lesson you drew from it, and ideally a brief note on how you applied that lesson later. This final beat transforms a story about falling short into evidence of professional growth.

This Approach Works Well for Experienced Candidates but Not for Graduates

This approach works well for candidates with several years of professional experience but not for recent graduates because the STAR framework assumes access to a meaningful workplace project with measurable outcomes. If you are early in your career, a university group project, a dissertation that missed its original scope, or a voluntary role that did not achieve its fundraising target are all legitimate substitutes. The key is ensuring the example still demonstrates reflection and learning rather than simply an unfortunate outcome beyond your control.

For guidance on structuring interview answers more broadly, the National Careers Service interview advice pages offer practical frameworks that complement the STAR approach and are updated regularly to reflect current employer expectations in the UK.

Behavioural Interview Questions With Example Answers

What Mistakes Do Candidates Most Commonly Make When Answering This Question?

The most damaging mistake is choosing an example that the interviewer can reasonably interpret as a success dressed up as a failure. Responses like “my only real failure was that I worked too hard and the team struggled to keep up” or “we failed to hit the deadline, but the client loved the final product” suggest a lack of self-awareness rather than genuine reflection. Interviewers have heard these deflections hundreds of times and they consistently report that such answers reduce confidence in the candidate.

A second common mistake is failing to name a specific, personal action that contributed to the outcome. Vague accountability — “communication broke down” or “the timeline was unrealistic from the start” — describes a situation without accepting any ownership. The interviewer is specifically trying to understand how you behave when things go wrong, so removing yourself from the narrative defeats the entire purpose of the question.

Avoiding Emotional Oversharing

Some candidates go to the opposite extreme and share too much emotional detail, describing how stressed or upset they were during the project at such length that the answer loses its professional tone. A single sentence acknowledging the difficulty — “it was a frustrating period” or “I found the fallout hard to deal with initially” — is sufficient. Everything beyond that risks making the interviewer feel uncomfortable or concerned about your resilience rather than reassured by your honesty.

Not Preparing a Failure Example in Advance

Arriving at an interview without a prepared failure example is a structural error. This question, or a close variant of it, appears in the vast majority of competency-based interviews in the UK. Candidates who improvise on the spot tend to either pick an example that is too recent and still feels raw, or one that is so distant and minor that it carries no credibility. Preparing two or three options in advance allows you to choose the example that best fits the role and organisation you are interviewing for on that particular day.

The CIPD guidance on recruitment and selection confirms that competency-based questions, including failure questions, remain one of the most widely used interview formats across UK employers, making preparation for them a practical necessity rather than an optional extra.

What to Say When You Have No Experience in an Interview

In practice, one of the most consistent patterns seen among candidates who answer this question poorly is that they treat the preparation stage as optional. A common mistake is spending significant time rehearsing answers about strengths and achievements while assuming the failure question can be handled spontaneously. The result is an answer that meanders, lacks a clear lesson, and often contradicts itself partway through. Candidates who prepare a structured, rehearsed response — even if they then deliver it in a conversational rather than scripted way — consistently come across as more reflective, more honest, and more professionally mature than those who wing it. Treat this question with the same preparation effort you would give to “what is your greatest achievement?” and it will almost always work in your favour.

Answer Approach	Level of Personal Ownership	Lesson Included	Interviewer Impression	Recommended
Blame shifted entirely to team or circumstances	None	No	Lack of self-awareness	No
Fake failure (success in disguise)	Minimal	No	Evasive and untrustworthy	No
Genuine failure, vague personal role	Partial	Sometimes	Honest but not fully credible	Only if improved
Genuine failure, specific personal action named	High	Yes	Reflective and mature	Yes
Genuine failure, STAR structure, lesson applied later	High	Yes, with follow-through	Confident, growth-oriented, memorable	Strongly recommended

“The candidates who answer failure questions most effectively are not the ones who have failed the least — they are the ones who have reflected the most. Accountability without defensiveness is one of the rarest and most valued qualities in any hire, at any level.”

Frequently Asked Questions

Can I use a failure from outside work like a personal project or university?

Yes, particularly if you are early in your career or the professional example you have does not feel relevant to the role. A university project, a student society initiative, or a voluntary commitment that did not deliver its intended outcome are all acceptable. The key requirement is the same regardless of context: you must be able to name a specific action you took or did not take, explain what you learned from the outcome, and demonstrate how that lesson changed your approach to similar situations afterwards.

How recent does the failure example need to be?

There is no strict rule, but examples from within the last three to five years tend to land better because they suggest the experience is still active in your thinking. Very old examples — more than a decade ago — can imply either that you have not faced real challenges since then or that you are avoiding more recent difficulties. If your most compelling example is older, acknowledge its age briefly and explain why the lesson remains relevant to how you work today.

What if I genuinely cannot think of a project that failed?

Almost every professional has experienced a project that missed its goals, overran its budget, failed to achieve stakeholder buy-in, or simply did not deliver the intended results. If nothing comes to mind immediately, consider smaller-scale failures: a report that needed significant revision, a process you introduced that the team did not adopt, or a client interaction that ended without the outcome you wanted. Failure does not need to be dramatic or high-stakes to be a credible and useful example in an interview context.

Should I mention if the project failure had serious consequences like job losses or financial loss?

You can mention serious consequences if they are relevant and proportionate to the role you are applying for. Senior and leadership roles often require examples of genuine high-stakes accountability, and downplaying a significant failure can seem evasive. However, be careful not to share confidential commercial information or speak disparagingly about former employers. Keep the focus on your own actions, your response to the consequences, and what you put in place to prevent a recurrence. Discretion and professionalism matter even when discussing difficult situations.

Is it acceptable to say the project failed because of factors completely outside my control?

External factors are a legitimate part of many project failures and acknowledging them briefly adds credibility. However, stopping there is not enough. Even when external circumstances played a significant role, interviewers expect you to identify something within your own sphere of influence: perhaps you did not escalate concerns early enough, misjudged the risk, or did not adapt your approach quickly when the external situation changed. Finding your personal contribution, however small, is what transforms