Thinking big: what interviewers score and how to build the story

This is the staff-plus and manager differentiator. It is also the competency where candidates most often mistake having an opinion for having evidence.

This lesson separates the two. It defines the competency and a quick horizon test for whether a story belongs here, sets out the signals — including the one that separates staff from strong senior — and the seven phrasings, and ends with the adoption test that sinks most otherwise-strong material.

The definition

Two halves, and candidates usually have one. The reasoning half is the idea: you saw where things needed to go. The adoption half is the persuasion work: who you convinced, what they objected to, and what changed as a result. Interviewers weight the second half more heavily, because the first is cheap.

What it is not

It is not seniority of language. Saying "aligned the organisation around a strategic direction" describes nothing. Interviewers translate it back into "who specifically changed what they were doing?" and score that.

It is not initiative at larger scale. Initiative is acting on a problem nobody assigned. Strategy is choosing which problem is worth several quarters, which includes choosing what not to do. The "not" is where most of the signal is.

It is not architecture. A technical design, however large, is not a strategy unless it comes with a case about what the business or the organisation needs and a plan for adoption.

It is not having been in the room. Being present when a director set a direction produces no evidence about you.

The horizon test

A quick check on whether a story belongs in this competency: how far ahead does the reasoning reach, and how far ahead did the payoff arrive?

If your story's payoff arrived inside a quarter, it is a good story for a different section.

Signals scored

Four positives, four negatives, and one that interviewers use to separate staff-level candidates from strong seniors.

The positive indicators

1. A multi-quarter horizon with a stated reason. Not "we'll need this eventually" — a specific forecast:

"Our contract volume with enterprise customers was growing about 40% a year, and every one of those contracts had a data-deletion clause. At that growth rate the manual process breaks somewhere in the next four to six quarters, and it breaks in the worst possible way, which is in legal review of a deal we've already priced."

2. Influence without authority, described concretely. Names, objections, and what changed:

"The team I needed most was the one that would benefit least. Their tech lead's objection was that this was a six-week migration to solve someone else's compliance problem. That was accurate."

3. Technical choices connected to business outcomes. The connection is explicit and measured, not asserted.

4. Knowing what not to do. The clearest staff signal available:

"I deliberately excluded analytics reads from the scope, which was about 60% of the total query volume and would have doubled the timeline. Analytics doesn't have the deletion requirement, so including it would have been building a data platform instead of solving the problem."

The negative indicators

The one that separates staff from senior

Whether you can name what you excluded, and defend the exclusion.

Strong seniors describe what they built. Staff candidates describe what they decided not to build, and why, with the cost of the alternative attached. It is the single most reliable discriminator in this competency, and it is easy to prepare for and rare to hear.

The reason it works is that scoping down is only possible if you understood the problem well enough to know which parts were load-bearing. A candidate who included everything either did not have to choose or did not know how.

Questions asked

Seven phrasings. Most of them are asked only at senior and above, and two are asked of managers specifically.

1. "Tell me about a technical direction you set."
2. "Tell me about a time you influenced a decision above your level."
3. "Tell me about a long-term bet you made."
4. "Tell me about a time you had to think beyond your immediate team."
5. "How do you decide what your team should not work on?" (manager)
6. "Tell me about a time you connected a technical decision to a business outcome."
7. "Where do you think our industry / your area is going, and what would you do about it?"

What each is really probing

Question 2 needs mechanics, not outcome

"I influenced a decision above my level" is answered with the outcome by most candidates and with the mechanics by good ones. The interviewer wants the sequence:

"I went to the three people most likely to object first, individually, before writing anything down. Two of the three objections changed the proposal. By the time it reached the group review, the two loudest sceptics had already had their concerns addressed, and one of them made the case for me — which was more persuasive coming from them than it would have been from me."

That is the answer. Not "I presented it well".

Question 7 is not a trick

"Where do you think this is going?" is asked to see whether you have a view at all, and whether you can hold it loosely. The failure is a neutral survey of trends. The strong answer has a position, a reason, a timeframe, and an explicit statement of what would change your mind.

Building the story

Two tests, and the adoption problem that sinks most otherwise-strong material.

Test 1 — the reasoning reached past your assignment

You noticed something that was not your job to notice. Usually one of:

• A pattern across incidents, teams, or deals that nobody was aggregating
• A trend line that breaks at a predictable point
• A cost that is currently invisible because it is spread across many people
• A constraint arriving from outside — a contract, a regulation, a partner, a market shift

Test 2 — adoption, not vision

This is the test that eliminates most material. A brilliant document that nobody acted on is not a strategy story. Adoption evidence, in descending order of strength:

How to show the persuasion work

Most candidates compress six months of convincing into "I socialised the proposal". Decompress it. The interviewer wants four things:

1. Who mattered. Not everyone. The two or three people whose agreement determined the outcome.
2. What their real objection was. Often different from the stated one.
3. What you changed in response. If nothing changed, you did not persuade, you announced.
4. What you gave up to get agreement. Scope, timeline, ownership, or credit.

Point 4 is the most under-used. "I gave the ownership of the service to the platform team even though my team had built it, because their owning it was what made the other teams trust it" is a strong sentence and it is the kind of thing that never makes it into a rehearsed answer.

The story card

STORY — <strategic story>Signal I noticed     what, aggregated from where, that nobody was looking atForecast             what breaks, when, and why that timingBusiness connection  the measured link, with the numberProposal             the thing, in one sentenceExcluded             two things, with the cost of including themPersuasion           3 people, their real objections, what I changedGave up              scope / ownership / creditAdoption             N teams, M of them optional; what rule changedWhere it is now      current state, honestly