The Twenty Minute VCSid Sijbrandij: How I Founded GitLab; Remote Work vs In-Person; CEO Coaches | 20VC
CHAPTERS
- 0:00 – 1:48
GitLab’s founding story: from open source project to DevOps platform
Sid recounts how he discovered Dmitriy’s open source GitLab project and realized it deserved full-time investment. He explains GitLab’s end-to-end DevOps scope and how the community-driven start became a 1,500+ person company used by millions.
- •Dmitriy starts GitLab to improve collaboration; makes it open source
- •Sid joins and frames GitLab as a complete DevOps platform (plan→build→secure→deploy→monitor)
- •Early community traction (hundreds joining) signals need for full-time team
- •Scale from project to global company with 1,500+ employees
- 1:48 – 3:54
Why GitLab went remote-first: an organic start and a scalability thesis
Sid explains remote-first wasn’t a grand strategy at first—it emerged from hiring globally from day one. Over time, GitLab found remote work scales better as headcount grows, and skepticism pushed them to become more intentional about remote operations.
- •First hires were distributed across countries; remote evolved naturally
- •Remote is less beneficial at ~7 people, more beneficial at 1,500+
- •Skepticism created a forcing function to invest in remote practices
- •Remote is framed as an advantage for scaling beyond a single building
- 3:54 – 5:30
Engineering informal communication in a distributed culture
Harry challenges Sid on how GitLab recreates the ‘watercooler’ effect remotely. Sid details specific mechanisms—especially normalized, agenda-free social time—designed to build trust and connection without forcing participation.
- •Coffee chats as a lightweight, agenda-free norm (25 minutes)
- •Onboarding nudges new hires to try informal chats (e.g., five chats)
- •Team hangouts and optional participation to respect different preferences
- •In-person meetups (flying everyone to one location) to strengthen bonds
- 5:30 – 6:49
Remote transitions: the hardest part is what people actually miss about offices
Sid argues companies over-focus on return-to-office decisions instead of improving remote execution. He claims what people miss isn’t the physical office but the informal communication and trust-building that offices enable by default.
- •Most effort goes to ‘when to return’ vs ‘how to work well remotely now’
- •Fully returning to office is unlikely; some portion will remain remote
- •Low office return rates suggest the real gap is social connection
- •Zoom’s on-time/start-stop nature removes organic relationship time
- 6:49 – 8:08
The future of work: remote, co-located, and two kinds of hybrid
Sid predicts more startups will be fully remote, while some legacy companies will remain co-located successfully. He distinguishes effective hybrid (same days in-office for everyone) from ineffective hybrid (mixed in-room vs remote), which can create inequity and attrition.
- •All-remote startups will become more common
- •Co-located can work for some companies, as proven pre-pandemic
- •Hybrid works when the whole team is in-office on the same days
- •Hybrid fails when some are remote while others are together, creating a ‘second-class’ dynamic
- 8:08 – 9:09
What GitLab still needs to improve: async work, time zones, and leadership geography
Sid identifies time zones as the hardest constraint in remote work and calls asynchronous collaboration the key solution—yet very difficult to do well. He notes his own calendar is call-heavy and wants leadership and board composition to better reflect GitLab’s global distribution.
- •Time zones force async, but async discipline is hard to sustain
- •Sid’s day is dominated by calls; leadership team skewed US-based
- •Aspiration for broader geographic distribution in exec group and board
- •Remote excellence requires continuous iteration, not a ‘finished’ playbook
- 9:09 – 11:02
Reducing meeting load: ‘no presenting in meetings’ and async-by-default habits
Sid describes GitLab’s meeting philosophy: presentations happen before meetings so synchronous time is reserved for Q&A and decisions. He shares a concrete example where even prep calls could be replaced with shared docs and notes.
- •Rule: no live presenting in meetings; use pre-read/pre-watch materials
- •Synchronous time is best for Q&A and resolving ambiguity
- •Async docs/notes can replace many prep calls and status updates
- •Leadership modeling matters—show remote/async competence in practice
- 11:02 – 13:23
Leadership values and boundaries of transparency
Sid outlines GitLab’s core values—results, iteration, transparency—and how his leadership evolved toward delegation, patience, and context-setting. He also clarifies transparency isn’t absolute and points to an explicit list of non-transparent items (e.g., salaries, M&A).
- •Leadership anchored in results, iteration, and transparency
- •Personal evolution: delegate more, be more patient, provide more context
- •Transparency-by-default requires explicit exceptions (17+ items)
- •Fundraising transparency depends on company attractiveness and market conditions
- 13:23 – 17:27
Feedback culture: rewarding candor and creating psychological safety
Sid explains how leaders must make giving feedback feel safe and appreciated, regardless of whether the feedback is ‘correct.’ He discusses filtering feedback by frequency and source credibility, and emphasizes public reactions (in group settings) to reinforce safety norms.
- •Normalize and reward feedback; never punish the messenger
- •Separate welcoming feedback from deciding whether to act on it
- •Filter signals by repetition, source credibility, and domain expertise
- •Publicly thanking feedback in group settings demonstrates safety to others
- 17:27 – 20:06
Tempering emotions as a leader: don’t assume bad intent and adapt your style
Prompted by Harry, Sid discusses managing anger and intensity, arguing leaders should avoid labeling others as ‘lazy’ and instead explore underlying causes. He references situational leadership and a set of factors he uses to decide when and how to delegate.
- •Avoid judging intent; ‘laziness’ is often an oversimplification
- •Procrastination can reflect an overly high bar or unclear path forward
- •Leaders won’t always be at their best; repair and self-critique matters
- •Situational leadership: vary approach depending on person and context
- 20:06 – 21:34
Written culture at scale: the handbook advantage and the speed tradeoff
Sid defines written culture as systematically documenting how the company works, exemplified by GitLab’s 2,000+ page handbook. He highlights the async benefits while acknowledging writing can be slow when context is uneven and speed is required.
- •Handbook as a durable operating system for the organization
- •Writing reduces dependency on synchronous help and unblocks work
- •Downside: writing is time-consuming when stakeholders lack context
- •Synchronous comms can be better for urgent, high-context, wide-audience decisions
- 21:34 – 27:22
Mentorship and CEO coaching: how to ask, who helps, and when to switch
Sid shares practical advice on finding mentors by starting with a specific problem and a small ask, rather than requesting a formal mentorship upfront. He describes the role of CEO coaches and key board members, including a coaching lesson on diagnosing problems and presenting a plan under pressure.
- •Best mentorship outreach: specific problem, why it matters, proposed thinking, small time request
- •Most valuable mentors: CEO coaches and experienced board members
- •Coaching story: missing a quarter—focus on understanding the problem and building a plan
- •Switch coaches when learning plateaus and company stage changes; coaches must match stage
- 27:22 – 34:31
Board management and board craft: maximizing value without commandeering execution
Sid explains how to run board meetings for discussion rather than presentation and why CEOs should tell the board what help they need. He also describes being a good board member—high signal, no showing off, specialty-driven—and advises raising company strategy issues in the meeting while avoiding ‘telling management what to do.’
- •Board meetings should minimize presentations; use pre-work (even video)
- •Explicitly request feedback on 2–3 priority topics to prevent low-value tangents
- •As a board member: ask questions, stay out of operator mode, be high signal
- •Raise strategy concerns in the room; challenge with questions and data, not directives
- 34:31 – 41:16
Investor selection, rapid-fire insights, and GitLab’s next decade
Sid briefly outlines investor selection as choosing constructive firms and individuals, even simulating board-style interactions. In quickfire, he covers his favorite book, org design tradeoffs, GitLab’s view that DIY DevOps is fading, his venture studio model for open core, personal improvement systems, and his market outlook for DevOps platforms.
- •Investor selection: prioritize reputation, constructiveness, and boardroom fit; ‘mock board meeting’ to assess value-add
- •Quickfire: favorite book is High Output Management; functional orgs make cross-functional initiatives hardest
- •Thesis: DIY best-of-breed DevOps toolchains are too costly/ineffective vs platforms
- •Open Core Ventures: create companies around open source, seed with $2M, recruit CTO then CEO; GitLab aims to lead platform adoption in a growing DevOps market
