Course page
Log in

You are watching a free preview. Enroll to open all 26 lessons, track progress and ask the course tutor.

Enroll for $79.99

Section 1: From engineer to manager

What changes when you become a manager

Video 9 min Lesson 1 of 26 Sample clip Preview

When you were an engineer, your output was visible: code merged, bugs fixed, features shipped. As a manager, your output is the output of your team, plus the output of the teams around you that you influence. This shift sounds simple. Living it is not.

Your job now

A useful definition: an engineering manager is responsible for the people, the delivery and the health of the team. In practice that means:

  • People: hiring, growth, feedback, performance, wellbeing.
  • Delivery: making sure the team commits to the right work and delivers it predictably.
  • Team health: clear goals, good collaboration, sustainable pace and a place where people can raise problems.

You will still care about technical quality, but you will rarely be the person writing the most code. Your leverage comes from making six people more effective, not from being a seventh engineer.

What feels different

  • Feedback loops get longer. Code gives feedback in minutes. People decisions show results in months.
  • Your calendar fills up. Meetings are a larger part of the job. Some are essential; your task is to make them valuable and cut the rest.
  • Context switching increases. You move between a performance conversation, a planning meeting and an incident in one afternoon.
  • You hear more, and you can share less. You learn about reorganisations, salaries and personal situations that you must keep confidential.
  • Relationships change. If you were promoted within your team, former peers now report to you. That changes conversations, even with friends.

What does not change

Your judgement about technical work is still valuable. Your credibility with the team still matters. Your curiosity, honesty and care for quality still shape the culture. You are not becoming a different person, you are applying the same strengths in a different way.

Meet Rui

Throughout the course we follow Rui, who has just become manager of the team he worked on for three years. In his first week he reviews every pull request himself, stays late fixing a bug instead of delegating it, and cancels one on ones because "there is too much to do". All of these are common, well meant mistakes. We will see what happens and how he recovers.

Is management for you?

Management is not a promotion in the sense of being better than engineering. It is a different job. Many organisations offer a parallel technical track for senior engineers. If, after this section, the job does not appeal to you, that is valuable to know early.

← → switch lessons