- You are here:
- Developer, Security
Top 10 reasons to work for GitLab:
- Work with helpful, kind, motivated, and talented people.
- Work remote so you have no commute and are free to travel and move.
- Have flexible work hours so you are there for other people and free to plan the day how you like.
- Everyone works remote, but you don't feel remote. We don't have a head office, so you're not in a satellite office.
- Work on open source software so you can interact with a large community and can show your work.
- Work on a product you use every day: we drink our own wine.
- Work on a product used by lots of people that care about what you do.
- As a company we contribute more than we take, most of our work is released as the open source GitLab CE.
- Focused on results, not on long hours, so that you can have a life and don't burn out.
- Open internal processes: know what you're getting in to and be assured we're thoughtful and effective.
- You can reason about software, algorithms, and performance from a high level
- You are passionate about open source
- You have worked on a production-level Ruby application, preferably using Rails. (This is a strict requirement)
- You know how to write your own Ruby gem using TDD techniques
- Strong written communication skills
- Experience with Docker, Nginx, Go, and Linux system administration a plus
- Experience with online community development a plus
- Self-motivated and have strong organizational skills
- You share our values, and work in accordance with those values.
- A technical interview is part of the hiring process for this position.
For this position, a significant amount of experience with Ruby is a strict requirement.
We would love to hire all great backend developers, regardless of the language they have most experience with, but at this point we are looking for developers who can get up and running within the GitLab code base very quickly and without requiring much training, which limits us to developers with a large amount of existing experience with Ruby, and preferably Rails too.
For a time, we also considered applicants with little or no Ruby and Rails experience for this position, because we realize that programming skills are to a large extent transferable between programming languages, but we are not currently doing that anymore for the reasons described in the merge request that removed the section from this listing that described that policy.
If you think you would be an asset to our engineering team regardless, please see if another position better fits your experiences and interests, or apply using the Open Application.
If you would still prefer to join the backend development team as a Ruby developer, please consider contributing to the open-source GitLab Community Edition. We frequently hire people from the community who have shown through contributions that they have the skills that we are looking for, even if they didn’t have much previous experience with those technologies, and we would gladly review those contributions.
A Security Specialist is a Developer who focuses on ensuring that GitLab and associated applications are as secure as possible. The Security Specialist works in close collaboration with the Security Lead.
The basics of GitLab development can be found in the developer onboarding document.
The handbook details the complete GitLab Workflow.
Applicants for this position can expect the hiring process to follow the order below. Please keep in mind that applicants can be declined from the position at any stage of the process. To learn more about someone who may be conducting the interview, find her/his job title on our team page.
- Selected candidates will be invited to schedule a 30min screening call with our Global Recruiters
- A technical interview is part of the process
- Next, candidates will be invited to schedule a first interview with an Engineering Lead
- Candidates will then be invited to schedule an interview with the Head of Product
- Candidates will be invited to schedule a third interview with our VP of Engineering
- Finally, candidates will interview with our CEO
- Successful candidates will subsequently be made an offer via email
Additional details about our process can be found on our hiring page.
Avoid the confidence gap; you do not have to match all the listed requirements exactly to apply. Our hiring process is described in more detail in our hiring handbook.
Work remotely from anywhere in the world. Curious to see what that looks like? Check out our remote manifesto.