Influence

The central challenge of the staff engineer role is that the impact you’re expected to have — shaping technical direction, driving alignment across teams, changing how engineering gets done — requires influence, not authority. You can’t direct anyone. You don’t have a reporting line. You get things done by persuading people who don’t report to you, earning trust with stakeholders who already have strong opinions, and navigating organizational dynamics that nobody explicitly documented. ...

Every company has two org charts. The official one lives in an HR system somewhere. It shows boxes, lines, and reporting relationships. It is neat, hierarchical, and largely fictional as a map of how decisions actually get made. The second one exists nowhere in writing. It lives in people’s heads — in the instincts of engineers who have been around long enough to know who you really need to talk to before a proposal goes anywhere. This is the shadow org chart, and understanding it is one of the more underrated career skills an engineer can develop. ...