Will Larson’s four “staff engineer archetypes”—team lead, architect, solver, right hand—make sense as descriptions but fall flat as career goals. Trying to act like a team lead won’t make you one. Instead, technical leadership and the trust that underpins it grow from delivering consistent, valuable work. Ship small features first, build relationships and domain knowledge, then take on bigger challenges. Jumping straight to high-profile projects without that foundation often backfires: you lack the political insight, execution track record and senior management trust to pull it off. You can’t learn to be an architect in the abstract either. Designing software requires deep familiarity with the codebase and the people who maintain it. The solver and right-hand roles both hinge on massive goodwill and influence, which only come from a long history of credible contributions. Treating the archetypes as targets misunderstands how staff engineering works. A staff engineer’s real job is staying useful when the mission shifts or when projects go sideways. Mid-level engineers execute assignments; staff engineers own outcomes, even those beyond their control. You must constantly ask, “Is this worthwhile for the company?” and drop any expectation of fairness. Learn to read your manager’s true priorities, adjust focus on the fly, and move projects forward quietly. At first you’ll look like a reliable executor who doesn’t complain, not like any single archetype. Over time you’ll naturally slot into one of Larson’s niches—but only because you’ve built that trust, not because you chased a label. Early advice should focus on earning credibility: deliver shareholder value in every task, understand the org’s real needs, and adapt. Once you’ve done that, the rest follows organically.