This process is managed by the People Operations Specialist team as the DRI, in partnership with Total Rewards. For any questions not addressed below, please email firstname.lastname@example.org.
If you are considering a move, it is best to discuss this with your manager as soon as possible, always before you are thinking of moving, to understand the impact on compensation or your role at GitLab. Moving to a new location is an exciting adventure to embark upon. However, there are multiple aspects to consider and eligibility to review.
Generally, team members may live or work outside their permanent residence for an aggregate amount of 183 days (6 months) per year. However, the amount does depend on the particular country (or state) and what it considers to be a "resident" for tax purposes, as well as what it considers the tax year. If you are not sure about the aggregate amount allowed by the country or state where you are visiting, you should check with your personal tax advisor. If you believe you or a team member you manage is at risk of exceeding (or has already exceeded) the aggregate amount of 183 days (6 months) (or less in certain countries), you must contact the People group immediately.
If the 6 month timeframe (or other timeframe, as applicable) is at risk of being exceeded or has already been exceeded, please contact the Team Member Relations Specialist team at email@example.com
Team members have the responsibility to ensure their own work eligibility by communicating their location if at risk of exceeding the 6 month timeframe, and managers have a responsibility to their team member and to the business to ensure compliance.
Having team members for 6 months or more working outside of their contractual location poses potential tax liability for both the business and the team member. For this reason, it is of utmost importance to communicate transparently and promptly with the People Team.
The consequences of not communicating to the appropriate group, and/or exceeding the 6-month timeframe allotment outside of an individual's country of employment could result in underperformance management action.
Keep in mind, GitLab retains discretion at all times whether it can accomodate you to continue your role in the new location. In some instances a move will not align to your proposed location, (e.g. a recruiter hired in EMEA to support EMEA would not be approved to move to the US), and in other instances the company may not be able to support a hire in the proposed location. Second, in almost all situations the compensation may change. For an idea about the compensation impact, please check with our Total Rewards team for an estimate. The actual compensation amount will be reviewed and will need approval before relocation can occur.
If you are not changing your permanent location (where you maintain permanent residency), but instead are traveling to different locations over a period of time, you are responsible for maintaining your health insurance, visas, and any other item directly relating to your travel.
Since any short-term stay is your decision and not required by GitLab as part of your role, you will not be eligible to use the Business Accident Travel Policy or submit any expenses related to your travel. If you are hired in a role requiring a time zone alignment, you must still be able to fulfill that requirement.
If your short-term stay is for less than 6 months in a new location, there should be no need to update your address in BambooHR. If you plan on staying in a location for more than 6 months, or are in that location for an aggregate of more than 6 months in a single calendar year, that becomes your residence and you must complete the long-term relocation process described below. In most countries, tax residency is determined by the place where a GitLab Team Member keeps its vital interests. This is the place where you are registered, where your SO and/or dependents live, the place where you work, where you live, where you keep your subscriptions etc.
** Please note that in some jurisdictions, even short term stays can add up to more than 183 days per year and can subject you to payroll tax in the new location. Anything that does not look like a temporary stay can be reviewed as staying somewhere to establish a residence for tax purposes. GitLab cannot provide you individual tax advice but you should always make sure to check with your tax advisor before traveling to any location where you will be performing work for an extended period of time, whether it is more than or less than 183 days.
If you are interested in a possible long-term relocation (defined below), you need to confirm that you would be eligible to work in that location. Except for the Netherlands, GitLab does not provide any form of sponsorship or immigration aid for team members who choose to move to new countries. For more information, please refer to our Visa page. GitLab cannot assist or facilitate a process to help you become eligible to work in a location if you do not already have that eligibility. You are of course free to apply and gain that eligibility if there are steps you can take that do not involve GitLab. Once you are certain that you are eligible to work in your requested Relocation country, you will need to provide proof of eligibility by uploading the proof in the Documents tab of your BambooHR profile. If you move before establishing eligibility to work, but then cannot establish eligibility to work in the new location within the first six months of residency, it may affect your ability to continue your role with GitLab.
A long-term relocation means that you will establish yourself in a new location outside of your current residential area. If you are ending your current residential living arrangement, spending more than six months in one calendar year 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 follow the steps below.
It is at the company's discretion to determine whether it can approve the relocation:
Assuming that relocation is approved, the location factor of the new location may result in an adjustment to compensation. Depending on the location factor and the benefits offered in the particular country, this adjustment may result in an increase or a decrease to compensation. At the onset, this practice sounds harsh when moving to a lower-paid location. 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 policy, but being fair to all team members is not negotiable. It is a value we stand behind and take very seriously.
Note: Assuming your relocation is approved, any applicable changes in compensation will not be effective until your move date (or the date you start working in the new location), which will be listed as the effective date on your new contract.
nonuspayroll @gitlab.com) for visibility on any upcoming changes.
Contracts & Changesfolder. This approval will include the converted salary where applicable in order for the authorised signatory on the contract / adjustment letter to audit against before signing.
Enter all applicable information based on the approval email and the team member's BambooHR profile.
Please note that the effective date of the change is the date of the expected move for the team member. If unsure, please confirm with the team member who is relocating.
Contracts & Changesfolder in BambooHR.
total-rewards@ gitlab.comand Payroll
nonuspayroll@ gitlab.comto notify them of the changes.
Note: If the team member is moving to a different country with a PEO, ensure we coordinate with the new PEO about the change in contract. To be added: Details for CXC
Note: If the team member is moving to the US, employment authorisation (I-9) is required for legal purposes. The People Experience Team will manage the I-9 process.
sent by email to:section must have a personal email address
#people-ops-expprivate slack channel.
Contracts & Changesfolder in BambooHR. -If the team member is relocating to the Netherlands, please see above.
If applicable, create a Mutual Termination Agreement. If unsure if one is needed, check with Director, Legal - Employment at least 30 days (or as soon as possible) before the relocation takes place to confirm whether an MTA is necessary. Stage in DocuSign and send for signature first to the VP, People Ops, Technology & Analytics and subsequently to the team member. Upload the signed document to the team member's
Contracts & Changes folder in BambooHR.
Relocation to [Country Name] [Effective Date]
total-rewards@ gitlab.comand Payroll
nonuspayroll@ gitlab.comto notify them of the changes. Be sure to mention that the Payroll type will be updated closer to the effective date.
I9 Processedfield in BambooHR under the Personal Tab
/pops run removei9 "bambooid"in Slack in order to terminate the team member in LawLogix. This will allow the I-9 to be purged at the correct time.
The steps our People Operations Specialist team uses to support relocation to the Netherlands:
Important: Best practice at GitLab is to take into consideration the entire tenure of the team member at time of relocation to determine the type of contract to create. Due to the usual 1-year tenure at GitLab prior to a team member requesting to relocate and immigrate to the Netherlands, if the team member has been at GitLab more than one year and less than two years, the best practice procedure would be to give the team member one 12-month temporary BV contract, followed by an indefinite contract, with approval from their manager. If the team member has been with GitLab for two or more years at the time they are asking to relocate to the Netherlands, the team member should be issued an indefinite contract, unless this is not supported by their manager and respective PBP.
These are the steps our People Operations Specialist team uses to send contracts to team members relocating to, or moving from Germany. All German contracts require a wet signature. As a placeholder, digital copies and signatures will be sent until our German Legal Counsel sends a copy of the wet signature documents.
Once the contract or Mututal Termination Agreement (MTA) has been created by the People Operations Specialist, next steps are to stage the documents in DocuSign, while also sending the documents to the signatories to have them physically sign and mail them.
At the start of each quarter the People Operations team will share a report with the People Business Partners, this report will include the following information.
My Infoor hover over your job title and click
View My Info
Personaltab, scroll down to the section where your current address appears
Your request will be sent to the Total Rewards team for final review and approval. Until the change is approved, which usually occurs within 24 hours, your address section will be greyed out.