Find answers to your questions about GitLab’s compensation framework.

Use the Compensation Calculator

Team members can access the calculator at any time with their GitLab credentials. Applicants will be given credentials and will be able access the calculator themselves as well, during the application process.


On this page, we’re detailing why we have the compensation framework we have now.

Contact Total Rewards

If you have any feedback or questions relating to compensation, please reach out to Total Rewards.

GitLab’s Compensation Principles

  1. We’re an open organization, and we want to be as transparent as possible about our compensation principles. Our compensation model is open to data driven iterations.
  2. We are paying local rates based on cost of labor market. There is no cost of living input in our compensation philosophy.
  3. Compensation aims to be at a competitive rate for your job family, your location, your level, your experience, and your contract type.
  4. We use a compensation calculator to ensure transparent and consistent compensation.
  5. We do not disclose individual compensation since compensation is not public.
  6. We adjust our calculator based on survey data, feedback from applicants and team members, and candidate data. Please email total-rewards@ gitlab if you want to contribute.
  7. We offer restricted stock units (RSUs) for most positions.
  8. We base compensation on current position and performance at GitLab – not on what we paid you last month – and, generally, we don’t reduce compensation.
  9. Increases within the market pay bands will be based on performance.
    • At hire, we base our compensation offer on the position and experience in the market.
    • For promotions, increases are based on ensuring alignment to the new role’s market range.
    • At Annual Compensation review, increases will ensure alignment to the market (by being within the entire range of the calculator), and resources will be allocated to top performing team members within the organization.
  10. GitLab will continue to monitor pay equality to ensure underrepresented groups are paid at the same rate as the company.
  11. We want to follow the processes on this page for everyone, please email total-rewards@ gitlab when we don’t. If you have a specific question around your compensation or one of your direct reports’ please schedule a call with total-rewards@ gitlab to review.
  12. We will update this page and the processes throughout the year.
  13. We’ll review your pay as soon as your job-family or level factor changes.
  14. If we change our SF benchmark for a job family without changing the requirements, we review the compensation both for existing team members and new hires. If the SF benchmark is changed together with the requirements this review might happen at the time of the change or in our yearly cycle.
  15. We offer bonuses and incentives, but we don’t offer ping pong tables or free lunches. We think it is more important to offer people flexibility and freedom. See the Top 10 reasons to work for GitLab on our culture page.
  16. We hire across the globe, but we’re not location agnostic. Your timezone, the location factor in your region, and the vicinity to users, customers, and partners can all be factors. For example, we may favor one applicant over another because they live in a region with a lower location factor or because we need someone in that timezone.
  17. All things being equal, factors such as whether a candidate is in an underrepresented group or a lower-cost market vs higher-cost market can help us come to hiring decisions. In this case, both factors are equally weighted and business needs will inform the final hiring decision.
  18. People on quota (account executives, account managers, and sales leadership) have variable compensation that is about 50% of their On Target Earnings (OTE). Individual contributors in the sales organization have variable compensation that is purely based on commission.
  19. Compensation decisions around level and experience levels and for functions not in the calculator are taken by the Compensation Group.

Competitive Rate

We want our compensation to be at a level where we can recruit and retain people who meet our requirements. Our requirements for all job-families are at or above the average in the market. Therefore, we can expect to be at or above the 50th percentile of the survey data gathered from providers like Comptryx and Radford. Please do not use the term market rate since this can mean either competitive rate or survey data. Also see our SF benchmark.

When discussing a competitive rate for a single person at GitLab, please refer to this as their lottery factor. For example, if this person won the lottery and left the company what impact would that have. Other common industry terms are walk away factor or bus factor, but those both hold a negative connotation.

Placement in the Compensation Range

As part of offering a competitive rate within our transparent Compensation Calculator, team members are able to see where they fall within the compensation range for their role in their location. Typically in the technology sector, the majority of team members are likely to sit between the minimum and slightly above the median of the overall compensation range. It is not common to see a team member at the top of the range as this would leave little to no room for salary growth.

It is important to note that where someone falls within the compensation range is not an indicator of performance, nor is it a sign of promotional readiness. For more information on how performance is linked to compensation please review the following handbook section. This is different from the Compa Groups GitLab used to have when the bands were more narrow. Additionally, where a team member sits in the range may change as GitLab’s compensation philosophy around competitive rates iterates to allow more room for salary growth.

Sharing Compensation

There are no policies in place at GitLab that prevent team members from sharing their personal compensation data, though we encourage that any concern a team member has with compensation be directed directly to your manager or Total Rewards as the most efficient route to address concerns and arrive to a resolution.

Paying Local Rates

Why we pay local rates

Competitive rates for roles vary depending on regions and countries. We pay a competitive rate instead of paying the same wage for the same role in different regions. Paying the same wage in different regions would lead to:

  1. If we start paying everyone the highest wage our compensation costs would increase greatly, we can hire fewer people, and we would get less results.
  2. A concentration of team members in low-wage regions, since it is a better deal for them, while we want a geographically diverse team.
  3. Team members in high-wage regions having much less discretionary income than ones in low-wage countries with the same role.
  4. Team members in low-wage regions being in golden handcuffs and sticking around because of the compensation even when they are unhappy, we believe that it is healthy for the company when unhappy people leave.
  5. If we start paying everyone the lowest wage we would not be able to attract and retain people in high-wage regions, we want the largest pool to recruit from as practical.

As more companies transition to partial or all remote workforces, we are tracking (internal only) the pay philosophy decisions made by these companies to understand the effects these decisions may have on the tech industry and future of remote pay.

Hire the best candidate

We hire the best candidate for each role regardless of location, cost, or other factors. During the sourcing we do optimize what potential candidates we approach in order to bring more diversity (both geographically and people from underrepresented backgrounds) to our team.

Blog Post

We also wrote a blog post about paying local rates.

Market-Based Approach

We have a market-based approach to compensation because:

  1. It allows for us to adapt to market changes, thus remaining competitive for local talent
  2. Role, location, and level benchmarks keep compensation bands consistent. Market-based benchmarks also help with keeping it fair and consistent rather than expecting our team members to negotiate their pay.
  3. Prevents wage compression which is when new employees negotiate and get higher wages than those being paid to current team members.
  4. As long as budget permits, we do what’s right for the market even if it means paying a team member higher than their “expected” pay.

Compensation Group

The Compensation Group is comprised of the CEO, CFO, and Chief People Officer. The Compensation Group is responsible for all Total Rewards escalations based on the approval matrix. When there is no time to coordinate with the group, the CEO can make a decision and inform the group. When the CEO is away (e.g. vacation), the two other members of the group can make a decision and inform the group. This group is different from the Compensation Leadership Development Committee at the board level.

Approval Matrix:

Approval Type Approvals Needed Process
Compensation Requests outside of band (cash/equity) for new hires and current team members Chief People Officer Process Document
Approval of Benefit Plan Changes (due to implementation or renewal) If Under 50k USD, Finance Business Partner (G&A)
If 50k-100k USD Finance Business Partner (G&A) and VP, Finance
If 100k+ USD Finance Business Partner (G&A), VP, Finance, and CFO
Total Rewards to summarize implementation or renewal details
Final Approval of Annual Compensation Review Chief People Officer, CFO, and CEO Total Rewards to present final proposed increases and budgetary impact
Review/approval of Executive and Board Compensation Chief People Officer and CEO Total Rewards to present summary of proposal, once approved escalate to Compensation Leadership Development Committee for Final Approval
Internal Demotion requests Chief People Officer Demotion Process

Compensation for Acting and Interim Roles

Effective Q2 of FY 2021, we have established a one time bonus payment process for team members that are asked to step into an acting or interim management role. Team Members in an acting or interim management role should review the expectations of an individual in the management group.

Criteria for Eligibility

  • For an interim role to be considered, the need for coverage would need to be longer than a 30 day time period.
  • The interim role has to be at a higher level than the current role of the team member.
    • If a team member assumes 100% of the workload of a lateral role for 60 days or more in addition to their permanent full time role, an interim bonus may be considered by the People Business Partner and leader of the group.
    • Effective 2023-02-01, interim bonuses in Go-to-Market roles (CRO Organization, Sales Development) will be available to people managers temporarily occupying a lateral or higher management position in addition to their permanent full time role.
  • In case the interim role is within another job family, team members will also be eligible for the interim compensation on a lateral level.

Since Acting roles do not typically end in promotion, the decision on whether the acting role meets the eligible criteria rests with the Hiring Manager and the Department head.

Calculation of Interim Bonus

The formula for the bonus recognizes the length of time that the team member is playing the interim role. Payment of the one time bonus would occur at the completion of the interim role. The bonus would be calculated using the following formula:

The greater value of the standard discretionary bonus amount ($1,000 at the current exchange rate) OR the following calculation:

For team members on a base salary compensation plan, your bonus will be an additional 10% of your salary for the duration of the interim role period. The calculation is as follows:

  • (Annual Base Salary in Local Currency/365) x .10 (10%) x # of Calendar Days in the Interim Role

For team members on an OTE (On Target Earnings) compensation plan in Go-to-Market roles, interim compensation will be based on results achieved by the interim team in the interim period:

  • Interim leaders will dotted-line manage the new team, meaning they will not assume direct management of the team in Workday, but will instead act as a temporary leader. As such, quotas will not change during the interim period.
  • When interim managing a lateral team:
    • The interim bonus will be calculated based on Net ARR closed during the period x a representative BCR (base commission rate), calculated based on the leader’s OTI and the interim role’s annual quota
  • When interim covering for a higher leadership position:
    • The interim bonus will be calculated based on Net ARR closed during the period x a representative BCR (base commission rate) for the higher leadership position
  • Standard commissions payments will continue for the duration of the interim role
  • All in-plan (within OTI) components are eligible to be included in an interim bonus calculation for a GTM role, e.g. Net ARR, New Logo, Professional Services Bookings, etc.
  • All people managers in GTM roles are candidates for interim management assignments, outside of members of the CRO or CMO leadership teams, i.e. direct reports of the CRO or CMO
  • Total bonus payments for GTM team members in an interim management role shall not exceed $50,000 USD for a single interim leadership assignment

The interim bonus should be calculated based on the team member’s salary during the interim period, not the salary after the interim period. If your compensation changes during the interim period (for example, relocation, country conversion, etc.), we will calculate the interim bonus based on the pay rate of each calendar day.

Tracking and Submitting Interim Bonuses


Interim/acting roles should be tracked in Workday, in some cases the process is initated in Greenhouse or may also be tracked in the Acting/Interim Tracker managed by the People Connect Team.

Guidance on different processes can be found below:

Greenhouse Acting/Interim Tracker
All interim roles that have gone through our Greenhouse interview process Lateral acting role in the same job family
More senior acting/interim role in the same job family Lateral acting roles in different job families

Greenhouse - Acting/Interim Tracker examples:

  • Engineering Manager takes on an acting role as a Product Designer
  • Engineering Manager takes on another Engineering Manager role simultaneously in a different group

Workday examples:

  • An Engineering Manager takes on an interim role as a Senior Engineering Manager
  • A Product Manager takes on an interim role as a Senior Backend Engineer (after having gone through an interview process)

The process for tracking interim/acting roles in both cases is as follows:

  1. Managers send an email to with their People Business Partner in copy with the following information:
    • Whether the role is interim or acting
    • Whether the role is in a new job family or the same job family
    • Whether the interim/acting role is lateral or a higher level
    • The effective start date of the interim/acting period
  2. (for interim) People Business Partner will submit a Job Change - Change Job Details request in Workday. Job title should not be changed, as compensation and job family are not altered as part of the interim/acting process. Only a modification to to the team member’s Business Title is required. This step is only done for interim positions as acting positions are not tracked in Workday, but exclusively on the spreadsheet.
  3. People Connect will either, 1) confirm that the interim/acting period has been added to the Acting/Interim Tracker, or 2) confirm that the job title has been added to Workday.


When the interim/acting period ends, the following process should be followed to submit the interim bonus request:

  • (For Acting bonuses) The manager replies to the initial email to and their People Business Partner to confirm the start/end date of the acting period and their initial bonus calculation
  • (For Interim bonuses) The manager references the Workday Job tab and clicks into Job History and review the ‘Business Title’ column to confirm the start date of the interim period
  • Once confirmed, the Manager submits the bonus in Workday. Follow the Request a One-Time Payment job-aid to submit an OTP. Manager must also provide the start and end date of the of interim period in Workday under the Additional Information section in Workday

Note: The team member must be an active team member of GitLab at the end of the interim role period to be eligible to recive a bonus payment. If a team member leaves GitLab during the interim role period, they will not be eligible for a prorated payment.

Examples of the Interim Bonus Calculations below

  • Senior Engineer has a base salary of $125,000. She has taken on the interim role of Engineering Mgr for 3 months (Jan-March) which is a total of 90 days. The bonus for this interim role would be ($125,000/365) x .10 x 90 = $3,082.19
  • Finance Business Partner has a base salary of $100,000. He has taken on an interim role covering multiple teams while his coworker is on leave for 4.5 weeks which is a total of 31 days. The bonus for this interim role would be ($100,000/365) x .10 x 31 = $849.32 so we would round up for this bonus and process as a discretionary award.
  • Area Sales Manager interim manages a lateral team after a peer ASM has been promoted. The ASM has a base commission rate of 1% for Net ARR and $3,000.00 per New Logo. During their interim coverage the Area closes $1,000,000.00 of nARR and 2 First Order new logos. The bonus calculation would be ($1,000,000.00 x .01) + (2 x $3,000.00) = $16,000.00.
  • Area Sales Manager interim manages an entire Region after an AVP leaves GitLab. AVP base commission rates are 0.3% for Net ARR and $800 per New Logo. During the interim coverage period, the team closes $5M of Net ARR and 4 New Logos. The bonus calculation would be ($5,000,000.00 x 0.003) + (4 x $800.00) = $18,200.00.

Exchange Rates

Point in time rate as 2023-06-01

Currency Rate from USD Rate to USD
AUD 1.5203 0.65776
AED 3.6731 0.27225
BRL 5.0146 0.19942
CAD 1.34455 0.74374
CHF 0.90564 1.10419
CLP 801.5 0.00125
CNY 7.0945 0.14095
CZK 22.0032 0.04545
DKK 6.9213 0.14448
EUR 0.92933 1.07604
GBP 0.79838 1.25254
HUF 344.8555 0.0029
ILS 3.74505 0.26702
INR 82.27695 0.01215
JPY 138.7455 0.00721
KES 136.9451 0.0073
KRW 1,313.17500 0.00076
MAD 10.16965 0.09833
MXN 17.5538 0.05697
NOK 11.05739 0.09044
NZD 1.6488 0.6065
PHP 56.081 0.01783
PLN 4.19845 0.23818
RON 4.6161 0.21663
RUB 81 0.01235
SEK 10.80972 0.09251
SGD 1.3473 0.74223
TRY 20.8952 0.04786
USD 1 1
ZAR 19.6259 0.05095

The compensation calculator is updated using the December 1 and June 1 point in time exchange rates according to Google Finance rates. We are using the point in time exchange rate due to significant lag when utilizing an average exchange rate.

The updates to the handbook, compensation calculator, and Workday for the December 1 rates will be made between December and January with an effective date of February 1. The updates to the handbook, compensation calculator, and Workday for the June 1 rates will be made between June and July with an effective date of August 1.

Adjustments to existing team members’ compensation who are paid in local currency are made only during the applicable compensation review cycle. We only adjust compensation during the review cycle since being paid in local currency means that your local purchasing power does not change.

Team members contracted through CXC or IT BV may have the option to choose to be paid in USD or EUR when there is volatility in their local currency. This change can only be made once during your employment and only if CXC and payroll can support it. USD and/or EUR payment options are not available in all countries.

Exchange Rates for Bonus Processing

All one-time bonuses including Discretionary, Referral, and Working Group Bonuses where the intended value is awarded in USD will be converted to local currency using the set exchange rates above. This is a reversion of the prior policy put in place to use monthly rates with the reversion going into effect as of September 1, 2023. In the future, when we are able to put an efficient process in place for maintaining more up-to-date conversion rates in Workday, we will further revise this policy to use more current rates.

Not paid in your local currency

There are a number of reasons why team members may not be paid in local currency. For example, GitLab’s bank might not support the currency or there may be a strong economic reason for the team member to choose a different currency. The currencies that GitLab can pay in are published on the contracts page.

  1. The Total Rewards team will analyze the difference in exchange rates from December to June (or vice versa) and their effect on local purchasing power using the following process:
    • The exchange rate between the team member’s local currency and chosen currency will be compared for both the current and previous conversion effective date.
    • The percent change is calculated between the two rates: (New Rate - Previous Rate)/Previous Rate.
  2. Criteria for review, the team member:
    • Is not paid in local currency.
    • Has been at GitLab for greater than six months.
    • Has not opted out.
  3. Only changes greater than +/- 5% will be processed in each review.
    • Changes must stay within band of the compensation calculator.
  4. The Total Rewards team will work with People Connect to confirm by job change letter any increases or decreases to compensation as a result of this review.
  5. Any significant increases or decreases will be reviewed on a case-by-case basis before any changes are made.
  6. Team members may also opt out of the reviews.
    • If an opt out agreement is signed, the team members will be excluded from any future Exchange Rate reviews. GitLab retains the right to revisit the opt-out status in the future.
  7. Additionally, if a team member is impacted outside of this review period they should reach out to total-rewards@domain.

Example: A team member’s local currency is the Russian Ruble (RUB) and they are paid in US Dollars (USD). They have not previously opted out and have been employed for greater than 6 months. If the exchange rate effective 2023-06-01 is 0.013 and for 2023-12-01, the exchange rate increases to 0.014, then this would result in a percent increase of 7.69%. The team member would have the option to either accept this increase to their salary or opt out of all salary fluctuations based on this review during their time at GitLab. Any changes to salaries based on this review will be made during the Annual Compensation Review cycle.

Due to the current economic climate, we will not be applying negative salary fluctuations based on the 2022-12-01 local purchasing power review for those not paid in their local currency. We will continue to monitor the economic situation and review the impact to the team as well as global currency volatility before reconciling missed reviews and reinstating the full process.

Hourly Employees

GitLab is committed to following all applicable wage and working hours laws and regulations. To help ensure that all work performed for GitLab is compensated correctly, team members compensated on the basis of hours worked must report and record time accurately.

Sales Compensation

Sales and Sales Development roles at GitLab that are subject to quota and paid commission based on the Sales Compensation Plan are not located in the compensation calculator. This includes roles in the following departments:

  • Channel
  • Commercial Sales
  • Enterprise Sales
  • Sales Development

These roles are still benchmarked using market dataand are assigned to a pay differential zone based on their location factor according to the following table:

Zone Location Factor Range Zone Differential
Zone 4 0.01 - 0.49 0.60
Zone 3 0.50 - 0.69 0.75
Zone 2 0.70 - 0.85 0.85
Zone 1 0.86 - 1.00+ 1.00

Variable Pay Frequency

The Variable Pay Frequency is a field held in Workday and applicable to roles that receive a commission or bonus. Variable Pay Frequency is assigned according to the following chart:

Department/Role Description Variable Pay Frequency Type
VP (non-sales), Executives Company Executive Bonus Program
VP (Channel, Field Operations, Customer Success) Sales Executive Bonus Program
VP (Commercial Sales, Enterprise Sales) Monthly Bonus
Director (non-sales) Company Director Bonus Program
Director (Field Operations) Sales Director Bonus Program
Director (Channel, Customer Success, Enterprise Sales) Monthly Bonus
Director (Consulting Delivery) Quarterly Bonus
Channel, Commercial Sales, Customer Success, Enterprise Sales, Sales Development (IC) Monthly Bonus
Sales Development (Manager) Quarterly Bonus
Consulting Delivery, Education Delivery, Practice Management Quarterly Commissions

Director Compensation

Director compensation is determined as part of the GitLab Compensation Calculator and is comprised of base salary and bonus. The location factors for Directors have a floor built in where the location factor for a team member is subject to either the US Director Minimum location factor of 0.8 or Global Director Minimum location factor of 0.7. If someone is in a location with a higher location factor then this minimum does not apply and the higher location factor will be used.

Directors who are not already enrolled in the Sales Compensation Plan or other performance incentive plan are eligible for a 15% bonus of current base salary. More information on the bonus plan can be found in the Company Director and above Bonus Plan section.

Executive Compensation

Executive Compensation (VP and above) is derived outside of the GitLab Compensation Calculator using the following process:

  1. The Total Rewards team collects survey data to review against current compensation to ensure alignment in cash (base/variable) and equity refresh values.
    • Survey Data from the GitLab peer group: GitLab will analyze the peer group data from Radford against peer group data from Compensia.
  2. The Total Rewards team will advise on a market increase or performance factor as determined in the performance enablement review, whichever is appropriate.
  3. The recommendation will be reviewed by the e-group leader for VPs and above. The final approval for VP compensation is the Compensation Group. Total Rewards will work with finance to ensure alignment to budget.
  4. E-Group compensation is reviewed in partnership with Compensia based on the peer group data provided. The CEO will recommend increaes and refresh grants for his direct reports to the Compensation Leadership Development Committee for approval.
  5. The Total Rewards team will then notify the CEO or direct manager of the increase who will then communicate it to the individual.

As each Executive has an individual market assessment upon hire, we expect compensation to be aligned to market at each compensation review. If there are large changes in the market for a specific role, those will be addressed.

Company Director and above Bonus Plan

Directors and above are eligible for the Company Bonus Plan.


  • Prior to the bonus payment and after Compensation & Leadership Development Committee approval, the CFO will confirm the achievement % of the bonus plan in the #director-and-above slack channel.


  • Payments expected to occur 60 days after the end of the fiscal period but are dependent on the accounting close process and committee approval.


  • The bonus will be paid out semi-annually.
  • The first semi-annual payment will be funded up to a maximum of 80% of Company Plan performance against targets. Any full plan year adjustments will be made as part of the final bonus payout.
  • The final bonus payout will be based on actual performance against plan less amount paid at the semi-annual payout.
  • If the first semi-annual bonus is achieved but Company performance falls below the annual threshold the second half bonus will not be achieved but the first half bonus will not be rescinded or otherwise payable back to the Company.


  • The bonus plan is approved by the Compensation Leadership Development Committee of the Board of Directors.
  • Performance against Plan targets is reviewed and approved by the Audit Committee of the Board of Directors.
  • Bonus payouts are recommended by the CFO and approved by the Compensation Leadership Development Committee of the Board of Directors.

Proration and Eligibility:

  • The Director bonus will be prorated for team members who start or are promoted into the Director bonus pool between February 1 and July 31 (first half bonus), or start or are promoted between August 1 and January 31 (second half bonus).
  • In addition, the team member must be actively employed by GitLab at the time of payout.

GitLab reserves the right to change or discontinue the bonus program at any time. All bonus payouts are discretionary and require the achieving of specific company results that will be communicated each year.

Sales Commissions handbook page.

Bonus Payout Approvals

The Compensation Leadership Development Committee approves all bonus payouts for direct reports to the CEO and overall bonus funding at the end of each Fiscal Year. The Compensation Group internally at GitLab approves all other bonus payouts.

  1. The Finance team will generate a calculation of the total bonus payout for the Fiscal Year within 30 days of the last day of the fiscal year including: Employee #, Name, Reporting to, Division, Department, Title, Hire Date, Total Eligible, Total Payout.
  2. The Total Rewards Team will audit the calculation and eligibility list.
  3. Once approved by the Total Rewards and Finance team, a meeting will scheduled with the CEO, CPO, and CFO for approval of the bonus payout. The CEO and CFO will review and approve all bonus payouts (aligned with the authorization matrix) and discuss exceptions with the CPO.
  4. The Total Rewards Team will collaborate with the Finance team to include the total spend for the bonus plan, attainment, and executive specific payout for the Compensation Leadership Development Committee meeting. Approval of the bonus plan would be captured in the Committee meeting minutes.
  5. Once approved by the Compensation Leadership Development Committee, the Total Rewards team will notify Finance that the bonuses are ready for processing via payroll. The file approved internally will be shared with payroll by the Finance team.

Compensation Data Analysis and Modeling Sheet

This is an internal process for the Total Rewards team which details how to refresh the Compensation Data Analysis and Modeling sheet which is used for processes such as calculating percent outside of compensation band.

To update:

  1. Navigate to the sheet “Comp Data Analysis and Modeling - Workday Report”.
  2. Download the “Comp Data Analysis & Modeling” report from Workday as a CSV.
  3. Duplicate the “Template” tab in the sheet and rename it based on the date the Workday report was pulled using format: yyyy-mm-dd.
  4. Copy and paste the Workday report starting from cell A2.
  5. Delete any test accounts, denoted “Test” in their name, by deleting the entire row.

Learning GitLab’s Compensation Framework

As part of our Q1 OKR, we will be working on ensuring there are materials for a compensation certification. The following are the initial questions to generate the certification.

Compensation Fundamentals Training

Please take time to complete the Total Rewards Compensation Fundamentals Training in Level Up.

This training includes details such as:

  • Purpose of Total Rewards
  • Components of Total Rewards (Cash, Equity, Benefits) resulting in a Total Package
  • Cash comp versus Equity
  • Market Pay Practices
  • Pay Ranges and how they operate
  • Pay for Performance vs Market Rates
  • Cost of Labor Market vs Cost of Living
  • Compensation in an emerging remote environment

The Why Questions

The What Questions

The How Questions

Knowledge Assessment

You can test your knowledge on our compensation by taking the GitLab Compensation Knowledge Assessment quiz.

If you have questions about compensation or the content in the Knowledge Assessment, please reach out to the Total Rewards team.

Compensation Review Cycle
On this page, we explain how we carry out the Compensation Review Cycle.
The Compensation Calculator
On this page, we explain the different factors that make up our Compensation Calculator and its alignment to GitLab's values and Compensation Principles.
Last modified October 2, 2023: Update 6 files (b075dbf9)