EM

Dock

HomeBlogAbout MeContact

Letting Go Without Losing Touch: Staying Technical as an Engineering Manager

You don’t have to abandon your technical edge as an EM — you just need to redefine what “technical” means and where your value truly lies.

Sandeep Varma

Jan 29, 2026 · 4 min read
Letting Go Without Losing Touch: Staying Technical as an Engineering Manager
Photo by airfocus on Unsplash

When engineers step into management, one of the biggest questions they wrestle with is:
"How do I stay technical without being in the code every day?"

It’s a real fear, that you'll drift too far from the craft that got you here. But the truth is, staying technical as a manager is not about clinging to code. It’s about evolving your technical engagement to match your new responsibilities, particularly as architectural guidance replaces direct execution, a shift I examine in Guiding Architecture Without Being the Architect.

Here’s how you can let go of coding without losing your edge.


Redefining “Technical”

Being technical as an EM doesn’t mean pushing PRs every week. Instead, it means:

  • Thinking in systems and architecture, not just functions and files.
  • Spotting design flaws and guiding tradeoff conversations.
  • Understanding where your team's time is going, and why.
  • Coaching engineers to think more deeply, not solving it for them.

You’re shifting from being the doer to being the multiplier. That doesn’t mean you're less technical, just technical in a different way.


Ways to Stay Close Without Being the Bottleneck

You can stay plugged in without being on the critical path:

  • Participate in design reviews: Ask good questions, challenge assumptions, and model system level thinking.
  • Read PRs periodically: Not to nitpick, but to understand patterns and gaps.
  • Pair program occasionally: This builds connection, reveals friction points, and shows you still care about the code.
  • Keep up with your team’s stack: Try out new tools or experiment with internal systems in a sandboxed way.

These actions keep your instincts sharp and your team confident in your technical presence, without you being a dependency.


Set Boundaries Around Coding

If you do code, be mindful:

✅ Do

  • Fix a one off, non blocking bug
  • Contribute to internal tooling or cleanup tasks
  • Work on personal side projects to stay sharp
  • Spike on prototypes to explore ideas (then hand off)

🚫 Don’t

  • Take on critical features
  • Own production code on the critical path
  • Commit to timelines that compete with your real job: leading

Coding should energize you, not stress your team. If you’re consistently pulled to write code, ask yourself: Are you avoiding the hard parts of management?


Technical Leadership is Still Leadership

Remember, staying technical isn’t about proving you can code. It’s about bringing clarity to complexity.

  • Can you identify the right abstraction?
  • Can you lead through ambiguity?
  • Can you guide teams through tradeoffs?

Those skills are deeply technical, and often more valuable than writing the code yourself.


Final Thoughts

Letting go doesn’t mean letting down your technical bar. It means raising your altitude and shifting your impact.

Staying technical as a manager is possible, but it requires a mindset shift. You’re not here to be the smartest coder in the room. You’re here to make everyone else better.

If you are also navigating what it looks like to stay technically credible while stepping fully into the manager role, Should Engineering Managers Write Production Code? makes a direct and opinionated case for where the line should sit.


Still figuring out how to balance coding and leadership? I’d love to hear your experience, drop a comment or reach out.


Did you find this useful?


Comments

Loading comments...

to post a comment.


About the author

Sandeep Varma

Senior Engineering Manager

I write about leadership and software engineering from experience as a software engineer, product owner, and engineering manager, grounded in a Bachelor’s in Computer Science Engineering and an MBA in IT Strategy.

View full profile

Continue reading

Next →

How to Guide Architecture Without Being the Architect


How to Guide Architecture Without Being the Architect

Your job as an EM isn’t to design the systems yourself — it’s to create the environment where great architecture can emerge.

Should EMs Code? A Balanced Perspective

An experience-driven argument for why writing production code often feels right in the short term, but quietly undermines the real responsibilities and long-term impact of engineering management.

The Real Meaning of Technical Debt in Software Engineering

Why software teams sometimes move fast with imperfect code and how responsible teams clean it up.