How to Answer 'Tell Me About a Time You Showed Initiative'
What "Initiative" Actually Means Here
The showed initiative interview question is more specific than it sounds. Candidates often answer it with a story about working hard, taking on extra tasks, or volunteering to help. Those aren't wrong — but they're not initiative.
To an interviewer, initiative means: you identified a problem or opportunity that wasn't assigned to you, decided to act on it, and drove a result that wouldn't have happened without you.
Three elements all need to be present:
- Unassigned — nobody told you to do this
- You decided — you judged it was worth doing and took ownership
- It produced a real outcome — not just an attempt, not just effort
A story about working late to finish an assigned project is hustle. A story about noticing a process was breaking the team's workflow, redesigning it without being asked, and shipping the fix to production — that's initiative.
Why Candidates Struggle with This Question
Two problems come up repeatedly:
Problem 1: The story is actually the team's story. "We noticed that our deployment process was slow so we built a CI/CD pipeline." Who is we? What did you specifically notice, decide, and do? If you strip out everything your teammates contributed, what's left? That's your answer — and it needs to be substantial.
Problem 2: The story is about doing your job well. Completing your assigned work on time, attending an extra meeting, or picking up a task when your manager was out — these are responsibilities, not initiative. The bar is: would something have gone undone or unmissed if you hadn't stepped in?
How to Structure the Answer
Use STAR, with specific attention to the "why I decided to act" moment:
- What you noticed — What was the gap, problem, or opportunity? How did you identify it?
- Why you decided to act — What made you think it was worth pursuing? Was there any friction to taking ownership (not your area, risky, time-consuming)?
- What you specifically did — The steps you took, the decisions you made
- What resulted — The measurable or observable outcome
The "why I decided to act" moment is often missing from these answers — and it's the one that shows judgment, not just action.
Bad Answer
"I took a lot of initiative at my last job. I was always the first to volunteer for new projects and I wasn't afraid to take on responsibilities outside my job description. I think proactivity is something I'm naturally good at."
Zero story, zero specifics, zero result. This is self-description, not evidence.
Good Answer
"About a year into my role, I noticed that our customer success team was spending about 3–4 hours a week manually copying data between our CRM and our billing system. They weren't engineering-adjacent and hadn't flagged it as a technical problem — it was just how things were done.
I brought it up with my engineering lead and asked if I could take a Friday to scope a fix. He said sure, but to timebox it. I built a lightweight integration using Zapier and the APIs for both systems over two Fridays. No code review required, no sprint ticket, no deployment risk to production — it ran as an external automation.
The customer success team went from 3–4 hours per week to about 10 minutes of spot-checking. Over a year that's roughly 150 hours returned to the team. The head of customer success flagged it in a quarterly review as a meaningful productivity improvement."
This answer identifies the exact moment of noticing (manual copying), explains the decision to act (asked permission, timeboxed it), describes the specific approach (Zapier integration, kept it low-risk), and closes with a real quantified result.
How to Find Your Initiative Stories
Go through your last two or three roles and ask:
- What was broken or inefficient that I fixed before being asked?
- What did I build or propose that wasn't in my job description?
- What would have continued going wrong if I hadn't stepped in?
- What did I do that surprised my manager — in a good way?
Even a small initiative can work if it was clearly yours and it produced a concrete outcome. The size of the impact matters less than the clarity of your ownership and the realness of the result.
One Distinction Worth Making Clear
If you worked with others on your initiative, that's fine — but be explicit about your role vs. theirs. "I proposed it, scoped it, and built the prototype; two other engineers helped implement the production version" is clear. "We came up with the idea and built it together" disappears you from your own story.
Practice This Now
Initiative stories sound confident and clear when they're prepared, and meandering when they're not. The difference usually comes out the moment you say it out loud.