Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Global Compensation

On this page

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.
  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 compensation@ domain if you want to contribute.
  7. We offer stock options for most positions.
  8. We base compensation on current position, experience at GitLab, and performance – not on what we paid you last month – and, generally, we don't reduce compensation.
  9. We want to follow the processes on this page for everyone, please email Compensation@domain when we don't. If you have a specific question around your compensation or one of your direct reports' please schedule a call with compensation@ domain to review.
  10. We will update this page and the processes throughout the year.
  11. We'll adjust your pay as soon as your job-family or level factor changes.
  12. If we change our SF benchmark for a job family without changing the requirements, we change 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.
  13. 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.
  14. 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. All things being equal, we will hire people in lower cost markets vs. higher cost markets.
  15. 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. The commission for all roles in the sales function is paid monthly with the exception of the following roles: Implementation Engineer, Sales Development Manager, Business Development Manager, Director of Customer Success. These roles are paid commission quarterly.
  16. Compensation decisions around level and experience levels and for functions not in the calculator are taken by the compensation group. This committee consists of the CFO, CEO, and Chief People Officer. When there is no time to coordinate with the committee, the CEO can make a decision and inform the committee. When the CEO is away (e.g. vacation), the two other members of the committee can make a decision and inform the committee. Whatever the decision is, the earnings committee should be cc-ed (or bcc-ed) on the final email so that the committee members can know that the loop was closed. This group is different from the compensation committee at the board level.

Competitive Rate

We want our compensation to be at a level were we can recruit and retain people who meet our requirements. Our requirements for most of our 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.

Pay Date

  1. Employees of our Dutch entity (GitLab B.V.) will get their salary wired on the 25th of every month, and can see their pay slip in their personal portal on HR Savvy's system towards the end of the month.
  2. Employees of our Dutch entity who are based in Belgium will get their salary wired around the last day of each month and will receive their pay slip in their personal portal on Boekfisk's system
  3. Employees of our Dutch entity based in India that are employed through GitLab's co-employer Lyra will get their salary wired around the last day of the month. Lyra will send pay slips electronically but will be switching to a HR portal very soon so that pay slips and tax declaration forms can be accessed directly.
  4. Employees of our US entity (GitLab Inc.) have payroll processed semi-monthly through ADP, and they can access their pay slips through the ADP portal.
  5. Employees of our UK entity (GitLab Ltd) will get their salary wired on the last day of every month, and can see their pay slip via their personal portal on Vistra's system towards the end of the month.
  6. Employees of our German entity (GitLab GmbH) will get their salary wired on the last day of every month, and can see their pay slip via their person portal on RPI International Payroll's system towards the end of the month.
  7. Employees of CXC Australia will be paid at the end of each month and can view their pay slips on CXC's portal. Everyone is given a login by CXC as part of their onboarding.
  8. Employees of CXC Canada are paid fortnightly and are required to submit timesheets to their managers and then CXC. Access is given to a the portal as explained in the point above.
  9. Employees of SafeGuard are paid monthly and on the last day of the month (depending on the country) with exception to Brazil, 15th of each month. Payslips are provided electronically by SafeGuard. Expenses are submitted through Expensify and reimbursed via payroll.
  10. Contractors from (Hungary, Italy, Japan, Nigeria, Poland, South Africa, Switzerland, Ukraine, and US) to GitLab (either entity) should send their invoices for services rendered to payroll@gitlab.com. All other contractors will get pay on the 22nd of the month and remittance advice will send to their gitlab email address.
    • For 'fixed fee' contracts, it is OK to send the invoice before the time period that it covers is over. For example, an invoice covering the period of March 1-31 can be sent around March 15.
    • All invoices are internally reviewed, approved, and then payment is processed. This is usually a fast process, but be aware that it can incur delays around vacations. In principal, payments go out once per week on Fridays.
    • An invoice template can be found as a Google sheet named "Invoice Template" (also listed on the finance page)

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. A concentration of team members in low-wage regions, since it is a better deal for them, while we want a geographically diverse team.
  2. Team members in high-wage regions having less discretionary income than ones in low-wage countries with the same role.
  3. 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.
  4. 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.
  5. If we start paying everyone the lowest wage we would not be able to attract and retain people in high-wage regions.

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.

Relocating

Different than business travel, vacation, or visiting a relative for a few weeks, relocation means that you will establish yourself in a new location outside of your current metro area. If you are ending your current residential living arrangement, spending more than six months in one location as part of an extensive period of travel and/or will have your mail delivered to an address in a different city please contact us.

As stated in the code of conduct section of the handbook, you should first obtain written agreement (from your manager) when planning a relocation. It is the company's discretion to offer you a contract in your new location. At the time of the location update, we will take into consideration your new metro region when making a salary offer for continued employment.

At the onset, this practice sounds harsh when moving to a lower paid region. One might argue that it seems unfair for the organization to pay someone less for the same work in the same role, regardless of where they go. However, if you look at it from another angle for a minute and compare this practice to what most companies do, it should make more sense. For example, say you work for a company with physical locations and say they haven't accepted that remote work is as productive as coming into the office yet. If you wanted to pack up and move to a location where they did not have a physical site, you would have no alternative but to resign and seek new employment in your new location. You would find quickly that companies in the area pay at a locally competitive rate.

Now, let's say the company did have a site in your new location and they offered the flexibility to transfer. If they did not have a similar position open, you would have to either apply for a different open position in the same company or resign and apply externally (back to the realization that other companies will pay at local competitive rate). If you were lucky enough that they did have a similar role in the new location, a transfer would come with a pay rate based on the local market to ensure equity across all incumbents (people in the job) by location.

Adjusting pay according to the local market in all cases is fair to everyone. We can't remain consistent if we make exceptions to the policy and allow someone to make greater than local competitive rate for the same work others in that region are doing (or will be hired to do). We realize we might lose a few good people over this pay policy, but being fair to all team members is not negotiable. It is a value we stand behind and take very seriously.

Please refer to the code of conduct to review the relocation process.

Blog Post

We also wrote a blog post about paying local rates.

Annual Compensation Review

During the fourth quarter of each year, People Operations Analysts will conduct a compensation review to ensure all team members are paid based on market data in the compensation calculator. This is not a Cost of Living Adjustment, but instead a review of the market changes. Rent Index and Experience Factor will continue to be a part of the compensation calculator equation. The annual compensation review is not directly linked to performance reviews nor the ability to be promoted. The increase percentage may vary for each person. For instance, experience factors are reviewed as part of a compensation adjustment or promotion, which GitLab encourages to happen independently from this review. If a team member was recently adjusted, the annual adjustment might yield no additional salary during the annual compensation review. This review acts as a sweep for each team member’s compensation to be evaluated at least once per year.

Annual Compensation Review Timeline

  1. People Operations Analysts will review all benchmarks, rent indexes, and country factors associated with the Compensation Calculator and propose revised inputs to the Compensation Committee for approval/implementation.
  2. People Operations Analysts will reach out the managers to obtain updated experience factors for each active team member.
    • People Operations Analysts will create a spreadsheet with all active team members listing the following information: employee number (for People Ops use only), name, title, and level.
    • Manager will then use the Experience Factor Guidelines to assess where each team member is within their current position.
    • Remember that this is also a good time to update your team’s position description if it does not reflect the role.
  3. People Operations Analysts will calculate the amount of the increase for each team member and obtain approval from Finance for the total budget impact. Depending on budget constraints, the increases may be adjusted up or down. Before sending to Finance, update the exchange rates to the most recent date available.
  4. People Operations Analysts will generate a google sheet which will serve as a summary of increases for each department and share with all direct and indirect managers. This manager review will be the time for management to verify the compensation calculator inputs and adjust increases. While these adjustments are based on market data and experience factors, rather than performance, team members who are currently struggling to perform at their current level should have that communicated clearly and the manager should consider delaying the increase until performance reaches an commendable level.
  5. Managers will inform the team members of the increase and adjustments to compensation compared to their experience factor.
  6. People Operations Analysts will stage the letters of adjustment, update BambooHR, and notify all payroll providers to be effective January 1st.
  7. People Operations Analysts will generate letters of adjustment and stage for signatures. Each letter should also be accompanied by the Code of Ethics Acknowledgment Form.

Annual Compensation Exchange Rate

Exchange rate used for the 2018 annual compensation review is taken from Oanda on the date of 2018-11-30.

Manager Review

As part of the new Annual Compensation Review, managers will review/approve the proposed salary increases to ensure that we are paying each team member to market. Please verify the compensation calculator inputs (experience factor, level, title) are accurate.

If you did not conduct an experience factor review with your direct report, please advise a People Operations Analyst and follow the guidelines from the handbook. It is very important to you use the Experience Factor Worksheet to determine the correct final Experience Factor and to have discussions with your direct reports. It is very important that GitLab team-members understand their experience factor.

While some GitLab team-members may not receive an increase due to already being at the right competitive rate for their Experience Factors, Level, Role, and Location there are other circumstances where an increase should be avoided. If there are any reasons as to why the team member should not receive the proposed increase to be aligned with their experience and market in our calculator, please ping compensation@ domain in the manager worksheet and add your comments in the “reasoning” cell. This could be due to a current performance issue, pending termination, etc. If you would like to delay the increase, please outline a proposed plan of action and deadline.

Additionally, it is important to note that deriving an experience factor based on the current compensation calculator is not advised. Experience factors should be based on the knowledge, skills, and ability in the current role. Second, the output of the compensation calculator may change due to the review of all inputs. We want each team member's pay to be an accurate reflection of their market, with the caveat that we adjust once a year in order to reduce the overhead of the adjustment process.

Cost of Living Adjustment (COLA)

For positions in the compensation calculator, each eligible team member will receive at least a prorated 3% increase in base salary as a Cost of Living Adjustment. Note: If the team member is on a variable + base plan and is not at the desired split for their role, the entire cost of living adjustment will be added to the base or variable compensation to get closer to the desired split. If the team member is at the desired split for the role, then the increase is equally divided among base and variable. This is also applicable to any compensation adjustments that may occur outside of COLA.

Compensation Calculator

Use the calculator

The calculator is embedded in every job family page but we also have a calculator that lets you select the job family.

Goals

As a natural extension of the Compensation Principles outlined above, and our commitment to transparency, sharing, efficiency, directness, and boring solutions (see our values) we developed a Compensation Calculator. The compensation of directors or above and anyone on a quota is not set with the calculator.

The goals of the calculator are:

  1. Calculate compensation for 200+ regions all over the world.
  2. Based on a simple formula.
  3. People with the same attributes should earn the same.
  4. The adjustment for paying local rates should be the same if you are in the same location.
  5. You should be able to calculate your compensation in case you know or made an assumption about your level and experience.
  6. That it is as close to a competitive rate as possible given the other constraints.
  7. Be able to calculate compensation for most of our offers without involving a compensation specialist.

As with all things at GitLab, the compensation calculator is a constant work in progress. Please send an email to compensation@domain if/when you find a big difference between what the calculator suggests vs. what market data indicates. Please make sure to include all relevant links and data.

Formula

Your salary = SF benchmark x Location Factor x Level Factor x Experience Factor x Contract Factor x Exchange Rate

Your options can be found on stock options.

See the calculator in action on each job description, or at its home page.

The compensation calculator is updated in January and July with the proper exchange rate, keeping compensation levels in line with local purchasing power.

Disclaimer

The compensation calculator is a tool to assist People Operations Analysts in determining a compensation package for new and existing team members. The results of the calculator are not binding. Written correspondence through a contract or letter of adjustment specify all official compensation changes. We reserve the right to change the calculator at any point in time.

SF Benchmark

Introduction

SF benchmark is the employee salary at an experience factor of 1.0 at or above market for the role in San Francisco, which we determine using various sources of market data including AdvancedHr, LinkedIn, Glassdoor, Paysa, Payscale, and Comptryx. The SF benchmark used in each position is available in the roles.yml file in this website's repo.

New Benchmark

Whenever a new role is established, a new benchmark must also be determined. The People Ops Analyst is pinged on the merge request for a compensation review to start the process. The People Ops Analyst should ensure that they request is not for a role that already exists and has a benchmark. Compensation Benchmarking is the process of using internal job descriptions to match salary survey job in order to identify the external survey data for each benchmark positions. Sources like Comptryx, Payscale, Paysa, LinkedIn and Glassdoor are some of the sources used to determine salary benchmarks. Compensation data can fluctuate from very high salary data to very low salary data for roles that have the same or similar job titles. Example would be Field Marketing Manager. A Field Marketing Manager at GitLab or another SaaS or Technology company salary benchmarks would and can be included with Field Marketing Manager for other Non Technology companies, as an example RedBull. Though they have the same "title" the role, scope and salaries for these roles are very different. Based on these variants in comp data we will look at the relevant comp data for each role and use the median for the benchmark. A review of the median against the average will be reviewed to ensure there is no large discrepancy with the proposed benchmark. What is the Mean - The mean is the same thing as the average. It is the result of dividing the sum of two or more values by the number of values. So (a+b+c)/3= the mean or average. What is the Median - The median, otherwise known as the midpoint, is a very common term used in compensation and preferred to the mean. In its simplest terms, the median is the middle value of a series of values laid out in numerical order. It's the middle point of the data set. Half of the values will be less than the median, and half will be higher than the median. To review the Compensation Benchmark process please refer to the New Roles Creation.

Benchmark Adjustment

As stated in competitive rate we want to recruit and retain people who meet our requirements. If more than 20% of the people do not accept our offers stating compensation as a reason this is an indication we're not offering a competitive rate. In this case the People Ops Analyst can review the compensation. During this review, we do not look to target at a certain percentile, but instead look at market rates and declined candidate offers when adjusting. A business case should be presented the the compensation group after approval from the People Operations Analyst in a google sheet with market data, candidate expectations, an impact to the current team; and in a google doc outlining the problem statement, likely cause, what the department has already tried, and an overall proposal which clarifies the budgetary impact.

If we change our SF benchmark for a job family without changing the requirements, we change 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.

Sometimes the requirements of a job family change. Usually this means the requirements become more restrictive as the complexity of our project and services demands more–or more specific–experience. This is different from a market adjustment because the market has not necessarily changed. This means that everyone on that benchmark does not get an automatic raise.

However, we want everyone who works at GitLab prior to a role requirement change to the have the same opportunity as new hires. They and their manager can then immediately begin technical and career development using the new role requirements. Promotions against this new criteria can also be requested on their own cadence.

It's not necessary, but it's easier for the organization to digest a benchmark change resulting from changes in a job's requirements if the name of the role changes as well. Two examples are:

Location factor

Introduction

Location Factor is reviewed in two ways. The highest resulting value is stored in the location factor file. This double process is an iteration as we attempt gather additional resources to make our model increasingly driven by market data. People Operations Analysts will use their best judgement in determining the input per location based on our Compensation Principles.

  1. A market analysis of compensation rates globally. People Operations Analysts will pull survey data in each Geo Area and compare the differential to SF.
  2. Where we are not able to find the proper data to conduct the analysis, we will use the Numbeo rent index normalized to San Francisco, or in math terms, (.7 x (Rent Index/1.26) + 0.3).

Geographical Areas

The location factor depends on your geographical area To determine your area:

  1. Select the country you live in. This will filter out all areas outside of your country. Based on the remaining choices under "area," if you live within a commutable one hour and forty-five minutes of a city listed, you may use that as your location. If not, you will select "Everywhere else." If the only item listed for the country is "All," the country has the same location factor regardless of the city you live in. If applicable, a state or province might be listed instead of a city.
  2. If your country is not listed, reach out to compensation@domain to gather relevant data.
  3. When you move, you have to inform us and we may adjust your compensation up or down. Refer to People Operations Analysts to see what the likely impact will be.

Calculating

To ensure our location factor is reflective of the ability to commute between nearby cities, we incorporated Geographical Areas into the compensation calculator. This process is only used when we do not have the proper data to determine a location factor based on a market analysis alone.

To determine geographical areas, we looked at what the United Nations outlines globally. To determine the rent index for each country please see the following process per geographical area and country:

  1. Research via an official website what appropriate regions are within the country/area. For example, in the United States there are four regions with nine subdivisions. In the United Kingdom, for compensation purposes, there are four different areas.
  2. Pull all numbeo data for the region selected.
  3. Determine any outliers for the region (on the high end). Make these separate geographical areas.
  4. Define a commutable region for the area (1.75 hours through a google search looking at prime time commute hours).
  5. From the remaining data points, select the highest to be used for everywhere else in the region. (Most of these data points should be very close.)
  6. If there is a historic Numbeo number that is higher than the current Rent Index, use the historic number.
  7. Determine if a minimum rent index should be used in the region. (This would normally occur if there is a large gap between remaining data points.)
  8. If there is no data for a country, do not include in the comp calculator. If needed, we can review the compensation based on the region and other salary data.
  9. If there is no data for a state/province within a country, assign the lowest value of the other states/provinces.

Note: The Compensation Calculator lists out metro areas or states for user interface clarity, but the process above is followed for each region, not per state.

Level Factor

Level Factor is currently defined as junior (0.8), intermediate (1.0), senior (1.2), staff (1.4), or manager (1.4). Not all levels of each job follow this same nomenclature. A summary of the naming of levels per role can be found in role_levels.yml.

Experience Factor

Introduction

The experience factor is determined by the direct manager for each team member, and reviewed by all indirect managers. This should be done at least once per year for current employees and during the offer stage for candidates. This factor does not directly reflect years of work experience, but instead, demonstrated ability to drive projects and deliverables from the position description to completion within GitLab. The goal of quantifying experience factors, as it relates to compensation, is to ensure they are accurate to work toward getting to the right salary. Experience Factors should also be used in coaching and developing team members.

If a manager is new to the team member, and has not had time to assess the experience factor, collaboration with previous managers or colleagues to determine the person’s skills is encouraged. This can serve as a strong data point when assessing experience factors.

Determining

  1. Create an individual Experience Factor Worksheet by saving a copy in the name of your team member.
  2. Use the role description, including any appropriate requirements or responsibilities, to help populate the responsibility line items in the worksheet. It is important to take all aspects of the position description into account when determining experience factor. If the position description isn't correct, use this as an opportunity to update it. Also be sure to update the soft skills section of the worksheet. The percentages are the same for each team member at GitLab, but level should be taken into account when evaluating experience.
  3. It is strongly recommended to complete this with the participation of your team member. There is a secondary input and formula for the team member to derive their own experience factor. This secondary input won't affect their compensation but will be used as a discussion point between the manager and the team member. At a minimum the manager should share the worksheet once the inputs are complete.
    • It is critical that all managers share the experience factors with the respective team member, including how they arrived at that factor. Team Members should understand where they stand in relation to the individual experience factors and weights that led to the final number.
    • If your manager has not yet discussed your experience factor with you, please reach out to your HR Business Partner.
  4. Once you have discussed the Experience Factor Worksheet and resulting final number with your team member, please add it to the file in BambooHR. This enables us to ensure that it is easy to find as a reference and discussion tool.
    • To add the file, login to BambooHR. Go to your team member's profile, and click on the documents tab. Upload the file to the "Experience Factor Worksheets" folder and select the option to share the file. Sharing the file will allow the team member to also view the worksheet.
  5. The most recent feedback cycle can be a helpful tool when distinguishing the experience factor the team member is currently performing at.
    • Feedback reviews should not be about judging, but helping people. We do not want feedback reviews where people are holding back, so these metrics are different as experience factors are used within the compensation tool.
  6. Use the following factors as a guideline for the inputs into the worksheet.
Experience Factor Range
Learning the role 0.9-0.949
Growing in the role 0.95-0.99
Thriving in the role 1.0-1.049
Expert in the role 1.05-1.1

Explanation

For additional guidance on how to determine an experience factor, please see the Experience Factor Training on the Google Drive.

If you have any questions around determining experience factors, please feel free to open an issue or email compensation@domain.

For Backend Engineers

On 2019-06-14, we had an AMA session about experience factor for Backend Engineers. Some of the main manager experiences to come out of this are below. These may not apply to all managers of Backend Engineers; they are common themes from those participating in the AMA.

  1. Because we have had historical movement in requirements for this position (see below), it's hard to compare one year to the next. In CY2019 we expect to be able to use the Engineering Career Framework which will hopefully align expectations going forward.
  2. We do not generally use the experience factor worksheets as part of career development discussions with our reports.
  3. We typically don't update the experience factor throughout the year. Instead, we treat it as a snapshot of where someone is at the point in time where it's needed: either the yearly review, a promotion, or a relocation.
  4. We don't fill out a worksheet for new hires. The experience factor at the time of offer can only be a best-effort estimate. Estimated experience factors can lead to two scenarios if we decide it's too high after the person has been at GitLab for a while:
    1. Individual performance is acceptable for the role, but below their experience factor. In this case, there is no underperformance, but the manager will need to have coaching conversations with the engineer.
    2. Individual performance is not acceptable for the role. This should be handled as any other underperformance would be.

For historical context: in late CY2018, we made a role change from Developer -> Backend Engineer. The experience factor range for existing Backend Engineers was therefore a little different. Instead of the definitions above, Backend Engineers were assessed based on how well they fulfilled the requirements for their position:

Contract factor

Contract Factor distinguishes between employee (1) or contractor (1.17), which can be found on the contract_factors.yml file. A contractor may bear the costs of their own health insurance, social security taxes and so forth, leading to a 17% higher compensation for the contractor. Visit our contracts page to learn more about the different types of contracts we offer.

Exchange Rates

The compensation calculator is updated in January and July with the proper exchange rate, keeping compensation levels in line with local purchasing power.

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. People Operations Analysts will analyze the difference in exchange rates from January to July (or vice versa) and the effect this has on local purchasing power.
  2. Criteria for review, the team member:
    • Is not paid in local currency.
    • Has been at GitLab for six months.
    • Has not opted out.
  3. Only changes of +/- 5% will be processed in each review.
    • Changes must stay within band of the compensation calculator.
  4. People Operations Analysts will confirm by letter of adjustment 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 compensation@domain.

2019-01-01 Oanda Rates

Currency Rate from USD Rate to USD
EUR 0.87979 1.13664
GBP 0.788 1.26904
CAD 1.30955 0.76362
SEK 9.29887 0.10754
PLN 3.74434 0.26707
INR 69.06077 0.01448
AUD 1.42546 0.70153
ILS 3.57245 0.27992
CNY 6.86813 0.1456
RUB 63.25111 0.01581
MXN 19.23077 0.052
JPY 107.99136 0.00926
ZAR 14.1203 0.07082
CZK 22.38138 0.04468
HUF 284.90028 0.00351
NZD 1.48916 0.67152
DKK 6.56814 0.15225
KES 103.30579 0.00968
RON 4.15939 0.24042
CHF 0.97725 1.02328
SGD 1.3538 0.73866
KRW 1162.7907 0.00086

Director Compensation

Directors and up are not part of the compensation calculator because:

  1. The difference between the abilities of different directors are large and we want to ensure a good organizational fit with accurate compensation.
  2. It is not practical and efficient to do a calculation for each director.

GitLab will use market data from Advanced-HR in order to generate offers and conduct a market review for Director level and above. Where market data is not available in the candidate or team member’s location, the People Operations Analyst will provide the Compensation Committee with an output using the location differential in the compensation calculator.

In addition to base compensation, Directors who are not already enrolled in the Sales Compensation Plan or other performance incentive plan are eligible for a 10% bonus of current base salary. The bonus will be paid out semi-annually solely based on Company performance against Plan targets, approved by the Board of Directors. The Director bonus will be pro rated for those team members who start after Jan 1st, or are promoted after July 1st. In addition, the team member must be actively employed by GitLab at the time of payout.

When pulling market data from Advanced-HR, the People Operations Analyst will provide the 50th percentile (or average if not available), in base pay and total target pay. Other data sources such as LinkedIn, Glassdoor, or Payscale may be used when market data is not available to cross check the compensation calculator output.

When hiring for a Director level or above position, the recruiters should tag the People Ops Analyst early on in the process to provide the relevant data.

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.