Tell me about a time when you took initiative to solve a problem or improve a situation without being asked
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess whether you notice meaningful problems on your own and take ownership of improving them without waiting for direction. They want to hear how you identified the opportunity, decided it was worth acting on, and carried the work through to a real outcome. At higher levels, they also listen for whether the initiative matched your expected scope and whether you improved a system, not just completed a task.
Key Insights
- You do not get much credit for merely noticing a problem. The real signal is that you framed it, chose a reasonable path forward under uncertainty, and followed through to an outcome.
- Pick an example where the initiative was actually useful, not just extra effort. Interviewers care whether your judgment was good, not whether you like being busy.
- Be explicit about why nobody asked you to do this and how you decided it was worth prioritizing anyway. That is often the hidden core of the question.
What interviewers probe atlevel
Top Priority
Even for a small initiative, show that it actually helped someone or reduced a problem rather than ending at 'I made a thing.'
Good examples
🟢After updating the guide, I asked the next new teammate to use it from scratch and they got through setup without the issue that had blocked me.
🟢I used the small automation over several test runs and saw that it removed the repeat mistakes I had been making before.
Bad examples
🔴I created a setup guide and sent it around; I assume it was useful because nobody complained afterward.
🔴I added a script for myself, and that was basically the end of the effort.
Weak answers stop at output; strong answers verify that the output changed the original problem.
Valuable
Example answers atlevel
Great answers
In my internship, I noticed that getting the app running locally was harder than it needed to be. I lost almost a day on one missing environment setting, and when I asked around, I learned other new team members had hit the same issue. Nobody had assigned this to me, but I wrote down the exact setup steps from a clean machine, found two outdated instructions in our guide, and updated them. Before I shared it, I asked another intern to try the new version from scratch so I could make sure it actually worked. After that, they got through setup without the same blocker, and my mentor started pointing new people to the updated guide.
In my part-time support role at a small e-commerce company, I noticed we were getting a lot of the same customer emails about order status, especially after we shipped on Fridays. I wasn’t asked to do anything about it, but I kept a simple log for a week and saw that most of the questions were caused by people not realizing the tracking email could take a day to go out. I suggested a small change to the order confirmation message and drafted a clearer version that explained when customers should expect updates. I also shared a short note with the team so we could answer those tickets the same way. After we made the change, the repetitive emails dropped, and I liked that I was able to help both customers and the support team without waiting for a formal assignment.
Poor answers
One time I took initiative by reorganizing a bunch of files in our project because I thought the structure was confusing. It wasn't part of my ticket, but I wanted the codebase to look cleaner and more modern. I moved things around and updated some names, then let the team know in chat. It felt good to improve things without waiting to be asked.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late July, 2026
Mid December, 2025
Hello Interview Premium
Your account is free and you can post anonymously if you choose.