People management is the practice of supporting, coordinating, developing, and evaluating employees. For an engineering manager, it often matters more day to day than writing code: the focus shifts toward people, projects, processes, and organizational goals. section 2.2.2 section 2.5.9
Practical people-management responsibilities include:
- Hold regular check-ins to discuss concerns, expectations, feedback, and progress. section 2.5.9
- Understand individual motivation, listen actively, and respond with empathy and compassion. section 3.1 section 2.5.9
- Provide timely, constructive feedback connected to goals, growth, and performance. section 2.5.9
- Support career conversations, recruitment, training, accountability, and performance concerns. section 2.5.9 section 3.1
- Protect confidentiality and resolve conflicts while maintaining trust and fairness. section 2.5.9 section 3.1
Balancing technical work with people leadership
A newly transitioned engineering manager may continue coding on noncritical work, such as onboarding a service to SonarQube, but should avoid becoming the only person able to complete critical project code. Code reviews and architecture discussions can preserve technical connection without displacing people-management responsibilities. section 2.2.2
Figure 2.2 Breakdown of coding and leadership skills based on roles. For an IC, the focus is on coding. If you take the EM track and become a manager of managers, you will focus the majority of your time on leadership skills.
Use the role comparison to see how emphasis shifts from coding for individual contributors toward leadership and people management for engineering managers. section 2.2.2
