Why interviewers ask about initiative
Initiative questions test whether you act on your own judgment or wait to be told what to do. Employers want people who identify problems and opportunities without being prompted and take action within their authority to address them. The question distinguishes candidates who are reactive (do what they are asked, well) from those who are proactive (find the things that need doing and do them). For roles where ownership and self-direction are expected, this question is a key differentiator.
How to structure your answer
The strongest initiative examples have three elements: you identified something that was not your assigned responsibility, you judged it was worth acting on, and you took action that produced a positive result. The "not your responsibility" part is key — doing your assigned work well is not initiative; going beyond it is.
Strong example: "Our team had a spreadsheet-based reporting process that was taking each team member about two hours per week and producing inconsistent formats. No one had been asked to fix it — it was just an accepted inefficiency. I spent a weekend building a Google Sheets template with automatic formatting and formulae that pulled from our shared data source. I documented how to use it, shared it in our team channel, and offered 10-minute walk-throughs for anyone who wanted one. The reporting process now takes 20 minutes per person per week. My manager used it as a case study in our team retrospective."
Common mistakes to avoid
Too small: "I noticed the coffee machine was empty so I made a new pot." Initiative at this level does not differentiate professional candidates. Not actually initiative: Describing something you were asked to do and did well. Too much detail on the task, not enough on the judgment: The interesting part is why you decided to act and what you risked by doing so (time, political capital, potential to look like you were overstepping). Include that reasoning.
More example scenarios
Good initiative examples by context: spotting a client at risk of churn before they raised it and proactively reaching out; finding a process inefficiency and fixing it without being asked; learning a skill the team needed before the project required it; surfacing a product bug you found while doing unrelated work; proposing a new way to onboard customers after observing friction in the process. The common thread: you saw something, judged it was worth acting on, and acted.