"Tell Me About a Time You Showed Initiative": They're Scoring Your Judgment

You've got a story ready. It goes something like: things were swamped, you stayed late, you ground through it, and the deadline got met. Hard work. Dedication. Probably some back pain.

Most interviewers hear that story and think: that's just your job.

Not because they doubt you worked hard. Because the question isn't about work ethic. "Tell me about a time you showed initiative" is a judgment probe. The interviewer wants to know whether you can identify something worth acting on, decide it's your problem to fix even though nobody assigned it to you, and then act. Those are three separate things, and the "staying late" story usually demonstrates none of them.

What "Tell Me About a Time You Showed Initiative" Is Actually Testing

Initiative has three specific characteristics. Psychologists Michael Frese and Doris Fay defined it in a 2001 paper that became foundational in organizational psychology: initiative behavior is self-starting, proactive, and persistent. Self-starting means nobody told you to. Proactive means you acted before the problem became obvious to everyone else. Persistent means you kept going when it got hard.

The interviewer is scoring whether your story hits all three, but especially the first one: nobody told you to.

That's what separates an initiative story from an ownership story (accountability, seeing things through) or an "above and beyond" story (standard of care). Initiative is specifically about the moment before you started. You saw something that wasn't your job, decided it was worth doing anyway, and acted.

The question underneath the question is: how is your internal radar calibrated? Do you notice things others miss? Do you have the confidence to act without a green light? Companies hiring engineers want people who improve systems they weren't explicitly asked to improve. This question is screening for exactly that.

Why "Worked Late" Is Almost Never the Answer

The effort trap is the most common mistake. A candidate describes a crisis, explains they personally burned a lot of hours, and concludes with a result. From the interviewer's side: the situation demanded effort, and you provided effort. Responsive, sure. Initiative? Not quite.

Initiative requires a gap nobody else was filling, and a decision to fill it that you made independently.

Stories that fail the test:

• The manager asked you to take point on something hard. That's delegation.
• The deadline was coming and you worked extra hours to hit it. That's commitment.
• You flagged a problem in standup and someone else fixed it. That's communication.
• The production incident was escalated to you and you stayed up to debug it. That's on-call duty.

None of these are bad things. They just don't answer the question. The test is simpler and harder: did you act on something you noticed, that wasn't your explicit job, before anyone asked?

How "behavioral round" sounds vs what the interviewer is actually trying to figure out about you.

There's also a scope problem that cuts the other way. Some candidates pick examples so large and unsanctioned that the story sounds reckless. You rewrote the entire authentication system without telling anyone. You committed to a customer something your team hadn't agreed to. The sweet spot is an action you could defend: big enough to matter, calibrated enough to show judgment. Too small reads as low ambition. Too reckless reads as poor judgment.

The Structure That Actually Works

STAR is fine, but the standard distribution doesn't serve this question. Most candidates spend too long on Situation and Task, rush through Action, and land on Result without explaining anything interesting. For an initiative question, Action needs to do most of the work, and it has three distinct parts.

Time split: Situation and Task together are 15 to 20 percent. Action is 55 to 60 percent. Result is 25 to 30 percent.

Inside the Action section, hit these three things:

The gap you spotted. Not what the problem was generally, but what you specifically noticed that others weren't addressing. Be precise. "Deployment was slow" is not a gap. "We were spending 40 minutes per release on manual steps that weren't documented anywhere, and new engineers were making different mistakes each time" is a gap.

Your judgment call. This is the part most answers skip, and it's the most important. Why did you decide this was worth acting on without being asked? What was the cost of doing nothing? Who else could have done it? Why were you positioned to act? The reasoning tells the interviewer how your brain works when there's no explicit directive. Many candidates describe what they did in detail but never explain why they started. The "why I started" is the signal.

The concrete steps plus stakeholder communication. What you actually did, in enough specificity to be scoreable. If your initiative touched other people's work or required resources that weren't yours, how did you handle that conversation? Interviewers listen for whether you balanced independent action with smart communication. Acting on your own is good. Steamrolling teammates is a different kind of signal.

Practicing this out loud, where you have to actually say the reasoning rather than just think it, makes a bigger difference than most candidates expect. SpaceComplexity runs AI-driven voice mock interviews with rubric-based feedback, so you can hear whether your judgment explanation lands or disappears into the story.

A Strong Answer, Annotated

Here's a condensed version of what a strong answer sounds like for a mid-level engineer:

"I noticed that our on-call handoffs were inconsistent. [Gap spotted.] We had no standard format, so every rotation the incoming engineer spent the first few hours re-discovering context the outgoing engineer already had. Nothing was on fire, so it had never been prioritized. [Judgment call: low urgency meant nobody would fix it, but the cost was real and compounding.] I drafted a one-page handoff template, piloted it with my counterpart for two rotations, then proposed it in our team retro with data on time lost to context ramp. The team adopted it with some adjustments. [Steps plus buy-in.] The next quarter, our median time-to-productivity on handoffs dropped from about three hours to under thirty minutes. [Quantified result.]"

What makes this work: the engineer noticed something that wasn't their job, articulated why they decided it was worth acting on, showed they didn't do it unilaterally, and named the impact. The gap is specific. The judgment is explicit. The result is real.

Compare that to a weak version: "I stayed late during the sprint to help get the release out, and we shipped on time." Same person. Worse answer. The interviewer can't score what they can't see.

Five Killers

The "I was asked" story. If someone assigned it to you, it's not initiative. Did a manager, peer, or customer explicitly ask you to do this? If yes, find a different story. This one is the most common disqualifier, and candidates walk into it confidently.

Effort without reasoning. A lot of hard work with no explanation of why you decided to start it. The decision to act is the whole signal. Without it, the story is noise. Interviewers aren't grading your output. They're grading your input function.

"We" throughout the Action section. Interviewers can only score what you personally did. Every "we" hides your contribution. Replace them with specific actions: "I drafted," "I proposed," "I flagged," "I built." Teams are great. Teams don't get offers. You do.

No stakeholder awareness. Initiative that ignores everyone else's interests reads as poor judgment, not confidence. If your action touched other people's work, your answer needs to show you thought about that. Getting informal buy-in, running a small pilot, proposing in retro rather than just doing: these signals matter.

The result without lasting change. One-time heroics read as reactive. Durable impact reads as initiative. The strongest stories show that what you did changed something: a process now exists, a system works differently, the team adopted a new approach. "And then we shipped on time" ends a crisis story. "And the team still uses that template two years later" ends an initiative story.

The Part Most Candidates Skip

There's one element almost nobody includes, and it's what interviewers often probe for in follow-up: what was the cost of doing nothing?

When you make the judgment call to act without being asked, you're implicitly answering: the cost of not acting is higher than the cost of my time, the disruption, and the risk of being wrong. Articulating that reasoning, even briefly, tells the interviewer you evaluated the decision rather than acting on impulse.

A small line in the Action section covering your cost-of-inaction reasoning often lands harder than doubling the word count on what you actually did.

This is what separates a rehearsed story from a window into how you actually think. Interviewers know when candidates have memorized an answer. The cost-of-inaction reasoning is hard to fake because it requires you to have genuinely thought through the decision, not just the execution. You can tell the difference between someone who ran the calculation and someone who just remembered to use the word "initiative."

---

For related behavioral prep: 'Tell Me About a Time You Showed Leadership' covers the related leadership probe, 'Tell Me About a Time You Took Ownership' explains how accountability differs from initiative, and 'Tell Me About a Time You Handled Ambiguity' is the closest cousin to this question in what it actually tests.

Further Reading

• Proactive Behavior in Organizations, Crant 2000 (Journal of Management)
• Personal Initiative: An Active Performance Concept for Work in the 21st Century, Frese and Fay 2001