Engineer to manager

From engineer to manager: the complete guide

9 min read Last updated
An engineer at his laptop, with an arrow rising to the same man standing as a confident leader
In short

Why the move fails, the skills it needs, and a roadmap for your first year leading people.

Why the move from engineer to manager goes wrong

Many engineers become managers the same way. You were the strongest technical person on the team, a role opened up, and you took it. On Friday you solved problems. On Monday your job was to help other people solve them.

The habits that earned the promotion start to work against you. You own the answer, check every detail and fix things yourself, so your team waits for you. You become the bottleneck. You work longer hours and still feel behind. The firm pays for it in stalled projects and good people who leave.

Engineering rewards precision and evidence. There is usually a right answer, and you can prove it. People problems rarely work like that. Two reasonable people can read the same situation differently, and both can be partly right. A difficult conversation comes with no spec.

Managers account for at least 70% of the variance in employee engagement across business units. Source: Gallup, State of the American Manager

So a first-time manager shapes how engaged their team is. Yet the promotion often comes with no preparation.

82% of people who step into management in the UK have had no formal management or leadership training. Source: Chartered Management Institute with YouGov, October 2023

The same move trips up consultants, finance and legal professionals promoted for their expertise. This guide uses engineers as the example. The advice holds for any technical or analytical team.

What is an accidental manager?

Accidental manager: a technical professional promoted to lead people because they were expert at the work, or because the next salary band required it, with no preparation in how to lead the people who do it.

Accidental managers can become excellent leaders. They start with one gap: they know the work inside out, and they’ve had no help to lead the people who do it.

Some leadership courses make that gap wider. They ask technical people to perform: act more confident, project presence, smile more in meetings. A rigorous mind reads that as fake, switches off, and the gap stays open. More on this in why leadership is not performance.

“Your technical skill got you the promotion. It won’t lead the team for you. Leading people is a skill, and engineers are very good at learning skills.”

Cam Smith, Global CEO, Engineering Leaders

The four skills that change

You keep who you are. You point what you already have, clear thinking and care for doing things properly, in a new direction.

Delegation

As an engineer, you measured your day by what you produced. As a manager, you measure it by what your team produces. Delegation makes that happen.

Hand over whole pieces of work. Make the outcome and the standard clear, and let people choose the method. Agree check-in points up front, then keep to them instead of hovering. Expect the work to come back done differently from how you would do it. Different can still be right.

A simple test: if you still do the work you’re best at, ask who on your team should be learning it.

Feedback

Small problems turn into performance problems when you don’t raise them. Give feedback early, in private, and about behaviour you saw. Say what happened, what effect it had, and what you’d like next time.

Give positive feedback with the same precision. “Good job” teaches nothing. “The way you walked the customer through the risk register kept the meeting on track” tells someone exactly what to repeat.

Ask for feedback on yourself too, and act on it where your team can see.

Conflict

Engineering teams argue about technical choices all the time, and that’s healthy. Trouble starts when disagreement turns personal or goes underground.

Bring it back into the open. Name the disagreement. Separate facts from preferences. Agree how the team will decide, and who decides, before you decide. Then back the decision, even if you’d have chosen differently.

Influence

Your title gives you less authority than you expect, especially with peers, customers and senior leaders. Influence comes from understanding what the other person cares about and making your case in their terms.

A board wants risk and cost. A site team wants to know what changes on Monday. A customer wants confidence the job will land on time. Same facts, three different stories.

Your first year, stage by stage

You won’t master this in a month. Treat your first year as four stages, each with one main focus. Move on when the foundation holds, whatever the calendar says.

First 30 days: listen and learn

Meet every person on your team one to one. Ask what works, what gets in their way, and what they need from you. Learn how your own manager measures success. Change very little. You’re building trust and a clear picture of the team, and both take time.

Days 31 to 90: set the rhythm

Agree a regular rhythm of team meetings and one-to-ones, and protect it. Make expectations clear: what good looks like, who decides what, and how people raise problems. Start to delegate real work, and pick one or two quick wins the team cares about. The first 90 days checklist takes you through it week by week.

Months 4 to 6: build trust through feedback

By now you know your people. Give regular feedback both ways, and have the conversations you’ve put off. Expect your first real conflict, and handle it in the open. This stage feels uncomfortable. That’s normal.

Months 7 to 12: lead beyond your team

Turn outward. Build relationships with peers, customers and senior leaders, and practise influencing without authority. Start developing the people who might lead after you. Then look back at how you lead under pressure, and choose what to work on next.

Your first year at a glance
Stage Focus Stop Start
First 30 days Listen and learn Fixing every problem yourself One-to-ones with every person
Days 31 to 90 Set the rhythm Deciding everything alone Clear expectations and real delegation
Months 4 to 6 Trust through feedback Putting off hard conversations Regular feedback, both ways
Months 7 to 12 Lead beyond your team Winning on technical argument alone Influence with peers, customers and leaders

Six mistakes new engineering managers make

We see the same six again and again. Most are good instincts used in the wrong place.

  1. Staying the best engineer on the team. You keep the hardest technical work because you’re fastest at it, and your team never grows.
  2. Fixing instead of coaching. Someone brings you a problem and you solve it. Next week they bring you another one.
  3. Waiting too long to give feedback. You hope it sorts itself out. It rarely does, and the later conversation is harder.
  4. Treating every disagreement as a technical debate. You win the argument and lose the person.
  5. Copying a manager you admired. Their style worked for them. Acted out by you, it reads as fake.
  6. Going it alone. You don’t ask for help, because you were always the one with the answers.

For the leaders who promote engineers

If you promote engineers into management, you decide whether the move works. Get it wrong and you lose a strong engineer, a project slips, and the team starts to drift. In Australia, workload, conflict and poor support also count as psychosocial hazards: every state and territory now has psychosocial duties in its workplace safety law.

  • Say what the job is. Tell new managers how you will measure their success now, and how much technical work they should keep.
  • Give them support before they need it. A program, a mentor or a coach in the first 90 days costs far less than a lost engineer or a failed project.
  • Make room for mistakes. New managers learn by doing. Protect them while they practise.

How we help new managers lead as themselves

Reading helps you name the gap. Closing it takes practice under real pressure, with someone who can show you what you can’t see in yourself.

We built our work on the Authenticity Cycle. We reveal how you lead in a simulation that puts your team under real pressure. We explain why you show up that way with an assessment. We develop the habits through a program and coaching on your own work, until they hold back at the desk.

More than 100 leaders in one electrical engineering business went through our Coaching for Performance program and rated it NPS 75. 75% were promoters and none were detractors. We’ve worked with 60+ companies across 11 sectors.

For people in their first one to three years of leading, start with From Accidental to Authentic.

Good leaders keep practising for as long as they lead.

Engineer to manager questions

How long does it take an engineer to become a good manager?

Expect the first year to be the hardest. Many people feel the shift once delegation and feedback become habits. The pace depends on your team, your own manager and the support you get.

Should engineers keep doing technical work after becoming a manager?

Some, early on, especially in a small team. Keep enough to stay credible and close to the work. Hand over anything someone on your team should be learning, and anything that stops you making time for your people.

What is the hardest part of moving from engineer to manager?

For many engineers it’s letting go of being the person with the answer. Your value moves from what you produce to what your team produces. Feedback conversations come a close second.

Do engineers make good managers?

Many do. Engineers bring clear thinking, care for quality and a habit of learning skills properly. They struggle when they get no support for the people side, or when a course asks them to act a part.

Is leadership training worth it for new engineering managers?

Yes, if it shows you how you lead under pressure, explains why, and lets you practise on real work. Courses that ask you to act a part rarely stick. Look for simulation, an assessment and follow-up coaching.

Can a software engineer move into management the same way?

Yes. The same four skills change: delegation, feedback, conflict and influence. Software teams often move faster and work remotely, so the rhythm of one-to-ones and written communication matters even more.

Ready to lead as yourself?

Tell us where your leaders are stuck. We'll tell you honestly whether we can help.