The GitLab Candidate Handbook is a space for recent applicants and candidates progressing through the interview process. We encourage every prospective job seeker to spend time learning more about the work we do, our culture & values, and what to expect during our hiring process.
The goal of curating these resources is to outline what hiring looks like at GitLab. We share the latest information about our processes and practices to ensure you have the information you need to feel confident during the interview process. The resources referenced here offer guidance on what to expect during each step of the interview process, where we hire, best practices for virtual interviewing, and other useful information.
The interview process consists of the following stages:
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.
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.
Thanks for your interest in GitLab! Our team will reach out if they need more information from you. In the meantime, read about what you can expect during the interview process below.
If your experience is a good fit for the role, we will be in touch soon. Please note that it's not possible for us to respond to every candidate, but we aim to review every application.
If it is determined that you qualify for continued consideration, the assigned Recruiter will conduct a screening call with you. Calls can last anywhere between 30 and 40 minutes (some specialist roles require more time), depending on the conversation. The Recruiter will wait 5 minutes for you to show up to the appointed video call, which is always shared via email. If you do not show up to the interview, or do not reach out in advance to reschedule, you will be classified as a no show and be disqualified. We will unreject when circumstances beyond your control cause you to miss a scheduled call.
You, the recruiter or the hiring manager can terminate the discussion 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.
Depending on the outcome of the call, the talent acquisition team or manager may either reject or move you to the Team Interview stage.
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.
After the Screening Call, a candidate will move into the Team Interviews stage if the Recruiter decides that the candidate is fit for the role. Team Interviews may consist of behavioral, panel and/or technical interviews (certain positions).
Feel free to ask your Recruiter which type of interview you can expect.
We want our interview process to be accessible to everyone. You can inform us of any reasonable adjustments we can make to better accommodate your needs by emailing ces@gitlab.com
at any point in the interview process. Examples of reasonable accommodation include making a change to the application process, providing documents in an alternate format, using a sign language interpreter, or using specialized equipment. As part of our interviewing process, we ask all applicants if they require any type of adjustment or accommodation.
Feel free to send an email to your Recruiter to get a status update on where you are in the interview process.
Yes. You can email your Recruiter or ces@gitlab.com to request your interviewer's email address.
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:
Example of dual Interview process outline
For internal candidates only (in addition to the above guidelines)
If you are invited for an interview with GitLab and you need financial support for your interview, you may be reimbursed for the following:
To initiate the reimbursement process, please email ces@gitlab.com
.
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.
The GitLab team understands the importance of inclusive interviewing, and we strive to ensure our hiring team is well versed in every aspect of diversity, inclusion, and cultural competence. A positive and comfortable candidate experience is our priority.
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.
References will be collected towards the end of the interview stage and they must be checked before an offer is made. The Hiring Manager or hiring team will contact your references. These reference checks will be performed in accordance with the applicable law of the jurisdiction. Where applicable, a reference check can also be used in the final decision for making an offer. The reference check is not the sole factor for a decision to hire or not hire an individual. However, in conjunction with the interview scores and the interview team feedback, all of these factors go into the hiring decision.
Three references will be requested and at least one needs to be a past manager. If you have only had 1 manager, and it is at your current company, it is okay to skip the manager reference (though at least two total references will still be required).
Depending on your location, a background screen will be initiated at the same time as references or once an offer has been extended.
At GitLab, we hire people from all over the world and all walks of life. Diversity, Inclusion & Belonging is one of our core values. As an all-remote company we do face challenges with hiring in certain countries. Each country has unique and complex rules, laws, and regulations, that can affect our ability to conduct business, as well as the employability of the citizens and residents of those countries. It unfortunately affects the employability of the citizens and residents of those countries. We are growing and continuously exploring our hiring capabilities in a variety of geographies. At present we are focusing our hiring in countries where we have entities & PEO's (Professional Employer Organization).
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
Country | Employed through an Entity or PEO |
---|---|
Australia | Entity |
Belgium * | Entity |
Canada | Entity |
Finland * | Entity |
France * | Entity |
Germany | Entity |
Ireland | Entity |
Japan | Entity |
South Korea | Entity |
Netherlands | Entity |
New Zealand * | Entity |
Singapore | Entity |
United Kingdom (England, Scotland, Wales, Northern Ireland) | Entity |
United States | Entity |
United States (Public Sector) | Entity |
Austria * | PEO |
Brazil * | PEO |
Chile * | PEO |
Costa Rica * | PEO |
Denmark * | PEO |
India * | PEO |
Italy * | Entity |
Kenya * | PEO |
Latvia * | PEO |
Luxembourg * | PEO |
Mexico * | PEO |
Philippines * | PEO |
South Africa * | PEO |
Switzerland * | PEO |
Sweden * | PEO |
UAE * | PEO |
Note: In countries with a star (*) hiring is limited to only certain roles
Our mission makes it clear that we believe in a world where everyone can contribute. We make that possible at GitLab by running our operations on our product and staying aligned with our values.
Interested in hearing about life at GitLab straight from our team members? You can hear right from them by checking out our careers page and clicking on the "See How" button under each team member feature or by heading to our Builtin page.