Initiative: what interviewers score and how to build the story

Initiative is acting, without being told, on something that mattered — and it is scored against a specific bar that rules out most of what candidates bring to it.

This lesson works through that bar in the order you will use it. First what the competency means and what it is confused with. Then the exact indicators the interviewer is writing down, the phrasings that open onto them, and finally the two tests your raw material has to pass before it is worth building into a story.

The definition

The four parts matter because each one is a place candidates fall out:

What it is not

Initiative is confused with three neighbours, and getting the boundary wrong is the most common reason a good story scores as something weaker.

It is not extra work. Volume is not initiative. Staying late to finish assigned work is delivery at best and poor estimation at worst. The question is not did you do more, it is did you choose what to do.

It is not innovation (Section 12). Initiative asks whether you acted unprompted; innovation asks whether the approach was non-obvious. Rebuilding an undocumented runbook is high initiative and zero innovation. Both are fine; they score in different rows.

It is not heroics. Firefighting a production incident at 2am is on-call working as designed. It becomes initiative only if you then went and removed the cause of the class of incident when nobody asked you to.

Where it actually shows up

Most people's real initiative stories are not projects. They are the things they did in the margins and never wrote down:

• The dashboard you built because you were tired of answering the same question
• The runbook you wrote after the third time someone paged you for it
• The conversation you started with another team about a boundary nobody owned
• The thing you deleted
• The process you stopped, or the meeting you killed

These are undersold constantly, usually because they were not "assigned work" and so do not feel like achievements. That is exactly what makes them initiative.

Signals scored

Once you know what counts, the next question is what the interviewer writes down. They are listening for four positive indicators and a set of negatives. Knowing which sentence produces which mark is most of the preparation.

The positive indicators

1. You found the problem yourself, from evidence. The strongest version names how you noticed — here, in a story about continuous integration (CI, the automated build-and-test pipeline that runs on every change):

"I noticed I was re-running CI two or three times a day, so I pulled the pipeline history for the team and found 38% of runs on main were failing for reasons unrelated to the change."

Noticing is weak; measuring is strong. The interviewer writes: quantified the problem before acting.

2. You chose to act, with a stated reason for the priority. Why this and not the ten other things you could have done?

"I picked it because it was costing about nine engineer-hours a week across seven people, which was more than the feature I'd been asked to look at was worth."

3. You secured buy-in proportionate to the blast radius. A dashboard needs nobody's permission. Changing a CI policy for three teams needs a conversation. Deciding to rewrite a service needs a real agreement. Interviewers score whether you matched the two.

4. You finished the boring part. The interviewer will look for it, because it is where initiative stories usually stop:

"The interesting part was finding the four root causes. The part that made it stick was the quarantine policy and getting it into the shared pipeline template, which took another three weeks and was mostly arguing."

The negative indicators

The one that decides it

Of the four positives, buy-in proportionate to blast radius is the one that separates scores at senior and above. Anyone can do unsanctioned work. Doing unsanctioned work that other people then own is a different skill, and it is the whole content of the competency at staff level.

The observable version is a sentence like:

"Before I put any real time into it, I took the numbers to my tech lead and to the two people who'd have to maintain the change, because if they weren't going to own it afterwards there was no point starting."

Questions asked

Seven phrasings all open onto that same indicator list. Recognising them is worth more than preparing an answer for each.

1. "Tell me about a time you saw a problem nobody else was addressing."
2. "Tell me about something you did that was outside your role."
3. "Tell me about a time you went above and beyond what was asked of you."
4. "Describe something you started yourself, from scratch."
5. "Tell me about a time you took ownership of something that wasn't yours."
6. "What's something you've improved that nobody asked you to improve?"
7. "Tell me about a time you had to act without complete direction."

What each is really probing

The disguised versions

Three phrasings look like other competencies and are scored as initiative:

"Tell me about a time you had to make a decision without your manager." Reads like autonomy or judgement. The rubric row is usually initiative, and the interviewer wants the buy-in question answered — who did you tell, and when?

"What would you change about your current team if you could?" Reads like a culture question. It is often a probe for whether you have already tried. A candidate who names three problems and has acted on none of them has answered an initiative question badly without realising a question was asked.

"Walk me through your last six months." Unstructured, and a good place to volunteer an initiative story unprompted. Nobody will hand you question 1 in an unstructured round.

Answering question 3 well

"Above and beyond" is the most misread phrasing in the set, because the words invite an answer about effort. Interviewers are not asking about effort. Redirect explicitly:

"The way I'd answer that is with something I chose to do rather than something I worked harder at — is that useful, or did you want an example of a crunch period?"

That single sentence does two things: it shows you know what the competency is, and it lets the interviewer confirm. Both are recorded favourably.

Building the story

Now to your own material. Two hard tests decide whether raw material qualifies. Most candidate stories fail one of them, and the failure is not repairable by rewriting.

Test 1 — it must have been genuinely optional

Nobody asked. No ticket existed. If you had done nothing, nothing bad would have happened to you.

This rules out:

• Anything with a ticket number, unless you wrote the ticket
• Anything your manager suggested, even lightly ("you might want to look at…")
• On-call work, unless the story is what you did after the incident closed
• Anything in a performance-review goal for that cycle

It does not rule out work that later became official. A common and strong shape is: you started it unsanctioned in the margins, produced enough evidence to make a case, and it then became a funded piece of work. That transition is the story.

Test 2 — it must have shipped, or been consciously stopped

An initiative story with no ending is not a story. Two acceptable endings:

It shipped and someone used it. Name who and how many.

You stopped it deliberately, with a reason. This scores better than most candidates expect:

"I spent about two weeks on it and then killed it. The prototype showed the actual saving was around forty minutes a week, not the four hours I'd estimated, and I'd have needed another month to make it production-grade. I wrote up what I found so nobody would repeat it, and went back to the roadmap work."

That demonstrates identification, action, evidence-gathering, and judgement about opportunity cost. What it does not demonstrate is follow-through, so it works better as a secondary story than a primary one.

What does not qualify, and cannot be fixed

Be honest with yourself here, because polishing weak material is the most common way to waste preparation time.

Notice the fix column. There is no wording that turns "I suggested we improve testing" into an initiative story, because the missing element is an action that did not happen.

Where to look for material you have discounted

Go through the last eighteen months and ask, for each month: what did I do that nobody would have noticed if I hadn't done it?

Productive categories:

• Something you automated because you were tired of doing it
• A document you wrote that other people now link to
• A question you kept getting asked, and what you built to stop being asked it
• A cross-team boundary you clarified
• Something you removed: a service, a flag, a meeting, a dashboard nobody read
• A measurement you started taking that did not exist before

The last one is undervalued. "Nobody was tracking X, so I started, and three months of data changed how we prioritised" is an excellent initiative story, and people routinely fail to count it because it felt like curiosity.