Behavioural interviews · Module 11 of 12 · Level 3: Company, level and delivery

Senior and staff signals

At senior and staff levels, the behavioural round often decides the level of the offer. The questions are the same; the bar is different. Interviewers listen for how wide a problem you owned, whether you found it or were handed it, and how many other people work better because of you.

1. The idea

A city's maintenance crew fixes potholes. Its traffic engineers redesign the junction where the potholes keep appearing. Its city planners decide where the next road goes, so the junction never gets that traffic in the first place. All three are skilled; the difference is how wide a problem each one owns. Levels in engineering work the same way.

Senior and staff candidates hear the same questions as everyone else. What changes is what a strong answer has to contain. Interviewers listen for five dimensions growing with the level:

Dimension	Mid-level	Senior	Staff and above
Scope	A feature or task	A project or a system for the team	Several teams, or the whole organisation's direction
Problem	Given to you, well defined	Vague, and you refined it	Nobody had noticed it; you found and framed it
Decisions	How to build it	What to build and the design	Which problems to work on at all, and the trade-offs across teams
Influence	Your own work	Your team, and nearby teams	Leaders and many teams, without authority over them
Time horizon	Days to weeks	Weeks to a quarter	Quarters to years

Level titles differ by company, so treat the columns as a direction, not a definition. The practical point: a story told with mid-level scope won't get a senior offer, however well it's told. Senior candidates need stories where they shaped the problem, not just solved it, and multiplied other people's work.

2. How it works

The same project told three ways. The events are identical; what's in the frame grows with the level.

3. Try it yourself

The scope ladder

Describe one of your stories on five dimensions. The ladder shows the level it signals and what would move it up.

4. What interviewers look for

At senior levels every answer is also scored on scope and judgement. The same story can land at different levels depending on what you include.

Signal	Weak	Good	Strong
Problem framing	"I was given a ticket"	"The requirements were vague, so I…"	"Nobody had noticed that…, so I made the case for fixing it"
Multiplying others	Only your own output	Unblocked teammates	Changed how several teams work: a standard, a platform, a practice
Trade-offs	None mentioned	Design trade-offs	Trade-offs across teams and time: what the organisation gives up
Long view	This sprint	This quarter	What the decision means in a year, and how you'd know it was right

5. A model answer

"(Senior / staff) Tell me about the most impactful project you've led." An invented answer, shown part by part. Read it for the shape, then build your own from a true story.

SituationTwo years ago, each of our eight product teams ran its own way of deploying, and our incident reviews kept finding the same cause: a risky change shipped to everyone at once.

TaskNobody had framed it as one problem: each team saw its own incidents. I wanted to show it was one problem and get the organisation to fix it once.

ActionI went through 18 months of incident reviews and found that 23 of 41 major incidents came from changes released to all users at once. I wrote a two-page proposal for progressive delivery (canary releases with automatic rollback) and spent two weeks in one-to-ones with the eight tech leads and our VP before any group meeting. I deliberately didn't build it alone: I recruited one engineer from each of two teams, so it wasn't "my" platform. We piloted on the two riskiest services, published the results, and then I wrote the migration plan with each team's lead, in an order they chose.

ResultWithin three quarters all eight teams used it. Change-related major incidents fell from about two a month to about one a quarter. The two engineers I recruited now run the platform, and I moved on to the next problem.

LearningI underestimated how much the migration order mattered to teams' roadmaps. Letting each lead choose their slot cost a month but removed every objection.

Why it scoresThe candidate found and framed the problem (nobody had seen it as one), influenced eight leads and a VP without authority, deliberately grew others to own the result, and measured the organisation-wide effect. That's staff-level scope, told in the same STAR shape as everything else.

6. Remember it

Memory hook: "Zoom out one level"Whatever you did, say what problem it belonged to, who else it changed, and what it meant over time.

How this hook works: what “Zoom out one level” means

What the slogan means, phrase by phrase

“Zoom out”: Show the frame around your work: why the problem existed, who else had it, what it cost the organisation.
“one level”: Tell the story at the level you're applying for: if you're aiming for senior, show team-wide scope; for staff, several teams.

Why this picture fits: The pothole crew, the junction redesign and the city plan: same road, different frame. Moving the camera back one notch shows the level you work at.

The story → the concept

The road	Your story
Fixing the pothole	Doing the task well
Redesigning the junction	Fixing why the problem keeps happening
Planning the next road	Choosing which problems the organisation works on
Moving the camera back	Telling the frame around your work

Watch it on an example

Task frame: "I added canary releases to our service."
Team frame: "I made canaries our team's default; our incidents dropped."
Organisation frame: "I showed 23 of 41 incidents shared one cause, and got eight teams onto one platform."

The trap it saves you from

Telling true, well-structured stories that only show half of what you did, and getting levelled down.

It still works when…

Your best stories are mid-scope. Then pick the ones where you shaped the problem or grew someone, and tell those parts fully.

7. Common mistakes

Only telling the technical partAt senior levels the people and the decision-making are most of the story. Tell how you got agreement.

Underselling"I just helped a bit" can get you levelled down. Be accurate about what you led.

OversellingClaiming you led what you didn't falls apart in follow-ups. Be precise about your part.

No multiplicationSenior and staff stories show other people getting better or faster because of you.

Short horizonSay what the decision meant months later, and how you checked.

8. Practice exercise (25 minutes)

Rate your bank (10 min). Run each story through the ladder above. Which level does each signal?
Zoom out your best story (10 min). Add the frame: why the problem existed, who else had it, what it changed beyond your team.
Find a multiplier story (5 min). A time someone else, or another team, got better because of what you did.

9. Self-check quiz

What most separates a staff-level story from a senior one?

Staff stories shape which problems get solved.

You did the work but tell it as "I helped a bit". What's the risk?

Be accurate about what you led.

Which shows multiplying others?

Others grew and own the result.

A strong senior answer to "your most impactful project" includes…

Scope, influence and long-term effect.

10. Go deeper

Resource	Time	Why
Staff archetypes (StaffEng, Will Larson)	15 min	The different shapes staff-plus roles take, from tech lead to architect.
From senior engineer to architect (Software architecture, Module 33b)	30 min	The scope shift in more depth.
Module 12: Follow-ups and practice	Next	Surviving the third "why?".