DEV Community

Cover image for Software Engineer to Engineering Manager. Should I?
Sergej Brazdeikis
Sergej Brazdeikis

Posted on • Updated on • Originally published at


Software Engineer to Engineering Manager. Should I?

You think about the manager path, and you see there is an opportunity, And you just can't put the dot on the decision. Let's explore it together.

Assess the motivation

Before doing it, first, explore why do want to do it? Writes down some notes for you:

  • Why do I think about it?
  • Do I imagine what the engineering manager role is?
  • Do I like it?
  • Am I curious to try it?
  • What benefits and disadvantages do you see?
  • There will be a lot to learn. Do I want to commit?
  • How do I see myself in two years? Five years?

Engineering manager. Should I switch from the engineer?

If you are curious to try it - do it.

When switched from an engineer to a more managerial role, I had to think on a team level. The very definition of success changed - now it is team success. System thinking on the team level is a daily exercise.

I also had to improve my soft skill tools. What I tell, how I speak, approach problems, react, behave, etc. All this suddenly had a way bigger impact. I learned many essential things about it for me as a manager. This experience had a very positive effect on my personality.

There are many other minor benefits from only getting this experience as an engineer and a person. This experience to look at teamwork from different expertise is invaluable.

It is not a promotion

Be aware of this! It is not a promotion - it is a track change!
When you switch from engineer to manager, you are a Junior Engineering manager. And it is fair. Folks who support your growth see you in that role.

Amount of coding

Hands-on is a very tricky topic. I can tell it is all in your hands, and it is tough to balance coding and accelerated growth as starting manager. I'm sure you will have to find the best balance for you while on the job, which approach works for you the best.

One thing is vital to say, as your responsibility will not be purely code related, we will have to delegate coding tasks on critical implementation path to full-time software engineers. This way, your other tasks as manager will not negatively impact the whole team's performance. I'm not saying you cannot do this, be aware of it.

What is Success for an Engineering Manager?

All managers are on a different path—some in first years, fifth or maybe tenth year. Our views will change during the trip, how we do stuff changes. Today I personally, the successful engineering manager is the one who facilitates the team to be successful. And we are accountable for that.

Today how I see the success for a team:

  • Software engineering team delivers measurable impact to end-users and business.
  • The team is motivated, engaged and happy. Team members are open and tell that it is a team, not just a group of people.
  • The team is excellent from the DORA metrics perspective
  • The team grows skills, and as the team as each personally.

If interested, I suggest reading about The Five Dysfunctions of a Team: A Leadership Fable

The window of opportunity for about two years

Even if you find out later that it is not for you - you can switch back to a single contributor.

Two years is a window opportunity because your coding skills will not have a chance to disappear; you, in any case, are still as an engineer as today. And the switchback will be smooth.

Worth mentioning that you will never really fully come back to a single contributor mindset after switching back. You will think on a team level. It is a permanent upgrade :)

The only possible downside is that you can potentially get not up to speed with the latest technologies. The reason is that you will have a lot to learn within your new role. When you switch back to engineer - you quickly catch up, and if you continue being a manager - you find a way to keep up.

Engineering manager salary

It is a natural motivator to scale. I want to clear one thing right away - if you think or find out that this is not your thing, there is no point living in pain. As a single contributor, you can grow further on the Software expert track. Staff engineers, Senior Staff Engineers, Architect roles are parallel growth tracks, and salary matches or, in some cases, surpasses the manager's path.

It is all about how good you are, your passion, and your role impact. Great Software engineers in the right company grow and significantly positively impact engineering quality.

Consult with a good manager

Talk to respected by you the manager, who you think it could be a good reference. A good manager will tell you how it is in the first person. What are the joys, the challenges, and what are the downsides? The experience can vary a lot. Ask a few managers to form a better understanding.

Types of the Engineering manager role

Here is a good dedicated blog post about it 5 Engineering Manager Archetypes from Pat Kua

If you choose to try it out, you will learn more techniques, like situational leadership and different ways to depend on the team state.

It is a rabbit hole on its own, and it is a beautiful path.

It is your decision

Whatever you decide is your choice, what path to go forward or when to do it. Do not get others to do it for you.

Enjoy the path you choose! It is most probably the right one :)

Top comments (5)

raphael_jambalos profile image
Raphael Jambalos

Agree on this post! I think treating being a manager as a promotion is bad, because it implies the only way to get promoted is to manage other people. But some people will thrive more just building their skills in their craft. In rejection of this ethos, I built my team at ECVPH to have 3 career tracks:

  • Managerial
  • Strong Contributor
  • Specialist

Performance bonus and promotions aren't supposed to be on how many people you manage but on how much your contribution is to the growth of the company, and to the growth of others

joelbonetr profile image
JoelBonetR 🥇

There are intermediate roles such tech lead which applies transversal knowledge in all those areas and in which you deal with the analysis and definition on the big picture of the project while managing people at high level (sometimes in detail about a given tech).

As the industry evolves it's trends come back to the time where you needed more people that can understand all parts even knowing much more on a couple of them (frontend, backend, data, infrastructure, DevOps, security, ML...) + Related "things".

I find myself in that role, being specialist in frontend [HTML, CSS, Sass/Scss, JS, websockets, how browsers work, 10+ years of experience...] + strong knowledge on [SEO, UX, Accessibility, Design] with the addition of backend [several years of experience on Node, PHP, Java... ] + Strong knowledge on Data [SQL, relational DBs, normal forms, scripting...] + Surface knowledge in [NoSQL, triggers, PLSQL...] + basic/intermediate knowledge in [Infrastructure, DevOps, Security, management, business, HR, marketing, economy, law...].

That makes me probably not the top tier single environment developer but the one who can plug all the pieces together and get the best of the team while defining E2E workarounds to reach the desired product.

it's a diverse industry with many specializations available and at the end it's all about project or company needs after all. 😁

jwp profile image
John Peters

Being a first line manager is the hardest job in IT. Only 2% are successful at it according to some studies. Don't forget that if you loved the programming side, you will have to leave it behind. I tried it for 5 years and got out. It didn't work for me.

dollardhingra profile image
Dollar Dhingra

This line here from your blog can be thought as a brief about what an engineer manager's role is about::

"When switched from an engineer to a more managerial role, I had to think on a team level. The very definition of success changed - now it is team success. System thinking on the team level is a daily exercise."

I really found your article very interesting and thought provoking, you covered a lot of ground here. Especially the part where you explain that one can always go back to individual contributor role from the managerial role. Looking forward for more similar articles from you!! Thanks

Also, would love if you can also check out my articles here on dev-to and if you can provide your feedback! Thanks again!!

metacollective profile image

Fantastic article. I went through a similar process few years ago and most of what you have written here is relevant. Specially things like soft skills, empathy, and not treating it like its a promotion. Become a servant leader and follow its principle.

I went through a phase where I had to be hands on dev for a while which made me realise how that changes everything. You tend to become more subjective to the task and loose bigger picture at times.

Thanks again!

Timeless DEV post...

Git Concepts I Wish I Knew Years Ago

The most used technology by developers is not Javascript.

It's not Python or HTML.

It hardly even gets mentioned in interviews or listed as a pre-requisite for jobs.

I'm talking about Git and version control of course.

One does not simply learn git