Sefism Staff and Leadership Roadmap

What this roadmap is

The Sefism Staff and leadership roadmap is for the step after senior. You already own designs and your team listens to you; the question now is what comes next. There are two honest answers. One is the staff engineer path: technical leadership across several teams, with no direct reports. The other is engineering management: people, hiring and delivery. Many engineers do not know which one they want, so the roadmap has a third option, "Not sure yet", which runs a structured trial of both.

By the end you own architecture decisions that span teams and are written down where every team can find the reasoning. You have led a multi-team project from scope to launch and run an incident through to a blameless postmortem. You write proposals and updates that get decisions made by directors and other teams. And you have done the core work of your path for a quarter, so the choice between staff and manager rests on evidence rather than on which title sounds more senior, knowing you can switch later.

Who it suits, and who should start elsewhere

It suits senior engineers and tech leads who already lead designs on their own team and want to widen their scope. It also suits newly promoted staff engineers or first-time managers who want a structured way into the job.

If you are not senior yet, this is the wrong starting point. The Mid-level to senior roadmap covers scope, ownership, design documents and visibility at the senior level, and it is what this roadmap assumes. If you are still in your first year, start with Your first tech job. If you are thinking about moving company rather than moving up, the Job search roadmap is the better fit.

Three paths, one shared core

When you add the roadmap you choose a path, and the stages follow that choice. Every path shares the first three stages, then splits:

Across all three paths the roadmap has seven stages and 54 topics. The hours are rough effort for someone new to each stage; Sefism turns them into weeks using the hours you say you have. At 8 hours a week the staff and "not sure yet" routes take about 24 weeks and the manager route about 27.

Prerequisites and realistic time

You need to be doing senior-level work already: leading designs for your own team, reviewing others' work, and being trusted to deliver without close supervision. Most of the roadmap is doing rather than reading, and much of it depends on real projects, real incidents and a manager willing to agree what you own. That is why it is slow: a quarter of staff-shaped work cannot be compressed into a fortnight.

If you are working full time (the usual case). Plan on 4 to 6 hours a week outside the work itself. Spend one evening on reading (a chapter of the stage's book or a few StaffEng stories) and use the rest to write: the design doc, the decision record, the proposal, the weekly status. The doing happens inside your job.

If you have more time, for example between roles. At 8 to 12 hours a week the reading goes faster, but the milestones still need real projects with other teams, so the trials take as long as they take.

Stage by stage

1. Owning architecture across teams (about 50 hours)

At this level the hard design problems sit between teams: shared data, service boundaries, platform choices and build versus buy. The topics are service and data ownership boundaries, trade-off analysis across teams, build versus buy, failure modes and blast radius, SLOs and error budgets, decision records other teams can find, and technical debt managed as a portfolio rather than a guilty list.

Milestone: write and defend a design doc for a change that affects at least two teams, with rejected alternatives and an operating cost estimate, and record the decision as an ADR both teams can find. Tauseef's note for this stage: default to the boring architecture the organisation can run at 3am, and name who owns each piece and who gets paged, because cross-team designs fail on ownership more often than on technology.

2. Leading projects and incidents (about 30 hours)

This stage is about work that runs through other people and teams. Topics: a one-page project brief, shaping and cutting scope, milestones and estimates as ranges, risks and cross-team dependencies, weekly status that surfaces trouble, incident command and roles, mitigating first and communicating second, and blameless postmortems. The checklist asks you to act as incident commander once while someone else debugs, and to cut scope early and say so in writing.

Milestone: lead a project of several weeks involving at least two teams from scope to launch with written milestones, and run or write a blameless postmortem for one incident.

3. Communication and influence across the organisation (about 30 hours)

Staff engineers and managers both lead mostly through writing and relationships. Topics: conclusion first, writing for directors and product, one-page proposals and strategy documents, stakeholder mapping and decision roles, aligning teams without authority, disagreeing without spending trust, and giving and receiving hard feedback.

Milestone: write a one-page proposal that gets a decision from people outside your team, and present it at a planning or architecture review beyond your own team. The practical rule here: put the conclusion in the first sentence and the ask in the second, and talk to the key people one to one before the meeting.

4. The staff engineer path (about 30 hours, staff and "not sure yet")

Staff is a different job from senior, not the same job with more tickets. Topics: what a staff engineer actually does, the four staff archetypes from StaffEng (tech lead, architect, solver, right hand), scope across teams, choosing work that matters, glue work made visible, working with your manager and being in the room, finding a sponsor, and the staff promotion case.

Milestone (staff): agree with your manager on one cross-team problem you will own for the next two quarters, with the outcome that would show staff-level scope written down. On the "not sure yet" path this stage becomes Try staff-shaped work: own a cross-team problem end to end for a quarter and keep a weekly note of what energised and what drained you.

5. Technical strategy and sponsoring others (about 40 hours, staff only)

Set technical direction for a group of teams and grow the next senior engineers. Topics: what engineering strategy is, writing strategy from existing design docs, technical vision documents, turning strategy into a roadmap and standards (optional), sponsorship versus mentorship, handing hard problems to others, and staying technical with less coding time.

Milestone: write a one-page technical strategy for your area, get it adopted by at least two teams, and sponsor one engineer onto a project that stretches them. A reliable way in, from the stage notes: collect the last five design docs in your area and write down what they already agree on.

6. The engineering manager path (about 40 hours, manager and "not sure yet")

Management is a career change rather than a promotion. Topics: what the manager job really is, one-on-ones that belong to the report, feedback that is frequent and specific, coaching instead of answering, delegation, career conversations, the move from tech lead to manager, and your first 90 days as a manager.

Milestone (manager): hold fortnightly one-on-ones with at least one engineer for a quarter as a tech lead or mentor, and give one piece of difficult feedback well. On the "not sure yet" path this stage becomes Try the manager side: the same one-on-ones, plus a one-page comparison of both trials and a chosen path for the next two years.

7. Hiring, performance and team health (about 50 hours, manager only)

The team side of management. Topics: structured hiring loops, rubrics and written feedback, performance reviews and calibration, handling underperformance early, team health and psychological safety, focus time and interruptions, team sizing and organisation design, plus two optional topics on delivery metrics without gaming and how engineering managers are themselves assessed.

Milestone: run or co-run a hiring loop with a written rubric, and write a team health review covering workload, focus time and on-call load with three changes you would make.

How it works on Sefism

Everything on Sefism is free to learn from. The public roadmap page shows the full list of stages for your chosen path, with the first two stages open to read in full. When you add the roadmap to your dashboard, every stage opens, you can tick off topics and milestones as you go, and Sefism paces the weeks to the hours you have. Each topic also gets a question to check yourself and a prompt that makes an AI assistant quiz you rather than do the work. Adding a roadmap uses credits: new members get 15 credits when they join, and the first roadmap you add is free. If you are learning seriously and run out, you can ask for more.

Following the roadmap also gives you its companion cheat sheet, and you can ask Tauseef a question about any stage, such as how to frame a staff promotion case or whether a trial result points one way or the other. If you would rather talk it through, you can book a 1:1 session. New here? Create a free account.

The companion cheat sheet

The Staff and leadership cheat sheet has the same structure in reference form: cross-team architecture, leading projects, incidents and postmortems, communication and influence, then the chapters for each path, in Staff engineer, Engineering manager and "Not sure yet" editions. Use it to revise a stage after you finish it and before a conversation where you need the vocabulary ready, such as a calibration meeting or a strategy review.

Related on Sefism

• Tech lead, engineering manager or individual contributor? is the short version of the choice this roadmap helps you make with evidence.
• How to explain technical ideas to other engineers and What to do when you disagree with a senior engineer go with stage 3.
• How to give code review feedback without creating conflict and How to handle a teammate who does not contribute go with the manager stages.
• From the library: StaffEng, The Staff Engineer's Path, The Manager's Path, An Elegant Puzzle and The Engineer/Manager Pendulum.
• On the blog: The habits that make an engineer worth routing work through.

What you can do afterwards

You can lead a cross-team design and leave behind a decision record that outlives you, run a multi-team project and an incident without drama, and write the kind of one-page proposal that ends a debate. More importantly, you will know which leadership job you actually want, because you will have done a quarter of it. From there, the staff route continues into a promotion case and wider strategy, and the manager route into a first team of your own.

FAQ

What is the difference between a staff engineer and an engineering manager? A staff engineer leads technically across several teams without direct reports: finding problems nobody owns, setting direction and getting teams to move. A manager is responsible for people: one-on-ones, feedback, hiring, performance and the team's health and delivery. Stages 4 to 7 cover each in turn.

How long does it take to become a staff engineer? The roadmap estimates about 180 hours of learning on the staff path, around 36 weeks at 5 hours a week. The promotion itself depends on your company's ladder and on scope you can only build over real quarters, which is why the stage 4 milestone is a two-quarter commitment agreed with your manager.

Is moving into management a promotion? The roadmap treats it as a career change, not a promotion. Your output becomes the team's output and your feedback loop stretches from days to months. Moving between the two paths every few years is normal.

I cannot decide between staff and manager. What should I do? Pick "Not sure yet". It replaces the path stages with a quarter of staff-shaped work and a manager-side trial in parallel, with weekly notes on what energises and drains you, and ends with a written comparison and a chosen path.

Do I need to be senior before starting? Yes, in practice. The milestones need you to lead work across teams. If you are not there yet, follow the Mid-level to senior roadmap first.