Sefism Staff and Leadership Cheat Sheet

What this cheat sheet is

The Sefism Staff and leadership cheat sheet is a reference for senior engineers stepping into leadership, as a staff engineer, an engineering manager, or both on trial. It collects the ideas you need at this level in one place: how to decide architecture across teams, how to lead projects and incidents, how to write and influence beyond your own team, and the core vocabulary of each path. Every concept follows the same short pattern: what it is in plain words, why it matters, often an example, and the mistake people make with it.

It is the companion to the Staff and leadership roadmap. The roadmap tells you what to do in what order; the sheet is what you open to revise a stage or check a term before a meeting where it matters.

Three editions

The sheet comes in three editions, matching the roadmap's paths:

• Staff engineer (6 chapters, 46 concepts): the shared foundations plus the staff path and technical strategy.
• Engineering manager (6 chapters, 48 concepts): the shared foundations plus the manager path and hiring, performance and team health.
• Not sure yet (8 chapters, 53 concepts): every chapter, with the essentials of both paths and how to compare them from real experience. This is the edition the public page opens with.

Across all editions the sheet holds 67 concepts.

Chapter by chapter

1. Owning architecture across teams

The hard design problems now sit between teams. Concepts: service and data ownership boundaries (which team owns each service, database and API, and who gets paged), Conway's law (systems mirror the communication structure of the organisation that builds them), build versus buy, choose boring technology (an organisation can afford only a few unproven technologies at once), decision records other teams can find, failure modes and blast radius, SLOs and error budgets, and technical debt as a portfolio.

2. Leading projects

How to lead work that runs through other people and teams. Concepts: the project brief, appetite and fixed time with variable scope (decide how much time a problem is worth first, then shape a solution to fit), cutting scope, milestones, risks and cross-team dependencies, the weekly status update, and Brooks's law.

3. Leading incidents and postmortems

Running incidents calmly with clear roles, then learning from them without blame. Concepts: the incident commander, incident roles, severity levels, mitigate first and fix later, incident communication, and the blameless postmortem.

4. Communication and influence

Both paths lead mostly through writing and relationships. Concepts: bottom line up front (the conclusion in the first sentence, the ask in the second), the one-page proposal, stakeholder mapping, decision roles such as DACI, aligning teams without authority, managing up, giving and receiving hard feedback, and disagreeing without spending trust.

5. The staff engineer path (Staff and Not sure yet editions)

The individual contributor route past senior. Concepts: what a staff engineer is, the staff archetypes, choosing work that matters, glue work (the less visible work that makes projects succeed, as described by Tanya Reilly), scope across teams, being in the room, finding a sponsor and the staff promotion case. The Staff edition adds partnering with engineering managers; the Not sure yet edition adds a staff-shaped trial.

6. Technical strategy and sponsoring others (Staff and Not sure yet editions)

Setting direction for a group of teams and growing the next senior engineers. Concepts: engineering strategy, technical vision, and sponsorship versus mentorship. The Staff edition goes further with strategy from existing decisions, handing hard problems to others, staying technical with less coding, the technical roadmap and organisation-wide standards.

7. The engineering manager path (Manager and Not sure yet editions)

The people side of leadership. Concepts: what an engineering manager is, one-on-ones, coaching, continuous feedback, delegation, the move from tech lead to manager and the engineer and manager pendulum. The Manager edition adds career conversations and your first 90 days as a manager; the Not sure yet edition adds a management trial.

8. Hiring, performance and team health (Manager and Not sure yet editions)

The team side of management. Concepts: the structured hiring loop, performance reviews and calibration, psychological safety, and focus time and team health. The Manager edition adds the hiring scorecard, handling underperformance early, team size and span of control, Team Topologies, DORA metrics (deployment frequency, lead time for changes, change failure rate and time to recover) and how managers themselves are assessed.

Each chapter ends with up to three library resources for going deeper, such as Shape Up, the PagerDuty incident response guide, StaffEng, Irrational Exuberance and The Manager's Path.

Rules of thumb inside

The sheet closes with eleven rules of thumb. A few of them:

• Name who owns each piece of a cross-team design and who gets paged, before debating technology.
• Cut scope early and say so in writing; late surprises cost more trust than smaller plans.
• In an incident, one person coordinates and nobody debugs and communicates at the same time.
• Sponsor people into visible work, not only into private advice.
• Choose the work you want to do on an ordinary Tuesday, not the title that looks more senior.
• Give corrective feedback within days, so nothing in a review is a surprise.

There is also a glossary of the smaller terms that do not need a full concept.

How to use it with the roadmap

• After each stage, read the matching chapter without notes first and see which concepts you cannot explain. Those are the gaps to close before the stage milestone.
• Before a meeting that needs the words ready, such as a calibration session, an architecture review or a first conversation with a sponsor, skim the relevant chapter.
• While doing the work, keep chapter 2 or 3 open as a checklist when you write a project brief or run an incident.
• When choosing a path, read chapters 5 to 8 in the Not sure yet edition side by side and notice which ones you find yourself wanting to do.

How it works on Sefism

Everything on Sefism is free to learn from. The public cheat sheet page lists every chapter title, with the first chapters open to read. Keeping the sheet in your member area uses credits, and if you follow the Staff and leadership roadmap the sheet comes with it. New members get 15 credits when they join, and the first roadmap you add is free. You can also ask Tauseef a question about anything in it. New here? Create a free account.

Related on Sefism

• Tech lead, engineering manager or individual contributor?
• How to explain technical ideas to other engineers
• The Staff Engineer's Path and An Elegant Puzzle from the library
• The Mid-level to senior cheat sheet, if you want the step before this one

FAQ

Is this cheat sheet only for people who want to be managers? No. Four chapters are shared by both paths, and the Staff engineer edition never touches people management. Choose the edition that matches the path you are on, or Not sure yet to see both.

What is glue work, and does it count towards promotion? Glue work is the less visible work that makes projects succeed: onboarding, coordination, reviewing designs, unblocking and documentation. The sheet's point is that it only counts when it is named and agreed with your manager as part of your role.

What are DORA metrics? Four delivery measures from the DORA research programme: deployment frequency, lead time for changes, change failure rate and time to recover from failed deployments. They appear in the Manager edition, with the warning not to turn them into targets people game.

Can I use the sheet without following the roadmap? Yes. It works as a standalone reference, though it is written to sit beside the Staff and leadership roadmap.