Staff Engineer vs Engineering Manager

Ewerlöf argues that Engineering Managers are accountable for both the people on their team and the technical artifacts that team produces. When either load outgrows what one person can carry, the EM delegates: admin work goes to tooling or an assistant, technical load goes to a Staff Engineer. Using a Staff Engineer as a translation layer for a non-technical EM gets named directly as an anti-pattern. If a manager isn’t technical, the fix is not a technical proxy standing between them and the work.

The piece locates the role’s real value outside any single team. A Staff Engineer scoped to one team is framed as a temporary arrangement, useful during onboarding or while clearing legacy debt. Across teams, the role works as glue: fewer meetings than an EM, more time in the technical depth, mapped to Will Larson’s four archetypes for the role.

Fichamento

#

• EM accountability covers people and the technical artifacts the team ships; when the load exceeds capacity, EMs delegate admin work or hand technical load to a Staff Engineer.
• A Staff Engineer acting as a translation layer for a non-technical EM is called out as an anti-pattern, not a fix.
• Team-scoped Staff Engineers are temporary by design (onboarding, a new EM, or a legacy debt pileup). The role’s real value comes from operating as glue across multiple teams.
• Will Larson’s four Staff Engineer archetypes: tech lead, architect, solver, right hand.
• Ownership breaks into three elements: knowledge of the tech and the product problem it solves, mandate to influence how the tech evolves, and responsibility for its health.
• The biggest pitfall for Staff+ engineers is drifting into an “Ivory Tower Architect” once soft skills crowd out the technical work.
• Not every org needs the role. The piece lists when it adds nothing: a technical EM, healthy tech debt, high cohesion within one team, an engineering org mature enough to self-organize.