2 Individual contributor to engineering manager

This chapter covers

Differences between an individual contributor and an engineering manager
Common misconceptions when transitioning to engineering manager
Sharing intentions and motivations for becoming an engineering manager
A three-phase approach for the transition
How to help others go from individual contributors to engineering managers

My job is not to be easy on people. My job is to take these great people we have and to push them and make them even better.
—Steve Jobs

In chapter 1, we explored the responsibilities of an engineering manager (EM) and emphasized the importance of managing teams and individuals in this role. As more software engineers consider a move into management, understanding the distinctions between the roles of an individual contributor (IC) and an EM becomes crucial.

ICs contribute to the team and organization without managing others. If you’re currently a software engineer, you fall into the IC category. On the other hand, an EM supervises and manages other engineers, orchestrating engineering excellence. If you’re responsible for a group of software engineers and engage in people management, you are considered an EM; if you do the same for other managers, you are a senior manager.

2.1 Differences between the IC and EM roles

2.2 Common misconceptions

2.2.1 IC to EM is not necessarily a promotion

2.2.2 EMs do not always write code

2.2.3 Coding rounds are not always necessary when changing jobs as an EM

2.2.4 Not every sound software engineer is a good manager

2.3 Intentions and motivations

2.4 A three-phase approach for ICs to EMs

2.4.1 Phase 1: Before becoming an EM

2.4.2 Phase 2: Transition period

2.4.3 Phase 3: Post-transition period

2.5 Challenges of a new engineering manager

2.5.1 Prioritizing coding over people

2.5.2 Setting clear goals and expectations

2.5.3 Struggling with delegation