Common Pitfalls

If What Good Looks Like is the mirror, this page is the shadow. These are the patterns we most often see when a Staff Engineer is not yet operating at the level — or has drifted away from it. They’re described without judgment because most of them are understandable, and many of us have been in at least one of these modes at some point. The goal is recognition, not shame.

The Senior Engineer Who Got Promoted

This is the most common failure mode. You were an excellent Senior Engineer — you shipped reliably, wrote clean code, owned problems end-to-end. Then you got promoted, and you kept doing exactly the same thing. Your output is still strong, your technical skills are sharp, but your impact hasn’t changed shape. You’re still the person who builds things, not the person who makes building better for everyone around you.

The Ivory Tower

You’ve embraced the “strategic” part of the role so fully that you’ve lost touch with the ground. You write architecture documents that don’t reflect the actual constraints teams are working under. You make pronouncements about technical direction without staying close enough to the code to know whether your direction is realistic. Engineers have stopped pushing back on your designs — not because the designs are good, but because they’ve learned it’s easier to nod and then quietly work around you.

The Context Hoarder

You sit in all the right meetings. You have organizational context that nobody else on your team has. And you keep it to yourself — not maliciously, but because translating context is hard and you’re busy. The result is that your team is constantly surprised by organizational decisions, doesn’t understand why priorities shifted, and can’t make good local decisions because they’re missing the bigger picture.

The Critic Without a Path Forward

You’ve developed a sharp eye for what’s wrong — bad architecture, poor process, misaligned priorities. And you name these problems loudly and often. But you rarely propose a solution, build a coalition to fix it, or do the unglamorous work of actually driving change. You’ve become the person who points at fires but never picks up a hose.

The Lone Wolf

You take on hard problems and solve them — alone. You don’t pair with other engineers, don’t bring problems to your local staff group early, and don’t use Architecture Office Hours. The work you produce is often good, but it doesn’t multiply. Nobody else learned from the problem, nobody reviewed the approach before you committed to it, and the team’s collective capability is unchanged.

The Conflict Avoider

You see a principle violation in a PR, a design that’s heading in the wrong direction, or a team decision that’s going to create technical debt — and you say nothing. Not because you don’t notice, but because engaging feels uncomfortable, you don’t want to be “that person,” or you tell yourself it’s not worth the political cost. Over time, your silence becomes a signal that the standard isn’t real.

The Space Filler

You’re in every meeting, on every Slack thread, and in every design review — but you’re not actually shaping outcomes. You’ve confused presence with participation and visibility with impact. Your calendar is full, but if someone asked you to name the three most important things you influenced this quarter, you’d struggle to answer.