‹ Field Notes
Ownership

Uber cut 3,300 jobs and promised “clearer ownership”. The question that tests for it.

On September 2, 2026, Al Jazeera reported that Uber was laying off 3,300 employees — about 10 percent of its workforce — in its largest cuts since the pandemic. Inside the announcement was a smaller, stranger detail: the company said it would halve the number of "micro-teams" in which managers have only one or two direct reports. Chief executive Dara Khosrowshahi framed the result this way: "A leaner organisation will mean clearer ownership, faster decisions and more time spent building rather than coordinating."

Read the promise on its own terms. Coordination is not being deleted; it is being moved. When a management layer is removed, the work that layer did does not evaporate — the status chasing, the cross-team unblocking, the decision that used to get escalated. It lands on whoever is still standing next to it. That is what "clearer ownership" means in practice, and it is why a phrase from a layoff announcement is also, exactly, an interview question.

The interview question
Tell me about a time when you took ownership of a project you weren't originally responsible for.

Why they ask it

Every organization has work that belongs to nobody. A service with no on-call rotation, a migration half-finished by a team that reorganized, a dashboard everyone reads and no one maintains. Companies do not run out of orphaned work; they run out of people who pick it up before it becomes an incident.

So the question is a test of initiative, but not the poster version of initiative. The interviewer is checking whether you can distinguish work that genuinely needed an owner from work that already had one. The first is ownership. The second is territorial, and at senior levels it is the more common failure — it reads as someone who cannot stay in their lane, and it costs the organization more than the gap it filled.

The trap

The weak version of this answer is the volunteer story: "Nobody was handling releases, so I started handling releases." Told without a before and after, it grades as busywork. You did more; the interviewer cannot tell whether it mattered.

The weaker version is the rescue story with a villain. "The other team dropped it, so I stepped in." Every sentence spent on their failure is a sentence not spent on your judgment, and it invites the interviewer to wonder what your former colleagues would say about the same events. You can describe a gap without prosecuting the people near it.

Both share a tell: no one ever agreed you should own the thing. An ownership story where the ownership was never made explicit is a story about doing extra work.

Applying STAR-T

Situation. Name the orphaned work and the cost of it staying orphaned. "Our schema migration stalled when the data team reorganized — half the tables were converted, and every new feature had to write against both shapes." The cost is what makes it worth owning; without it you are describing a preference.

Task. Be honest that it was not yours. That is the premise of the question, and candidates skip past it because it feels like an admission. It is the opposite: "It wasn't my project and it wasn't in my quarter" is what makes the rest of the story load-bearing.

Action. Two verbs, in this order. You made the ownership explicit: took it to the people who would have been accountable, got an actual yes, and put your name on it somewhere durable. Then you did the work: finished the migration in a defined scope, with a date, and a written definition of finished. The order matters more than either half. Acting first and telling people afterwards is the territorial version, and interviewers hear the difference immediately.

Result. Land it in numbers if you have them, and include the handoff. "We finished the remaining forty tables in six weeks, deleted the compatibility layer, and I handed the runbook back to the data team with two of their engineers trained on it." Ownership that ends in permanent ownership is not a success story; it is how a person becomes a single point of failure.

Trade-off. Say what it cost. "My own roadmap slipped a sprint, and I cleared that with my manager before I started, not after." A candidate who names the price and who agreed to pay it is describing a decision. A candidate who implies they absorbed it for free is describing a myth.

The follow-up that breaks weak answers

Expect "how did you decide it was yours to take?" This question is aimed precisely at the line between ownership and encroachment, and it is very hard to answer after the fact.

A strong answer already contains the check: "I asked the two people it could plausibly have belonged to whether they were picking it up. Both said no and said so in writing, and I took it from there." That is a candidate who understood the difference in the moment. The alternative — "it obviously needed doing" — is the answer of someone who has never had that conversation, and interviewers who have managed a team have watched what happens next.

Score your answer against the director’s bar

Q: Tell me about a time when you took ownership of a project you weren't originally responsible for.

Ready when you are

Bank an ownership story where someone actually agreed you should own it, and rehearse it in L8 Loop until the handoff lands as clearly as the rescue. Try it free →

Go deeper
Rehearse this in L8 Loop →