In this article
Before you start
This page is one step of the behavioral interview questions guide.
Why interviewers ask this
A mistake you can describe calmly tells an interviewer more than a success story, because success stories are easy to polish. Google's guide to structured interviewing (updated March 2026) says behavioral questions test how a candidate responded to a past situation, and "Tell me about a time you were wrong" applies that to the moment your judgment failed.
Amazon, for example, writes the same trait into its stated values. Its Leadership Principles say leaders are "vocally self-critical, even when doing so is awkward or embarrassing" and that they work to disconfirm their beliefs. Variants of this question are reported by candidates at several large technology companies; those reports are not confirmed by the companies.
A weak answer picks a trivial error or blames someone else. A strong answer names a real mistake, owns its cause and shows a change in behavior. A Staff-level answer also says how you would have caught it earlier.
Admitting a mistake from first principles
- Intellectual humility
- Intellectual humility is a habit of holding a belief only as strongly as the evidence supports and changing it when better evidence arrives. In an interview it shows up as a story where you updated your view without defending it.
- Disconfirming evidence
- Disconfirming evidence is information that would show a belief of yours is false. Looking for it before you act, instead of after something breaks, is the practical form of changing your mind early.
In plain words
Think of a pilot reading a checklist. A good pilot is not someone who never errs. A good pilot is someone who finds an error early, says so out loud and changes the plan. The interviewer wants to hear that you work the same way.
The analogy breaks in one place. A pilot's checklist is written down in advance. Your lesson is something you must show you actually adopted, not only promised.
In one precise sentence: the answer tells a true story in which you held a belief, found it false, took responsibility for the cause, and changed a habit.
A common way to order a spoken answer is situation, task, action, result (STAR). The STAR structure is that order, and the answer here follows it only loosely. Here the "result" is split into the cost of the error and the change you made, because those two parts carry the point.
Step 1: Pick a real mistake with real stakes
Choose a mistake where you made a judgment call and the call was wrong. Input: your past work. Output: one story with a belief, a decision and a consequence someone else could notice.
A real mistake has a cost: lost time, a rollback, a missed target, a worse result for a customer or a teammate. A strong answer shows you were wrong about something that mattered. A trivial slip, such as a typo caught in review, gives the interviewer nothing to probe.
Avoid a disguised strength, such as "I care too much about quality". That is the pattern covered in what is your greatest weakness, and it fails here because the question asks about being wrong, not about a trait. You now have the raw material; the next step is the sentence that decides how it sounds.
Step 2: Own the cause in one sentence
Say what you believed and why it was reasonable, then name the cause as yours. Input: the story. Output: one sentence of the form "the cause was mine: I reasoned from X when the risk was in Y."
The rubric line sits here. A mid-level answer says "the data was wrong" or "the requirements changed". A Staff answer says which of your own reasoning steps failed, such as relying on an average when the failure lived in the tail. The cause is a fact about your judgment, so it carries over to your next job.
Do not apologize at length. One clear sentence of ownership is stronger than three of regret. If someone else also contributed, mention it after you have owned your part, not before. Ownership first is the signal; the context can follow.
Step 3: Show how you found out and what it cost
Describe how the error surfaced, how fast you reacted and what it cost. Input: the timeline. Output: two or three factual sentences with a quantity where you have one.
Say who or what told you: a user, a metric, a colleague, a failed test. Then say what you did first, which is usually to stop the damage before looking for blame. A rollback, a message to affected people or a pause in the launch all count.
State the cost in plain terms: hours, customers affected or a missed date. If you do not remember an exact figure, say "roughly" and give the order of magnitude; never invent precision. An honest "I did not measure it then" is better than a made-up number. Knowing the cost lets the interviewer judge whether the stakes were real.
Step 4: Say what changed afterwards
End with a change in how you work, not a lesson in general terms. Input: what you learned. Output: one habit that you can name and a sign that it held.
"I learned to communicate more" is too vague to check. "Before I ship, I write down what evidence would prove me wrong" is a habit an interviewer can picture and test. If you can add that the habit caught a similar problem later, say so in one sentence.
This is the part interviewers remember, because it predicts how you will act on their team. It also connects to Amazon's stated principle that leaders are never done learning. You now have all four parts; the next section puts them into a spoken answer.
Step-by-step description
- Pick a judgment call that cost something.
- Name your flawed reasoning in one sentence.
- Say how you found out and what it cost.
- End with a habit you can name.
- Choose a real mistake with a visible cost.
- Own the cause in one sentence.
- Show how you found out and what it cost.
- End with a specific change in how you work.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →The Staff-level answer
Tell me about a time you were wrong.
I led the rollout of a caching layer for a search service. I was confident that entries could live for a day, because I had checked the average update rate. It turned out I was wrong, and the cause was mine: I reasoned from an average when the risk sat in the tail.
Updates came in bursts, and during a sale customers saw stale prices for hours. I learned it from a support ticket, not from our dashboards, and I rolled the change back within the hour. Since then, before I ship, I write down what evidence would prove me wrong, and I check the worst hour, not the typical one. My next launch caught a similar gap in review.
The scenario is an invented, illustrative example, not a report of a real person or company. The answer is 120 words; at an illustrative speaking pace of 130 words a minute that is about 55 seconds, just under a spoken target of 60 to 90 seconds (illustrative), which leaves room for a follow-up.1
What makes it Staff-level is the cause sentence and the habit change: it names a flaw in reasoning, not a flaw in luck, and the change is specific enough to be checked.
The words split across four parts: the belief takes 30, the cause 23, the cost 34 and the change 33.1 The cause and the change together take nearly half the words (56 of 120), which is the point of the answer.
Text description of the diagram
- The sample answer is 120 words long.
- It spends 30 words on the belief, 23 on the cause, 34 on the cost and 33 on the change.
Say it in your own words and with your own story. A borrowed story collapses at the first follow-up. If you want to practice the delivery before a round, rehearse it out loud and time it.
The rubric
| Dimension | Weak answer | Strong answer | Staff answer |
|---|---|---|---|
| Choice of mistake | A trivial slip or a disguised strength | A real decision with a visible cost | A real decision where the reasoning itself was flawed |
| Ownership | Blames people, data or timing | Says "I was wrong" and names the error | Names the flawed reasoning step as their own |
| Evidence of discovery | Vague: "it came out later" | Says who or what showed the error | Also says how they would have caught it sooner |
| Change afterwards | A general lesson such as "communicate more" | A specific new habit | A habit plus a later case where it worked |
Three variants of this question
Tell me about a time you disagreed with someone and you were wrong
Use the same four parts, but make the other person's view the one that proved right. Say how you recognized their point, and what you did to credit it. The link to influencing without authority is useful here: being wrong in a disagreement is an influence story in reverse.
Describe a time a major architectural decision of yours turned out to be wrong
Pick a design choice, say what trade-off you accepted and which assumption failed. Add how you walked it back: a migration, a rollback or a staged replacement. The extra Staff signal is that you set up a way to notice earlier.
Tell me about a time you thought you had the solution but were wrong
Stress the moment of confidence. Say what made you sure, which evidence you skipped, and how a test, a colleague or a result showed the gap. The change you describe should be about how you check your own confidence.
Common mistakes
- "Honestly, I can't think of a time I was wrong." (wrong) It sounds either guarded or unaware. (right) "A recent one is a decision where I trusted an average and missed the tail."
- "We were wrong because the requirements kept changing." (wrong) It moves the cause outside you. (right) "The requirements shifted, and I should have asked earlier which one was fixed."
- "My biggest mistake is that I work too hard." (wrong) A disguised strength reads as evasion. (right) "I shipped a change on a belief I had not tested, and it cost us a rollback."
- "I fixed it and we moved on." (wrong) It stops before the learning. (right) "I fixed it, and now I write down what would prove me wrong before I ship."
- Telling a very long story and giving the lesson in a single clause. (wrong) The proportion is upside down. (right) Spend about half your words on the cause and the change.
Follow-up questions
What did the mistake cost, and how did you find out?
Give the cost in real units such as hours, customers or a missed date, and name the signal that showed the error: a ticket, a metric or a colleague. If you did not measure it, say so and give a range.
What if you cannot think of a time you were wrong?
Look at decisions rather than errors: a design you reversed, an estimate you missed, a belief about a user that data overturned. Any of these works if it had a visible cost and you changed a habit.
Can the mistake come from outside work?
It can, if you were responsible, the stakes were real and the lesson carries into a team setting, such as a volunteer project or a study group. Work stories are easier to follow up on, so prefer one if you have it.
Why do you think we should not hire you?
The question about why we should not hire you asks for a real limit and how you manage it, which is close to this question. Name a genuine gap relevant to the role and the system you use to cover it; see why should we hire you for the positive side.
Tell me about a time you thought you were right and you were wrong?
Treat it as the same question: the belief, the evidence that overturned it, the cause as your own, and the habit that followed. The companies' own stated values, such as those summarized in the Amazon Leadership Principles, describe what they want to hear, and the Google behavioral questions guide shows how such answers are judged. For wider coverage see common interview questions.
- Choose a real mistake with a visible cost; a trivial slip or a disguised strength fails.
- Own the cause in one sentence, naming the reasoning step that was wrong.
- Show how you found out and what it cost, in plain units.
- End with a specific change in how you work and, if you can, a later case where it held.
- Keep the answer about 120 words, spending about half on the cause and the change.
Sources
- Leadership Principles — Amazon Jobs (accessed 2026-10-26; page undated), 26 Oct 2026
- A guide to structured interviewing for better hiring practices — Google re:Work (updated March 2026), 1 Mar 2026
