GitLab normally prefers to hire full-time permanent engineers for its development teams using entities and [PEOs](/handbook/people-group/employment-solutions/#peo-professional-employer-organization-employer-of-record-and-not-a-gitlab-entity-or-branch). However, there are times when teams will have a need to hire temporary contingent workers to help with execution.
GitLab normally prefers to hire full-time permanent engineers for its development teams using entities and PEOs. However, there are times when teams will have a need to hire temporary contingent workers to help with execution.
These are a few examples of situations where a contingent workers may be required:
@@ -8,22 +8,13 @@ The DRI for all Employment Solutions is the [Employment Solutions Partner](/job-
## Country Hiring Guidelines
The GitLab team has members in countries and regions all over the world and from all walks of life. Diversity, Inclusion & Belonging is one of our [core values](/handbook/values/). Maintaining operations in a large number of countries, some of which have complex rules, laws, and regulations, can affect our ability to conduct business efficiently. Unfortunately, this affects the employability of the citizens and residents of those countries. We are continuously exploring our hiring capabilities in a variety of geographies.
GitLab has team members in countries and regions all over the world and from all walks of life. Diversity, Inclusion & Belonging is one of our [core values](/handbook/values/). Maintaining operations in a large number of countries, some of which have complex rules, laws, and regulations, can affect our ability to conduct business efficiently. Unfortunately, this affects the employability of the citizens and residents of those countries. We explore hiring in new locations when business needs require and where we can provide a consistent and fully supported team member experience.
Some roles may carry specific location-based eligibility requirements. Our Talent Acquisition team can help answer any questions applicants may have about location after starting the recruiting process.
GitLab hires in countries where we have an entity that does not carry any hiring restrictions. We focus on an approach that delivers three key benefits:
All of our roles are remote, however, some roles may carry specific location-based eligibility requirements. Our Talent Acquisition team can help answer any questions applicants may have about location after starting the recruiting process.
In the past GitLab would hire in any country except those we had already determined were not feasible due to certain restrictions. At present, we are focussing our hiring in countries where we have an [entity](/handbook/people-group/employment-solutions/#gitlab-entities-and-branches) or a [PEO](/handbook/people-group/employment-solutions/#peo-professional-employer-organization-employer-of-record-and-not-a-gitlab-entity-or-branch), that do not carry any hiring restrictions.
Compared with our former approach of hiring contractors in any country and later planning to implement an entity/PEO, we see four instant benefits with this approach:
- Delivers consistent global team member experience (e.g. payroll, benefits, support, etc.)
- Reduces operational complexity
- Provides a stable footprint and makes it easier to grow in particular countries
- Closes the gap in building a scalable employment solution for 100% of team members
We can consider an exception to hire outside of these countries through the use of a PEO for future team members when supported by business needs, on a case-by-case basis. This approach enables a scalable solution from the onset and allows us to continue to hire diverse global talent whilst providing a consistent and positive team member experience. This approach will require a formal business need justification and will be addressed on a case-by-case basis.
Countries that do not have an entity/scalable PEO will be converted as part of our [country conversion process](/handbook/people-group/employment-solutions/#country-conversions).
- Deliver consistent global team member experience (e.g. payroll, benefits, support, etc.)
- Reduce operational complexity
- Provide a stable footprint and make it easier to grow in particular countries
## Team Member Types at GitLab
@@ -42,7 +33,7 @@ Countries that do not have an entity/scalable PEO will be converted as part of o
## Team Member Types by Country
GitLab has a few different team member types. The following tables each show how we hire and scale around the world, where we have entities, where we use Professional Employer Organisations, and how we add new countries to our list.
GitLab has a few different team member types. The following table shows the countries where we directly employ team members through a GitLab entity. For questions about PEO locations or other employment arrangements, please reach out to the Employment Solutions Partner.
To ensure the accurate entry of information in Workday, we created this table as guidance of what is applicable in which location. When adding new team members to Workday, please ensure you use this terminology for accurate reporting.
@@ -73,64 +64,15 @@ Note: In countries with a star (*) hiring is limited to only certain roles.
| United States | Employee | GitLab Inc | 24 | GitLab Payroll Dept | Y |
| United States (Public Sector) | Employee | GitLab Federal LLC | 24 | GitLab Payroll Dept | Y |
### PEO (Professional Employer Organization/ Employer of Record and not a GitLab entity or Branch)
This table reflects the countries in which we utilize PEO's. These countries are open for hiring but there may be times where we pause, close or are unable to hire in a given location due to the limitations or requirements of a particular role, or as a result of key projects or business needs. Our Talent Acquisition team can help answer any questions applicants may have about location once the recruiting process has begun:
Note: In countries with a star (*) hiring is limited to only certain roles.
### Team Members Hired as Contractors via our GitLab Services Inc Entity
| Country | Agreement Type(s) | Hiring Partner | Entity to Invoice (for AP only) | Pay Frequency | Paid By | Currency paid in | Workday Profile (Y/N) | Scalable PEO (Y/N) | Open for hiring (Y/N) |
| Austria * | Employed via a PEO | Global Expansion | GitLab Services Inc | 14 | PEO | EUR | Y | Y | Y |
| Chile * | Employed via a PEO | Global Expansion | GitLab Services Inc | 12 | PEO | CLP | Y | Y | Y |
| Costa Rica * | Employed via a PEO | Global Expansion | GitLab Services Inc | 12 | PEO | USD | Y | Y | Y |
| Denmark * | Employed via a PEO | Global Expansion | GitLab Services Inc | 12 | PEO | DKK | Y | Y | N |
| Kenya * | Employed via a PEO | Global Expansion | GitLab Services Inc | 12 | PEO | KES | Y | Y | Y |
| Latvia * | Employed via a PEO | Global Expansion | GitLab Services Inc | 12 | PEO | EUR | Y | Y | Y |
| Luxembourg * | Employed via a PEO | Remote.com | GitLab Services Inc | 12 | PEO | EUR | Y | Y | Y |
| Mexico * | Employed via a PEO | Global Expansion | GitLab Services Inc | 12 | PEO | MXN | Y | Y | Y |
| Philippines * | Employed via a PEO | Global Expansion | GitLab Services Inc | 24 | PEO | PHP | Y | Y | Y |
| South Africa * | Employed via a PEO | Global Expansion | GitLab Services Inc | 12 | PEO | ZAR | Y | Y | Y |
| Switzerland * | Employed via a PEO | Remote.com | GitLab Services Inc | 12 | PEO | CHF | Y | Y | Y |
| Sweden * | Employed via a PEO | Remote.com | GitLab Services Inc | 12 | PEO | SEK | Y | Y | Y |
This table reflects the countries in which we have utilized PEO's but are currently NOT open for hiring.
There are no current plans to open these countries for future hiring. If we do open for hiring, it will be based on business needs.
| Country | Agreement Type(s) | Hiring Partner | Entity to invoice (for AP only) | Pay Frequency | Paid By | Currency Paid in | Workday Profile (Y/N) | Employer of Record | Open for hiring (Y/N) |
| Armenia | Contracted via a PEO | CXC | GitLab IT BV | 12 | PEO | USD | Y | N | N |
| Czech Republic | Contracted via a PEO | CXC | GitLab IT BV | 12 | PEO | CZK | Y | N | N |
| Greece | Contracted via a PEO | CXC | GitLab IT BV | 12 | PEO | EUR | Y | N | N |
| Poland | Contracted via a PEO | CXC | GitLab IT BV | 12 | PEO | PLN, EUR, USD | Y | N | N |
| Portugal | Contracted via a PEO | CXC | GitLab IT BV | 12 | PEO | EUR | Y | N | N |
| Romania | Contracted via a PEO | CXC | GitLab IT BV | 12 | PEO | EUR, USD | Y | N | N |
| Serbia | Contracted via a PEO | CXC | GitLab IT BV | 12 | PEO | EUR | Y | N | N |
| Slovenia | Contracted via a PEO | CXC | GitLab IT BV | 12 | PEO | EUR | Y | N | N |
| Turkey | Contracted via a PEO | CXC | GitLab IT BV | 12 | PEO | USD | Y | N | N |
| Ukraine | Contracted via a PEO | CXC | GitLab IT BV | 12 | PEO | USD, EUR | Y | N | N |
| Hungary | Employed via a PEO | Remote.com | GitLab IT BV | 12 | PEO | HUF | Y | Y | N |
| Denmark * | Employed via a PEO | Remote.com | GitLab IT BV | 12 | PEO | DKK | Y | Y | N |
| Brazil * | Employed via a PEO | Remote.com | GitLab IT BV | 12 | PEO | BRL | Y | Y | N |
| UAE * | Employed via a PEO | Global Expansion | GitLab Services Inc | 12 | PEO | AED | Y | Y | N |
| Italy * | Employed via a PEO | Remote.com | GitLab IT BV | 14 | PEO | EUR | Y | Y | N |
Contact information for our PEO representatives is found in the `Entity & PEO Contacts` note in the PeopleOps vault in 1Password. If a team member, manager or PBP has a question relating to a PEO, their process, or any related procedure for a PEO-employed team member, please reach out to the Employment Solutions Partner (@hdevlin) who will liaise and find a solution with the PEO's support.
### Team Members Hired as Contractors via our GitLab IT BV Entity
Where we do not have an entity or a PEO, team members contract with our GitLab IT BV entity as independent or C2C contractors. We are not currently hiring in locations that do not have an entity or PEO. Some PEO's are not open for hiring, see table above for details.
Where we do not have an entity or a PEO, team members contract with our GitLab Services Inc entity as independent or C2C contractors. We are not currently hiring in locations that do not have an entity or PEO.
## International Expansion
### Country Conversions
As GitLab continues to scale, we will be converting all team members to an employment scalable solution. Team members are hired in the following ways:
- Contractor through a PEO (Professional Employer Organization with a local presence)
- Employees through a PEO (Professional Employer Organization)
- GitLab entity
As GitLab continues to scale, country conversions may occur from time to time based on business needs and our location strategy. Any conversions will be managed by the Employment Solutions Team.
The Employment Solutions Partner is responsible for managing the country conversion processes outlined [here](https://gitlab.com/gitlab-com/people-group/people-operations/General/-/blob/master/.gitlab/issue_templates/country_conversions.md).
### Compensation Review for Country Conversions
@@ -145,44 +87,8 @@ For roles directly relating to Research and Development in the Netherlands, GitL
#### Organizing WBSO
**Applications**
As of 2019 GitLab must submit three applications each year and the deadlines for those are as follows:
1.**31 March 2019**, for the May - August 2019 period (Product Manager for Create Features)
1.**31 August 2019**, for the September - December 2019 period (Product Manager for Gitaly)
1.**30 November 2019**, for the January - April 2020 period (Product Manager for Geo Features)
There is a [translated English version of the application template](https://docs.google.com/document/d/15B1VDL-N-FyLe84mPAMeJnSKjNouaTcNqXeKxfskskg/edit) located in the WBSO folder on the Google Drive. The applications should be completed by a Product Manager, responsible for features or a service within GitLab, who can detail the technical issues that a particular feature will solve. Assistance on completing the application can also be sought from the WBSO consultant (based in the Netherlands). The contact details for the consultant can be found in a secure note in the People Ops 1Password vault called WBSO Consultant. The People Operations Team member will assist with co-ordinating this process. It is currently owned by Finance.
**Hour Tracker**
Each year a spreadsheet with the project details and hours logged against the work done on the project(s) will need to be created. This is for the entire year. The current hour tracker is located in the WBSO folder on the Google Drive, and shared only with the developers that need to log their hours (located in the Netherlands), Total Rewards Analysts, Finance and the WBSO consultant. Once the projects have been completed for the year, the WBSO consultant will submit the hours and project details to claim the R&D grant from the [RVO](https://english.rvo.nl/). The WBSO consultant will contact Total Rewards Analysts should they have any queries.
## Engineering internships
Engineering is currently hiring interns. The [engineering internships handbook page](/handbook/hiring/) has more information on this.
Interships require a fixed term contract during the internship, which is not possible in all countries.
The countries where we currently can hire interns are:
@@ -485,7 +485,6 @@ This section describes the approval chain after the People Business Partner subm
#### Job Change Letter
1. For [GitLab entities](/handbook/people-group/employment-solutions/#gitlab-entities-and-branches) and [Independent Contractors](/handbook/people-group/employment-solutions/#team-members-hired-as-contractors-via-our-gitlab-it-bv-entity) a job change letter may be required, as per the steps mentioned below. If the team member is employed by a PEO, notify the applicable [PEO](/handbook/people-group/employment-solutions/#peo-professional-employer-organization-employer-of-record-and-not-a-gitlab-entity-or-branch) either by email or for remote.com via their dashboard. See the People Operations 1password vault for contact details.
1. Review the [Signature requirements per country](/handbook/hiring) and process the job change letter accordingly. Please note not all entities and country locations require Job Change Letters (for example team members in the US will not receive a Job Change Letter).
1. Make a copy of the applicable Job Change Letter template and enter all applicable information based on the Workday request and add the applicable [Signatory](/handbook/hiring) or [Company Signature Stamp](https://docs.google.com/document/d/1RWkI7zuFIUkW_sh1TmYii6e8zNOmz9USUoEr1wBIBpQ/edit?usp=sharing). The effective date is as follows:
- For sales personnel with a variable change, the effective date is always the 1st of the month regardless of their entity.
@@ -185,7 +185,7 @@ The contract phase is unique based upon the team member's relocation. The differ
1. If applicable:
- A [Mutual Termination Agreement](https://docs.google.com/document/d/1MJCWQupiqfU7rUk99qowHuxd64OPIHKfD05gLlfs7K8/edit) is needed, if the team member is relocating from IT BV.
- A [Side letter Relocation - Transfer from one entity to another](https://docs.google.com/document/d/1UesnGAH1y0MMgWU37RRX2DuSP14mDLff/edit) is needed if the team member is relocating from one entity to another.
- Inform the current PEO of the relocation effective date. See People Operations 1password vault for contact details. A resignation email (within notice period) from the team member to their current PEO is also required, if the team member is relocating away from a location with [PEO Employment](/handbook/people-group/employment-solutions/#peo-professional-employer-organization-employer-of-record-and-not-a-gitlab-entity-or-branch).
- Inform the current PEO of the relocation effective date. See People Operations 1password vault for contact details. A resignation email (within notice period) from the team member to their current PEO is also required, if the team member is relocating away from a location with PEO Employment.
1. Ping a People Operations Team member for auditing in the private slack channel. The person auditing should make a private comment in the HelpLab case confirming the audit.
1. Stage the contract in DocuSign and send for signature first to the GitLab signatory and subsequently to the team member.
- In the event that the team member requests any changes to the contract, once approved and updated, send an email to the team member with the breakdown of the applicable changes once the contract has been sent for signature via DocuSign.
