Candidate Handbook Page

All of our open positions can be found on our jobs page. You can view jobs by department and/or location. Click on a job that interests you and select the “Apply Now” button at the top of the page to fill out an application.

Interested in another role internally? Review internal mobility eligibility here.

If you are a current team member and are interested in applying for a current vacancy, please follow the steps below.

1. Log in to your Greenhouse account
2. If you are a GitLab team member who signed in to Greenhouse you can access the Internal Job Board. If you do not yet have a Greenhouse account, you can activate yours by clicking the Greenhouse tile in Okta.
3. You can also access the internal job board under the “Helpful Links” section. For more information (and screenshots!), feel free to read the Greenhouse help article.
4. Click on the position title that interests you.
5. 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 if the position is open to US applicants.
6. Once you have finished, click “Submit Application” at the bottom.

GitLab is proud to be an equal opportunity workplace and is an affirmative action employer. GitLab’s policies and practices relating to recruitment, employment, career development and advancement, promotion, and retirement are based solely on merit, without regard to all legally protected classes, including, but not limited to: race, color, religion, ancestry, sex (including pregnancy, sexual orientation, or gender identity), national origin, age, citizenship, marital status, gender identity, disability and genetic information (including family medical history), and any other status protected by federal, state or local law. GitLab will not discriminate on the basis of disability or veteran status.

At GitLab, we do not accept solicitations from recruiters, recruiting agencies, headhunters, or outsourcing organizations. If you email us about this type of opportunity, we’ll reply with a link to this paragraph to indicate that we’d like to be removed from the contact list.

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/study 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 the Visa and Sponsorship handbook section 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 team interview stage or later can access our compensation calculator by following applicants sign up.

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.

At GitLab we pride ourselves on ensuring that everyone can contribute. To make certain that everyone’s interview experience is a positive one, we encourage those who require a reasonable accommodation to successfully carry out the interview process, to reach out to ces@gitlab.com. The Candidate Experience team along with Talent Acquisition leadership will work with you to define and accommodate those needs. This could include but is not limited to the following:

• Translation Services
• Use of additional services or assistive technologies
• Assistance in setting up Closed Captioning for interviews

Feel free to send an email to your Recruiter to get a status update on where you are in the interview process.

If you’d like to send a note to the hiring team, please send it to your Recruiter and they will forward it on.

In the event that you are interested in more than one opening, there is no limit on the number of roles you can apply for but keep in mind the following:

1. You will have to complete a full interview process for each role you apply to, so be mindful of the time commitment for each application you submit.
2. Due to capacity, the recruiting team will only process 3 of your applications at a time based on which ones you decide to prioritize. Any other applications outside of the 3 will be processed after the prioritized roles’s interviews are completed.
3. In the effort to be as transparent as possible and avoid sending multiple competing GitLab offers, there will be an added step to the process after your final interview where you will discuss with your recruiter which role you’re interested in before any official offer documents can be sent.
4. If you already have interviewed with us, you can apply for a different role again, but please take note that there may be a cooldown period of 6 months or more if it’s a similar role, depending on the reason for not moving forward which is communicated by the recruiter.

Example of dual Interview process outline

1. Application Process
2. Screening Call
3. Assessment (required for certain roles)
4. Technical Interview (required for certain roles)
5. Team Interviews
6. Discussion with your recruiter on which role you’re interested in
7. References
8. Offer sent for role discussed in step 6 & Background Screen

For internal candidates only (in addition to the above guidelines)

1. If you are interviewing for two roles within the same job family and job grade, the offers will be the same.
2. If you are interviewing for two roles in different job families the offers may be different.

If your application is rejected because you are insufficiently qualified for the role, you are welcome to reapply to the same position once 6 months have passed. If you gain the skills, experience, or knowledge we outlined in our feedback to you, you are welcome to reapply at any time.

If you are reapplying to a role in R&D and have already completed interviews following a technical interview, your technical feedback also remains valid for up to 6 months as long as you are applying to the same job family. The recruitment team will aim to run a reduced interview process in this scenario, however, if you are reapplying outside of the 6 month window or applying to a different job family, you will be required to restart the interview process with us again.

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 you have completed a screening call with the recruiter and are ready to be scheduled for the Team Interview stage, you’ll receive an email requesting availability. To move through this process as quickly as possible, please give us many different days and times spread across at least 2 weeks. This will prevent us from having to reach out again asking for more availability, as some interviewers could be across many different time zones. Sometimes if the interviewer has a schedule that is difficult to fit interviews into, we’ll suggest specific times and dates via your availability link.
2. After receiving your availability, we will compare it to the interviewers’ working hours. If we find a match, we will schedule an interview and send you a link to a Guide and invite in your time zone to download to your computer. If we do not, we will reach back out and work with you to find an alternative. Sometimes there is a very small overlap between time zones, so we appreciate your patience as we identify alternatives!
3. If you need to reschedule, follow the special instructions in your confirmation email if the interview is within 24 hours. You can also email ces@gitlab.com anytime.

Please refer to a specific job listing to see if the position is hiring in the country where you are located. You check our handbook for more in-depth information

Note: In countries with a star (*) hiring is limited to only certain roles

• Life at GitLab
• How We’re Changing the Look of DevOps and Remote Work, One Iteration at a Time
• GitLab’s guide to starting a new remote role
• Life at GitLab Content Library