Interviewing at GitLab

We strive to be as expeditious as possible in our hiring process. However, the speed of the process can and does vary. To see our historical and recent trends related to time-to-hire, please view the Time to Offer Accept (Days) chart on the Talent Acquisition Performance Indicators page.

To note, this metric is calculated by taking the number of days it takes from the time a candidate starts the recruitment process to when they accept an offer.

Should you reach out on any social media platform to any GitLab team member with whom you have not previously worked or do not know and request a referral, instead of or in addition to applying to our jobs page, you'll receive the following reply: "Thank you for your interest in GitLab. We would much rather prefer you apply for the position you have in mind directly via our Jobs page. This will ensure the right GitLab team member reviews your profile and replies back to you! Unfortunately at this time, I cannot refer you for the position as we have not had a chance to work together. To ensure we stay inclusive, I also cannot influence your application."

If you are invited for an interview with GitLab and you need financial support for your interview, you may be reimbursed for the following:

• Childcare or adultcare for dependents
• Rental costs associated with laptop or computer if you don't own or have access to one
• Transportation to a facility with internet access if your home does not have reliable internet service
• Meeting room costs in a co-working space if your environment is not conducive to an interview
• Translation services if you are d/Deaf or hard of hearing

To initiate the reimbursement process please email ces@gitlab.com. Additional details found here.

1. Log in to your Greenhouse account to view "My Dashboard".
2. At the top right corner of your dashboard, click "Hi [Name]" and select "Internal Job Board" from the dropdown. You can also access the internal job board under the "Helpful Links" section on your dashboard. For more information (and screenshots!), feel free to read the Greenhouse help article.
3. Click on the position title that interests you!
4. You will be redirected to the vacancy description and application form, where you will be asked to fill out basic personal information, provide your resume, LinkedIn, GitLab username, and/or cover letter, and answer any vacancy-specific application questions, as well as answer a voluntary Equal Employment Opportunity questionnaire. While the EEO questionnaire has US in its title, it's open to all applicants from around the world.
5. Once you have finished, click "Submit Application" at the bottom.

1. Ask the candidate if they require any reasonable accommodation or adjustments in the invite for a screening call (this is built into the email template) as well as during the screening call in case they missed the question in the invite.
2. If the candidate requests an accommodation, add the Interview Adjustments during the screening stage, have them email those requests to ces@gitlab.com which is managed by the Candidate Experience Specialist (CES) team.
3. The CES will ask the candidate if they have any recommendations on how to make the adjustment(s). If none are provided they will work with the Recruiter and ask for assistance from the Absence Management Team at leaves@gitlab.com to arrange adjustment(s).
4. The CES will note the adjustment(s) in the Private Notes section on their profile and tag the upcoming interviewer. Close the issue once accommodations are agreed upon.
5. As long as the candidate is in the interview process, the CES will notify the interview team of the adjustment(s) ahead of the upcoming interviews and ensure all involved in interviewing are equipped to provide a positive experience for the candidate.
6. If extra time is given for the interview as an adjustment, CES will adjust scheduled interviews as necessary.
7. CES will set a follow-up reminder on the candidate's profile to remind the interviewer(s) 24 hours before the interview of the adjustments that are being made to ensure they are top of mind. You do not need to share why the adjustment is being requested but what the required adjustments are.
8. The Recruiter should follow up with the candidate via email after the interview process to ensure they felt the adjustments made were sufficient for them to perform the interview to the best of their ability.

1. Prior to interviewing, the talent acquisition team will identify the most qualified candidates for the vacancy by reviewing Internal Applicants, searching the GitLab Talent Community, reviewing Employee Referrals, and searching through a variety of sources including, but not limited to LinkedIn. The hiring team will also source for candidates that may not be actively looking. There are many factors to consider when reviewing profiles. Some of those factors can be aided through technology within an Applicant Tracking System (ATS), others require human eyes to evaluate the qualifications. There are several posts that reveal suggestions for reviewing profiles that our team may utilize. Greenhouse, Zip Recruiter and The Balance Careers are three examples.
2. The talent acquisition team and/or hiring team does the first round of evaluations by reviewing candidate profiles. This team will refer to the country hiring guidelines before moving candidates forward. Disqualified candidates will be sent a note informing them of the rejection. There are templates in Greenhouse to assist, but messages can be tailored as appropriate. Make sure the message is professional and respectful.
3. Pre-screening Questionnaire: Some candidates will be sent a pre-screening questionnaire relating to the position to complete and return to the sender. The questionnaire and answers are kept within the candidate's Greenhouse profile.
   1. Team members who review the pre-screening questionnaire answers should refer to the private GitLab project that holds guides on how to review each of the questionnaires. Contact your assigned Recruiter for a direct link to the guides. Candidates who receive an assessment are moved to the "Assessment" stage in Greenhouse by a member of the Talent Acquisition team and sent the questionnaire. The talent acquisition team also chooses a member of the hiring team to review the responses once they are submitted.
   2. When a candidate returns their assessment, the talent acquisition team member who sent the assessment and the hiring team member who was chosen to review it will receive a notification. Once a reviewer submits the feedback for the assessment in Greenhouse, the talent acquisition team will be notified.
   3. Candidates that have satisfactory assessment results may be invited to a screening call. Disqualified candidates will be sent a note informing them of the rejection.
4. Screening call:
   1. If the candidate qualifies for continued consideration, one of our recruiters will conduct a screening call using Zoom and scheduling it via Greenhouse.
   2. A member of the employment team will move the candidate to the "Screening" stage in Greenhouse. They will reach out to the candidate to collect their availability and then send out calendar invitations to both the interviewer and candidate.
   3. Our recruiters will do a screening call; depending on the outcome of the call, the talent acquisition team or manager may either reject a candidate or move the candidate to the team interview stages in Greenhouse. Note: A resume is required before scheduling candidates for Customer Success roles.
   4. The recruiter will wait 5 minutes for the candidate to show up to the appointed video call link, which is always shared with the candidate via email. If the candidate does not show up to the interview or reach out in advance to reschedule, the candidate will be classified as a no show and be disqualified. We will unreject a candidate when circumstances beyond their control cause them to miss a scheduled call.
   5. The recruiter, hiring manager, or candidate can terminate the discussion early at any point during the interview if either party determines that it isn’t a fit. Be as transparent and honest as possible and provide feedback.
   6. After the screening call, the recruiter will verify that the candidate is not on any known Denied Party List. If the candidate is on a list, the application process will end.
5. Technical interview (optional): Certain positions also require technical interviews.
6. Behavioral interview: Some roles include a behavioral interview with a team peer or leader. Behavioral interviews may be conducted as panel interviews.
7. Further interviews: All interviewers will assess the candidate's values alignment by asking behavioral questions and scoring the values alignment as part of their feedback form in Greenhouse. Additional interviews would typically follow the reporting lines up to the CEO. For example the technical interview may be conducted by an individual contributor, with subsequent interviews being conducted by the manager, director, executive team member, and then potentially the CEO.
   • **Senior Director and above roles will always have the relevant functional People Business Partner on the interview panel.
   • Interviewers will follow the same no show policy as the recruiters. If a candidate does not show up or reach out to the team, they will be disqualified.
   • All interviewers will complete interviewing training, which will be assigned to them from someone on the talent acquisition team; generally CES. Interview training issues can be found in the People Group Training issue tracker.
   • The individual who created the issue will receive a notification when the issue is closed. The issue should be checked to ensure all tasks are completed. If an issue is closed before all tasks are finished the issue will need to be reopened and tag the assignee that items are missing.
8. References: The hiring manager or the hiring team will contact references for promising candidates. References will be collected towards the end of the interview stage for final candidates, and they must be checked before an offer is made.
   • Three references will be requested, but at least two references need to be completed, and at least one needs to be a past manager. If the candidate has only had 1 manager, and it is at their current company, it is okay to skip the manager reference (though at least two total references will still be required).
   • The talent acquisition team will move the candidate to the "Reference Check" stage in Greenhouse, and email the candidate to request their references' contact details.
   • After the reference checks are completed, the person performing the reference check will input a scorecard in Greenhouse with their findings.
9. At the same time as starting the reference check process, the talent acquisition team will start the background check process.
10. Offer package: After reference calls are completed successfully, the talent acquisition team moves the candidate to the "Offer" stage and submits the offer package in Greenhouse for approval.
11. CEO interviews: The CEO may choose to interview candidates in a last round interview after reviewing the offer package.
12. The recruiter, hiring manager, executive, or CEO should make an offer verbally during a call with the candidate, and it will be followed with an official contract as described in preparing offers and contracts.
13. The talent acquisition team will, if applicable, add language to the contract that states that employment or engagement is contingent on a valid work permit or visa. A start date should factor in that the approval of a new work permit may take several weeks.
    • Note that, when scheduling a start date, People Ops Specialists require at least 4 days notice from the receipt of an executed offer until the GitLab team-member's proposed first day.
14. The manager follows up to ensure that the offer is accepted and that the contract is signed.
15. CES starts the onboarding issue.
16. The hiring manager considers closing the vacancy.

• We will make our best effort so that each candidate's full interview panel has at least one non-male GitLab team-member on it.
• The following teams will always have one non-male team member in the same department as the candidate on the interview panel. We are working to make it so that every team practices our value of diversity, inclusion and belonging in their hiring practices. We are improving, but we aren't there yet. According to our value of iteration, we aren't waiting for a system to be in place for the entire company, but instead are practicing diversity, inclusion and belonging now by listing the teams that can currently commit to this practice. Hiring managers can make MRs to add their team to this list when they are able to meet this requirement.
  • Accounting
  • Business Operations
  • Corporate Marketing
  • Customer Support
  • Demand Generation
  • Development
  • Field Marketing
  • Finance
  • Growth Marketing
  • Marketing Operations
  • People Operations
  • Product Management
  • Quality
  • Talent Acquisition
  • Revenue Marketing
  • Sales Development
  • UX

Example questions include:

1. Why are you interested in GitLab?
2. What are you looking for in your next position?
3. Why did you join and leave your last three positions?
4. What is your experience with X? (for each of the skills listed in the position description)
5. STAR Method questions and simple technical or skills-related questions
6. What is your current location and do you have any plans to relocate? (relevant in context of compensation, country-hiring guidelines, and in case an offer would be made)
7. Do you require visa sponsorship or a work permit to work for GitLab? Or do you require the work permit to be transferred to GitLab? If the answer is yes, we will not be able to proceed, unless you currently hold a work permit in the Netherlands. You can refer to this page for further clarity
8. What is the notice period you would need if you were hired?
9. Is this salary range in line with your expectations? At GitLab, we are committed to paying competitively and equitably. Therefore, we set our offers based on market pay rather than a candidate's pay history. We walk through the Compensation Calculator with each candidate so that we can address any gaps in expectations early on. Only candidates who are in the screening stage or later can access our compensation calculator by following applicants sign up.
10. Do you know how GitLab will employ you in the country you’re based? (As GitLab keeps growing rapidly it is important to share how we can employ people in each country. We should redirect the candidates to the Contracts and International Expansion page and go through it with them.)

At the end of the screening call, the recruiter will tell you what the next steps will be, if any. There should be time for you to ask any questions you may have.

Those on the interview team should prioritize the interview in their schedules. If it means you have to miss an already scheduled or recurring meeting, please consider participating in the interview a priority and reviewing notes from the missed meeting agenda afterwards instead. Hiring an amazing team is critical for GitLab, and how we spend our time shows where our priorities are.

Maintain candidate confidentiality. All candidate names and details are kept confidential within the hiring team to avoid bias or the potential to jeopardize a candidate's current employment as well as to maintain data protection. The only people who should have access to details about candidates are Talent Acquisition, People Ops, the hiring manager(s), approved interviewers or reviewers within that team, the executive of the department, the legal team, the CFO, and the CEO.

• Exceptions to this rule include when an existing team member refers the candidate or when the candidate intentionally reaches out to someone at GitLab. Even then, the team member should know only their name, that they are interested in GitLab, and, if they are a referral, what stage they are in.
• Do not include identifying personal details in your feedback notes for a candidate.
• Anytime you want to discuss a current, past, or potential candidate, please do so privately (whether in a private Slack channel/message, email, or within Greenhouse). If you have access to it, you can also provide the direct Greenhouse link and avoid mentioning names or identifying details.
• Emails from the candidate are synced on our ATS, and for that reason, the entire hiring team for that position has access to it. Remember to ensure any sensitive information is marked as secret/private in the candidate profile.

Remember to inform candidates about what stage they are in. For example, if in the hiring process for the particular position / team you've agreed that there will be four stages, be sure to inform the candidate of where they are in the process during each call / stage. To better manage candidates’ expectations, at the end of the interview, let them know what stage they are in as well as what the next step/stage will be if they do pass this interview. Considering we are speaking with other candidates, they can expect to hear back within a couple of days. Some brief feedback from the previous stage can also be included to help the candidate gauge their progress. If there will be additional or fewer stages than expected, be sure to let the candidate know so they are aware of where they are in the process.

The process can differ from team to team and from position to position. If a candidate submits a resume to a particular open position and is being considered for another open position, send a short note to update the candidate and get their approval as well as to inform them that their process may be slightly different than previously expected or delayed. If the roles are on different teams, the candidate will ideally only move forward with one, depending on their interests and qualifications. If the candidate is being rejected for one or all of the positions they applied for, they will be notified of which vacancies they are being rejected for.

• If at some point during the interview process it is uncovered that a candidate is better suited for another open position the interviewer should @ mention the Recruiter assigned to the candidate and provide feedback regarding what other position(s) the candidate should be considered for. The Recruiter will then loop in the new Recruiter(s) and Hiring Manager(s) for the said position(s) and if there is interest complete a warm handoff of the candidate to the new Recruiter(s).

Talent Acquisition will schedule the next person in the process. Someone on the talent acquisition team will move candidates forward to the next person in the interview plan if the candidate has received positive feedback. Interviews should be scheduled with a minimum of 48 hours (two business calendar days) notice in order for the GitLab interviewer to review their schedule and fully prepare so that both the interviewer and the candidate get the most out of the experience. We do allow exceptions to be made when the hiring manager would like to expedite the interview plan. If the 48 hours cannot be met, CES will reach out to the interviewer directly to coordinate.

Communicate urgency where necessary. Recruiters, CES team members, and interview panelists should inform the Hiring Manager when a candidate shares they have other interview processes at the offer, or other similarly late stages. We will do our best to expedite a candidate's interview process while continuing to follow the necessary steps in the hiring plan.

Compensation is discussed at start and end but not in between. Compensation expectations are asked about during the screening call. If the expectations seem unworkable to the manager or recruiter (based on what had been approved by the compensation committee at the creation of the vacancy), then the recruiter can send a note to the candidate explaining that salary expectations are too far apart, but they should also ask how flexible the candidate is and if they would consider adjusting their expectations. If expectations are aligned, then the topic of compensation should not re-surface until an offer is discussed internally. Following this guideline avoids conflating technical and team interviews with contract discussions and keeps the process flowing smoothly.

If the manager has a question about compensation, please ping the People Ops Analyst for review. If the question needs to be escalated, the People Ops Analyst will add the Chief People Officer to the conversation.

GitLab Employment and Contractor Agreements are internal-only. If an applicant requests to see one or more of our contracts from our Internal-only Employment and Contractor Agreements section, please advise them that we are unable to share them with the applicant. Talent Acquisition and CES may point the applicant to the relevant Benefits handbook section or pages, or direct any specific questions to the relevant internal teams, be it Legal, Total Rewards, or People Ops.

An approval team authorizes all offers. The manager proposes a suggestion for an offer (including bonus structure if applicable, etc.) as a private comment in Greenhouse and informs the talent acquisition team on its details depending on what is applicable. The talent acquisition team will create an offer package to present to an approval chain consisting of the People Business Partner, executive of the division, and Chief People Officer for approval. Verbal offers should not be extended to the candidate until the offer is approved. The CEO may choose to interview the candidate, and any offers given before the CEO's approval are premature.

1. At any time during the hiring process the candidate can be rejected.
2. Everyone who interviews a candidate must complete a scorecard and are required to input pros and cons as well as an overall recommendation.
3. We will not cancel an interview within less than 24 hours' notice if the candidate is being rejected. The recruiter will notify the candidate that the candidate is no longer in consideration for the role and present them with the option to continue with the scheduled interview slot. The interviewer will not discuss the feedback that led to the decline. The interviewer will frame the conversation as an opportunity to answer general questions about life at GitLab and future opportunities in our team.
   • If the candidate's interview is outside 24 hours, the interview will be deleted in Greenhouse before the candidate is rejected and notified.
4. The candidate should always be notified if they've been rejected, and the talent acquisition team is primarily responsible for declining the candidate. Please note that due to a variety of reasons, including high applicant volumes and other factors, it may not be possible for the talent acquisition team to provide detailed decline feedback.
5. If people argue with the feedback that we provided:
   • Do not argue with or acknowledge the validity of the contents of the feedback.
   • Share their feedback with the people involved in the interviews and the decision.
   • Template text: "I've shared your feedback with the people involved in the interviews and the decision. We do not expect to revert the decision based on your feedback. In our hiring process we tend to err on the side of being too cautious. We would rather reject someone by mistake than hire someone by mistake since a wrong hire is much more disruptive. Organizations can reject people with great potential (https://www.adweek.com/digital/whatsapp-facebook-twitter-brian-acton/) so please don't be discouraged from seeking a great job."
6. The talent acquisition team may send out an inquiry to candidates to gather our own feedback after they have exited the hiring process.
   • The talent acquisition team will review all feedback and use it to improve the hiring process.

As an all-remote, global company, GitLab gives all team members the flexibility to determine their time away from work, including the holidays they observe. There will likely be holidays that our candidates observe that a recruiter, hiring manager, or CES may not. If there's a time during the year when a significant portion of the company will be taking time off, we'll be sure to send a communication to all active candidates to let them know of a possible delay in communication. Please note that not every member of the team will be observing that holiday, so you may still receive emails from them.

1. Once a candidate has completed a screening call with the recruiter, the candidates are moved onto the Team Interview stage. This is the most difficult stage to schedule for as it involves many different people most of the time spread all across the world.
2. The candidate will receive an email from either the Recruiter or CES requesting availability to schedule interviews. The best thing a candidate can do is to give us many different days and times spread across at least 2 weeks. This will prevent us having to reach out again asking for more availability. Note Sometimes if the interviewer has a schedule that is difficult to fit interviews into, there will already be suggested times for the interview to take place in the availability link.
3. After receiving the candidate's availability, CES will compare it to the interviewers working hours. This is why it is very important for candidates to give multiple times and days for availability as sometimes we are only able to find 1-2 hours that overlap timezones.
4. Once a good time is found on the interviewer's calendar, CES will send the interviewer an invite via the calendar and the candidate an interview confirmation via email, all using our ATS; Greenhouse.
5. There is one section of the interview confirmation email the candidate should pay extra close attention to, the timezone. Greenhouse, our ATS, defaults the timezone in the interview confirmation to the timezone the CES team member is located in. However, there will always be an attached calendar invite that shows the interview time in the candidates home timezone so they can add it to their own calendar.
6. If the interviewer or candidate should need to reschedule, they should email their CES, or follow the special instructions in the confirmation email if the interview is within 24 hours.