A written version of the interactive roadmap above — every station, what you'll learn, and a small thing to build — laid out for reading, reference and search.
The Staff Shift Start here
F1. Beyond Senior
Intermediate · 40 min
Staff is not "senior plus a few years" — it’s a different job. Senior means you reliably deliver hard projects yourself; staff means you make the engineers and projects around you more effective, and your impact is measured in the outcomes of a team or org, not your own commits. Learn what actually changes at the boundary, why "just code harder" stops working, and what staff-level impact really looks like.
Skills: Senior vs staff, honestly · Impact through others · Outcomes over output · Why the senior playbook stops scaling
Build it: A great senior engineer keeps shipping more code but stalls at staff. Explain what the promotion committee is looking for that more code won’t show.
F2. Scope & Leverage
Intermediate · 45 min
Staff engineers are defined by scope — the size and ambiguity of the problems they own — and by leverage: getting outsized impact by working on the right thing, not just working hard. Learn to identify the highest-leverage problem in your area, to work at the level of "what should we build and why" rather than only "how", and to consciously trade hands-on coding time for higher-leverage work.
Skills: Scope and ambiguity · Leverage over effort · Finding the right problem · Trading coding for leverage
Build it: You have time to either fix 10 bugs or redesign the flaky system that generates them. Explain the leverage argument for each and which is staff work.
F3. The Staff Archetypes
Intermediate · 35 min
There isn’t one way to be staff. Learn the common archetypes — the Tech Lead (drives a team’s execution), the Architect (owns technical direction of a critical area), the Solver (parachutes into the hardest problems), and the Right Hand (extends a leader’s reach) — and figure out which fits your strengths and your org’s needs. Knowing your archetype tells you where to invest and how to describe your value.
Skills: Tech Lead / Architect / Solver / Right Hand · Matching archetype to strengths · Reading what the org needs · Describing your value
Build it: Name your most natural archetype and the one your org most needs right now. Where they differ, what would you do about it?
F4. Technical Judgment
Advanced · 50 min
The core staff skill is judgment: making good calls under uncertainty, with incomplete information, where the cost of being wrong is high. Learn to weigh trade-offs explicitly, to know when "good enough" beats "perfect", to spot the decision that will be expensive to reverse, and to be right often enough that people trust your calls. This judgment — earned through experience and pattern recognition — is exactly what AI can’t supply for your specific systems.
Skills: Deciding under uncertainty · Explicit trade-offs · Reversible vs one-way-door calls · Earning trust in your calls
Build it: A team wants to adopt a shiny new datastore. Walk through the trade-offs a staff engineer would surface before saying yes or no.
F5. Influence Without Authority
Advanced · 50 min
Staff engineers usually can’t tell anyone what to do — they lead by influence. Learn to build the credibility and relationships that make people follow your technical direction, to bring others along rather than mandating, to disagree and commit, and to get alignment across teams that don’t report to you. This is the skill that separates a strong senior from a real staff engineer, and it’s deeply human.
Skills: Credibility and trust · Bringing people along · Disagree and commit · Cross-team alignment
Build it: Two teams need to adopt a shared approach but neither reports to you and both resist. Describe how you’d actually get alignment.
F6. Writing & Communication
Intermediate · 45 min
At staff level, your leverage runs through communication — a clear design doc aligns dozens of people, a sharp technical argument changes a decision, a good explanation levels up a whole team. Learn to write design docs and technical proposals that persuade, to tailor the message to the audience (engineers, leadership), and to make complex trade-offs legible. Writing is how staff engineers scale their thinking beyond the room.
Skills: Design docs that persuade · Technical proposals · Audience-tailored messaging · Making trade-offs legible
Build it: Your architecture proposal keeps getting stuck in meetings. Describe the design doc that would get it decided async instead.
Technical Leadership Lead the work
T1. Technical Strategy
Advanced · 55 min
Staff engineers set technical direction: where the systems should go over quarters and years, not just the next sprint. Learn to connect technical decisions to business goals, to build a technical vision people can rally around, to sequence the path from here to there, and to say no to work that doesn’t serve the direction. Strategy is judgment applied over time, and it’s a defining staff responsibility.
Skills: Technical vision · Connecting tech to business · Sequencing the path · Saying no to off-strategy work
Build it: Your area has five competing rewrite proposals. Describe how you’d turn them into one coherent 12-month technical direction.
T2. Architecture at Scale
Advanced · 55 min
Staff engineers own the architecture of systems that are big, critical, or both. Learn to design for scale and evolution — clear boundaries, sensible trade-offs on consistency and coupling, and architectures that can change as needs do. Just as important: knowing when NOT to add complexity. Deep system-design judgment, applied to real constraints, is what an architect-archetype staff engineer is paid for.
Skills: Designing for scale and change · Boundaries and coupling · Trade-offs on consistency · Avoiding needless complexity
Build it: A monolith is slowing the org down and everyone wants microservices. Explain the trade-offs a staff engineer weighs before agreeing.
T3. Driving Alignment
Advanced · 45 min
A staff engineer’s decision only matters if the org actually acts on it. Learn to drive alignment across many stakeholders — surfacing disagreements early, finding the option people can live with, building consensus without watering the decision down to mush, and knowing when to escalate for a decision rather than let a stall continue. Turning a good technical idea into an org-wide reality is core staff work.
Skills: Surfacing disagreement early · Consensus without mush · When to escalate · Idea → org reality
Build it: A decision is stuck because two senior engineers fundamentally disagree. Describe how you’d break the stall and get a real decision.
T4. Leading Big Initiatives
Advanced · 50 min
Staff engineers often lead large, cross-team technical initiatives — a migration, a platform, a re-architecture — that span months and many people. Learn to break an ambiguous, scary effort into a sequenced plan, to coordinate across teams without formal authority, to manage technical risk, and to keep the thing moving when it inevitably hits trouble. This is where technical leadership meets execution.
Skills: Ambiguous effort → plan · Cross-team coordination · Managing technical risk · Keeping momentum through trouble
Build it: You’re asked to lead a year-long migration touching eight teams. Describe how you’d structure it so it doesn’t stall in month three.
T5. Leveling Up Others
Intermediate · 45 min
A big part of staff impact is making other engineers better — mentoring, reviewing, and setting technical standards that raise the whole team. Learn to mentor effectively (teach the reasoning, not just the answer), to give code and design review that grows people, and to establish practices and standards that spread good engineering across the org. Multiplying others is one of the most durable forms of leverage.
Skills: Mentoring the reasoning · Growth-oriented review · Setting standards · Multiplying the team
Build it: Describe how you’d turn a recurring class of production bugs into a lasting improvement in how the whole team designs, not a one-off fix.
T6. The Glue Work
Advanced · 40 min
Much of what holds a team together — noticing the gap no one owns, unblocking others, writing the doc everyone needed, keeping the big picture coherent — is "glue work": essential, high-impact, and easy to undervalue. Learn to do the glue work that genuinely matters, to make it visible so it counts, and to avoid the trap of drowning in glue at the expense of the technical leadership that defines the role.
Skills: Spotting the unowned gap · Unblocking others · Making glue visible · Avoiding the glue trap
Build it: You keep doing critical glue work that no one notices at review time. Describe how you’d make it visible without it looking like busywork.
Org Impact & AI Era Own the future
P1. Navigating the Org
Advanced · 45 min
Staff+ work happens inside org dynamics, and pretending politics don’t exist is a career limiter. Learn to read how decisions really get made, to build a network of trust across teams and leadership, to partner with your engineering manager and other leaders, and to navigate competing priorities without becoming cynical. This isn’t about playing games — it’s about being effective in a real human organization.
Skills: How decisions really get made · A network of trust · Partnering with EMs and leaders · Effective, not cynical
Build it: Your technically-correct proposal keeps losing to a worse one with more support. Explain what a staff engineer learns from that.
P2. Making Technical Bets
Advanced · 50 min
Staff engineers are trusted to make bets — adopting a technology, committing to an architecture, choosing what to build vs buy — whose payoff is uncertain and whose cost of being wrong is high. Learn to evaluate a bet honestly (upside, downside, reversibility), to de-risk with prototypes and staged rollouts, and to own the outcome either way. Good bet-making, over time, is a big part of what earns staff-level trust.
Skills: Evaluating a bet honestly · Reversibility and de-risking · Prototypes and staged rollout · Owning the outcome
Build it: Leadership wants your call on adopting a new AI framework company-wide. Describe how you’d de-risk the bet before committing everyone.
P3. Staying Technical in the AI Era
Advanced · 50 min
As AI makes writing code cheap, the staff engineer’s value concentrates even harder in judgment: what to build, which architecture will hold, whether the AI-generated system is actually sound. Learn to stay deeply technical without being the one typing every line — direct and review AI-assisted work at scale, keep your judgment sharp by staying close to the systems, and lead teams that are themselves AI-augmented. The role gets more valuable, not less, when construction is cheap.
Skills: Judgment over typing · Reviewing AI work at scale · Staying close to the systems · Leading AI-augmented teams
Build it: Your teams now ship AI-generated services fast. Describe the staff-level review and judgment that keeps quality and coherence high.
P4. Sponsorship & Visibility
Advanced · 40 min
Staff-level impact that no one sees rarely gets recognized or repeated. Learn to make your work and its impact visible (without self-promotion that grates), to find sponsors — leaders who advocate for you when you’re not in the room — and to build the track record and reputation that let you take on bigger scope. Visibility isn’t vanity at this level; it’s how you get entrusted with the problems worth solving.
Skills: Making impact visible · Finding sponsors · Reputation and track record · Earning bigger scope
Build it: You did the highest-impact work of the year but leadership barely knows. Describe how you’d have made it visible as it happened.
P5. Measuring Staff Impact
Advanced · 40 min
Staff impact is famously hard to measure — it’s diffuse, flows through others, and rarely maps to a commit count. Learn to articulate your impact in terms of outcomes (this system is reliable, this team ships faster, this bet paid off), to set goals that are ambitious and legible, and to help your manager and the promotion process actually see staff-level value. Being able to name your impact is essential to sustaining and growing the role.
Skills: Impact in outcomes · Legible, ambitious goals · Helping the process see value · Naming diffuse impact
Build it: Write the three-sentence impact summary that would convince a promotion committee you’re operating at staff, without listing tickets.
P6. The Staff+ Career
Advanced · 40 min
Staff is not the end of the IC track — principal, distinguished, and fellow extend it, and the management track is always an option. Learn where the IC leadership ladder goes, how the choice between staying IC and moving to management actually differs, how to keep growing scope and impact over a career, and how to build a portfolio and narrative that reflects staff-level leadership. Decide the path deliberately rather than drifting into it.
Skills: Principal / distinguished / fellow · IC vs management, honestly · Growing scope over a career · A staff-level narrative
Build it: Write the six-month plan that moves you from senior operating occasionally at staff to consistently owning staff-level scope.