At the core of our team’s vision, mission, and strategy is our ability to impact GitLab’s overarching mission: to make it so that everyone can contribute. When everyone can contribute, users become contributors and we greatly increase the rate of innovation.
As a Talent Acquisition team, we have an outsized impact on GitLab’s ability to make this mission a reality, by connecting top talent to profound careers from wherever they are in a truly distributed, remote workforce.
To create globally inclusive access to opportunities so that everyone can contribute.
It is the Talent Acquisition Team’s mission to predictably build distributed, representative teams that enable our vision of creating globally inclusive access to opportunities so that everyone can contribute.
As we set out over the next decade to achieve this vision, we will continue to rely on core guiding principles to define how we build toward the future.
We strive to be as transparent as possible, but these sections are only available for our GitLab team members. FY24 TA Strategy
Job: A job refers to the job title (ex: Customer Support Specialist). This will also be what appears on external job boards. In the case there are multiple positions open that are the same, and we only want to list once, we can have multiple 'openings' (see next section) opened within one 'Job'. Each job will have a unique identifier called a Requisition ID (example- 1001).
Opening: A job can have multiple openings attached to it (ex: you are hiring 3 Customer Support Specialists. You would then have 1 ‘Job’ and 3 ‘openings’ against that job). A job can have multiple openings against it, but an opening can not be associated with multiple jobs. Each opening will have a unique identifier called an Opening ID (example- 1001-1, 1001-2, 1001-3).
GHPiD: GHP ID is the link between Adaptive (what we use to track our operating plan) and Greenhouse (our ATS). A GHP ID has a one to one relationship with an Opening ID. It is the key interlock between our hiring plans and our Talent Acquisition activity. This is a custom field in Greenhouse.
Please find pages for potential and active applicants below.
</details>
There are no perfect or required ways to set up your Greenhouse notifications, but these are some of our recommendations.
Stay tuned!
Remote.com: remote.com onboarding timeline
Country | Working days |
---|---|
Austria | 9 |
Denmark | 9 |
Hungary | 9 |
Italy | 9 |
Mexico | 3 |
South Africa | 5 |
Spain | 7 |
Switzerland | 7 |
Global Upside:
Country | Working days |
---|---|
India | 7 business days |
Philippines | 17 ( Including 7 business days for pre hire medical test and 3 business days for social registration) |
Kenya | 7 business days |
Costa Rica | 12 ( Including 5 business days for social registration) |
Latvia | 8 ( Including 1 business day for social registration) |
Chile | 12 ( Including 5 business days for social registration) |
Papaya
Processing for the United Arab Emirates could take up to a month, so we recommend start dates at least 6 weeks after the offer is generated.