Changes for content/handbook/engineering/workflow/hiring/_index.md: 31 added lines, 9 removed lines.
Original line number
Diff line number
Diff line
@@ -6,27 +6,49 @@ title: Engineering Hiring
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 their team 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.
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.
For more context, please review [a Engineering All-Hands recording (internal)](https://drive.google.com/drive/search?q=title:%222024-04-17%20Sabrina%20on%20hiring%20in%20engineering%22) emphasizing the importance of contributing to hiring efforts within Engineering.
## Hiring practices
## Hiring Practices
Engineering Leadership categorizes each engineering role as either generalist or niche. The category determines which interview process a candidate goes through.
Please reference our [internal hiring repository](https://gitlab.com/gitlab-com/people-group/hiring-processes/-/tree/master/Engineering) for internal best practices and guidelines.
| | 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 |
### R&D New Headcount GHPID Request, Backfill & Transfer Process
If you are unsure how a role is categorized, ask your manager.
#### New Headcount and Backfill Processes
### 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](/handbook/engineering/workflow/hiring/generalist-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](https://gitlab.com/gitlab-com/people-group/hiring-processes/-/tree/master/Engineering) 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](/handbook/engineering/workflow/hiring/generalist-hiring/#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](/handbook/hiring). Please note that we no longer require a Backfill Issue to be created and approved before we can start recruiting. 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/engineering/careers/#mobility-principles) handbook page.
The process for both new headcount and backfill processes can be found in the [Talent Acquisition handbook section](/handbook/hiring). 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/engineering/careers/#mobility-principles) handbook page.
#### Headcount Transfer Process
### 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](/handbook/hiring).
1.**Talent Acquisition**: TA will own the process of creating an Approved Needing Swap issue in the Headcount Project to confirm that both departments are in agreement with the move.
1.**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.
1.**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.
GitLab Engineering has introduced a new "generalist" hiring process. This process hires for GitLab first. Candidates are assessed on fit for GitLab, including level and skill sets first, then matched to a team on hire. This process is being initially tested in India only.
This process applies to roles categorized as generalist. Roles that require specialized domain or team expertise are categorized as niche and use the niche process. Roles are categorized at the VP level. See [Hiring practices](/handbook/engineering/workflow/hiring/#hiring-practices) on the Engineering Hiring page for more on how roles are categorized.
This page is an introduction. The detailed process, interview kits, scoring rubrics, and interviewer training are maintained in [The Loop](https://theloop.gitlab.com/app/home), which is the single source of truth. If this page and The Loop differ, follow The Loop and open a merge request to update this page.
## Why we hire this way
Our previous approach was organized around individual teams. Each team ran its own interview process, often with its own language requirement and a small group of interviewers. This works at low volume, but it does not scale when most hiring is at a few common levels across many teams and regions.
Generalist hiring helps us:
-**Hire at scale without lowering the bar.** One shared bar is applied consistently across teams and regions.
-**Provide a consistent candidate experience.** Every generalist candidate goes through the same stages, designed for speed and accurate signal.
-**Distribute interview load.** Shared, calibrated interviewer pools replace a small number of interviewers on each team.
-**Place strong candidates where they are needed.** A candidate who meets the bar can be matched to any eligible open role, not only the team that opened the requisition.
## How it works
The process has two parts. A shared interview process decides whether to hire and at what level. Team matching then places the candidate.
### Hire and level decision
1.**Recruiter screen.**
1.**CodeSignal take-home.** A take-home assessment sets the technical qualifying bar before any live interviewer time is spent. It replaces the previous merge request (MR) based assessment. Candidates who do not pass exit before live interviews.
1.**Technical interviews 1 and 2.** Two live technical interviews on CodeSignal use shared questions and a shared rubric. Candidates choose their coding language. There is no specific language requirement.
1.**Hiring manager interview.** A behavioral and engineering-judgment interview evaluates how a candidate will operate at GitLab and at the proposed level.
1.**Debrief.** Interviewers record evidence in Greenhouse. When feedback is aligned, the candidate proceeds. Mixed feedback or level disagreement goes to a recruiter-led debrief, and unresolved cases go to the Talent Acquisition (TA) manager to determine next steps.
A candidate with a clear no-hire signal exits at the appropriate stage.
Assessments are organized by craft: Backend, Frontend, and SRE. Each craft has its own CodeSignal assessment and a matching interviewer pool, plus a shared Hiring Manager pool. Interviewers assess for GitLab Engineering as a whole, not for a specific team.
### Team matching and offer
1.**References.** References are checked after a hire decision.
1.**Team match.** TA, in partnership with Engineering Leadership, matches the candidate to an eligible, funded opening. Openings are prioritized based on business priority and teams cannot decline a candidate.
1.**Offer.** An offer is extended only after the team match and headcount are confirmed.
1.**Team call.** An optional 30-minute call when requested by the candidate, where the team shares its mission, success expectations, and working norms, and answers any follow-up questions the candidate might have.
If the candidate declines the offer, TA may choose to resubmit them into the team match process, depending on reason for decline and strength of the candidate.
## Guidance for interviewers
Generalist hiring depends on a large, well-trained interviewer pool. See [Who interviews](/handbook/engineering/workflow/hiring/#who-interviews) for interviewer expectations across Engineering.
When you interview for generalist roles:
-**Score the shared Engineering bar, not stack familiarity.** Score evidence against shared competencies and transferable engineering fundamentals, using the approved rubric for your stage. Do not score an exact match to your team's language, framework, or tools, personal stack preference, or extra team-specific requirements.
-**Keep hire and level separate.** If a candidate meets the bar at a different level, record **Hire** with a suggested level. Do not record **No Hire** only because of a level mismatch.
-**Complete thorough interview feedback.** Complete and thorough feedback ensures we can run this hiring process smoothly and fairly. Please take the time to complete your scorecards thoroughly with evidence-based detail, within 1 business day.
-**Complete the required training** for your interviewer pool, including CodeSignal training. Training is available in [The Loop](https://theloop.gitlab.com/app/home).
-**Keep your calendar up to date.** Pooled scheduling books interviews automatically, so include on-call shifts, time off, meetings, and working hours.