No management needed: anti-patterns in early-stage engineering teams | Antoine Boulanger
ablg.io · 1,769 words · saved by 1 readers
Sharing a reluctant, "node & postgres" approach to engineering management for early-stage startups
▶ Addendum 1/15/2026 This article is for early-stage (Seed, Series A) founders who think they have engineering management problems ( building eng teams, motivating and performance-managing engineers, structuring work/projects, prioritizing, shipping on time ). The gist: if you think you have these problems, it is likely that the correct solution is to do nothing, to not manage, and to go back to building product and talking to users . Put another way, and having managed teams at all scales, I don’t think it’s a good use of your time as a founder to be "managing" engineers at such an early stag
related reading
- Typical First Years of Startup Engineering Leadershipmarcgg.com
- Guides | Stay SaaSystaysaasy.com
- Do Things that Don't Scalepaulgraham.com
- Do Things that Don't Scalepaulgraham.com
- Becoming An Engineering Manager Can Make You Better At Life And Relationships – charity.wtfcharity.wtf
- What "The Best" Looks Like | Alex Kurilinkuril.in
- Do Things that Don't Scalepaulgraham.com
- Hiring the First 5 Engineers: What Sort of People Do You Want on Your Team?blog.eladgil.com
- #define CTOblog.gregbrockman.com
- ‘Give Away Your Legos’ and Other Commandments for Scaling Startupsreview.firstround.com
- Building the initial team for seed stage startups at andrewchenandrewchen.com
- Stop just using “Frontend” or “Backend” to describe the Engineering you like - Michelle Limmichellelim.dev