Moving from code to people means trading pull requests for coaching, meetings, and feedback; the article shares concrete steps and mindset shifts that helped the author succeed as an engineering manager.
The jump from developer to engineering manager is not a promotion-it's a whole new job. The author realized that success now depends on the team's growth rather than on individual code contributions, forcing a fundamental mindset shift from building features to enabling people.
Daily life as a manager turned into a mix of spreadsheets, endless meetings, feedback sessions, and navigating team dynamics. Tasks that once lived in pull requests now live in Google Sheets, 1:1 conversations, performance reviews, and decisions about delivery. The author stresses the importance of resisting the urge to fix things personally and instead focusing on coaching others to solve problems.
Without a manual, the author turned to Google, blogs, and templates for every new challenge-running 1:1s, conducting reviews, and running retrospectives with tools like Miro and EasyRetro. Books such as The Manager's Path and Become an Effective Software Engineering Manager provided a structured foundation and practical advice.
The piece ends with a reflection on how AI tools like ChatGPT now fill the role of the old search friend, helping managers stay productive while reminding them to think critically. The core takeaway is that leadership is practiced daily, and the impact of a manager multiplies through the people they support.
Check out the full stdlib collection for more frameworks, templates, and guides to accelerate your technical leadership journey.