Tell me about a time you stepped up to own something nobody had picked up.
answer
- the gap, and who it hurt
- why you and why then
- who you cleared it with
- what you finished, not started
- where it lives now
basics
~20 sTests initiative plus judgement, not heroics. Name the unowned gap and who it hurt, say how you checked it was yours to take and what it cost you, then give a finished result and who holds it now.
how to answer
5 beats- the gap you noticed and who it was hurtingOpen with the concrete thing nobody was handling and the consequence of leaving it. Keep it to two or three sentences — this is roughly fifteen percent of your airtime, and the interviewer needs only enough to believe the gap was real.
- why you decided it was yours to takeSay who you spoke to before starting and what it would cost. Naming the person who might reasonably have owned it, and your lead who agreed the time, is the beat that turns initiative into judgement.
- what you actually didThe bulk of your airtime, around sixty percent. Walk the specific steps, including how you kept it small enough to finish and where you asked for help. Resist summarising this beat into one sentence about hard work.
- the result, with a numberGive the before and after, and if you can, the second-order effect on the people who were being hurt at the start. One number said clearly beats three approximate ones.
- who holds it nowClose by naming the owner, check or routine that carries it, or say honestly that it faded and why. Then add one sentence on what you would do differently and stop.
your answer
5 story prompts- Pick something genuinely unassigned that you finished, not an assigned task you did well.
- Note who might reasonably have owned it, and whether you spoke to them before starting.
- Write down exactly what it cost you — the work that slipped and who agreed to the slip.
- Find the before-and-after number, plus one effect on the people the gap was hurting.
- This can be the same story as your ownership or initiative answer, re-angled onto the judgement call.
draft and rehearse your own answer in a learn session
go deeper
This probes ownership and judgement together. Interviewers want to see that you notice unassigned work that matters and act on it, but also that you weigh it against your commitments and clear it with the people affected rather than freelancing. The strong answer proves initiative with a finished result, an honest account of what it cost, and an owner other than you at the end.
I was about a year into my first job, on the mobile team at an agency, working on a retail client's Android app. We had just come through a rough patch where the app was failing to finish installing for people on cheaper handsets, and once the hotfix was out everyone went back to feature tickets. While I was digging through the build for that fix, I noticed we were still shipping assets for an onboarding flow the client had dropped two releases earlier: video files, three icon sets, a typeface we no longer referenced anywhere. Nobody was removing them because nobody had spotted them. I did not just start deleting. I asked the engineer who originally built that flow whether anything still depended on it, and I asked my tech lead whether a couple of days on this was a fair trade against my current ticket. Both said yes, and my lead asked me to split it into one pull request per area so reviews stayed quick. It took about six working days alongside my normal work. Fourteen unused video assets removed, the duplicate icon sets consolidated, and a short note added to the repo on how to check whether an asset is still referenced. The download went from 62.4 MB to 47.8 MB. What I am most pleased about is not the megabytes. It is that the next person wondering whether an asset is dead has a two-line answer to read, and install completion on cheap handsets went back to where it had been before that release.
The two conversations before touching anything are what lift this above a keen junior tidying up unprompted — they show judgement about ownership and about time. Splitting the work for reviewability and leaving a note behind are small senior-flavoured touches. Without the number and the finished state, this would read as busywork.
I was the mid-level engineer on a two-squad account at a mobile agency, and this came out of a bad week for a client's iOS app. After their marketing push, the app was getting killed by the OS on older devices and install completion in one region was visibly worse than everywhere else. The incident review closed with a fix and a list of things we should look at. One of them — what belongs in the base install versus what we can fetch afterwards — had no name next to it, and it sat untouched for two sprints. I picked it up, but with the cost visible. I went to both squad leads together and said I wanted a sprint of my capacity for it, that my part of the checkout work would slip by roughly a week, and why I thought that trade was worth making. They agreed, and one of them freed a few hours a week from an engineer on the other squad, which mattered more than my own time did. We moved the locale packs and the tutorial media out of the base install and fetched them on demand, and we added a size line to the release checklist that gets read out before every submission. Base install dropped from 58.1 MB to 34.6 MB, and the weak region came back in line with the others inside two releases. It is not my initiative any more; it is a checklist line and a rota, which is the only reason it survived me moving accounts.
The middle-band signal is the negotiated trade said out loud — capacity requested, the slip named, the reasoning offered — rather than quietly absorbing the work. Borrowing a few hours from another squad and landing the change into an existing routine are what make it stick. Hiding the cost would downlevel it immediately.
A small, concrete gap is exactly right here — a cleanup, a broken script, a missing check. The signal is that you asked before you took it and that you finished it, not that it was ambitious.
Feature-sized scope, and the trade-off should be explicit. Show that you weighed it against committed work, negotiated the slip openly rather than absorbing it, and pulled in a peer or two where you needed them.
The gap should be one that carried real risk to the team or to production. Show that you sized that risk before spending team capacity, made the spend visible to whoever owns the roadmap, and left a named owner behind you.
Name the class of unowned work, not the single instance, and the mechanism that stops it accumulating. Equally important is what you declined to pick up, and why picking up everything would have been the worse choice.
saying these in an interview costs you the question
- Claiming work was unowned when it plainly belonged to someone you never spoke to
- Starting a rescue without telling anyone, then presenting it as a fait accompli
- A story about starting something, with no evidence it ever reached done
- Framing it as heroics — late nights and rescue — instead of judgement about what was worth doing
- No sense of cost: committed work quietly slipped and the answer never mentions it
- Choosing something so trivial that no judgement or trade-off was involved
- What did you have to drop to make room for it?Answer honestly with a specific trade. Saying nothing slipped invites doubt unless the work was genuinely small. Better: name what moved, say who you told before it moved, and confirm the person affected agreed. Absorbing the cost silently by working evenings is the answer to avoid — it reads as poor judgement rather than commitment.
- Did you check with anyone before you started?Say who and what you asked. The strongest version includes a conversation with whoever might reasonably have felt ownership, plus your lead for the time. If you did not check and it caused friction, say that and say what you now do first — a candid correction scores better than a clean story nobody believes.
- How did you know it was actually worth doing?Point at the evidence you had at the time, not the outcome you know now. A recurring incident, a support thread, a number you could see trending. Show you had a rough sense of the cost of leaving it alone before you spent time on it, and that you were willing to be told no.
- Who owns it now?Name the person, rota or automated check, and describe the handover in a sentence. If it decayed after you moved on, say so and name the reason — no owner, no check, no place in an existing routine. Learning why it did not stick is a legitimate and often stronger ending.