How and Where Should an Engineer Grow After Senior?

Beyond senior, careers can continue through people management or individual technical contribution. Both require leadership skills alongside engineering depth. Technical influence may remain focused within a domain or extend across many teams. Engineers at a comparable level therefore do not necessarily need identical day-to-day responsibilities.

Will Larson's classification identifies four archetypes. A Tech Lead guides engineering practices within one or several related teams. A Solver tackles a particular difficult problem. An Architect coordinates cross-team decisions around requirements and constraints. A Right Hand amplifies a senior executive's technical influence. These describe kinds of work, not a mandatory sequence of positions every engineer must pass through.

The process starts with understanding the competency matrix. For software engineers, it considers scope, impact, complexity, leadership, and improvement. The engineer then takes on work associated with the next level. Before a Staff+ transition, discussing that work with a manager is especially important: the problem must matter to the organization and provide evidence of the relevant capabilities, rather than merely be technically difficult.

Managers provide feedback through one-to-ones and performance reviews. The article describes moving toward an application after jointly assessing that a substantial share of the next-level criteria is already met. Its reference to more than half of the criteria belongs to this particular process, not a universal promotion rule. The important point is a shared assessment of actual work, rather than expecting a new title to create the experience.

The application lists completed tasks, achieved results, and colleagues who can comment on the contribution. Professional leads then review it; these specialists also help develop competency frameworks, tools, and hiring criteria. Staff+ applications receive an additional review by technical directors. This broadens assessment beyond the immediate team's local practices.

An unsuccessful application should produce an explanation and development recommendations. Following approval, new terms are agreed and the manager communicates the result. The process does not replace everyday work and feedback; it organizes existing evidence into a basis for a decision. The practical lesson is to choose consequential work early, make contributions understandable to others, and discuss expectations with the manager throughout the work.