Engineering Hiring

Overview

Hiring is a cornerstone of success for our engineering organization, contributing to our growth and our ability to drive results for our customers. As such, it’s not just a responsibility but fundamental to every engineer’s contribution to GitLab. It should be deeply ingrained in every engineer’s role at GitLab, regardless of their seniority.

By actively participating in recruitment efforts, engineers help shape company culture, elevate technical standards, and ensure a continuous influx of diverse perspectives and skillsets. Contributing to hiring efforts allows GitLab to grow responsibly and affects our collective success within Engineering.

Interviewing is a skill, and takes up a significant amount of time and effort to facilitate and improve upon. We should recognize and appreciate the efforts we take to contribute to scaling the engineering organization.

Hiring practices

Engineering Leadership categorizes each engineering role as either generalist or niche. The category determines which interview process a candidate goes through.

Generalist Niche
Role requires Core engineering skills that transfer across teams, not tied to one team’s language, framework, or tools Specialized domain or team expertise
Candidates are assessed for GitLab Engineering and a level, then matched to a team on hire A specific team and role
Share of roles Most roles are expected to be generalist, including most Backend, Frontend, and SRE roles Roles that truly require specialized expertise
Process Generalist hiring (CodeSignal) Niche hiring (classic MR process)

If you are unsure how a role is categorized, ask your manager.

Generalist hiring

Generalist candidates go through a shared interview process with a CodeSignal take-home, two technical interviews, and a hiring manager interview. Once a hire and level decision is made, Talent Acquisition, in partnership with Engineering Leadership, matches the candidate to an eligible open role. See Generalist Engineering Hiring for why we hire this way and how the process works. This process is being initially tested in India only.

Niche hiring

Niche roles use the classic merge request (MR) based interviewing process, where candidates are assessed for a specific team and role. Please reference our internal hiring repository for internal best practices and guidelines.

Who interviews

Interviewing is part of every engineer’s role. Qualified engineers who have been at GitLab for six months or more are expected to interview.

Interviewers for generalist roles join a shared, calibrated pool for their craft (Backend, Frontend, SRE, or Hiring Manager) and complete the required training. See Guidance for interviewers.

R&D New Headcount GHPID Request, Backfill & Transfer Process

These processes apply to both generalist and niche roles.

New Headcount and Backfill Processes

Budgeted new headcount review occurs on a regular basis across Engineering Leadership, Talent Acquisition, Finance Business Partners (FPB), and People Business Partners (PBP). The process to open a new headcount is Talent Acquisition and Finance-driven, with a focus on ensuring communication, consistency and collaboration between the Engineering and People teams.

The process for both new headcount and backfill processes can be found in the Talent Acquisition handbook section. Backfills are first reviewed on a weekly basis by the CTO and Engineering Leadership and a business decision is made to either open, close or repurpose the position. Your assigned recruiter will be in touch to Kickoff the role once a decision has been made. All backfills default to an Intermediate/Grade 6 level unless there is a business need to re-level, more information can be found in the Engineering Mobility Principles handbook page.

Headcount Transfer Process

  1. Department Heads and PBPs: If two Department Heads agree to move a new headcount between their teams each leader should reach out to their respective PBPs to discuss org structure and/or org planning considerations. PBPs will share relevant information (org design/level/placement) with Finance and Talent Acquisition through the Triad process.
  2. Finance Business Partner: The FBP will create a GHPID for the forecasted role in Adaptive, add the GHPID to the Issue and mark the step as complete, signaling the forecast has been updated. If more information is required, the FPB will reach out to the department leader or PBP before providing a GHPID.
  3. People Business Partner: After a GHPID has been allocated, the PBP will ensure that both the “Cost Center” and “Supervisory Org” dimensions in Workday are updated and accurate.

Generalist Engineering Hiring
An introduction to generalist hiring in Engineering: what it is, why we use it, and how it works at a high level.
Last modified October 20, 2026: Add Generalist Engineering Hiring page (61443de5)