How Gitlab Runs Remote Engineering with 2000 Developers

Episode notes

In this episode of The CTO Podcast, Lucas and Luna dive into the operational and cultural mechanics behind GitLab's all-remote engineering organization. With over 2000 developers spread across 65 countries, GitLab has become a case study in asynchronous work, written documentation, and intentional culture-building. Lucas walks through GitLab's handbook-first approach, how they structure teams around 'stable counterparts' to avoid silos, and the specific tools and rituals that keep a global engineering org aligned. Luna challenges the model's trade-offs: burnout risk in async environments, the difficulty of onboarding without synchronous mentorship, and whether remote scales differently for engineering versus other functions. Together, they unpack what GitLab learned when it hit 1000 engineers - and how it adapted. Specific numbers, concrete practices, and honest criticism. If you're building or leading a distributed team, this episode gives you the architecture behind the architecture.

• How Airbnb Rebuilt Search for 8 Million Listings62 / 100
• How GitLab Built a Single Codebase for One Million CI Pipelines65 / 100
• How Slack Rebuilt Its Search Index for 10 Million Daily Queries57 / 100
• How Notion Rebuilt Its Sync Engine for Offline-First
• How Notion Rebuilt Its Block Engine for Hybrid Local-Sync