Vibe Engines is free, interactive AI engineering & system design — runs in your browser. Pick a learning path →
18 stations. 3 tracks. The IC leadership track, not management: from what staff actually means, scope and the archetypes, through technical strategy, architecture at scale, driving alignment and influence without authority, to navigating the org, making technical bets and staying technical as AI reshapes engineering.
18 stations on 3 ladders, in order — each rung is written assuming the one above it. Mark them off as you go; your progress is saved in this browser.
6 rungs · ~5h · ends at Writing & Communication.
F1 · 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.
Build itA 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.
✓ CheckpointName a task you are good at that you should now be handing to someone else — and explain why doing it yourself is the lower-impact choice.
F2 · 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.
Build itYou 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.
✓ CheckpointTake an ambiguous problem you were handed and state the version of it you chose to solve, plus what you deliberately left out of scope.
F3 · 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.
Build itName your most natural archetype and the one your org most needs right now. Where they differ, what would you do about it?
✓ CheckpointSay which staff archetype your last six months actually looked like — not the one you would prefer — and whether that is what your org currently needs.
F4 · 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.
Build itA team wants to adopt a shiny new datastore. Walk through the trade-offs a staff engineer would surface before saying yes or no.
✓ CheckpointTake a decision you made recently and classify it as reversible or one-way-door. Explain how that classification should have changed how much time you spent on it.
F5 · 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.
Build itTwo teams need to adopt a shared approach but neither reports to you and both resist. Describe how you’d actually get alignment.
✓ CheckpointDescribe a time you got a team to change direction with no authority over them, and name the thing that actually moved them.
F6 · 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.
Build itYour architecture proposal keeps getting stuck in meetings. Describe the design doc that would get it decided async instead.
✓ CheckpointTake a design doc you wrote and identify who it was really for. If the answer is “anyone”, it was for nobody.
6 rungs · ~5h · ends at The Glue Work.
T1 · 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.
Build itYour area has five competing rewrite proposals. Describe how you’d turn them into one coherent 12-month technical direction.
✓ CheckpointState a technical direction in one sentence a non-engineer would understand — and name one reasonable piece of work you would refuse because it does not serve that direction.
T2 · 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.
Build itA monolith is slowing the org down and everyone wants microservices. Explain the trade-offs a staff engineer weighs before agreeing.
✓ CheckpointPoint at a boundary in a system you know and justify why it sits there. If the honest answer is “that is where the team split was”, say so.
T3 · 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.
Build itA decision is stuck because two senior engineers fundamentally disagree. Describe how you’d break the stall and get a real decision.
✓ CheckpointExplain the difference between consensus and everyone being too tired to argue, and describe how you would tell them apart in a room.
T4 · 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.
Build itYou’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.
✓ CheckpointTake a large initiative and name the risk most likely to kill it. Explain why you would attack that first even if it is not the critical path.
T5 · 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.
Build itDescribe 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.
✓ CheckpointDescribe how you would review a correct pull request in a way that still teaches something — and why the reasoning matters more than the diff.
T6 · 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.
Build itYou keep doing critical glue work that no one notices at review time. Describe how you’d make it visible without it looking like busywork.
✓ CheckpointName a piece of glue work you own, and say honestly whether it is raising your impact or quietly absorbing your week.
6 rungs · ~5h · ends at The Staff+ Career.
P1 · 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.
Build itYour technically-correct proposal keeps losing to a worse one with more support. Explain what a staff engineer learns from that.
✓ CheckpointDescribe how a real decision at your company got made — not the process on paper — and where in that path you have influence.
P2 · 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.
Build itLeadership wants your call on adopting a new AI framework company-wide. Describe how you’d de-risk the bet before committing everyone.
✓ CheckpointTake a technical bet you would like to make and state what would prove it wrong within a month, cheaply.
P3 · 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.
Build itYour teams now ship AI-generated services fast. Describe the staff-level review and judgment that keeps quality and coherence high.
✓ CheckpointExplain what you now check first when reviewing AI-generated work at volume, and why reading every line is not the answer.
P4 · 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.
Build itYou did the highest-impact work of the year but leadership barely knows. Describe how you’d have made it visible as it happened.
✓ CheckpointExplain the difference between visibility and self-promotion, and name what makes work legible to people who were not in the room.
P5 · 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.
Build itWrite the three-sentence impact summary that would convince a promotion committee you’re operating at staff, without listing tickets.
✓ CheckpointDescribe an impact you had that no metric captured, and how you would make that legible without inflating it.
P6 · 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.
Build itWrite the six-month plan that moves you from senior operating occasionally at staff to consistently owning staff-level scope.
✓ CheckpointTell your own staff-level narrative in three sentences — the problems you take on, the way you take them on, and the scope you are growing toward.
The common questions before you start — how long it takes, whether to follow it in order, and how it stays current.
It runs 18 stations across 3 tracks — roughly ~15h of focused learning, plus the time you spend actually building. It is self-paced, so most people work through it over a few weeks, an evening or a single station at a time.
The tracks are ordered so each station builds on the one before, and following them start to finish is the intended path. But every station also stands alone — if you already have the foundations, jump straight to the part you need.
Yes. The whole roadmap, and every handbook, lab, and challenge it links to, is free and open — no sign-up and no paywall.
It teaches the durable fundamentals of the role first, then the tooling and the AI-era shifts on top — so most of it stays relevant as individual tools churn, and it is revised as the role itself changes.
Anyone stepping into or leveling up in the Staff Engineer role — whether you are switching in, early-career, or a senior filling gaps. Start where you are; the ladder shows what is left.
See this alongside everything else on the same subject — handbooks, system designs, challenges and tools, in one place.