Blog

From engineer to engineering manager: your first 90 days

· 6 min read

The promotion from engineer to manager is not a promotion. It is a change of profession. The skills that earned it — solving hard problems yourself — are no longer the job, and continuing to rely on them is the most common way new managers fail.

Here is a plan for the first three months that keeps you out of the usual traps.

Days 1–30: listen, and stop being the bottleneck

  • Hold a one-on-one with every person on the team. Ask what is working, what is not, and what they would change if they were you.
  • Meet your manager and agree what success looks like in six months. Write it down.
  • Hand off your critical-path coding work. Your calendar is about to fragment, and work that waits on you will block others.
  • Meet the people your team depends on, and the people who depend on your team.

Resist the urge to fix things in the first month. You do not yet know which problems are real, and early changes made on thin information are expensive to undo.

Days 31–60: create clarity

By now you will have heard the same two or three problems from several people. Most will come down to unclear priorities. Your highest-leverage act as a manager is to remove that ambiguity: say what matters most this quarter, what does not, and why.

  • Write down the team's top priority and its measure of success. Share it and invite objections.
  • Set up a steady one-on-one rhythm, weekly or every two weeks, and protect it.
  • Start giving specific feedback, positive and corrective, within a day or two of what you observed.
  • Delegate one thing you would normally do yourself, with a clear outcome and agreed checkpoints.

Days 61–90: build the system

The last month is about making the team work without your constant attention. Look at how work flows from idea to production and remove one recurring source of friction. Look at who is growing and who is stuck, and have a career conversation with each person. Look at your hiring pipeline, if you have one, and make sure there is a scorecard for the role.

How to tell it is working

  • People bring you problems early rather than late.
  • The team can state its priority in one sentence, and the sentences match.
  • Work no longer waits on you.
  • You have given every report at least one piece of feedback they acted on.

None of these show up in your commit history, which is the uncomfortable part. A manager's output is the output of the team, and it arrives later and less directly than you are used to. That lag is normal. Measure yourself by what the team ships and how its people grow.

Practice this in a lesson

Each engMBA lesson pairs a short explanation with practice questions that grade themselves. Free, with no signup.

See the full curriculum

Keep reading