The reality of being a distinguished engineer

Estimated reading time: 6 minutes

Key takeaways:

• It’s not tech vs. leadership – it’s both. Distinguished engineers are “IC executives” who shape direction, not just code,
• Impact comes from systems, not heroics: the real job is designing organizational systems so great engineering outcomes happen by default.
• Influence > authority in a self-defined role.

---

The path to becoming a distinguished engineer is rarely a straight line. I’ve spent years swinging back and forth on the engineer-manager pendulum.

Deeply technical work brings me immense joy, that’s just where my heart lies, but leadership roles build valuable skills you can’t get any other way.

When I read Staff Engineer by Will Larson, I realised I didn’t have to choose between the two. It taught me that technical leadership is a path in its own right. My organization didn’t have a distinguished engineer title at the time, so I made the case for one. I’m grateful they took the chance!

Perhaps because of the title, there’s a certain mystery around this role. The most frequent question I’m asked is “what does a distinguished engineer actually do?” My honest answer is usually something like “that’s a great question, and I wish I knew the answer.” It’s just not the sort of role that comes with a well-defined job description.

What is a distinguished engineer?

Each step along the staff+ path is an expansion in scope and context. At the distinguished level, that expansion is significant.

Charity Majors, CTO of Honeycomb, calls it the “IC executive” role, and I think that captures it well. The work becomes less about solving problems yourself and more about helping the organization figure out which problems to solve, and helping others find the path through them.

In practice, it’s a uniquely self-directed role. Sometimes you’ll be pointed at a specific problem; just as often you need to find it yourself. You’re expected to find where you can add the most value. This means no two distinguished engineers operate the same way. The role is shaped as much by the person in it as by the organization around them.

You spend your days moving between teams, domains, and layers of the organization. That gives you a breadth of context that most people don’t have, and with it the ability to ask the right questions at the right time.

When a problem has been growing in perceived complexity as different teams engage with it, everyone is looking at it from within their own area. They each assume the whole thing must be enormous. Often the answer is much simpler than the conversation has become. The value you bring is the vantage point to find a simpler framing and a path forward.

Who you collaborate with

The role puts you in conversation with people across the full breadth of an organization – executive leadership one day, a recently joined graduate the next.

You get to see what people at every level are dealing with: the challenges they’re working through, the decisions they need to make, the tools they have at their disposal. You find yourself scaling across all of it, up and down, side to side.

There are periods where the work takes you outside engineering entirely, into governance, operations, or other parts of the business where technical decisions have real consequences. People in those areas are often grateful to have someone with technical expertise in the room who can translate.

However, the collaboration that matters most, and gets talked about least, is with the engineers in the teams. Not directing their work, but creating the conditions for them to take pride in what they do.

I’ve long believed that excellence isn’t achieved through individual heroics, but by designing systems in which great work becomes the natural outcome. That’s what this role is really about: designing those systems – the guardrails, the feedback loops, the structures that help teams move quickly while keeping customers safe – not just in software, but in the human organization that produces it.

Something that doesn’t get spoken about enough is how lonely this role can be. There are very few distinguished engineers in most organizations. The ones who exist are often spread across different parts of the business with limited crossover.

If most of your peers are on the management track, their day-to-day concerns and priorities will be quite different to yours. You can find yourself being a different shape to everyone else in the room. It’s not always obvious who your first team is, and that’s something worth thinking about if you’re considering this path.

The skills that matter for distinguished engineers

For distinguished engineers, technical skills are table stakes. You wouldn’t get here without deep expertise, but what defines the work at this level is a different set of capabilities:

Systems thinking

This does not mean distributed systems (though that helps), but learning to see the organization itself as a system. Understanding how incentives, structures, and communication patterns shape the software that gets built.

If teams are producing tightly coupled services, a better architecture document is unlikely to fix it. The system is producing exactly what it was designed to produce, and you need to understand the aim of the system before you can change its outputs.

Judgement born from experience

Career progression is primarily about expanding cognitive scope. Early on, the question is “can I make this work?” Later, it becomes “how does this fit together?” and then “how do teams produce good outcomes?”

At distinguished level, the question becomes “how do we design the system that designs systems?” You get there by having been wrong enough times, in enough different contexts, to start recognizing the patterns.

Influence without authority

Your impact comes through authentic collaboration with a wide network, the clarity of your thinking, and the trust built over time. The title helps open doors, but if it’s the only reason people listen, something has already gone wrong.

Thinking in abstractions

The ability to reason from first principles and apply lessons from one context to another is fundamental to this role. For me, that came from two places.

One was the engineer-manager pendulum: each swing between management and IC work gave me a different lens, and you don’t lose the skills from one side when you cross to the other, you layer them. The other was working across organizations of very different sizes, from startups and scale ups to large enterprises.

Each environment has its own constraints and tradeoffs. Having experienced that range gives you a broader set of abstractions to draw from.

How the distinguished engineer role is evolving in 2026

One of the tensions of senior technical roles is the tradeoff between execution and scope. The broader your remit, the harder it becomes to stay hands-on.

Some distinguished engineers manage to remain deeply involved in building, while others find their time consumed by the strategic and cross-cutting work the role demands.

AI is easing that tension for many. Anyone whose scope has outgrown their ability to stay hands on is finding that the calculus has shifted.

AI is also creating entirely new categories of work and changing the nature of existing roles. How engineers operate, what skills matter, what scope they own, how teams are structured, how quality is maintained – all of these are shifting. That represents a real opportunity for all engineers, distinguished included.

With the level of context and scope the role provides, and access to people at all levels of the organization and across departments, we have the visibility to spot patterns as they emerge and the reach and influence to draw attention to the things that need it.

So much of how we organize engineering work was designed for a world where humans did all of it. That’s no longer the world we’re in, and most of it is open for redesign. For a role built around seeing systems and designing better ones, it’s a genuinely exciting time.

The tools are new and our reach stretches further. Now we just need to figure out how to build the system that builds the right things well.

Get articles like this in your inbox

Choose your LeadDev newsletters to subscribe to.