Staff archetypes

Staff and principal continue the senior arc across wider organizational surface area. Will Larson's Staff Engineer popularized a useful taxonomy of staff-plus shapes. Names vary by company. You do not need the staff title to borrow the patterns. You do need honesty about which game you are playing.

The IC vs manager fork is a different question. Management is a different job: people outcomes, hiring, performance, prioritization theater, and less hands-on building. It is not a promotion above senior IC. It is a lateral craft switch at healthy companies.

The four shapes

• Tech lead: deep in one area's execution and coordination
• Architect: cross-cutting design and standards (danger: architecture without adoption)
• Solver: dropped onto the hardest messy problems
• Right hand: partner to a leader, amplifying org priorities

Architect without adoption is slideware. Solver without a finish line is ghost chasing. Tech lead who never hands off becomes a local-maximum hero. Right hand who never ships artifacts becomes a meeting senior.

Walking through the fork

Charity Majors argues for a pendulum: time as an engineer, time as a manager, back again — because each side teaches skills the other needs. You do not have to pendulum. You should choose consciously. Trying to be full-time manager and primary technical IC usually produces a mediocre version of both.

If the org cannot offer senior-scoped IC work, that is career strategy data, not a reason to take a people-manager seat you do not want.

Common mistakes

• Architecture without an execution path. Pair every design with who will ship it.
• Accidental management. A blocked IC path is a transfer or exit problem.
• Doing both jobs at once. You get a mediocre version of each.
• Copying a staff title's politics instead of a shape of work. Imitate the artifacts, not the theater.

Check yourself

1. Promo to senior IC is blocked, and a manager seat opens. What should you not do? Take the seat only to escape the block. Fix the IC path or change teams.

2. You wrote a grand design nobody adopted. Which archetype went wrong? Architect without adoption. Pair the next design with an execution path.

Key takeaways

• Staff archetypes are choices: tech lead, architect, solver, right hand.
• Management is a lateral craft switch, not a promotion above senior IC.
• Do not become a manager because the IC path is blocked.
• Borrow the patterns before you have the title; stay honest about the game.

Further learning

Will Larson reflecting on Staff Engineer — archetypes, anti-patterns, and how senior roles actually work.

Charity Majors on the Engineer/Manager Pendulum.

StaffEng (Will Larson)Staff Engineer: Leadership beyond the management trackStaff Engineer: Leadership beyond the management track The Engineer/Manager Pendulum (Charity Majors)Lately I’ve been doing some career counseling for people off Twitter (long story).charity.wtf

Next, put a calendar under it with a 12–24 month plan.