Vibe Engines
YouTube

Vibe Engines is free, interactive AI engineering & system design — runs in your browser. Pick a learning path

Handbooks  /  Staff Engineer Behaviors
Handbook~16 min readLeadershipworked math + runnable code
The Staff Engineer Behaviors Handbook

Multiply,
don't add.

The hardest promotion in engineering is senior to staff, and it's hard because people aim at the wrong target: they try to write more and better code, when the level isn't about code volume at all. Staff+ is a change in the unit of impact — from what your own two hands ship to the output you create in others: the architecture that unblocks three teams, the standard that speeds everyone, the mentee who levels up. Senior engineers add; staff engineers multiply. The defining line is measurable — the moment your leverage exceeds your personal output. This handbook is that shift, made concrete and runnable.

01

Output to leverage

A senior engineer is, roughly, someone who independently delivers complex projects well — they're measured by their own output, and they're very good at it. The staff engineer (and staff-plus: principal, distinguished) is measured by something different: leverage, the impact created through others and across the organization, beyond what any individual could personally ship. This is why the promotion trips people up — they double down on the thing that got them to senior (more, better personal output) when the next level rewards a different thing entirely.

Think of it as a change in the multiplication. A senior adds their output to the team's total. A staff engineer multiplies the team's output — a good architecture makes ten engineers meaningfully faster, a clear standard removes friction for everyone, a mentored engineer levels up permanently. The value isn't in the artifact with your name on it; it's in the amplification of everyone else. The clearest single signal that someone is operating at staff level is that impact through others has come to dominate their personal output — a threshold you can literally compute, and the spine of this handbook. Get this reframe and the rest follows; miss it and you'll be the best senior engineer who never quite makes staff.

The one-sentence version

Senior is measured by your own output; staff+ is measured by leverage — the output you create in others and across the org — and the level is defined by the moment that leverage dominates your personal output.

02

The archetypes

"Staff engineer" isn't one job — it's several. Will Larson's widely-cited framing names four archetypes, and knowing which one a moment calls for keeps you applying leverage instead of defaulting to writing code:

The four staff-engineer archetypes
Tech LeadGuides a team's direction & execution, usually paired with an engineering manager.
ArchitectOwns the technical direction & quality of a critical area across the org.
SolverParachutes into the hardest, most ambiguous problems wherever they are.
Right HandAn extension of senior leadership, taking on org-level scope and priorities.

Most staff engineers lean into one archetype at a time depending on what the organization needs, and many rotate through several over a career. The point of the taxonomy isn't to label yourself — it's to recognize that these are genuinely different modes of applying leverage, and that a role or a moment usually calls for one in particular. A team drifting without technical direction needs a Tech Lead or Architect; a critical system on fire needs a Solver; an executive who needs a technical partner needs a Right Hand. A common failure is bringing the wrong archetype to the situation — trying to Solver your way through a problem that actually needs Architect-style alignment, or hands-on-coding when the org needs you facilitating a cross-team decision. Match your mode to the need, and your leverage lands where it counts.

03

Glue work

A huge share of staff leverage takes the form of glue work — the essential, often invisible activity that holds a project or organization together but never shows up as a shipped feature. Unblocking someone stuck. Aligning two teams heading for a collision. Writing the design doc everyone ends up referencing. Noticing the thing falling through the cracks that no one owns. Mentoring, reviewing, facilitating the decision that had been stuck for weeks. None of it has your name on a commit, and all of it can be worth more than any feature you'd have built instead.

Glue work is high-leverage almost by definition — a single well-run alignment or one clarifying document can save many people many weeks — which is exactly why staff engineers do so much of it: multiplying others is this kind of connective work. But there's a real tension, made famous by Tanya Reilly's talk on the subject: glue work is often under-credited because it isn't a visible artifact, so if organizations don't see and reward it, people rationally avoid it and it falls to whoever cares most (frequently, and unfairly, along demographic lines). Two lessons follow. As a staff engineer, do the glue work and make it visible — write it down, name it in updates, so the leverage is legible. And as an organization, count glue work as real work, because it's frequently where the highest leverage in the whole system quietly lives. The connective tissue isn't overhead; at staff scope, it's the job.

04

The leverage math

Total impact is your own output plus the added output you create in others; the leverage is that second term, and a team-wide improvement is worth the whole team times the per-person boost:

total impact  =  own_output + Σ multipliers     team multiplier  =  team_size × per_person_boost

A decision that makes 10 engineers 20% more effective = 10 × 0.2 = 2 "engineer-equivalents" of added output — more than most individuals ship personally.

Staff level is the threshold where leverage — impact through others — dominates your own hands-on output:

staff-level  ⟺  Σ multipliers ≥ own_output     leverage ratio  =  Σ multipliers / total impact

Own output 1, multipliers [3,4] → leverage 7 dominates → staff-level. Own 5, multipliers [1,1] → 2 < 5 → not yet. The runnable version below computes total impact, leverage, the ratio, and the staff threshold.

RUN IT YOURSELF

Leverage over output, quantified

The senior-to-staff shift is a change in what you multiply. Total impact is your own output plus the added output you create in others — and a decision that boosts a whole team is worth team-size times the per-person improvement, often more than any one person ships. Leverage is the portion that comes through others, and staff level is the threshold where that leverage dominates your own hands-on output. The leverage ratio tells you how much of your impact is amplification versus personal delivery. Change the own-output and the multipliers and watch the total, the leverage, the ratio, and the staff threshold.

CPython · WebAssembly
05

How to operate

Knowing leverage is the goal, here's how staff engineers actually generate it day to day:

BehaviorWhy it's leverage
Work on what mattersFind the highest-leverage problem — often the important-but-unowned work no one is driving — not just what's assigned.
Write relentlesslyAt org scope, influence travels through writing: design docs, technical strategy, clear async updates. Writing is a core skill, not a side task.
Influence without authorityYou usually can't order anyone — you persuade with clear reasoning, good judgment, and a track record. Trust is the currency.
Be a force multiplierMentoring, review, standards, and tooling raise everyone's ceiling — the most scalable form of impact.
Stay technically credibleKeep close enough to the details to have earned opinions; your leverage rests on being right, not just senior.

Two of these deserve emphasis because they're the biggest surprises for new staff engineers. First, writing is the job: at a scope that spans teams and quarters, you can't be in every room, so your ideas propagate as documents — a crisp design doc or technical strategy is how a single person aligns dozens and outlives their own attention. Engineers who neglect writing cap their leverage no matter how strong their code. Second, influence without authority: a staff engineer commands almost no one, so every bit of impact is earned through persuasion, credibility, and trust rather than a title — which means being consistently right, communicating clearly, and building relationships is not politics, it's the actual mechanism of the role. Combine these — pick the highest-leverage problem, propagate your thinking in writing, persuade with earned trust, multiply others through mentoring and standards, and stay technically sharp — and you're doing the job the leverage math describes: turning one person's effort into an organization's output.

06

Pitfalls

The first is staying a hero individual contributor — hoarding the hardest coding and out-shipping everyone. It feels productive and it got you to senior, but it caps your impact at one person's throughput and, worse, deprives the people around you of the growth and the space you're supposed to be creating. The staff move is often to hand off the work you're best at so you can do the multiplying only you can do. The second is the mirror image: floating up into pure abstraction — becoming an "architecture astronaut" who pronounces on strategy while losing touch with the code and the real constraints. Leverage rests on credibility, and credibility rests on being close enough to the details to be right; a staff engineer who can't get their hands dirty stops being trusted, and untrusted influence is no influence.

Two more. Doing invisible glue work with no visibility: the connective work is high-leverage but easy to leave uncredited — do it and make it legible (write it down, name it), or you'll be quietly essential and never recognized. And bringing the wrong archetype: Solver-ing a problem that needs Architect-style alignment, or hands-on-coding when the org needs facilitation — match your mode to the moment. The unifying idea is that staff engineering is a genuine phase change, not a continuation: you stop being measured by the excellent thing you personally build and start being measured by how much you multiply everyone around you. Internalize "leverage over output," pick the highest-leverage problem, propagate through writing and trust, make your glue work visible, and stay technically grounded — and you cross the gap that the best senior engineers so often stall at, from adding to a team's output to multiplying it.

Worth knowing

Don't stay a hero IC (caps you at one person) or float into pure abstraction (kills credibility). Do the highest-leverage work, propagate your thinking in writing, influence through earned trust, make glue work visible, match the right archetype to the moment, and stay technically sharp. The level is leverage over output — impact through others dominating your own.

By the numbers

Worked example: three ways to spend one quarter

Say an engineer’s own output, shipping alone, is worth 1.0 engineer-equivalent a quarter. Run the page’s formulas on three plans. Time spent multiplying others comes out of own output, so own output falls as leverage rises.

PlanOwn outputMultipliersTotal, leverage, ratio
A. Ship the big feature alone1.0none1.0 total, 0 leverage, ratio 0. Not staff-level.
B. Half the quarter on a shared build cache: 12 engineers 5% faster0.712 × 0.05 = 0.61.3 total, 0.6 leverage, ratio 0.46. 0.6 < 0.7, so not yet.
C. A design doc that aligns 3 teams of 6 (10% faster each), plus mentoring one engineer (+0.2)0.418 × 0.1 = 1.8, plus 0.22.4 total, 2.0 leverage, ratio 0.83. Staff-level.

Plan C ships the least code and has 2.4 times the impact of plan A. Plan B is good work that still falls short, because the boost is small and the team is small. The model also leaves one thing out that helps C even more: a multiplier keeps paying next quarter (the cache, the agreed design, the mentee’s skills), while a feature you shipped alone is done once it ships. The weak point of the maths is the inputs. “10% faster” is a guess, so write down what you expected and check it afterwards. That written record is also how glue work becomes visible.

Trade-offs

Trade-offs: what each mode costs you

Here Time is how soon the impact shows up, Space is how far it reaches, and Why is the risk you take on.

CaseTimeSpaceWhy
Hero ICImmediately: the feature shipsOne person’s throughputCapped at what you can type, and it takes the growth chances from the people around you.
Tech LeadWithin the projectOne teamEasy to slip back into writing the hardest code yourself, which brings back the hero cap.
ArchitectMonths: designs pay off as teams build on themMany teams, over yearsIf you lose touch with the code, the designs stop being trusted. That is the architecture-astronaut trap.
SolverFast, on one hard problemDeep but narrowYou leave once it is fixed. If no one owns it afterwards, it breaks again.
Right HandSlow, through leadership decisionsThe whole orgThe work is the hardest to see and the hardest to credit, so write down what changed.
Glue workOften invisible: a meeting that never had to happenWherever teams meetIt is high leverage but under-credited (the page’s Reilly point). Undocumented, it does not count.

No mode is free. The ones that reach furthest pay off slowest and are hardest to see, which is why staff engineers have to write so much. Writing turns leverage that would otherwise be invisible into something other people can check.

In the wild

Where this shows up: promotions, reviews and interviews

  • The promotion case

    A case for staff is argued from evidence of impact beyond your own work. Feature lists rarely make it. Name the decision, who it unblocked and roughly what it saved, the way plan C is written above. Glue work that never got written down cannot be cited.

  • Design reviews and RFCs

    This is where influence without authority happens day to day. A clear doc that states the options, the trade-offs and a recommendation lets dozens of people agree without a meeting. It also outlasts your attention, which is the page’s “writing is the job” point.

  • Incidents

    This is Solver mode at its most visible. The staff move is not only fixing it. It is writing up why it happened and changing the system or standard so the whole class of failure stops, which turns a one-off fix into a multiplier.

  • The behavioral interview

    Expect “tell me about a time you influenced a decision you did not own” or “you disagreed with another team’s design”. A strong answer names the archetype you used, how you persuaded people without authority, and the measurable result for other people, not for your own code.

Self-check

Check yourself

Own output 3, multipliers [1, 1.5]. Staff-level by the page’s test? What is the leverage ratio?

Leverage is 1 + 1.5 = 2.5, which is less than 3, so not yet. Total impact is 5.5 and the ratio is 2.5 ÷ 5.5 ≈ 0.45. This is a strong senior: most of the impact still comes from their own hands.

Option 1: make 8 engineers 10% more effective. Option 2: make 30 engineers 2% more effective. Which adds more?

8 × 0.1 = 0.8 against 30 × 0.02 = 0.6. The bigger audience loses here. Reach only helps if the boost is real, so do the multiplication before chasing the org-wide project.

Two teams are each building their own auth service and will collide next quarter. Which archetype fits, and what is the wrong move?

This needs Architect alignment: get both teams to agree on one design, written down. The wrong move is Solver or hero mode, where you build a third, better auth service yourself. It is a technical fix to an alignment problem, and you end up with three.

You spent a month unblocking three teams and nobody above you noticed. What does the page say to do?

Make the glue work visible. Write it down and name it in updates: what was stuck, what you did, what it saved. The work was real leverage, but leverage nobody can see is not credited, and people stop doing work that is never credited.

Frequently asked

Quick answers

Senior vs staff engineer?

Senior is measured by own output; staff+ by leverage — impact through the people and teams you multiply. The level is when leverage dominates personal output.

What are the archetypes?

Larson's four: Tech Lead (team direction), Architect (cross-org technical direction), Solver (hardest problems), Right Hand (leadership extension).

What is glue work?

The invisible connective work — unblocking, aligning, documenting, mentoring — that holds things together. High-leverage but under-credited; make it visible.

How do you operate as staff?

Work on what matters, write relentlessly, influence without authority, multiply others, and stay technically credible. Writing and trust are the mechanisms.

Finished this one? 0 / 209 Handbooks done
NextThe Agentic AI Interview Handbook Closest handbook to this one

Explore the topic

See this alongside everything else on the same subject — handbooks, system designs, challenges and tools, in one place.