Backend Engineers

Backend Engineering Roles at GitLab

Backend Engineers at GitLab work on our product. This includes both the open source version of GitLab, the enterprise editions, and the GitLab.com service as well. They work with peers on teams dedicated to areas of the product. They work together with product managers, designers, and frontend developers to solve common goals.

Unless otherwise specified, all Backend Engineering roles at GitLab share the following requirements and responsibilities:

Requirements

Nice-to-haves

Responsibilities


Unless otherwise specified below, please note that a significant amount of experience with Ruby is a strict requirement.

We would love to hire all great backend engineers, regardless of the language they have most experience with, but at this point we are looking for engineers who can get up and running within the GitLab code base very quickly and without requiring much training, which limits us to engineers with a large amount of existing experience with Ruby, and preferably Rails too.

For a time, we also considered candidates 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.


Levels

Read more about levels at GitLab here.

Junior Backend Engineer

Junior Backend Engineers share the same requirements and responsibilities outlined above, but typically join with less or alternate experience than a typical Backend Engineers.

Senior Backend Engineer

The Senior Backend Engineer role extends the Backend Engineer role.

Responsibilities


A Senior Backend Engineer may want to pursue the engineering management track at this point. See Engineering Career Development for more detail.

Note: Staff and above positions at GitLab are more of a role than just a "level". We prefer to bring people in as Senior and let the team elevate them to Staff due to an outstanding work history within GitLab.


Staff Backend Engineer

The Staff Backend Engineer role extends the Senior Backend Engineer role.

Responsibilities

Distinguished Backend Engineer

The Distinguished Backend Engineer role extends the Staff Backend Engineer role.

Engineering Fellow

The Engineering Fellow role extends the Distinguished Backend Engineer role.

Engineering Management Roles at GitLab

Managers in the engineering department at GitLab see the team as their product. While they are technically credible and know the details of what backend engineers work on, their time is spent hiring a world-class team and putting them in the best position to succeed. They own the delivery of product commitments and are always looking to improve productivity. They must also coordinate across departments to accomplish collaborative goals.

Engineering Manager

Unless otherwise specified below, all Engineering Manager roles at GitLab share the following requirements and responsibilities:

Responsibilities

Requirements

Nice-to-haves

Hiring Process

Candidates for this position can generally expect the hiring process to follow the order below. Note that as candidates indicate preference or aptitude for one or more specialties, the hiring process will be adjusted to suit. Please keep in mind that candidates 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.

Additional details about our process can be found on our hiring page.

Director of Engineering

The Director of Engineering role extends the Engineering Manager role.

The Director of Engineering, Backend at GitLab manages multiple backend teams in the product development organization. They see their teams as their product. They are capable of managing multiple teams and projects at the same time. They are expert recruiters of both engineers and managers alike. But they can also grow the existing talent on their teams. Directors are leaders that model the behaviors we want to see in our teams and hold others accountable when necessary. And they create the collaborative and productive environment in which engineers and engineering managers do their work.

Responsibilities

Requirements

Nice-to-haves

VP of Engineering

The VP of Engineering role extends the Director of Engineering role.

Specialties

Read more about what a specialty is at GitLab here.

Distribution

The Distribution team closely partners with the rest of the engineering organization to build, configure, and automate GitLab installation. GitLab's distribution team is tasked with creating a seamless installation experience for customers and community users across multitude of platforms.

Distribution engineering is interlaced with the broader development team in supporting newly created features. Notably, the infrastructure team is the distribution team's biggest internal customer, so there is significant team interdependency. The Distribution team also provides significant variety in tasks and access to a diversity of projects, including helping out on various community packaging projects. This is reflected in the job requirements: we are tasked with creating and maintaining a Cloud Native GitLab deployment and upgrade methods, Omnibus GitLab package installation across multiple Linux based Operating Systems, and various Cloud providers deployment methods (such as AWS Cloudformation, GC Deployment Manager and so on).

Requirements

Packaging

Packaging engineers are focused on creating the binary repository management system that will extend our Continuous Integration (CI) functionality to allow access and management of artifacts manipulated by projects.

By extending the current CI artifacts system, the Packaging team will expose GitLab as a package repository allowing access to the most common package managers, e.g. Maven and APT and similar. Additionally, the Packaging team is improving the Container Registry and is responsible for items listed under Packaging product category.

Requirements

Responsibilities

Secure

Focus on security features for GitLab. This role will specifically focus on security; if you want to work with Ruby on Rails and not security, please apply to our Backend Engineer role instead. This role will report to and collaborate directly with the Secure Engineering Manager.

Requirements

Responsibilities

Configuration

The configuration team works on GitLab's Application Control Panel, Infrastructure Configuration features, our ChatOps product, Feature flags, and our entire Auto DevOps feature set. It is part of our collection of Ops Backend teams.

Requirements

Responsibilities

CI/CD

CI/CD Backend Engineers are primarily tasked with improving the Continuous Integration (CI) and Continuous Deployment (CD) functionality in GitLab. Engineers should be willing to learn Kubernetes and Container Technology. CI/CD Engineers should always have three goals in mind:

  1. Provide value to the user and communicate such with product managers,
  2. Introduce features that work at scale and in untrusting environments,
  3. Always focus on defining and shipping the Minimal Viable Change.

We, as a team, cover end-to-end integration of CI/CD in GitLab, with components being written in Rails and Go. We work on a scale of processing a few million of CI/CD jobs on GitLab.com monthly. CI/CD engineering is interlaced with a number of teams across GitLab. We build new features by following our direction. Currently, we focus on providing a deep integration of Kubernetes with GitLab:

  1. by automating application testing and deployment through Auto DevOps,
  2. by managing GitLab Runners on top of Kubernetes,
  3. by working with other teams that provide facilities to monitor all running applications,
  4. in the future implement A-B testing, feature flags, etc.

Additionally, we also focus on improving the efficiency, performance, and scalability of all aspects of CI/CD:

  1. Improve performance of developer workflows, e.g. faster CI testing, by improving parallelization,
  2. Improve performance of implementation, ex.:by allowing us to run 10-100x more in one year,
  3. Identify and add features needed by us, ex.:to allow us to test more reliable and ship faster.

The CI/CD Engineering Manager also does weekly stand-up with a team and product managers to talk about plan for the work in the upcoming week and coordinates a deployment of CI/CD related services with infrastructure team.

Requirements

Geo

GitLab Geo is an enterprise product feature that speeds up the work of globally distributed teams, adds redundancy for GitLab instances, and provides Disaster Recovery as well.

Requirements

Requirements (Staff Level)

Growth

Growth Engineers work with a cross-functional team to influence the growth of GitLab as a business. In helping us iterate and learn rapidly, these engineers enable us to more effectively meet the needs of potential users.

Requirements

Quality

Quality Engineers are primarily tasked with improving the productivity of the GitLab developers (from both GitLab Inc and the rest of the community), and making the GitLab project maintainable in the long-term.

See the description of the Quality team for more details. The position also involves working with the community as merge request coach, and working together with our Backend Engineers to respond and address issues from the community.

Gitaly

Gitaly is a new service in our architecture that handles git and other filesystem operations for GitLab instances, and aims to improve reliability and performance while scaling to meet the needs of installations with thousands of concurrent users, including our site GitLab.com. This position reports to the Gitaly Lead.

Responsibilities

Requirements:

Meltano (BizOps Product)

Meltano is an early stage project at GitLab focused on delivering an open source framework for analytics, business intelligence, and data science. It leverages version control, data science tools, CI, CD, Kubernetes, and review apps.

A Meltano Engineer will be tasked with executing on the vision of the Meltano project, to bring the product to market.

Requirements

Database

A database specialist is an engineer that focuses on database related changes and improvements. You will spend the majority of your time making application changes to improve database performance, availability, and reliability; though you will also spend time working on the database infrastructure that powers GitLab.com.

Unlike the Database Engineer position the database specialist title focuses more on application development and less on knowledge of PostgreSQL. As such Ruby knowledge is absolutely required, but the requirements for PostgreSQL knowledge / experience are less strict compared to the Database Engineer position.

Example Projects

Requirements

Release Management

Release management specialist is an engineer that focuses on improving the engineering workflows, creates new tools, improves release process and works closely with the whole Engineering team to ensure that every GitLab release reaches the public in time.

Release Management specialist also leads a Crew that gets organized per monthly release cycle and carry out the release tasks.

Responsibilities

Gitter

Gitter specialists are full-stack JavaScript developers who are able to write JavaScript code that is shared between multiple environments. Gitter uses uses a JavaScript stack running Node.js on the server, and bundled with webpack on the client. The iOS, Android, MacOS (Cocoa) and Linux/Windows (NW.js) clients reuse much of the same codebase but also require some knowledge of Objective-C, Swift and Java. Gitter uses MongoDB, Redis, and Elasticsearch for backend storage.

Requirements

Responsibilities

Compensation

Annual Compensation
--
Unfortunately GitLab is not hiring at your selected country at this time. Please read our hiring handbook for more details.

How did we calculate your compensation?

SF benchmark $160,000
x
(
0.7
x
(
max
(
0.2,
Rent Index --
+
Hot Market Adjustment --
)
/
1.26
)
+
0.30
)
x
Level 1.0
x
Experience 0.9 to 1.1
x
Contract Type --
x
Country Factor --
Find out how our calculator works. You are also eligible for stock options and other benefits.

Apply

Please note that if we are actively hiring for a position, you will see it listed on our jobs page, where all of our current openings are advertised. To apply, please click on the name of the role you are interested in, which will take you to our applicant tracking system (ATS), Greenhouse.

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.

About GitLab

GitLab Inc. is a company based on the GitLab open-source project. GitLab is a community project to which over 1,000 people worldwide have contributed. We are an active participant in this community, trying to serve its needs and lead by example. We have one vision: everyone can contribute to all digital content, and our mission is to change all creative work from read-only to read-write so that everyone can contribute.

We value results, transparency, sharing, freedom, efficiency, frugality, collaboration, directness, kindness, diversity, boring solutions, and quirkiness. If these values match your personality, work ethic, and personal goals, we encourage you to visit our primer to learn more. Open source is our culture, our way of life, our story, and what makes us truly unique.

Top 10 reasons to work for GitLab:

  1. Work with helpful, kind, motivated, and talented people.
  2. Work remote so you have no commute and are free to travel and move.
  3. Have flexible work hours so you are there for other people and free to plan the day how you like.
  4. Everyone works remote, but you don't feel remote. We don't have a head office, so you're not in a satellite office.
  5. Work on open source software so you can interact with a large community and can show your work.
  6. Work on a product you use every day: we drink our own wine.
  7. Work on a product used by lots of people that care about what you do.
  8. As a company we contribute more than we take, most of our work is released as the open source GitLab CE.
  9. Focused on results, not on long hours, so that you can have a life and don't burn out.
  10. Open internal processes: know what you're getting in to and be assured we're thoughtful and effective.

See our culture page for more!

Work remotely from anywhere in the world. Curious to see what that looks like? Check out our remote manifesto.