Tell me about a team or project failure you took ownership of.

Question

Accepted Answer

This tests **accountability beyond your own tasks** — owning a shared outcome rather than pointing at others. Use "I" for your actions and "we" for the team, but don't deflect blame.

## How to approach it

```text
1. Describe the failure honestly and your part in it
2. Resist blaming individuals — own the system or the call
3. Explain what you did to recover and to prevent it
4. Show the lasting change
```

## Worked example

```text
S: A feature we shipped tanked a key metric and had to be rolled back.
T: As the senior IC on it, I felt responsible for the outcome.
A: Instead of pointing at the unclear spec, I owned that I hadn't pushed for an
   A/B test. I ran a blameless retro, we added experiment gates for risky
   changes, and I re-launched a tested version.
R: The re-launch moved the metric the right way. Experiment gates are now
   standard for the team.
```

## Good vs weak

```text
✓ Owns the shared outcome, fixes the system
✗ "The PM gave us bad requirements"
✗ Owning so much it sounds like you alone failed
```

## Why it matters

Ownership of shared failures — not just personal ones — is a hallmark of senior behavior.

Fixing the system instead of blaming a person is what actually prevents the next failure.

Leaders look for people who run *toward* problems and accountability, not away from them.