Working at GitLab in 2026: The All-Remote Pioneer's Culture, Salary & Reviews

GitLab is one of the most fascinating companies in tech — not because of its DevOps platform (though that's impressive), but because of how it operates. Founded in 2011 by Sid Sijbrandij and Dmitriy Zaporozhets, GitLab has been fully remote from day one. No headquarters. No offices. No "hybrid Wednesdays." Just ~2,000 people spread across 67+ countries, coordinating entirely through async communication, merge requests, and what might be the most comprehensive public company handbook ever written.

GitLab went public on NASDAQ (GTLB) and built a DevOps platform used by millions of developers. But what sets it apart culturally is the radical transparency experiment: nearly everything — from compensation formulas to meeting notes to strategic decisions — is documented publicly. It's a company that treats its own operating system as an open-source project. Whether you're evaluating a GitLab offer, researching remote-first companies, or simply curious about what radical transparency looks like in practice, here's what you need to know about working at GitLab in 2026.

GitLab at a Glance

GitLab occupies a unique position among the companies in our Culture Directory. It's the company that other remote-first startups point to when they need to justify their own remote policies. It pioneered the public handbook model that companies like Sourcegraph and PostHog later adopted. And it did all of this while building a serious enterprise software product that competes with GitHub, Atlassian, and a dozen other DevOps incumbents. But the Glassdoor data tells a more complicated story than the remote-work evangelism suggests — one of genuine strengths paired with real organizational challenges.

The All-Remote Reality

When most companies say "remote-friendly," they mean some people can work from home some of the time. When GitLab says "all-remote," they mean it literally. There are no offices. There is no headquarters building with a reception desk. The San Francisco address exists for legal and financial purposes. Every single one of GitLab's ~2,000 employees works from wherever they choose, across 67+ countries and hundreds of cities.

This isn't a pandemic-era experiment that stuck. GitLab was remote before remote was trendy. Sid Sijbrandij and Dmitriy Zaporozhets started building the product from different countries, and the company never saw a reason to change. By the time COVID-19 forced the rest of tech into remote work, GitLab had been operating this way for nearly a decade and had already documented everything they'd learned.

The practical reality of all-remote at GitLab means a few things. First, your timezone is your own. GitLab doesn't mandate core hours. If you're most productive at 6 AM or 11 PM, that's your call. Second, there are no "in-office" employees who get preferential access to leadership or spontaneous hallway decisions. Every conversation that matters happens in writing — in issues, merge requests, or handbook updates. Third, you can relocate without asking permission. Move from Berlin to Bali, and your work doesn't change (though your compensation might — more on that later).

But all-remote also means genuine isolation. There's no office to go to when you want social interaction. There are no team lunches, no after-work drinks, no whiteboard sessions. GitLab tries to offset this with virtual coffee chats, team off-sites, and an annual company gathering called Contribute. But multiple Glassdoor reviews mention loneliness and disconnection as real downsides, particularly for people earlier in their careers who benefit from the mentorship and social fabric that offices provide.

The Public Handbook: GitLab's Operating System

If GitLab's all-remote model is its most visible cultural feature, the public handbook is its most radical one. The GitLab Handbook is a publicly accessible, continuously updated document that describes how the entire company operates. It covers everything: how to run a meeting, how compensation is calculated, how to give feedback, how to get promoted, how engineering teams ship code, how the sales process works, how the CEO makes decisions.

The handbook contains thousands of pages. It is, in many ways, the source code for GitLab as an organization. And it's public. Anyone — prospective employees, competitors, journalists, curious engineers — can read exactly how GitLab works. This level of transparency is almost unheard of in corporate tech. Most companies guard their operating procedures jealously. GitLab publishes them for the world to see.

For employees, the handbook creates a distinctive working experience. On the positive side, it eliminates ambiguity. When you're new, you don't need to figure out "how things work here" through trial and error or political navigation. The answer is written down. Promotion criteria? In the handbook. Expense policy? In the handbook. How to disagree with your manager? In the handbook. This is particularly powerful for remote workers who can't walk over to a colleague's desk and ask.

On the negative side, the handbook can feel bureaucratic. Some employees describe a culture where "if it's not in the handbook, it doesn't exist" — and where updating the handbook becomes an end in itself rather than a means to better outcomes. The sheer volume of documentation can be overwhelming for new hires. And the emphasis on written process can sometimes slow down decisions that would be faster with a quick conversation.

Glassdoor Ratings Breakdown

GitLab's overall Glassdoor rating of 3.7 out of 5.0, based on 707 employee reviews, places it in the middle tier of companies in our directory. It's lower than many developer-tools peers — GitHub and other DevOps companies often score higher. But the sub-category breakdown reveals where GitLab genuinely excels and where it struggles.

The Work-Life Balance score of 3.9 is the standout — and it makes sense. When you control your own schedule, work from anywhere, and operate async-first, you have genuine flexibility to structure your day around your life rather than the other way around. This is GitLab's strongest selling point as an employer, and employees consistently call it out.

The Culture & Values score of 3.6 is more nuanced. GitLab's stated values (Collaboration, Results, Efficiency, Diversity, Iteration, Transparency — forming the acronym CREDIT) are well-documented and genuinely influence how people work. But the gap between aspirational values and daily reality is wider than at some companies. Multiple reviews mention that transparency can feel performative when leadership makes decisions that contradict the handbook's principles.

The Career Opportunities score of 3.4 is the weakest area. Several reviews note limited upward mobility, flat career ladders in some functions, and a sense that growth paths aren't always clear despite being documented. For a company that prides itself on documentation, the gap between written career frameworks and actual promotion velocity has been a recurring concern.

Engineering at GitLab

GitLab's engineering culture has a unique meta-quality: engineers use GitLab to build GitLab. The product is the tool, and the tool is the product. This creates an unusually tight feedback loop where every engineer is simultaneously a builder and a user. If something about the development workflow is broken, you feel it immediately — and you have the power to fix it in the same codebase.

Tech Stack

GitLab's core application is a large Ruby on Rails monolith — one of the biggest in the world. Performance-critical components like Gitaly (the Git storage service) are written in Go. The frontend uses Vue.js. Infrastructure runs on Kubernetes. It's a stack that reflects pragmatic choices made over a decade of development rather than a greenfield architecture optimized for resume points.

How engineering works

• Async-first development. Code reviews, design discussions, and technical decisions happen in merge requests and issues, not meetings. Engineers in Tokyo and engineers in Toronto contribute to the same feature without ever being online at the same time. This is async at its most genuine — not "we have fewer meetings" but "meetings are the exception, not the rule."
• Open-source core. GitLab CE (Community Edition) is fully open-source. Engineers contribute to a codebase that millions of developers worldwide use, fork, and contribute back to. This creates a unique accountability — your code is public, your commit history is visible, and the community will tell you directly if something is broken.
• Monthly release cadence. GitLab ships a new version on the 22nd of every month, without exception. This predictable cadence creates clear deadlines and a rhythm that engineers either love (for its clarity) or find constraining (for its rigidity). Features that miss the cutoff wait until the next month.
• Dogfooding everything. GitLab's CI/CD, issue tracking, code review, and project management are all done in GitLab. If a feature is frustrating to use internally, it gets prioritized for improvement. This creates a product development culture where empathy for users is built into the daily workflow.

Compensation & Equity

GitLab's approach to compensation is as transparent as everything else — and as controversial. The company uses a location-based compensation calculator that is publicly documented in the handbook. Your pay is determined by a formula that factors in your role, level, and the cost of living in your location. An engineer in San Francisco earns more than an identical engineer in Lisbon, even though they do the same work.

This approach is philosophically consistent — GitLab argues that paying the same salary regardless of location would mean either underpaying in expensive cities or overpaying in affordable ones. But it creates friction. Engineers in mid-cost cities sometimes feel their compensation doesn't reflect their skill level or contribution. And the transparency of the formula means everyone knows exactly what everyone else earns, which can create uncomfortable comparisons.

As a publicly traded company (GTLB), GitLab offers RSUs (Restricted Stock Units) as part of compensation. The stock's performance since IPO has been mixed, which affects how employees perceive the total value of their package. Unlike pre-IPO companies where equity is a bet on future value, GitLab RSUs have a known market price — for better or worse.

Leadership Challenges

The most consistent criticism of GitLab across Glassdoor reviews centers on leadership. While the handbook documents how decisions should be made, multiple reviews describe a gap between the written process and the lived experience. Frequent organizational restructuring, shifting strategic priorities, and leadership turnover have been recurring themes.

Sid Sijbrandij, as co-founder and long-time CEO, is a polarizing figure. Supporters praise his commitment to transparency, remote work, and the handbook-driven culture he built. Critics describe a leadership style that can feel disconnected from the daily realities of individual contributors. The 61% "recommend to friend" rate — while not terrible — is notably lower than many companies of similar profile and reflects this ambivalence.

It's worth noting that leadership instability is not uncommon at publicly traded companies navigating the transition from startup to mature enterprise. GitLab is under constant pressure from investors to grow revenue, improve margins, and compete effectively against GitHub (backed by Microsoft) and Atlassian. Some of the organizational turbulence reflects the genuine difficulty of that challenge rather than poor leadership per se.

Who Thrives at GitLab (and Who Doesn't)

GitLab is a strong fit for a specific type of person. Based on the culture signals, employee reviews, and the company's operating model, here's who tends to do well:

• Self-directed remote workers. If you're the kind of person who thrives with autonomy, structures your own day, and doesn't need an office to stay motivated, GitLab is built for you. The async-first culture rewards people who communicate clearly in writing and don't need synchronous validation to move forward.
• Documentation-first thinkers. If you naturally write things down, prefer clarity over ambiguity, and believe that institutional knowledge should be accessible to everyone, GitLab's handbook culture will feel like home. You'll contribute to a living document that shapes how the company operates.
• Open-source enthusiasts. If contributing to a codebase used by millions of developers excites you, and you're comfortable with your work being publicly visible, GitLab's open-source model is deeply rewarding. The community engagement adds a dimension to the work that you don't get at most companies.
• People who value flexibility over prestige. GitLab won't offer you a sleek office, catered lunches, or the social scene of a San Francisco tech company. What it offers is genuine freedom — to live where you want, work when you want, and design your life around your work rather than the reverse.
• Global citizens. If you want to work with colleagues across dozens of countries and time zones, GitLab's global footprint creates a genuinely international experience that few other companies can match.

GitLab is not ideal for people who need in-person collaboration to do their best work, who thrive on spontaneous brainstorming sessions, or who want the social environment of an office. It's also a challenging fit for people who prefer clear, stable organizational direction — the leadership challenges and frequent reorgs can feel disorienting. If you want top-of-market compensation regardless of location, companies like GitHub or companies in our strong equity directory may be a better fit.

The Pros and Cons, Summarized

What employees consistently praise

What employees consistently criticize

Open Positions at GitLab

GitLab currently has 191 open roles on Greenhouse, spanning engineering, product, security, sales, and marketing. As a fully remote company, most positions are open to candidates worldwide, though some roles may have geographic restrictions based on entity and compliance requirements. If the async-first, handbook-driven, all-remote culture described in this post resonates with you, GitLab is worth serious consideration — particularly if you value location independence and schedule flexibility above all else.

For full details on GitLab's culture values, employee reviews, and open roles, visit the GitLab culture profile page or browse all GitLab jobs.