How to scale a unicorn-building engineering team (and stay sane)
summary
Describes how Melio grows engineering from 1 to 25 people in a year by mapping eight engineering domains, running SWOT on gaps, and turning each domain into one-pagers with problem, current state and a vague North Star. Engineers join task forces led by engineers paired with non‑direct managers, get 20% research time for a month, produce OKRs and timelines, then share learnings. Concrete practices include senior–junior pairing, measurable testing and onboarding metrics, tech‑lead ambassadors, and visible increases in engagement and retention.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:12Scaling Milio’s team to 40
- 4:01Building a remote team
- 8:37SWOT gaps and actions
- 13:55Scaling to multiple squads
- 19:16Engineering-led task forces
- 29:15Beyond task forces
- 33:27Tech lead role
- 34:32Key takeaways
- 35:15Q&A
related talks
23mGad Salner- How to scale a unicorn-building engineering team (and stay sane)
16mEnlarge your team!
53mThe art of scaling an Engineering Organization
31mScaling
32mSynergy: Building Strong Engineering Teams
30mThe Elements of Scaling
53mScaling Engineering by Hacking Conway's Law
26mScaling engineering organizations