A few weeks ago, I had the opportunity to give a presentation to my engineering team at Athenian. It was important for me to provide them with a clear understanding of the different career paths available to software engineers and how they can coexist within our organization.
I wanted to emphasize that transitioning from an individual contributor (IC) to a management position is a significant change. It requires a different skill set, mindset, and approach to work. As the Head of Engineering at Athenian, I’ve personally experienced this transition and the challenges that come with it.
To help software engineers navigate this career path and make informed decisions, I decided to distill the key points from my presentation into this article. Whether you’re considering a move into management or simply want to understand the different paths available, this article will provide valuable insights.
The IC to Manager Pipeline
When you’re an IC, promotions typically come automatically based on technical expertise. However, becoming a manager requires an opportunity to lead a team. This opportunity arises when a particular area of the engineering organization, such as the web application team, starts to grow. At that point, someone from the team is given the chance to step up and manage the team.
Ideally, the person who takes on this role should already have a clear understanding of what it means to be a manager and a genuine interest in the position. This allows them to be more effective and fulfilled in their new role.
The Existential Crisis
Before I became the Head of Engineering at Athenian, I mistakenly believed that being a leader meant still being heavily involved in coding. However, I quickly discovered that being a full-time manager is an entirely different game. As a manager, you’re no longer expected to code, and this can lead to an existential crisis for those who come from a software engineering background.
It’s crucial for software engineers to be aware of this struggle when deciding between growth as a developer or pursuing a managerial role. The best software developer on the team may not necessarily make the best manager. This is why both the team and engineering leaders must have a clear understanding of the responsibilities and qualities required for effective management.
The Mindset Shift
As I transitioned from a developer to a manager, I realized that my productivity would no longer be measured by what I was building but by how much I was empowering others to succeed and continuously improve. This mindset shift is essential for managers to appreciate the output of their team and understand that their role is to enable great things to be built.
Talking to experienced engineering leaders who have gone through this transition can be immensely helpful. They can provide valuable insights into the challenges they faced initially and continue to face today. When stepping into a leadership or management role, understanding whether your passion lies in coaching or building will guide your journey.
The Salary Myth
It’s important to note that the compensation for managers and ICs can be the same, level by level, up to the VP/CTO level. While this may not be true for all companies, at Athenian, we believe there’s no need to become a manager solely for higher compensation. Instead, your career path should be based on what you truly enjoy doing, rather than how much money you will make.
The best results come from aligning responsibilities with passion and involvement, not from focusing solely on money. So, when deciding whether to pursue a managerial role, consider what path resonates with you and aligns with your goals and interests.
Choosing a Path
To determine which software engineering career path is right for you, consider the types of responsibilities that appeal most:
- Tech Mastery: Expertise in a specific domain or framework
- Tech Management: Focus on architecture and best practices
- People Management: Mentorship and career progression
- Execution Management: Planning, prioritization, and delivery
Depending on the company’s context, these responsibilities may be split differently. It’s crucial to understand how technical the company is and how they value ICs and managers.
Life as a Manager
As the Head of Engineering at Athenian, my days are a blend of tech, people, and execution management. I’m focused on preparing the engineering organization for scale, aligning with other leaders, managing execution, and maintaining a strong tech focus. It’s important to note that this is based on the current size of our team, and the responsibilities may evolve as we grow.
Working in a supportive environment with a high-quality leadership team has allowed me to continuously grow as a leader. It’s rewarding to work towards a shared vision for the company and enable my team to build great things.
In conclusion, understanding the various software engineering career paths and the mindset shifts required for each role is essential for making informed decisions. Whether you choose to pursue a managerial position or continue as an IC, it’s crucial to align your career path with your passion and goals. At Athenian, we value the overlap of responsibilities and passion, believing that this leads to the best results. So, go ahead and choose the path that speaks to you and empowers you to thrive as a software engineer.