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

Contracts

Disclaimer

These agreements are examples of the agreements that we currently use at GitLab. However, the terms and conditions of an employee or contractor’s agreement will vary based on each employee or contractor’s specific circumstances. GitLab reserves the right to amend or change the sample agreements, as well as each employee or contractor’s actual agreement. The samples below are samples only — they are not valid as such and do not replace personalized signed agreements.

How to create a contract

More detailed insructions on our contract and employer agreement processes can be found on the Completing a Contract page.

Available Currencies

The preference is for team members and future team members to be paid in their local currency. However, there may be instances where this is not possible and another currency may be chosen by the team member. This should be discussed and agreed with the Compensation Committee and the People Operations Analyst ahead of creating the appropriate contract (at offer stage for new team members) so a new one can be issued or confirmed by Letter of Adjustment. The effective exchange rate date used in these cases will be either January 1 or July 1 depending on the hire date of the new team member. This is to minimize significant fluctuations to salaries due to currencies that either strengthen or weaken throughout the year. Further details on this review period can be found in the Global Compensation page under Exchange Rates.

GitLab can pay local currency in the following countries:

Country ISO Code
Australia AUD
Bahrain BHD
Canada CAD
China CNY
Czech Republic CZK
Denmark DKK
Ethiopia ETB
Great Britain GBP
Hong Kong HKD
Hungary HUF
India INR
Indonesia IDR
Israel ILS
Japan JPY
Kenya KES
Kuwait KWD
Morocco MAD
Mexico MXN
Netherland Antilles ANG
New Zealand NZD
Norway NOK
Poland PLN
Romania RON
Russia RUB
Saudi-Arabia SAR
Singapore SGD
South Africa ZAR
Sweden SEK
Switzerland CHF
Thailand THB
Tunisia TND
Turkey TRY
United Arab Emirates AED
United States USD

Amended Contracts

The source of truth of all data for a contract or amended contract, should come from an Offer Packet in Greenhouse. This offer packet remains our source of truth of information. Amended contracts must be uploaded to Greenhouse and BambooHR and the People Operations Specialist must be informed.

  1. If the old contract was never active, delete the old contract from BambooHR
  2. Upload the updated contract in 'Contracts and Changes' folder and also in Greenhouse to ensure this is consistent in both systems
  3. Notify the People Operations Specialist of the change in the GitLab Onboarding Tracker

It is essential that the People Operations Specialist is informed of all changes, as they must be updated in BambooHR

Employee Types at GitLab

To ensure the accurate entry of information in BambooHR, we created this table as guidance of what is applicaple in which location. When adding new team member's to BambooHR, please ensure you use this termnology for accurate reporting.

Country Employee Type Hiring Partner PEO (Y/N) Entity Pay Frequency
Australia Employee Not applicable N GitLab PTY LTD 12
Belgium Employee Not applicable N GitLab BV 13.92
Brazil Employee Safeguard Y GitLab BV 12
Canada Employee-PEO and Contractor CXC Y GitLab Inc 12
France Employee-PEO Safeguard Y GitLab BV 12
Germany Employee Not applicable N GitLab GmbH 12
Hungary Employee-PEO and Contractor Safeguard Y GitLab BV 12
India Employee-PEO Lyra Y GitLab BV 12
Ireland Employee-PEO Safeguard Y GitLab BV 12
Italy Employee-PEO Safeguard Y GitLab BV 14
Japan Employee-PEO Safeguard Y GitLab BV 12
Netherlands Employee Not applicable N GitLab BV 12.96
New Zealand Employee-PEO and Contractor CXC Y GitLab BV 12
Poland Contractor-PEO CXC Y GitLab BV 12
Portugal C2C (Company to Company Contractor) Not applicable N GitLab BV 12
Spain Employe-PEO Safeguard Y GitLab BV 12
South Africa Employee-PEO and Contractor Safeguard Y GitLab BV 12
South Korea Employee-PEO Safeguard Y GitLab BV 12
Switzerland Employee-PEO Safeguard Y GitLab BV 12
UK Employee Not applicable N GitLab LTD 12
Ukraine Contractor-PEO CXC Y GitLab BV 12
US Employee Not applicable N GitLab Inc 24
US Federal Employee Not applicable N GitLab Federal LLC 24
Everywhere else Contractor Not applicable N GitLab IT BV 12

Employer of Record Providers

There are multiple options for employers of record in the market. This is not the exact list of providers GitLab uses, but is intended to help the wider community when looking for vendors.

United States Employment Status

Fair Labor Standards Act: Exempt v. Nonexempt Employees

Portugal Employment Status

In Portugal, we can only hire individuals that are hired on a C2C basis. This means, contractors that are hired through our BV Contractor agreement, via an established company in Portugal, with more than one client. Unfortunately at this time, we are not able to hire any team members in sales whatsoever.

Core Team Member Non-Disclosure Agreements

Core team members are an important part of the GitLab community. In order for these individuals to be able to participate in confidential GitLab communications we ask core team members to sign a Non-Disclosure Agreement. This document is reviewed and signed by the CFO.

Letter of Adjustment

When a team member receives any change in compensation and/or title we need to create a Letter of Adjustment instead of staging an entirely new contract. This document is signed by the Compensation & Benefits Manager, the Director, Global People Operations or the Chief People Officer and the team member through either DocuSign (if the adjustment was a transfer/promotion done through Greenhouse) or HelloSign (if the adjustment was not done through Greenhouse, e.g. cost-of-living increases). When a team member applies for and receives a new position through Greenhouse, a Letter of Adjustment is prepared in lieu of a new contract using DocuSign. The Candidate Experience Specialist will prepare the letter. Using the Offer through DocuSign - Letter of Adjustment template in Greenhouse the letter is Cc'd to the Compensation team for processing.

Once the document has been signed, the Candidate Experience Specialist hires the individual in GreenHouse (if applicable) and the signed letter is uploaded into BambooHR under the Contracts and Changes folder on the Documents Tab by the People Operations Analyst. The Compensation team team ensures the information in HRIS and Payroll systems is updated.

Probation Period

Upon joining GitLab some team members (location dependent, see the below table for detail about each location) will have a probationary period of 3 to 9 months. As per the onboarding process a notification in BambooHR would have been created.

Important steps during the Probation Period:

  1. Hiring Manager's are responsible for reviewing performance half-way through the probation period. If any under-performance has been found, this should be communicated to the People Group immediately (either via a People Operations Business Partner or by emailing the People Operations Team).
  2. Towards the end of the Probation Period, the Hiring manager will receive a notification from BambooHR, mentioning the probation period is coming to an end. The People Operations Specialist receives the same notification.
  3. The People Operations Specialist will log into BambooHR and check who the current manager is, and also check the data this person started reporting to this manager. If it was a very recent change, please include the previous manager in the probation period confirmation email.
  4. The People Operations Specialist will email the manager to confirm the probation period was successfully completed and cc peopleops@domain.
  5. Once the Manager has confirmed that they are satisfied with their performance, the People Operations Specialist will send a confirmation email to the team member to confirm their probation period has been completed. Please cc peopleops@domain and the Manager.
  6. The confirmation email from the Manager, should be printed and saved to pdf, and should be saved in BambooHR in the "Contracts & Changes" folder for proof that the probation period was completed.
  7. The People Operations Specialist will update the team member's status to "Active" under the employee status tab in BambooHR, effective to the date after the probabion period expires.
  8. Should their performance not be at a level that their Manager is comfortable with at any time during the probation period, the Manager should reach out to a People Business Partner for further discussion and guidance, right away.

Current Entities and Co-employers with Probationary Periods:

Location Probation period Notice during probation Notice after probation
Australia 6 months 1 week 1 month
Brazil WIP    
China 3 months 3 days  
France 1 - 3 months dependant on reason for exit    
Germany 6 months 2 weeks 4 weeks
Hungary 3 months Immediate effect  
India 6 months 1 week 30 days
Ireland 6 months 1 week  
Italy 6 months for all other employees Not applicable Not applicable
New Zealand WIP    
Netherlands 1 month 1 day 1 month before contract end
Nigeria 6 months 2 weeks  
South Africa 6 months 1 week  
Spain 6 months for skilled workers, 2 months for “other” workers    
UK 3 months 1 week 1 month
USA (Inc) No probation period Not applicable None
USA (Fed) No probation period Not applicable None

Approval for Outside Projects / Activities

Before beginning work on outside projects, second jobs, additional work - paid or unpaid, that could potentially impair your ability to perform your obligations to GitLab or could be deemed a conflict of interest, you must obtain approval in writing from your Manager and further approval from the People Operations team. To submit approval, email your manager to request approval and once given, please send that email to People Operations with details of the project/activities that you would like to work on. Confirmation will usually be in the form of an email and once received will be filed in the team member's BambooHR record under the Contracts and Changes folder on the Documents Tab. Projects involving a 1099 might require additional legal approval which will be coordinated by the People Operations team. For team members employed in the Netherlands confirmation will be given in the form of a Authorization Letter once signed, this will be filed as outlined above.

For any approved outside activity in which the GitLab team-member will use his or her GitLab account, outside activity must be stored in a separate, personal project. All other work completed as part of the GitLab employment or contract should be stored in a GitLab namespace with a GitLab copyright.

PIAA Agreements

GitLab strives to help its Contributors maintain the ability to work on projects that are unrelated to GitLab’s business, including other open source projects. Our PIAA does not grant GitLab any rights in any creations that you may make that are not related to GitLab's business or the work you do for GitLab. That is, you are free to develop those creations without requesting approval in advance from GitLab. We have created an amendment to the PIAA agreement which can be viewed in amendment to PIAA. Please email people operations who will complete and stage the document for signatures. Given that there is necessarily some ambiguity about which projects relate to or don't relate to our business, we have created a process to increase clarity on this issue and encourage outside work by our Contributors. If you're pretty sure that a project you want to work on is unrelated to GitLab's business, but you want GitLab to confirm this ahead of time (or afterwards), you can fill out the Acknowledgement Letter we've provided with a detailed description of the project. GitLab will review your submitted project details, and if we agree that it is not related to our business and does not result from your work for GitLab, we'll sign the letter and return it to you.

Consent Form for GitLab Usability Test

During this usability test I agree to participate in an online session using my computer and telephone. During the session I will be interviewed about the site, asked to find information or complete tasks using the site, asked to complete an online questionnaire about the experience, and I may be video recorded (together, these form the “Materials”).

I understand and consent to the use and release of the Materials by GitLab B.V. (“GitLab”). These materials will likely be made public. I understand that it is the discretion of GitLab to decide whether and how to use the Materials. I relinquish any rights to the Materials and understand the recording may be copied and used by GitLab without further permission. I hereby agree to release, defend, and hold harmless GitLab and its agents or employees, from and against any claims, damages or liability arising from or related to the use of the Materials, including but not limited to libel, defamation, invasion of privacy or right of publicity, infringement of copyright or trademark, misuse, distortion, blurring, alteration, optical illusion or use in composite form, either intentionally or otherwise, that may occur or be produced in taking, processing, reduction or production of the Materials, their publication or distribution.

I have read the above authorization, release, and agreement and I am fully familiar with the contents thereof. This release shall be binding upon me and my heirs, legal representatives, and assigns. I understand that participation is voluntary and I agree to immediately raise any concerns I might have.

If you have any questions after today, please contact {GitLab Contact Person}.

Please sign below to indicate that you have read and understand the information on this form and that any questions you might have about the session have been answered.

Date:{Date}

Please print your name: {Usability Tester Name}

Please sign your name:

Thank you!

We appreciate your participation.