Staff-Engineer

The RFC process is well-understood at most engineering organizations. You have a problem, you have a proposed solution, you write it up, you get feedback, and you either proceed or revise. RFCs are structured around a decision: should we do X, and if so, how? Strategy documents are different — and the difference matters. A strategy document is not asking “should we do X.” It is answering the question “why are we doing what we’re doing, and how does it connect to everything else we care about?” It is less about proposing a specific solution and more about establishing a shared understanding of the problem space, the constraints, and the reasoning that should govern future decisions in a domain. ...

Most performance review advice is written for engineers who are trying to get to senior. Pass code reviews. Ship features. Demonstrate ownership. Get visible. That playbook breaks at the staff level — and breaks in a particular way. Not because the work is harder, but because the feedback loop disappears. Your manager is often not technical enough to evaluate your architectural decisions in detail. Your impact is measured in quarters and years, not sprints. The “did I do well this week” signal that used to arrive through PR comments and 1:1s no longer exists. You are flying on instruments. ...

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. ...

We’re building VividMap to give Senior+ engineers a clearer picture of where they are, where they’re going, and what’s standing between them and their next milestone. This blog is where we’ll share everything we learn along the way — career frameworks, org chart strategies, skill-building approaches, and honest reflections on what it actually takes to operate at the Senior+ level. What to expect Career mapping — how to visualize your position, your landscape, and your path forward Org chart intelligence — reading power structures, building influence, finding sponsors Skill tracking — prioritizing learning with real cost estimates (time, money, stress) Staff+ perspectives — what changes when you move from senior to staff engineering Join the waitlist VividMap is currently in early access. If you’re a Senior+ engineer who wants clarity on your career — join the waitlist and be among the first to get access. ...