Most engineers become managers because they were great at engineering.
And that makes sense on paper. In practice, though, it’s where the trouble starts.
The skills that got you here don’t disappear, but they’re no longer enough.
Running a team means your job is no longer to be the best engineer in the room. It’s to make sure the right problems get solved, by the right people, in the right order.
The good news is that it’s a learnable skill.
In this article, we cover everything you need to make the transition: technical foundations, people skills, strategic thinking, and a practical plan to get up to speed.
Let’s dive in!
Key takeaways:
- The skills that got you here won’t be enough on their own. People management, strategic thinking, and business fluency are now just as important as technical credibility.
- Your most important tool is the one-on-one. You need a dedicated space for your team members to raise concerns, think through their development, and feel genuinely supported. Managers who get this right see significantly lower turnover.
- The first 90 days set the tone for everything that follows. Listen before you act, fix one visible problem before you set direction, and involve your team in shaping the plan.
4 essential skills every engineering manager needs
Here, we’ll take a closer look at the key skills you need as an engineering manager.
Technical expertise
One of the first temptations for new engineering managers is to step back from technical work entirely to focus on people and processes.
This is a mistake. Your engineers need to trust that you understand what they are dealing with.
Technical credibility does not mean coding all day. It means you can:
- You can read a pull request and spot an architectural problem
- You can hold a meaningful conversation about trade-offs
- Your team believes you when you push back on an unrealistic deadline
According to Pluralsight’s research, as a manager, your hands-on coding time will drop to around 5 to 10 percent of your working week, down from 60 to 75 percent as an individual contributor.
That remaining time is still valuable, especially for maintaining context on the codebase and earning respect from your team.
The harder adjustment is learning where your time actually goes now. Your work shifts toward people, process, and strategy:
- One-on-ones with your direct reports
- Sprint planning and roadmap sessions
- Hiring, interviewing, and onboarding
- Cross-team coordination and communicating with stakeholders
- Strategic thinking and longer-term planning
The engineers who struggle most with the transition are often the ones who were the strongest individual contributors.
Your output is still there. You just can’t quantify it on a sprint board.
Soft skills
Technical skills will get you the manager role. People skills will determine whether you keep it.
According to Gallup, the manager is the single biggest factor in employee engagement. They account for at least 70% of the difference in how engaged one team feels compared to another.
The most common mistake first-time engineering managers make is underestimating what people management actually requires.
Managing people is active, ongoing work. Don’t think it’s just scheduling one-on-ones and staying out of the way.
The core people skills for engineering managers fall into a few categories:
- Emotional intelligence. Understanding what motivates each person on your team, recognising when someone is struggling before they say so, and adjusting your communication style to the individual.
- Active listening. Being genuinely present in conversations, not formulating your response while the other person is still talking.
- Giving feedback. Engineers are used to blunt technical critique, but feedback on work behaviour or career development needs more nuance. Aim for feedback that’s specific, timely, and focused on behaviour.
According to Jellyfish’s 2024 State of Engineering Management Report, teams with strong management see 40% lower voluntary turnover than those with poor management.
Retention comes down to consistent one-on-ones, honest conversations about career growth, and making people feel genuinely supported.
The one-on-one is your most important management tool.
A good one is a dedicated space for the individual to discuss what’s on their mind, raise concerns, and think through their career development.
Come prepared with questions, but let the engineer set the agenda.
Most engineering managers underestimate how much this side of the job matters. The ones who take it seriously tend to build the best teams.
Strategic and business thinking
Engineering managers are responsible for more than delivery.
You’re responsible for making sure what your team builds actually moves the business forward.
You need to understand why the things on your roadmap matter and how your team’s work connects to company strategy, revenue, and competitive position.
The most important skill here is translating technical constraints into business language.
If your team needs 3 months to address technical debt before building the next feature, you need to explain that trade-off in terms a product manager or CFO will understand.
A few areas where this thinking gets applied most often:
- OKRs. If your team’s work can’t be connected to a measurable key result, that’s a signal either that the work is pointing in the wrong direction or that the key results need revisiting. Either way, it’s your job to start that conversation.
- Headcount decisions. Knowing when to ask for more resources, and how to make the case for it, is part of the role.
- Build vs. buy. These calls aren’t purely engineering decisions. They require you to understand what the business is optimising for and advocate for your team.
None of this happens overnight. But the sooner you start thinking about your team’s work in business terms, the more effective you’ll be in the role.
Delegation and decision-making
New managers often struggle with delegation because they know they could do the task themselves, probably faster and better.
But holding on to work that belongs to your team is one of the most common ways you create bottlenecks without realizing it.
And that’s why you need to learn how to delegate.
Effective delegation is about matching tasks to the right person, giving them the context they need to succeed, and staying available without micromanaging them.
Decision-making at the manager level works differently too.
You’ll face more decisions with incomplete information and real consequences. You need to learn the difference between reversible and irreversible decisions:
- Reversible decisions. Make them quickly and adjust based on what you learn. Waiting for certainty on low-stakes calls is a time drain.
- Irreversible decisions. These deserve more deliberation. Slow down, gather input, and think through second-order consequences before committing.
Managing up is a skill many engineers find uncomfortable, but it’s essential.
It means keeping your own manager informed of risks, blockers, and context they need before problems escalate.
It also means advocating for your team’s needs clearly and with evidence.
The most effective engineering managers make proactive communication a habit.
A brief weekly written update covering what the team accomplished, what’s at risk, and what decisions need to be made is one of the simplest tools available.
It builds trust and prevents the kind of surprises that will damage your credibility.
How to build and mentor high-performing teams
High-performing engineering teams don’t happen by accident.
You build one through deliberate attention to two things: psychological safety and clear expectations.
Research shows that teams with high psychological safety are 50% more productive and 76% more engaged than those without it.
Psychological safety means people feel safe speaking up, asking questions, raising concerns, and admitting mistakes without fear of punishment or ridicule.
It’s the manager’s responsibility to establish this culture, and it’s you do it through your own behavior.
Clear expectations are the other half. Your team needs to know what excellent work looks like for their role, how you measure success, and where they have autonomy.
Ambiguity creates anxiety, and anxiety kills a person’s output.
Mentoring is different from managing.
Managing means enabling the team to hit its goals. Mentoring, on the other hand, is about developing the individual over a longer period of time.
The best engineering managers do both. It comes down to 3 things:
- Career development conversations. Regular, honest discussions about where someone wants to go and what’s standing in the way.
- Stretch assignments. Giving people work that’s slightly beyond their current level, with enough support to succeed.
- Honest feedback on growth areas. Not just what someone is doing well, but what’s holding them back and how to address it.
When you’re building a team from scratch or adding to an existing one, pay close attention to what skills and working styles the team currently lacks.
Hiring for technical strength alone consistently produces teams that underperform.
Communication, curiosity, and good collaboration matter just as much, if not more, as raw technical ability over the medium and long term.
Creating your 90-day onboarding plan
The first 90 days in an engineering manager role are the most important.
How you spend them sets the tone for your credibility, your relationship with the team, and your effectiveness as a manager for months afterward.
Most new managers make the mistake of trying to change things too quickly. So, we’ve put together a short roadmap on what you should do instead.
Days 1 to 30: listen. Do one-on-ones with every member of your team and ask open questions.
Ask them what’s working, what isn’t, what would they change if they could.
Meet your peers in product, design, and other engineering teams. Read everything you can about the roadmap, the architecture, and the team’s recent history.
Days 31 to 60: identify patterns. What came up repeatedly in your conversations? What consistenly causes friction? What does the team seem most energised about?
Treat this like you’re a doctor diagnosing a patient.
What you find should drive your first decisions about what to focus in the coming months.
Days 61 to 75: fix one visible thing. It doesn’t need to be the biggest problem.
It needs to be something the team mentioned, something you can actually address, and something that signals you were listening.
This will build more credibility than just talking about your future plans.
Days 76 to 90: set direction. By now you’ve earned enough trust to have a real conversation about where you see the team going in the long term.
Share your thinking on what the team should focus over the next six months, and ask for honest input. People back plans they helped build.
Moving forward as an engineering manager
The skills covered in this guide aren’t a checklist you complete once.
Technical credibility, emotional intelligence, strategic thinking, delegation, and team building are all things you keep getting better at, if you put in the work.
The managers who grow fastest treat their own development as seriously as their team’s.
They ask for feedback, they reflect honestly on what went wrong, and they don’t wait for someone else to tell them where they need to improve.
Engineering management is one of the most important roles in a technology company.
Done well, it multiplies the impact of everyone around you. Done poorly, it becomes the single biggest constraint on what your team can achieve.
The skills are learnable. Changing your mindset takes longer.
Our best advice? Start with listening and go from there.
