Published July 30, 2024 · 8 min read

I often get asked whether someone should transition into management. In the past, this might have been the only viable growth path. However, in most large organizations today, this is no longer true, as you can be a leader without managing people. It really comes down to a fundamental question: do you genuinely want to, and would you enjoy it? Additionally, there are a few pros and cons to consider about management.

Before even discussing the pros and cons, there's one crucial point I want to make: management is an entirely different job. While you can leverage your technical judgment, you will rarely engage in technical tasks. The most I do nowadays is to use Math.random() to select someone for a fun task. Yes, you might still face technical interviews, including coding and design questions, but this usually changes once you reach a higher level, where these skills become almost irrelevant. Why would you want your Director to code, really? That individual demonstrated those abilities years ago. 

Returning to the question at hand, transitioning into management means taking on a different role that you need to consider carefully. There are aspects of this job that you may not fully anticipate but might find appealing. Here are a few things you would typically do, from manager transition.

• Hiring and Forming a Team
• Onboarding
• Attrition
• Performance Improvements
• Layoffs, Letting Go, and Firing
• Growth and Promotions
• Crucial Conversations
• Team Happiness
• Team Success
• Team Harmony
• Conflict Resolution and Avoidance
• Reacting and Taking Action
• Tracking and Reporting
• Trade-Offs
• Budget
• Planning
• Stakeholder Asks
• Focus Time
• Soft Skills and Technical Skills
• Changing Companies
• Promotions

being a clown of a manager

You are expected to handle all these responsibilities, yet you likely were never trained for any of them. That’s why I emphasize that management is an entirely different job. This transition comes at a cost, especially if you are passionate about your craft. For instance, you may have to fire people, which is unpleasant. You'll also need to consider aspects of the job that you previously didn’t care about because they seemed fine at the time.

Engineering Manager vs. Software Engineer

Now, I hope I convinced you that this is a different job. Let’s now see what the pros and cons are. 

Engineering Manager

Pros:

1. Higher Compensation: Engineering managers typically earn higher salaries than individual contributors due to the increased responsibility and leadership skills required.
2. Leadership and Decision-Making: The role allows for significant influence over project direction, team strategy, and organizational goals, offering a sense of accomplishment from guiding successful projects.
3. Career Advancement: The managerial track often leads to further opportunities for career growth, such as senior management or executive roles.
4. Expanded Network: Engineering managers interact with various stakeholders, including executives, clients, and other departments, which can broaden professional networks and open doors to new opportunities.
5. Impact on Team Development: Managers have the opportunity to mentor and develop their team members. Witnessing someone improve and succeed due to your guidance feels immensely rewarding.

Cons:

1. Reduced Technical Engagement: Managers often spend less time on hands-on technical work. It eventually leads to a decline in technical skills over time.
2. Increased Administrative Duties: The role also involves more meetings, performance reviews, approving leaves, and other administrative tasks.
3. People Management Challenges: Handling interpersonal issues, team dynamics, and performance management can be stressful.
4. Performance Pressures: As a manager, you represent the team. You are accountable for both its failures and successes. You need to handle the pressure of leading the team and ensure that organizational goals and deadlines are met.
5. Work-Life Balance: A manager often needs to work outside of regular working hours. While some believe it should be possible to avoid this, the reality for many is different.
6. Job Opportunities: The higher you advance in your role, the fewer open positions there will be. Companies often prefer to promote from within for higher roles, making it increasingly challenging to climb the career ladder as a manager.

Software Engineer

Pros:

1. Hands-On Technical Work: As a software engineer you keep working on your craft. Immediate return from your work is satisfying.
2. Regular Hours: Engineers can typically work standard business hours. You might occasionally need to spend time overlapping with different regions, but this usually isn't a daily requirement.
3. Technical Mastery: Engineers have the opportunity to specialize and deepen their expertise in specific programming languages, tools, and technologies.
4. Clear Career Path: There are distinct junior and senior roles, providing opportunities for career progression based on technical skills and experience.
5. Less Administrative Overhead: You focus on technical tasks with minimal administrative responsibilities​.

Cons:

1. Potential Salary Limitations: While software engineers can earn good salaries, they are generally lower than those of engineering managers.
2. Limited Influence on Strategy: As an engineer, you don’t get to decide on the strategic direction of projects and the organization. You can influence it, but making these decisions is primarily within the manager’s realm.
3. Need for Continuous Learning: You need to keep up with evolving technologies. It requires ongoing education and skill development.
4. Guidance and Mentorship: Engineers may require guidance from senior colleagues or managers, which can slow down their workflow and project progress.
5. Career Ceiling: There might be a limit to how far one can advance purely on the technical path without transitioning into some form of management​.

Making the Transition

Alright, we now understand that management is a different job and have discussed its pros and cons. So, when is the right time to make the change? Honestly, I don’t know. What I do know is that you need to be technically sound and somewhat prepared interpersonally for the role. If you try to become a manager too early in your career, you might struggle to gain respect as you won’t yet have technical mastery. Interpersonal skills also develop over time, so it's important to spend a few years in the field.

Most large companies require you to be at least a senior software engineer before considering a transition to management. Even then, I would argue that you should be at the ceiling of that level before seriously thinking about it. Ideally, a senior-plus role is a good time to make the change.

What happens when you want to make the change? Well, nothing initially. You need to express your interest and let your manager know that you’re considering this path. Remember, management opportunities depend on business needs. If there isn’t a business reason for you to become a manager, it won’t happen. So, keep that in mind.

If there is a business reason and you’re making the transition, you should definitely go through some training, read relevant books, and get up to speed. You don’t want to become just another incompetent manager. Ideally, your boss should guide you, as it’s in their interest to make you successful.

It Ain’t for You

So, you made it—you became a manager. Now you realize it’s not what you expected and it sucks. What do you do? Remember, you’re still technical. This isn’t the end of the world. You tried it, and you simply don’t like it. Maybe it’s not the right time for you. I've seen this happen multiple times: someone becomes a manager, doesn’t enjoy it, returns to being an engineer, and then, after a few years, tries management again. This time, they are mentally prepared and find they actually like it.

But what does "liking it" really mean? It doesn't mean the job isn’t challenging or that you won’t have tough days. Management is a different, often difficult job. You’ll feel like you don’t know many things, and your team might ask questions that make you feel stupid. That's normal. Even experienced managers don’t have all the answers right away. It gets easier over time.

Liking it means feeling that this role is for you, even if it pushes you out of your comfort zone. Despite all the challenges and frustrations, you kind of enjoy it. You appreciate your impact, and you enjoy the leadership aspects, even the corny "boss" jokes. If you feel this way, then it might be worth sticking with it. Otherwise, there’s no shame in returning to an engineering role and perhaps trying management again later if you still have the interest.

This has been more than a blog post I guess but here we go. I hope I answered different aspects of this transition. Transitioning to management is a major shift from engineering, involving new responsibilities like meetings, performance reviews, and mentoring. The best time to make this change is when you have strong technical and interpersonal skills, usually at a senior level. If you try management and don’t like it, you can return to engineering and possibly try again later. Ultimately, if you enjoy the leadership role despite its challenges, it might be a good fit; otherwise, stepping back is okay.