GitLab is a rare case in tech: a publicly traded company (NASDAQ: GTLB) that publishes its entire compensation framework in a public handbook. Salary bands, location factors, equity philosophy, promotion criteria — it's all available for anyone to read before they even apply. No other company of GitLab's size does this.
That radical transparency makes GitLab one of the most interesting compensation case studies in the industry. Combined with its all-remote structure — 2,500 employees across 65+ countries — GitLab's comp strategy involves challenges that most companies never face: how to pay fairly across wildly different cost-of-living markets while remaining competitive for top talent. Here's how it works in 2026.
How GitLab's Compensation System Works
GitLab structures compensation around three components: base salary (via Total Target Cash), equity (RSUs + ESPP), and benefits. What makes the system unusual isn't the components — it's the methodology.
Base Salary & Total Target Cash
Base salaries are benchmarked using external compensation data from Radford, with most roles targeted at or above the 50th percentile of the software market. Critical technical roles — the kind that keep GitLab competitive for senior engineers — are positioned closer to the 75th percentile.
For roles with variable pay (sales, customer success), GitLab uses Total Target Cash (TTC), which combines base salary plus target variable comp. The split varies by role, but the total target is set against the same external benchmarks.
The most distinctive feature is location-based pay. GitLab doesn't pay the same base salary regardless of where you live. An engineer in San Francisco will earn more than the same role in Lisbon or Nairobi. The rationale, documented extensively in their handbook, is that pay should reflect the local labor market while remaining competitive within it. GitLab benchmarks against the 50th–75th percentile of each local market, not against a single global number.
The Location Factor Trade-Off
Location-based pay is controversial. Critics argue it penalizes people for where they live. GitLab's counter: an engineer earning $180k in Lisbon captures far more purchasing power than one earning $250k in San Francisco. The company targets competitive local pay — meaning you should be among the best-paid engineers in your city, even if the number is lower than a Bay Area peer. Whether this philosophy works for you depends on where you live and what you optimize for.
Equity: RSUs & ESPP
As a publicly traded company, GitLab grants Restricted Stock Units (RSUs) rather than stock options. RSUs vest into real, liquid GTLB shares — you don't need to exercise anything or worry about strike prices. This matters: at a stock price of roughly $25 (as of May 2026) with a $4.3 billion market cap, RSUs represent tangible, sellable value from day one of vesting.
GitLab also offers an Employee Stock Purchase Plan (ESPP) that lets employees buy GTLB stock at a discount. For employees who believe in the company's long-term trajectory — FY2026 revenue was $955 million, up 26% year-over-year — the ESPP is a way to increase equity exposure beyond RSU grants.
The equity component is where GitLab's comp differs most from private AI startups. At companies like Anthropic or OpenAI, equity is illiquid and speculative — potentially worth a fortune, or potentially worth much less. GitLab's RSUs are publicly traded. The upside is lower, but the downside risk is also dramatically smaller. For risk-averse engineers who've been burned by startup equity that never materialized, this is a meaningful advantage.
Software Engineer Compensation by Level
Based on verified compensation data across our research, here's what GitLab software engineers earn in the US in 2026:
| Level | Base Salary | Total Comp (incl. equity) |
|---|---|---|
| Junior (IC1–IC2) | $100k – $140k | $117k – $170k |
| Mid-Level (IC3) | $130k – $170k | $160k – $215k |
| Senior (IC4) | $155k – $200k | $200k – $270k |
| Staff (IC5+) | $180k – $235k | $250k – $310k+ |
Note: These are US-based figures. International compensation varies based on GitLab's location factors. Actual offers depend on experience, scope, and the specific team.
How does this compare? GitLab's total comp is competitive for a DevSecOps platform company but sits below the highest-paying AI companies. For context:
- Anthropic senior engineers: $300k–$490k total comp
- Stripe senior engineers: $280k–$400k+ total comp
- Databricks senior engineers: $250k–$420k total comp
- GitLab senior engineers: $200k–$310k+ total comp
The gap is real. But GitLab offers something those companies don't: full remote work from 65+ countries, async-first culture, and the ability to live where you choose. An engineer earning $250k from a small city in Colorado or Portugal captures more purchasing power than one earning $350k in San Francisco while commuting to an office. The comp comparison only makes sense when you factor in the lifestyle GitLab enables.
The Public Compensation Calculator
GitLab's most unusual feature is its compensation calculator, published openly in the company handbook. You can look up the expected salary range for any role, at any level, in any supported location — before you apply.
This changes the negotiation dynamic entirely. At most companies, candidates go in blind, trying to guess the range or leverage competing offers to establish a floor. At GitLab, the bands are public. You know what the role pays before the first call. What's left to negotiate is your level — whether you come in as a Senior or Staff, IC4 or IC5 — and the equity component within the band.
The calculator also reduces internal pay inequity. When everyone can see the bands, it's harder for managers to give one person a significantly better deal than a peer in the same role. GitLab conducts annual pay equity audits to catch and fix discrepancies.
The downside? Transparency can create frustration when your comp is at the low end of a band and you can see exactly how far away the top is. Some employees report that the structured system leaves less room for exceptional performers to negotiate outsized packages. If you're the kind of engineer who expects to earn well above band because of your track record, GitLab's system may feel constraining.
Benefits & Perks
GitLab's benefits are designed for a globally distributed workforce. The core package includes:
- Health insurance — comprehensive medical, dental, and vision coverage (US). Country-specific plans for international employees.
- 401(k) matching — with company match for US-based employees.
- Equity — RSU grants with vesting schedules, plus ESPP at a discount.
- Unlimited PTO — with genuine encouragement to use it. GitLab tracks usage patterns to identify burnout risk.
- Home office stipend — since every employee is remote, GitLab provides budget for setting up your workspace.
- Coworking reimbursement — if you prefer working from a shared space rather than home.
- Growth & development budget — annual stipend for conferences, courses, books, and professional development.
- Parental leave — generous leave for both parents.
- Mental wellness support — including counseling and mental health resources.
The benefits are solid but not the lavish perks you'd find at companies like Stripe or Airbnb. GitLab's philosophy is to pay competitively and let employees allocate their own lifestyle spending rather than providing on-site meals and gyms that only work if you're in an office.
What Employees Say About Comp
GitLab has a 3.9 Glassdoor rating from 700+ reviews. Compensation and benefits are generally rated positively, though with caveats. Here's the consistent feedback:
The stock performance concern is worth addressing. GTLB traded above $130 in late 2021 before the broader tech correction. At roughly $25 per share in May 2026, employees who received RSU grants at higher prices have seen the equity portion of their comp decline significantly. For new hires, the current price means your RSU grants are based on the lower valuation — which creates more upside if the stock recovers but less immediate value than a grant would have been two years ago.
GitLab's revenue grew 26% year-over-year to $955 million in FY2026, which suggests the underlying business is healthy. Whether the stock reflects that growth trajectory is a market question, not a compensation question — but it affects how employees feel about their total comp.
Should You Optimize for GitLab Comp?
GitLab's compensation is not the highest in tech. It's not designed to be. The company competes on a different axis: radical transparency, all-remote flexibility, async-first work, and the ability to live wherever you want in 65+ countries.
This works exceptionally well for:
- Engineers in lower-cost cities who want competitive local pay without relocating to SF or NYC.
- People who value transparency and want to know exactly what they'll earn before applying.
- Caregivers and parents who need genuine schedule flexibility, not just "unlimited PTO" that no one uses.
- International engineers who want to work for a US-listed tech company from their home country.
- Open-source enthusiasts who want their work to be visible and impactful in the broader developer community.
It works less well for engineers who optimize purely for total comp numbers. If your priority is maximizing TC, companies like Anthropic, OpenAI, Stripe, or Databricks will pay meaningfully more — but they'll also require you to be in an office (or at least a major city). The question isn't whether GitLab pays enough; it's whether the lifestyle it enables is worth more to you than the comp premium elsewhere.
Open Positions at GitLab
GitLab currently has 168 open roles across engineering, product, sales, and operations — all remote. If the transparent comp model, async culture, and genuine location flexibility appeal to you, browse the GitLab culture profile for the full picture.
Frequently Asked Questions About GitLab Compensation
Explore GitLab's 168 open roles
See all GitLab positions alongside 13,941 jobs from 116 companies — all with culture and compensation context.
View GitLab Profile → Browse GitLab Jobs →