Senior doesn't mean you stop writing code

There's a common trajectory in tech: junior developer, mid-level developer, senior developer, tech lead, engineering manager. At each step, the expectation of how much code you write decreases. By the time you're a tech lead, you might spend most of your time in meetings, reviewing work, and writing documents.

This trajectory is not inevitable, and it's not always right.

What You Lose When You Stop Building

Engineering intuition is perishable. The sense of what's expensive, what's risky, what's elegant—it degrades when you're not practicing it. A year away from production code and you're estimating based on how hard things used to be, not how hard they are now with the libraries and patterns the team is actually using.

You also lose credibility. Engineers notice when their lead can't answer a specific technical question because they haven't touched that part of the stack in eight months.

What Senior Actually Means

Seniority is about judgment and impact, not about writing less code. A senior engineer makes the whole team more effective—through code review, through clear architectural decisions, through mentoring, through writing code that sets patterns others follow.

The output changes. The hands-on work doesn't have to.

Staying Sharp

The simplest approach: own something technical. Pick an area—the deployment pipeline, the performance monitoring, the design system—and be the person who maintains and improves it. Not as extra work, as part of the job.

When I do code reviews, I try to understand the code well enough to have written it differently. That requires actually thinking like a developer, not a reviewer.

The Exception

Some people want to move into pure management and that's a legitimate path. But be clear with yourself that you're making that choice, not drifting into it. And know what you're giving up.