In the tech industry, there is a common myth about career progression. The default roadmap is often presented as a straight line: you start as a Junior Developer, grow into a Senior Developer, and eventually, if you perform well, you become an Engineering Manager.
But this roadmap is fundamentally flawed.
Moving from writing code to managing people is not a promotion—it is a complete career change.
In his video series on the Google for Developers channel, engineering leader Addy Osmani tackles this crossroads. Deciding between staying on the Individual Contributor (IC) track or transitioning to the Engineering Manager (EM) path is one of the most critical decisions in a developer's career.
This guide breaks down both paths, debunks common misconceptions, and helps you identify which route aligns with your professional strengths and personal energizers.
---
1. Management is a Career Change, Not a Promotion
When a highly skilled individual contributor is moved into management simply because they are the most senior developer, it often results in the "Peter Principle"—promoting someone to their level of incompetence.
Why? Because the core responsibilities of these two roles are entirely different:
- As an IC: Your primary resources are code, architecture, algorithms, and technical systems. Your day is filled with direct, hands-on problem-solving.
- As an EM: Your primary resources are people, processes, communication, and organizational alignment. Your day is filled with meetings, one-on-ones, conflict resolution, and strategic planning.
When you transition into management, your technical coding output drops, and you must start as a beginner in a completely new set of human-centric skills.
---
2. The Individual Contributor (IC) Path
The IC path is designed for engineers who want to stay close to the technology. As you progress along this track (moving from Senior to Staff, Principal, and Distinguished Engineer), your impact scales through your technical expertise.
Core Responsibilities
- Writing, refactoring, and maintaining clean, high-performance code.
- Architecting scalable, robust systems.
- Drafting technical design documents and steering engineering standards.
- Building technical prototypes to prove concepts.
- Solving deep, complex technical bugs that block the team.
You will love this path if you are energized by:
- Solving logic-based puzzles and building concrete software assets.
- The deep satisfaction of shipping code and seeing it work.
- Spending long stretches in deep, focused concentration (Maker’s Schedule).
---
3. The Engineering Manager (EM) Path
The EM path is designed for engineers who find satisfaction in enabling others. A manager's success is not measured by what they build, but by what their team delivers.
Core Responsibilities
- Conducting regular one-on-one meetings with team members to mentor them and support their career growth.
- Removing organizational roadblocks and resolving resource constraints.
- Structuring team workflows, sprints, and release calendars.
- Collaborating with product managers and business stakeholders to align engineering tasks with company goals.
- Hiring, building, and retaining high-performing team cultures.
You will love this path if you are energized by:
- Helping people solve career blocks and achieve their professional goals.
- Organizing chaotic tasks into structured, efficient team workflows.
- Shifting from a "me" mindset (my output) to a "we" mindset (our team’s output).
- Navigating cross-functional conversations and managing project stakeholders (Manager’s Schedule).
---
IC vs. EM: A Side-by-Side Comparison
| Dimension | Individual Contributor (IC) | Engineering Manager (EM) |
| :--- | :--- | :--- |
| Primary Focus | Systems, code quality, and technical vision | People development, delivery, and team health |
| Daily Output | Code, architecture designs, code reviews | Aligning stakeholders, 1-on-1s, roadmap planning |
| Metric of Success | System stability, elegant code, technical impact | Team productivity, retention, successful launches |
| Daily Schedule | Blocked time for deep work (Maker) | Fractured time for meetings and alignment (Manager) |
| Coding Time | High (50% to 100% of the day) | Low to None (0% to 15% of the day) |
---
4. Leading Without Authority
A common misconception is that you must be a manager to lead. The reality is that senior ICs are expected to lead, but they do so without formal authority.
While managers lead by organizing people and project structures, senior ICs lead through:
- Influence: Persuading the team to adopt new architectural standards or tools through clear reasoning, prototypes, and data.
- Mentorship: Coaching junior developers on clean code practices and system design.
- Credibility: Building deep trust within the organization by consistently delivering high-quality, reliable work.
If you enjoy leading projects and setting technical direction, but do not want to handle personnel reviews, salary negotiations, or team conflicts, the Senior/Staff IC track is your ideal destination.
---
5. The Career Pendulum
The choice between the IC and manager tracks is rarely a permanent, "one-way door." In modern engineering cultures, professionals frequently swing between both paths—a concept known as the Career Pendulum.
``
[ Technical Skills ]
/ \
/ \
[ IC Track ] <============> [ EM Track ]
(Maker) (Manager)
\ /
\ /
[ Leadership Skills ]
``
- From IC to EM: Developers who step into management bring strong technical empathy. They understand the real-world complexities of code systems and respect the need for focused development time.
- From EM to IC: Managers who return to the technical track bring deep business context, product understanding, and communication skills. They understand how their code impacts the business and how to align team goals.
Swinging between these tracks makes you a more balanced, multi-dimensional engineer, regardless of which path you ultimately settle on.
---
Conclusion: Focus on Your Energizers
When choosing your path, ignore the default expectations of others and focus on what genuinely energizes you. Ask yourself:
At the end of a long week, what makes you feel accomplished? Is it shipping a complex system update or helping a teammate resolve a major career roadblock?
If it's the code, double down on technical excellence and scale your impact through the IC track. If it's the people, step into management and focus on enabling teams. Both tracks are essential, and both are highly rewarded in modern software organizations.
---
FAQs
Do managers make more money than ICs?
In progressive tech companies, the IC and manager tracks have parallel compensation bands. A Senior Staff or Principal Engineer can earn as much as (or more than) an Engineering Manager or Director of Engineering.
What is the easiest way to test if I will like management?
Start with low-risk leadership opportunities:
- Mentor a junior developer or intern.
- Lead the coordination of a small, multi-week feature release.
- Organize team retrospectives or stand-ups.
- Participate in hiring loops and candidate interviews.
Can I transition back to an IC role after being a manager?
Yes. It is very common to transition back. In fact, many tech companies value "hands-on" leaders who have spent time on both sides, as it builds rounded technical judgment and interpersonal skills.