Hiring

1. You are here:
2. Handbook
3. Hiring

On this page

• Hiring pages
• Related to hiring
• Definitions
  • Title
  • Headline
• Equal Employment Opportunity
• Country Hiring Guidelines

Hiring pages

• Greenhouse
• Principles
• Job families
• Vacancies
• Recruiting Alignment
• Interviewing
• Sourcing
• Job offers and post-interview processes
• Recruiting Process Framework
• Recruiting Metrics Process
• Hiring Charts

Potential applicants should refer to the jobs FAQ page.

Related to hiring

• Current vacancies
• Contracts
• Benefits
• Compensation
• Stock options
• Visas
• Background checks
• Onboarding

Definitions

Job families and vacancies are different things and can't be used interchangeably. Hopefully this information will help to clarify the differences.

• A job family is a permanent item; its content is a superset of all vacancies for the job family, and it is created with a merge request. Since it is permanent please don't include text that becomes outdated when we hire someone, for example: "We are seeking".
• A vacancy is a temporary item posted on Greenhouse; its content is a subset of the job family, and it is created by copying parts of a job family based on an issue.

We don't use the word "job" to refer to a job family or vacancy because it is ambiguous.

People at GitLab can be a specialist on one thing and expert in many:

• A specialization is specific to a job family, each team member can have only one, it defined on the relevant job family page. A specialist uses the compensation benchmark of the job family.
• An expertise is not specific to a job family, each team member can have multiple ones, the expertises a team member has are listed on our team page.

The example below shows how we describe what someone does at GitLab:

1. Level: Senior
1. Job family: Developer
1. Specialist: Gitaly specialist
1. Location: EMEA
1. Expert: Reliability, Durability

We use the following terms to refer to a combination of the above:

Title

Level and job family as listed on the contract, for example: Senior Developer

Headline

All parts except expertise, as listed on vacancies, for example: Senior Developer, Gitaly specialist, EMEA

Please use the same order as in the examples above, a few notes:

• Level comes before job family.
• Specialist comes after job family and always includes 'specialist'.
• Location comes after specialization.

We preface a title with "interim" when we're hiring for the position.

Equal Employment Opportunity

Diversity & Inclusion is one of GitLab's core values and GitLab is dedicated to providing equal employment opportunities (EEO) to all team members and candidates for employment without regard to race, color, religion, gender, national origin, age, disability, or genetics. One example of how put this into practice is through sponsorship of diversity events

GitLab complies with all applicable laws governing nondiscrimination in employment. This policy applies to all terms and conditions of employment, including recruiting, hiring, placement, promotion, termination, layoff, recall, transfer, leaves of absence, compensation, and training. GitLab expressly prohibits any form of workplace harassment. Improper interference with the ability of GitLab’s team members to perform their role duties may result in discipline up to and including discharge. If you have any complaints, concerns, or suggestions to do better please contact People Business Partner.

Country Hiring Guidelines

Please go to country hiring guidelines for more information.