(Why engineering leaders can’t afford to stop being engineers)
Being a leader in an IT organization often means spending most of your time with people.
Meetings, alignment, one-on-ones, cross-team collaboration.
That’s why it’s natural for us, when we think about growth, to invest in people skills such as communication, empathy, leadership, and influence.
But along the way, we often start to overlook the very skills that brought us here in the first place.
The technical skills that allow us to make fast, instinctive decisions.
The skills that help us understand complex systems, business trade-offs and the realities of the IT environment we operate in.
This article is a reminder that technical competence doesn’t stop being important once you become a leader.
Maintaining your technical craft is not about nostalgia or not beeing able to make another step.
It’s about credibility, responsibility and ownership.
Why it matters
The higher you go in engineering leadership, the stronger the temptation to drift away.
Less code, more meetings.
Less design, more reporting.
You stop touching systems, you start talking about them.
You stop understanding architecture, you start approving it.
At first, it feels natural. After all, you’re responsible for strategy, people, and long-term plans now.
However this is exactly where the technical debt of leadership begins.
Joel Spolsky once coined a brilliant term the astronaut architect. That’s the kind of technical leader who orbits high above teams, drawing diagrams, attending architecture reviews, making decisions, but having no idea what’s really happening in the code.
You don’t want to be this person.
Another examples are words of Captain David Marquet who wrote in Turn the Ship Around:
“You can’t lead a ship you don’t understand.”
A captain must know the ship, its engines, its structure, its limitations.
In engineering, it’s the same. You can’t design a good system, or lead the people building it, if you don’t understand how it works.
If someone tells you that a manager doesn’t need to understand their team’s work, they’re wrong. Our job isn’t to manage from a distance, but to lead through understanding.
Let’s be honest, none of us wants to be that kind of manager who just nods along.
We want to be the kind of leaders who truly understand what’s being said, who can ask meaningful questions, recognize the team’s challenges and help solve them.
That’s what builds credibility and trust. It’s what allows us to take real ownership of the project, the product, and the code.
How to stay close to your technical roots
It’s not enough to care about technology. Here are a few ways to keep your technical edge alive, even in a senior leadership role:
1. Make small code contributions and review code regularly
Once a month, or at least once a quarter, make a small contribution to the codebase.
It doesn’t have to be a feature. Fix a configuration, update a script, tweak a test.
The goal isn’t to deliver huge value, it’s to stay connected.
It’s extremally important to be able to clone, build and run the system locally.
It gives you enormous value of understanding the full lifecycle of a commit: push code, observe the CI build and watch the deployment process.
That experience gives you a grasp of what your engineers go through every day.
This allows you to see where processes slow down, what frustrates teams and where small changes could make a real difference.
Similar value you can get from performing occasional code reviews.
Reviewing code helps you understand the codebase, see how architectural and design principles are applied in practice and sometimes spot patterns or opportunities for improvement.
It’s also one of the most effective ways to observe technical growth within your team. You can notice progress, who’s improving, who’s plateauing and who might need more support.
2. Read leadership books rooted in engineering reality
Not all leadership books are equally useful for engineering leaders.
Generic management advice often breaks down when confronted with real systems, real constraints, and real engineers.
That’s why it’s worth investing time in leadership books written specifically for technical and IT environments. Books like:
- Accelerate: The science of Lean Software and DevOps…,
- The Phoenix Project,
- Team Topologies,
- The Manager’s Path.
They connect leadership decisions directly to system design, delivery flow and team structure.
Reading this kind of material strengthens your ability to make decisions that work both for people and for technology. It keeps your leadership grounded in the reality of IT industry in the reality of your teams.
3. Learn through architecture and technical discussions
Actively participate in architecture reviews, design sessions and regular technical discussions with your engineers.
Not to dominate the conversation, but to understand why decisions are made and what trade-offs they involve.
These discussions keep you aligned with your technical leaders and grounded in the real direction of the system. They help you understand current challenges, emerging patterns and architecture changes.
You can’t understand architects you don’t understand.
Don’t treat these conversations as status updates. Treat them as mentorship from your experts.
When you ask questions and engage with curiosity, you gain access to condensed technical and domain knowledge, insight that would otherwise take months to acquire on your own.
At the same time, you send a strong signal that expertise matters and that thoughtful technical leadership is valued.
4. Read every ADR and architecture document
Make it a habit to read most of Architecture Decision Records (ADRs) and system documentation.
Comment, ask clarifying questions and give feedback.
When leaders read documentation, it sends two powerful signals:
- Documentation matters, because someone reads it.
- You care enough to understand the system and its domain.
Documentation isn’t bureaucracy. It’s the living memory of your organization’s technical decisions.
5. Use Certifications as Structured Learning
Certifications can be a powerful tool, not as a badge, but as a learning framework.
They force you to revisit fundamentals, update outdated knowledge, and understand systems end-to-end.
Good examples include:
- cloud certifications from Amazon Web Services, Google Cloud, or Microsoft Azure,
- architecture-focused paths like The Open Group (TOGAF),
- security, reliability, or DevOps certifications depending on your domain.
Even if you never take the exam, following a certification curriculum can be an excellent way to systematize your technical understanding.
6. Stay Curious About the Industry (Beyond Your Company)
Technical growth doesn’t stop at your organization’s borders.
Read engineering articles regularly, especially long-form content:
- architectural case studies,
- failure analyses,
- scaling stories,
- trade-off discussions.
Platforms like Medium are particularly valuable here, because they expose you to how other teams think, not just what tools they use.
You don’t need to chase every trend, but you do need to stay technically literate in the present.
Final Thought
Great engineering leadership is built on understanding, not distance.
You don’t need to write production code every day to be a strong leader, but you do need to stay close to the craft.
When you understand the systems your teams build, you make better decisions. When you understand the challenges they face, you earn their trust. The real technical debt of leadership is not stepping away from the keyboard. It is stepping away from learning.
That’s how technical leaders grow and how they earn the right to lead.
