Tell me about a time you took ownership of something that was not explicitly assigned to you.
- Technology:
- Behavioral
Quick answer
Describe a problem you noticed, why you decided to act, how you coordinated with others, and the impact of taking ownership.
What the interviewer is evaluating
- Initiative
- Ownership
- Judgment
- Collaboration
How to structure your answer (STAR)
- Situation: the unowned problem.
- Task: what needed to happen.
- Action: how you took ownership safely.
- Result: improvement and team impact.
Example answer
I noticed our service had no clear runbook even though engineers were repeatedly asking the same questions during incidents.
I gathered the existing knowledge, drafted a short runbook, asked the on-call engineers to review it and linked it from the incident channel.
New responders could handle common issues faster, and the team later expanded the runbook into our standard incident documentation.
Discussion
This question separates people who only complete assigned tickets from engineers who notice and solve important problems.
Do not describe work you simply volunteered for without explaining why it mattered to users, reliability, delivery or the team.
Show initiative without suggesting that you ignored ownership boundaries or other people.
Key points
- Identify an unowned problem
- Explain why it mattered
- Coordinate before changing shared systems
- Show impact
Common mistakes
- Taking credit for team work.
- Changing shared systems without communication.
- Choosing an unimportant task.
Follow-up questions
- Why did you decide to act?
- How did you get others involved?