StaffEng

What is on the site

StaffEng has two halves:

• Guides: the staff archetypes, what staff engineers actually do, getting promoted to staff, finding and operating in a staff role, writing engineering strategy, managing technical quality, staying aligned with authority, and more.
• Stories: interviews with staff and principal engineers at a range of companies, describing their paths, what their days look like and what helped them get there.

The same material forms the book Staff Engineer: Leadership beyond the management track, published in 2021, which is also available in print.

The idea worth taking: four archetypes

StaffEng argues that "staff engineer" is not one job. It names four common shapes:

• Tech Lead: guides one or more teams, scopes complex work, coordinates execution and keeps cross-team relationships working.
• Architect: responsible for the direction and quality of a critical technical area over a multi-year horizon.
• Solver: digs into hard, ambiguous problems, sometimes in one area for a long time, sometimes moving between hotspots.
• Right Hand: extends an executive's leadership bandwidth, operating with borrowed scope across a large organisation.

Each suits different people and gets promoted through different evidence. Knowing which one you are aiming at turns a vague ambition into a plan.

Why the stories matter

Promotion to staff is unusually opaque at most companies. The interviews are candid about the parts that are rarely written down: sponsorship, visibility, choosing projects for leverage rather than interest, and the fact that the title often follows the work by a long time.

How to use it

1. Read the archetypes guide first and decide which shape fits your strengths and your company's needs.
2. Read three or four stories from people in that archetype.
3. Read "Getting the title where you are" and discuss it with your manager.
4. Return to the operating guides once you are in the role, especially on strategy and technical quality.

Who should read it

Senior engineers wondering what comes next, and anyone weighing management against the individual contributor track. It is also useful for managers who have staff engineers reporting to them.

Students and junior engineers can read the stories for perspective, but most of the advice applies several years in.

Pair it with

• The Staff Engineer's Path by Tanya Reilly, which goes deeper on execution and influence
• Engineering Ladders to map your current strengths
• An Elegant Puzzle if you are leaning towards management

Common questions

Is it really free? Yes, the guides and stories are free to read online. The book is sold separately.

Do all companies have staff engineers? No. Smaller companies and many services firms do not use the title, but the work it describes exists everywhere as senior technical leadership.

Best for: senior engineers deciding between management and the staff-plus track, and new staff engineers learning the role.