Refactoring

Refactoring

Share this post

Refactoring
Refactoring
How Far Can You Go Without Engineering Managers? 👑
Copy link
Facebook
Email
Notes
More

How Far Can You Go Without Engineering Managers? 👑

And do tools make engineering management any easier?

Luca Rossi's avatar
Luca Rossi
Jun 09, 2022
∙ Paid
13

Share this post

Refactoring
Refactoring
How Far Can You Go Without Engineering Managers? 👑
Copy link
Facebook
Email
Notes
More
1
Share

A couple of months ago, Aditya Agarwal, former CTO at Dropbox, made a splash on Twitter with his take on engineering management 👇

Twitter avatar for @adityaag
Aditya Agarwal @adityaag
1/ How far can you go without formal engineering management? This might surprise some but the answer is: pretty damn far. How did WhatsApp build a $20B company without any eng management? Read below for details but the big reason is ‘Software eats the World’ applied unto itself
3:50 PM ∙ Mar 30, 2022
211Likes32Retweets

Aditya argues that modern tooling like Asana or Slack have made management drastically easier.

Today, teams of 100 can stay in sync at the same level as a team of 10, and you need way fewer managers than in the past — if any.

Quoting Aditya:

In my experience, you can have roughly 30-35 engineers without formal management. You will likely want some Tech Leads before then but that is way simpler than a management layer

This take is clearly controversial and, unsurprisingly, has spawned a hot debate both on social media and on the Refactoring community.

Do you really need managers anymore? Or, how far can you go without them?

This week I tried to break this down in a way that is more nuanced than a Twitter thread. We will cover:

  • 3️⃣ Management is three things (+1) — 10,000 feet view of what a manager does.

  • 🔨 How tools are helping — are they?

  • 👑 Formal managers vs management — do you need full-time, formal managers?

  • 🔄 Distributed management — can you replace managers with processes?

Let’s dive in 👇

Refactoring is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

Management is three things (+1)

Paraphrasing Aditya himself, engineering managers’ responsibilities can be organized into three main areas (plus one):

  • 🗺️ Planning — organizing work into OKRs, sprints, weeks, or whatever process you use. It includes scoping, prioritizing, allocating resources, and negotiating with stakeholders.

  • 🔀 Alignment — keeping people coordinated on what needs to be done. Removing obstacles. Adding what’s missing at any given time.

  • ❤️ Health & Growth — managing people and the overall team’s health. Taking care of feedback, careers, and recruiting.

  • ✨ Bonus: Tech Leadership — this is largely a separate responsibility than EM, but let’s face it, many companies don’t have the headcount to separate the two, so these roles may conflate on the same person.

How are tools helping with these areas? Well, it’s complicated.

Let’s see them one by one.

🗺️ Planning

This post is for paid subscribers

Already a paid subscriber? Sign in
© 2025 Refactoring ETS
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture

Share

Copy link
Facebook
Email
Notes
More