Tell me about a time you took initiative: example answers
Describe a problem you noticed that wasn't assigned to you, show that you checked it was worth fixing and told the right person, then say what you did and the measurable result. A good initiative story proves you act without being asked, but not behind anyone's back.
What the interviewer is looking for
Initiative means doing something useful that wasn't on your list. Employers ask because they want people who notice problems and act, instead of waiting for instructions. But they also worry about the opposite: the person who changes things without telling anyone.
So the strongest stories show four things:
- You noticed. Something was slow, broken, wasteful or missing, and nobody had asked you to look at it.
- You checked. You confirmed it was a real problem and that it was okay for you to fix it.
- You acted. You did the work, often on top of your normal job.
- It mattered. Time saved, errors cut, customers kept, money saved, or a habit that others now follow.
Step 2 is what separates initiative from going rogue. One sentence is enough: "I asked my manager if I could try fixing it."
Initiative versus "above and beyond"
These questions sound similar but want different stories.
| Question | What it rewards | Typical story |
|---|---|---|
| Took initiative | Spotting a problem nobody assigned | You built a checklist because orders kept going wrong |
| Went above and beyond | Extra effort for a customer or colleague | You stayed late to finish a client's order |
| Showed leadership | Getting other people to move | You organised the team around a shared goal |
For initiative, the key word is noticed. If your story starts with "My manager asked me to…", it's not an initiative story.
Where initiative stories hide
If nothing comes to mind, think about these:
- A spreadsheet, template or checklist you made that others now use.
- A recurring complaint from customers that you traced and fixed.
- A task you automated or simplified.
- Training you gave a new starter without being asked.
- A risk you spotted and flagged before it became a problem.
- Something you learned on your own because the team needed it.
Small is fine. A one-page guide that saved new starters a day of confusion is a good story.
Example answers
These examples use invented details to show the shape. Swap in your own.
Administrative assistant
"Our office booked meeting rooms through a shared calendar, and about once a week two teams turned up for the same room. It wasn't my job, but it kept landing on my desk. I looked at the last month of clashes and saw nearly all of them came from people booking by email instead of the calendar. I asked my manager if I could try a fix. I wrote a half-page guide, put a QR code to the calendar on each room door, and sent a short note to team leads. Clashes dropped to about one a month, and the facilities team now uses my guide for new starters."
Warehouse associate
"On my shift, we kept losing ten or fifteen minutes at the start because pickers were waiting for scanners to charge. Nobody had been asked to sort it. I checked with the shift lead that I could change the charging routine, then started plugging the scanners in during the last half hour of the previous shift and labelled each one with a number. That gave us back the start-of-shift time, and my lead asked the other shifts to do the same."
Marketing graduate
"In my internship, I noticed our social media team answered the same five product questions in comments every week. I wasn't on that team, but I asked the social lead if a quick reply library would help. I collected 30 recent questions, drafted short answers, and had the product team check them. The social team said it cut their reply time roughly in half, and they kept using it after I left."
Software developer
"Our test suite took around 25 minutes to run, so people often skipped it before merging. I wasn't assigned to it, but I spent a few Friday afternoons looking into why. Three tests were creating full test databases from scratch. I raised it in our team channel, got a thumbs up from my lead, and changed those tests to share one setup. The suite dropped to about 9 minutes, and skipped test runs became rare."
Make the result specific
The result is where many initiative stories go flat. "It helped a lot" doesn't land. Try one of these:
- A time number: "saved about an hour a week."
- A count: "errors went from four or five a week to one."
- A spread: "the other two shifts adopted it."
- A lasting effect: "it's still part of onboarding."
Only use numbers you can stand behind. "About" and "roughly" are fine.
Mistakes to avoid
| Mistake | Why it hurts | Instead |
|---|---|---|
| Acting without telling anyone | Sounds like you ignore your manager | Mention a quick check before acting |
| Fixing someone else's work without asking | Sounds like you step on toes | Show you involved the owner |
| Taking credit for a team effort | Follow-ups will expose it | Say "I started it, and two colleagues helped" |
| A story where you were asked | It's not initiative | Start with what you noticed |
| Neglecting your main job | Initiative shouldn't cost your core work | Say when you did it, if it was on top |
Questions people ask
Can I use an example from school or volunteering?
Yes, especially as a graduate. Starting a study group, fixing a club's sign-up process, or organising a fundraiser all count, as long as nobody asked you to do it.
What if my manager didn't like what I did?
That story can still work if you show what you learned about checking first. Focus on how you put it right. If it ended badly, it may fit better as an answer about a mistake.
How long should the answer be?
About a minute. Spend most of it on what you noticed and what you did, then land the result in one clear sentence. Practise it out loud and time yourself with the interview answer review.
Do I need a result with a number?
It helps a lot, but an honest qualitative result also works, such as "it's still used for every new starter." Don't invent figures.
What if my job doesn't allow much initiative?
Look for small things: a better way to hand over a shift, a note that saved a colleague time, a question you asked that caught an error. Initiative in a structured job is often about noticing.