Technical Leadership
The Staff+/Principal engineer track — leading through influence, not authority
Most management content is written for the manager track: one-on-ones, performance reviews, hiring, delegation. This section is for the other track — the senior individual contributor who leads without a reporting line. The Staff Engineer, the Principal Engineer, the Architect.
The defining shift at this level is not "writes more code." It is that your impact stops being bounded by what you can build yourself, and starts being bounded by how good your technical judgment is and how far you can spread it. You lead through influence, written artifacts, and the decisions of people who don't report to you.
What Changes at Staff+
- From output to outcomes. A senior engineer is measured by what they ship. A Staff+ engineer is measured by what the org ships differently because they were there.
- From authority to influence. Nobody reports to you. You can't tell teams what to do; you have to make the right thing the obvious thing.
- From answers to judgment. The questions stop having clean answers. The value you add is the trade-off, not the fact.
- From code to leverage. Your highest-leverage hours are often not spent coding — they're spent in a design doc, a decision, or a conversation that redirects ten engineers.
Contents
Staff+ Archetypes
The Tech Lead, Architect, Solver, and Right Hand — and how the IC track differs from management
Technical Strategy
Setting technical vision, multi-team direction, and roadmaps that survive contact with reality
Technical Decisions
Trade-off thinking, decision frameworks, and translating engineering into business impact
RFCs & Design Docs
The primary artifact of a Staff+ engineer — writing and running design documents and review
Influence Without Authority
Driving cross-team alignment when nobody reports to you
Scaling Yourself
Leverage, glue work, sponsorship, and avoiding the single-point-of-failure trap
Migrations & Rewrites
Leading large-scale technical change safely — strangler fig, incremental cutover, and the rewrite trap
Working with Product
Partnering with PMs and stakeholders — product thinking, trade-offs, and shaping the roadmap
Career Progression
Advancing on the IC track — scope, sponsorship, the promotion case, and getting to Staff+