Tell Me About a Time Something Went Wrong and You Took Responsibility
The question: "Tell me about a time when something went wrong in your work and you had to take responsibility for it. How did you approach this situation?"
Also asked as: "When has something gone wrong that wasn't entirely your fault? What did you do?" · "Tell me about a failure with other people involved. What was your part?" · "What did you do the last time your team's mistake reached someone senior?"
Who's asking: an Engineering Director or Senior Engineering Manager, in a behavioral round.
Executive Summary: Most failures have more than one author, so the director is deciding whether you'll stand in front of a problem without blaming anyone and without playing the martyr. What grows with level is who else has a share: a teammate, an engineer you lead, other teams, then other organizations, and sometimes the public.
What the director is really asking
Other failure questions ask what you learned. This one asks what you did when you could honestly have pointed somewhere else. A director is screening out three answers:
- The blamer. Every fact is accurate, and each one ends on someone else.
- The martyr. "It was all on me." It sounds noble and it's usually false: it hides causes that then stay unfixed, and it takes the other person's part away from them.
- The fog. "Mistakes were made." "We dropped the ball." Nobody in the story did anything.
They want what sits between those: your share, in proportion. They listen for:
- The share. What was yours, in one sentence, and what wasn't. The test: could you say it with the other person in the room?
- The words. What you said, to whom and when. Standing in front of a problem happens out loud, usually before you know the whole story.
- What you left with others. Their part stays theirs, stated as fact. You don't hide it to look generous, and you don't lead with it to look innocent.
The decision it feeds: "when something breaks on their watch and someone senior calls, will they stand in front of it, and will I get the true account?" It maps loosely to Amazon's "Ownership" and "Earn Trust"; both approximate. It turns on ownership, "I" vs "we" and conflict.
Level fit at a glance
| SDE | Senior SDE | Staff | Principal | |
|---|---|---|---|---|
| Asked at this level? | Common | Common | Common | Common |
| Story scope they expect | A bug in your team's code, with a teammate's name on it too | A failure in your team's system, with someone you lead at the centre | A failure across teams, each with a case against the others | A failure across several orgs, sometimes public, and your direction among the causes |
| The bar in one line | Say what you touched first, and leave your teammate their part | Stand in front of your engineer outside the team, and let them own it inside | Put your share on the table first, so others can name theirs | Price your direction's share, keep the others' shares honest, leave a check someone else runs |
| Instant down-level | "It was my teammate's change. I only reviewed it." | "I took full responsibility and fixed it myself." | "I got the teams in a room and found out whose bug it was." | "A supplier changed its codes. We corrected it and moved on." |
All four are Common, not Core: the plain mistake question is the one in nearly every loop. Senior gets this as "your team's failure reached someone senior", Staff inside a cross-team incident, Principal as a direction gone wrong.
SDE: say what you touched, then leave your teammate their part
What meets the bar
- A failure in your team's code with another name on it too, and a real part of your own.
- You said your part out loud, without being asked.
- The other person kept their part. You didn't blame them or take the fix from them.
- Check your altitude: "my lead sorted out who did what" reads below the bar. If you changed how the team runs reviews, it reads as Senior.
Model answer
"A subscriber with a 412-day meditation streak finished a session on a Sunday night, and our yoga app said, 'Day 1. Great start.' I was about two years in, on the five-person team behind practice tracking. That Friday a teammate had shipped a change counting streak days in UTC instead of local time, and I'd reviewed and approved it. Most of our subscribers are in the Americas, where a Saturday-morning session followed by a Sunday-evening one now skipped a day, and weekends are when people move their practice around.
Support put the screenshot in our channel at 8:10 on Monday. I looked at recent changes and posted, 'Looks like Friday's time-zone PR,' tagging my teammate. It was accurate. It also tagged only them, they weren't online yet, and my approval sat at the bottom of that same page. The description said 'tested in UTC'. I'd read the logic and never asked what happened across a local midnight.
Ten minutes later I posted again: 'I approved that change and didn't test it across a day boundary. I'm pulling the affected list and writing the restore.' Then I called my teammate before they could read the channel, told them what I'd posted both times, and asked if they wanted the fix. They did, and it was theirs.
My lead asked me afterward whether this was on me or on them. I said they'd written the bug, I'd been the check and missed it, and our test suite only ran in UTC, which predated us both.
My teammate reverted it by nine, the proper fix shipped Tuesday morning, and that afternoon my script restored about 3,400 streaks from session history. Support handled about 170 tickets, about 30 people cancelled that month and named it, and my own ticket slipped a week. I added three time zones to the streak tests, and they caught a streak-badge change two months later. When something breaks, the first thing I type now is what I touched, before any link to anyone's change."
Why this lands at SDE
- "they'd written the bug, I'd been the check and missed it": the line only an SDE would say. Each share in a clause, and the scope stays in one team's code.
- "It was accurate": the link was good triage. Tagging one of two names was the miss, and catching it in ten minutes is the story.
- "it was theirs": no rewriting the fix to look good, which keeps this from being the martyr's version.
Follow-ups to expect
- "You'd already posted it. What did they say on the call?": the most dangerous one → say what they actually said, and don't shrink it.
- "So whose bug was it?": tests the split → the three parts, in one sentence.
- "How did you decide when to bring your lead in?": tests escalation → straight away, because users were affected.
Red flags
- ❌ "I only reviewed it." Reviewing is a job, and you did it.
- ❌ "It was really all my fault for approving it." Your teammate wrote it, and the director can see that.
Senior SDE: outside the team it's yours, inside it's theirs too
What meets the bar
- A failure in a system your team owns, with someone you lead at the centre of it.
- You took the outside call yourself and kept their name out of it.
- Inside the team, they still owned their part, and did the fixing.
- The line: a name can stay with the people who can act on it; causes go to everyone who must fix them. If anyone who must fix this, or manage this person, believes something false, you've crossed it.
- The team's process changed, not only your habit.
- Check your altitude: a story about your own bug reads as SDE. If you aligned several managers on a change across teams, it reads as Staff.
Model answer
"The head of store operations called my cell at 9:40 on the first snow Saturday and asked who had done this. I'm the tech lead on the six-engineer team behind appointments at a tire-shop chain with about 160 locations. On Thursday we'd launched 30-minute express swaps, and the booking check was letting them overlap with hour-long jobs in the same bay. Customers were lined up at shops with bays promised twice.
An engineer on my team, in their second year, wrote that check. I'd estimated the ticket at two days and waved off a design review because of the season. On the call I said, 'It's my team's system. You'll get me, not a name, and I'll call you at noon with how many shops.' I'd say that again. I told our manager before noon.
Then I overdid it. We had express booking off by eleven. I told the engineer to take the weekend, rewrote the check myself on Sunday, and wrote the review with one cause: my design miss. On Monday the engineer saw their code was gone and asked our manager whether they were being managed out. Our manager asked me what else I'd left out: the missing tests, my skipped review, and a marketing email nobody told us about, which tripled Friday's express bookings. That review was inaccurate, and with one cause and my name on it, we'd fix none of those.
I told the engineer I'd taken their code to cover my own call. We rewrote the review. The engineer took the overlap section, presented it to the team, and reworked the check with tests. I kept the estimate and the skipped review. I took the email to the marketing lead, and launches and campaigns now share a calendar. Outside the team the failure stayed mine, and the name never left.
Store operations gave about 1,400 customers $25 off, $35,000, and got the corrected causes. Express came back the next Thursday and took about a fifth of bookings for the season, with no overlaps from the code. On my team now, whoever wrote the change drafts the review's first page and presents it to us, and the lead takes the calls. Two reviews have run that way since."
Why this lands at Senior SDE
- "Outside the team the failure stayed mine, and the name never left": the line only a Senior would say. It's their system and their engineer, with one adjacent lead and no managers to align.
- "That review was inaccurate": the wrong turn after the right move. Keeping the name back was fine; one false cause to our manager wasn't, and left three causes unfixed.
- "whoever wrote the change drafts the review's first page": the team's process changed, which is the Senior ending.
Follow-ups to expect
- "If I called that engineer, what would they say about how you handled it?": the most dangerous one → both halves: the phone call, then the Monday they feared for their job, and what you said to them.
- "What if the head of operations had insisted on the name?": tests where you'd hold → you answer for the system; the name is your manager's to handle.
- "When did your manager know, and what did they say on Monday?": tests whether they ever had a false picture → Saturday; and that the review you gave them was wrong.
- "Your manager had to ask what you'd left out. Would you have found it yourself?": tests honesty about the correction → maybe not that week. Say so.
Red flags
- ❌ "I rewrote it over the weekend so my engineer wouldn't have to." Told as a virtue, that's the wrong turn, unnoticed.
- ❌ "Nobody above me ever knew who wrote it." That's concealment, not protection.
Quick check before moving on:
Staff: your row first
What meets the bar
- A failure across several teams, where each team had a real case, and so did you.
- You named your own share first, which made the page possible. What moved each manager was their own objection answered.
- You didn't end it by taking it all, which would have left real causes in place.
- "I" is the framing and the alignment; the teams built the fix. Friction: who said no first.
- Check your altitude: running one team's incident well reads as Senior. A funded direction priced in business terms reads as Principal.
Model answer
"For two weeks, three teams each had a document proving the bad work orders were someone else's, and I was reading all three. I'm a staff engineer at a natural-gas distributor, with no reports. After an asset-ID migration I'd planned, about 4 percent of our 5,000 scheduled work orders a week sent a crew to the wrong service line. Emergency calls go by radio and weren't touched; scheduled leak surveys were, with regulatory due dates.
Mobile said scheduling sent bad records. Scheduling said the mapping team's IDs had changed. Mapping said its export met the spec and mobile's cache was stale. All true. Our director asked me to find out whose it was, and I took that as the job. My plan said consumers would update by cutover, not who translated IDs in between. I was acting as referee, and I was one of the parties.
I finally told the director it was the wrong question and I was in the answer. I sent the three managers one page with a row per team, mine first: the plan's gap, and two weeks of letting the argument run. Calling it all my plan's fault would have ended it by Friday, and mobile's cache, with no expiry, would have broken the next migration. I put one line of fact in each other row for its manager to rewrite.
The scheduling manager said no first: that row could follow the team into the compliance review. I asked our compliance lead, who confirmed the filing would report late surveys, not teams, and the manager rewrote the row more bluntly than I had. Mobile's manager gave up a month on an offline-forms release to rebuild the sync, stale cache included.
The teams built a shared mapping table in three days, work that never depended on whose fault it was. First report to fix took three weeks: about 600 bad orders, about $110,000 in truck time, and 14 late surveys, which compliance self-reported, with no fine. Two of those weeks were the argument. Bad orders fell below 0.2 percent. Our migration plans now name who translates IDs at cutover, and the meter migration used that. On a cross-team problem I write my own row first and send it that week."
Why this lands at Staff
- "I was acting as referee, and I was one of the parties": the line only a Staff engineer would say. No authority, three teams, and a share only they could name.
- "Calling it all my plan's fault would have ended it by Friday": the martyr's exit, named and turned down, with the reason.
- "The scheduling manager said no first": the alignment had friction, and a fact moved the manager, not rank.
Follow-ups to expect
- "Crews drove to wrong addresses for two weeks. What were you doing?": the most dangerous one → don't defend it. You told yourself evidence would settle it, and you had a reason not to read your own plan. Then the cost.
- "Why was this yours?": tests whether the gap was real → you'd written the plan, and you could see all three teams.
- "How did you get the other managers to agree?": tests influence without authority → what the scheduling manager feared, who could answer it, and why mobile's manager gave up a month: their cache would break the next migration too.
- "How did your director see it?": tests how you carry it upward → what they said when they read it, including that two weeks was long.
Red flags
- ❌ "I got everyone in a room and we found the root cause." That's incident leadership. Where's your share?
- ❌ "All three teams were at fault, and I brought them together." You've left yourself out.
Principal: price your direction's share, and leave a check
What meets the bar
- A failure beyond any one org, with a direction you own among the causes.
- Your seat is plain: the technical direction and one engineering fact are yours, and you can say what belonged to the people who decide.
- You said it where it counted, and left the others' shares with their owners.
- Net, in business terms, then a mechanism someone else runs, and has used.
- Check your altitude: several teams with no funded direction at stake reads as Staff. Speaking for the institution with no technical call of your own reads as a spokesperson.
Model answer
"The first draft of the correction notice said our retail sales figure was wrong 'owing to a change by a data supplier'. That was true, and it left out my part. I'm the principal engineer for statistical production at a national statistics office. The platform's direction is mine, method is the chief methodologist's, and the chief statistician signs what gets published.
The direction was a four-year, $40 million, ministry-funded move from costly surveys to administrative and card-payment data, saving about $11 million a year. My plan ended parallel surveys once the series tracked closely. For retail sales, I argued for 12 months rather than 24, saving $4 million. Methodology signed it and the chief statistician approved. After that, the check I'd specified compared each month with the last, and a slow drift passes that test every time.
Five months later the card supplier began recoding marketplace merchants in batches, so a growing share of their sales counted twice. Its bulletin went to a mailbox my team didn't watch. Seven releases read high, ending at 3.1 percent annual growth against a true 2.3. National accounts caught it when VAT receipts wouldn't reconcile. My team traced it in two days, and the correction went out before the next release.
In the chief statistician's meeting, everyone had a sound case: supplier changed, methodology signed, pipeline passed. I said ending that survey was my proposal, and it's why nothing saw this sooner, and I asked for a second sentence in the notice saying we'd ended a comparison early. Communications objected that it handed a parliamentary committee its question. The chief statistician kept it, and took that question two weeks later. I didn't claim it all: procurement rewrote the supplier's change-notice terms, and methodology its sign-off.
My $4 million saving cost more. The ministry held the next $9 million for nine months, so the labour survey we were replacing ran on, about $4.5 million, and I proposed a benchmark sample at $1.5 million a year. Payback went from under four years to over four. My team built the check against that sample. Methodology owns it and can hold any release without asking engineering. Last spring it held one when a grocery feed diverged."
Why this lands at Principal
- "ending that survey was my proposal, and it's why nothing saw this sooner": the line only a Principal would say: the direction's share, in the room where shares were being set. Five months plus seven releases falls inside the year the survey would have run.
- "the check I'd specified": a slow drift passes it, and that engineer's fact keeps this from reading as a spokesperson's story.
- "My $4 million saving cost more": net and unflattering. Be ready to show it: $4.5 million once and $1.5 million a year. Payback was $40 million over $11 million, then $40.5 million over $9.5 million, counting the $4 million you saved.
Follow-ups to expect
- "Methodology signed it and the chief statistician approved. Are you taking too much?": the most dangerous one → no. You made the case they signed, and that part is yours. Their sign-off process was theirs to change.
- "What did you personally decide or build?": separates the engineer from the spokesperson → the survey argument, the check you specified, and what it compares with now.
- "Who relied on that figure?": tests whether you priced the harm or only the program → the small GDP revision (0.8 points on a sector near 6 percent of output, about 0.05), and who was told first.
- "What mechanism outlived your involvement?": tests whether it outlasts you → the benchmark, who owns it, and the grocery feed it held.
Red flags
- ❌ "The supplier changed its codes without telling us." It did tell you, in a bulletin your team didn't read.
- ❌ "I took full responsibility and offered to step down." That's the martyr at altitude, with the contract and the sign-off left as they were.
Quick check before moving on:
One story, four altitudes
| SDE | Senior SDE | Staff | Principal | |
|---|---|---|---|---|
| Situation | 412-day streak shows Day 1 | Bays double-booked on the first snow Saturday | Three teams, three documents, 4% bad work orders | A national figure wrong for seven releases |
| Your share | Approved it without testing a day boundary | The estimate and the skipped design review | The plan's gap, and two weeks as referee | Proposed ending the comparison survey early |
| What you said, to whom | "I approved that" to the team channel | "You'll get me, not a name" to the head of operations | Your row first, to three managers | "It's why nothing saw this sooner" to the chief statistician |
| Result | 3,400 streaks restored; about 30 cancellations | $35,000 in credits; express back in five days | About $110,000 and 14 late surveys; a three-day fix | $4M saved; $4.5M spent, plus $1.5M a year |
| Reflection | Type what you touched first | The author drafts the review; the lead takes the calls | Your row first; plans name who translates | A benchmark methodology owns |
Draft your answer
Step 1: Pick the right story
- SDE: Is there another name on it, and did you write, review, test or ship something that mattered?
- Senior SDE: Was it your team's system, with someone you lead at the centre, and did you handle what reached the outside?
- Staff: Did at least two teams have a case against each other, did you have a share, and did their managers change something because of you?
- Principal: Was a direction of yours among the causes, with other orgs in it, and can you price your share and name a check someone else runs?
Then:
- You could honestly have pointed elsewhere. If nobody else had a part, save it for a mistake question.
- You can say your share in one sentence, with the other person in the room, and quote what you said.
- It's from the last three years, and there's a number.
You don't need a disaster, and your share can be small. A small bug where you said what you touched before anyone asked is a strong story. If your part was small, say so. Inflating your share to seem accountable is as false as hiding it.
If you're a new grad. A group project, a hackathon team or a shared research lab works if someone else really had a part and the damage reached past you: a teammate's grade, a demo that died in front of judges. The stakes can be small. The director still wants your share in one sentence, what you said and what you left with others. "Two of us had touched the merge script that wiped our lab's shared results folder."
Aiming a level above your current title? Tell your own-level story honestly and show you see the next one. A Senior aiming at Staff tells the tire-shop story and adds: "The email and our launch shared no calendar. Next time I'd take that gap to the marketing and store-operations managers, my team's part first, before the season."
Step 2: Fill the skeleton
WHAT WENT WRONG (15s) — What someone saw, and your role: ______
YOUR SHARE (15s) — One sentence you'd say with them in the room: ______
WHO ELSE HAD A PART (10s) — The people or teams, as facts, not verdicts: ______
WHAT YOU SAID (20s) — The words, to whom, how soon; and the first thing you
got wrong, if you did: ______
WHAT YOU LEFT WITH OTHERS (10s) — What stayed theirs, and why you didn't take
it: ______
LEVEL BEAT (wherever it falls; say it once): ______
SDE: what you touched, said before anyone asked.
Senior: yours outside the team, and theirs too inside it.
Staff: your row first, and who said no to theirs.
Principal: your direction's share, priced, and who decided.
WHAT YOU DID NEXT (20s) — The fix, and who did which part: ______
RESULT (20s) — The number, net, including what slipped: ______
NOW (10s) — What changed, and one time since: ______
Step 3: Calibrate it
| If your answer says… | It reads as… | Fix |
|---|---|---|
| "I took full responsibility" and nothing specific | The martyr, or a slogan | One sentence on what was yours, and one on what wasn't |
| Thirty seconds of context that clears you | Blame, however accurate | Say your share before the context |
| A Senior answer: "I fixed it myself so my engineer wouldn't have to" | Covering, and a team that doesn't learn | What they owned and did |
| "We dropped the ball" | The fog | Who did what, starting with you |
Step 4: Rehearse the follow-ups
Say each of these out loud once:
- "If I called the other person, what would they say about how you handled it?" The one to prepare first. Include the unflattering part; if you don't know, say what you'd guess.
- "So whose fault was it?" Your share first, then theirs as fact, with no verdict on anyone.
- "Are you taking too much of this?" What was yours, and what you deliberately left with its owner.
- "What exactly did you say, and to whom?" The words, and how soon.
- "What did it cost, and what changed?" Net, with something that has happened since.
Common mistakes
- Confusing protection with concealment. Keeping a name back can be right; a false cause never is.
- Confessing to what wasn't yours. A director will simply ask who else was involved.
- Verdicts about colleagues. "The PM should have caught it" is a verdict. "The PM saw it Tuesday" is a fact.
- Stopping at the apology. Owning it without fixing anything isn't owning it.
Key takeaways
- It tests whether you'll stand in front of a problem without blaming anyone, playing the martyr or hiding in "we".
- A strong answer has your share, your words and what you left with others.
- As the level rises, more people have a share; keep yours in proportion.
Test yourself on this question's key ideas: