Interview, Fireside Chat
Sid Sijbrandij: How I Founded GitLab; Remote Work vs In-Person; CEO Coaches | 20VC
- GitLab's origins trace back to co-founder Dimitri's desire to improve work collaboration through open source, evolving into a public, fully-remote DevOps platform.
- The company currently employs over 1,500 people, up from 300 in its first year, with hundreds of new contributors joining monthly.
- GitLab operates across over 60 countries, though the leadership team (C-suite and board) currently lacks this same geographic diversity.
- The company views asynchronous work as the primary solution to time zone challenges, though it acknowledges the difficulty of fully decoupling daily operations from synchronous calls.
- GitLab intentionally facilitates informal communication through structured "coffee chats" (25-minute, agenda-free calls) and mandates five such interactions for every new hire.
- While GitLab organizes annual in-person gatherings where employees congregate in a single location for a week, these events remain entirely optional to accommodate varying personal needs.
- Sid Sijbrandij predicts the future of work will bifurcate between fully remote startups and legacy companies that adopt a "same-day" hybrid model, where all co-located employees arrive on the same days to avoid fragmentation.
- The company argues that the "hybrid" model fails when remote workers feel on a different level than office staff, potentially causing top talent to leave for fully remote organizations.
- GitLab's written culture is codified in a 2,000-page handbook, which reduces synchronous meeting needs but can slow down rapid decision-making if context is missing.
- Leadership values are explicitly defined as results, iteration, and transparency, with a philosophy of delegating context to empower autonomous decision-making.
- While GitLab maintains a default stance of transparency, they have published a specific list of over 17 items (including salaries, M&A, and fundraising) that are restricted from public visibility.
- Feedback culture is protected by never penalizing messengers; Sid Sijbrandij emphasizes accepting feedback based on the source's specialty and frequency rather than immediate correctness.
- The CEO utilizes "situational leadership," adapting management styles based on 19 specific factors to account for varying team needs and employee maturity.
- Sid Sijbrandij recommends CEO coaches for leaders of fast-growing companies but advises transitioning to new coaches once the learning curve plateaus or information begins to repeat.
- As a board member, Sid prioritizes asking questions and remaining informed over offering execution advice, aiming to avoid the trap of staying in the "operator seat."
- GitLab board meetings are structured with 1.5 hours of open sessions followed by 45 minutes of closed sessions, including a specific 15-minute segment to evaluate CEO performance.
- Founders are advised to clearly state the three specific areas where they need board feedback prior to meetings to prevent wasted time on low-priority strategic discussions.
- GitLab's investor selection criteria focus on firm reputation, constructive relationships, and the potential individual to serve on the board.
- Sid identifies the "DIY DevOps" approach—integrating ten best-in-class tools with custom maintenance—as obsolete, advocating for a single unified platform instead.
- The DevOps market is projected to grow from $20 billion to $60 billion by 2024, with GitLab positioned to consume a larger share of the toolchain.
- Sid is co-founding OpenCore Ventures with the strategy of creating companies around open source projects before they formally exist, investing $2 million to recruit CTOs and build proprietary open-core models.
- To mitigate his known tendency toward cynicism in meetings, Sid employs "CEO shadows" who attend 80% of his meetings to rate his positivity and provide feedback.
- Sid's favorite book is High Output Management for its integration of situational leadership concepts.
- The biggest current challenge in GitLab's structure is managing cross-functional initiatives, which inherently struggle against functional organizational boundaries.