Staff+ Archetypes and Role Fit

An archetype is a recurring pattern of how a role creates value, not a formal title or personality test. Will Larson's StaffEng research describes four useful patterns—Tech Lead, Architect, Solver, and Right Hand—because senior individual contributors do not all lead in the same way.

Engineers may blend patterns or move between them over time. That flexibility is a course synthesis: use archetypes to clarify the operating problem, then validate the fit with real organizational needs and local role expectations.

The Tech Lead archetype coordinates technical execution for a team or group while usually remaining an individual contributor. The leverage comes from decisions, sequencing, interfaces, and developing owners—not from taking every critical task.

The Architect archetype establishes technical direction across an enduring area such as identity, data, or developer platforms. An enduring area persists across projects, so the work requires stewardship, adoption, and revision rather than a one-time design document.

An effective Architect starts from real constraints, invites the teams who must adopt the direction, and measures whether the direction improves outcomes. A weak version produces elegant diagrams that do not survive contact with ownership, migration cost, or product priorities.

Example: instead of declaring one event schema for the company, the Architect maps failure modes, defines compatibility rules, tests them with two teams, and creates a decision and migration path that domain owners can sustain.

The Solver archetype enters unusually complex, urgent, or ambiguous problems and creates a path through them. “Bounded” matters: the assignment should have an outcome and an exit, otherwise the Solver becomes a permanent rescue service.

Engineer lens: define the handoff before starting and teach the local owners while solving.

Manager lens: protect the Solver from an endless queue of emergencies. Judge success partly by whether the area can proceed without them afterward.

The Right Hand archetype works closely with a senior leader to extend that leader's ability to understand, decide, and communicate across a broad area. The role needs high trust and organizational context, but its purpose is institutional effectiveness—not proximity or private influence.

Good Right Hand work turns weak signals into clear options, connects decisions across groups, carries technical context into leadership forums, and returns decisions transparently to owners. The failure mode is becoming an unaccountable gatekeeper whose authority nobody understands.

Engineer lens: test whether you enjoy translating across technical, product, and organizational perspectives while giving credit and decisions back to owners.

Manager lens: state the mandate publicly, preserve direct access to decision-makers, and prevent the role from becoming a substitute for healthy leadership systems.

Role fit sits at the intersection of organizational need, personal energy, and demonstrated capability. Preference alone cannot create a role the organization does not need, while need alone does not make a sustainable assignment.

A shared observability platform is failing to gain adoption. The archetypes reveal different problems hiding inside the same situation.

An archetype experiment is a time-bounded way to test fit without redesigning a person's title. This script is a course synthesis.

Engineer: “The identity domain seems to need coherent direction more than another project lead. I would like to test the Architect pattern by framing principles and an adoption decision with the three owning teams.”

Manager: “The need is real. Success is not a perfect architecture; it is a usable decision, named owners, and early adoption evidence. I will secure access to the decision forum and find a peer reviewer.”

Engineer: “Let us review energy, capability, impact, and whether the organization still needs this pattern after 90 days.”

Archetypes make Staff+ work more legible without claiming there is one correct path. They remain descriptive tools, subordinate to real organizational context.

• Tech Leads create coherent execution and distributed ownership.
• Architects create adopted direction across enduring technical domains.
• Solvers unblock hard bounded problems and then transfer ownership.
• Right Hands extend senior leaders' technical and organizational capacity transparently.
• Most people blend patterns; an archetype is not a permanent identity or promotion checklist.
• Fit requires need, energy, capability, access, support, and a planned reassessment.

This exercise identifies one operating pattern worth testing. Complete it with your manager or a trusted Staff+ peer, then compare interpretations.

1. Name one important outcome that is stuck.
2. Diagnose whether the bottleneck is execution, direction, hard bounded ambiguity, or leadership context.
3. Select the closest archetype and write why the other three are weaker fits.
4. Define a 90-day experiment, required access, and an exit condition.
5. Record one energy signal and one capability signal each month.

Template:

Because [outcome] is blocked by [bottleneck], we will test the [archetype] pattern through [assignment]. The engineer receives [access/authority] and [support]. At the end, we will assess [outcome evidence], [capability], [energy], and [continued need].

StaffEng supplies the four archetypes; the fit matrix, experiment, and scripts are course syntheses.

• StaffEng: Staff archetypes
• StaffEng: Operating at Staff
• Dropbox Engineering Career Framework
• Monzo Engineering Progression Framework v4.1