Pros
GitLab has a strong product and a compelling vision around consolidating the DevOps lifecycle into a single platform. For organizations willing to fully commit to the platform, the value can be significant. The territory structure for sellers was also defined, which gave clear direction on which accounts to prioritize. The remote culture was one of GitLab’s biggest strengths early on, and the company attracted many smart and capable people across the organization. I worked alongside several talented colleagues who were passionate about the product and the mission.
Cons
Over time, the “single application” platform approach appeared to lose some momentum in the market as more organizations shifted toward best-in-breed tooling. This made deals more challenging unless customers were willing to fully rip and replace multiple legacy tools with GitLab. Leadership changes across the executive and sales organizations also had a noticeable impact on the culture. What once felt like a flexible and empowering remote environment gradually shifted toward heavier micromanagement and more internal processes, which sometimes made simple tasks unnecessarily complex. Manager turnover was also a challenge. Several experienced leaders left the organization seemingly all at once, which created inconsistency for sellers and made it harder to maintain continuity within teams. Pipeline generation expectations existed (such as structured prospecting days), but there was often limited direction from leadership on how to effectively approach target accounts. At the same time, the sales engineering team was stretched thin due to a high rep-to-SE ratio, which noticeably slowed deal momentum. Compensation for sales roles also felt below market relative to the workload and expectations, particularly when external hires were brought in at higher compensation levels than tenured high performing internal reps.