Senior Backend Developer

At GitLab, developers are highly independent and self-organized individual contributors who work together as a tight team in a remote and agile way.

Most backend developers work on all aspects of GitLab, building features, fixing bugs, and generally improving the application. Some developers specialize and focus on a specific area, such as packaging, performance or GitLab CI. Developers can specialize immediately after joining, or after some time, when they have gained familiarity with many areas of GitLab and find one they would like to focus on.



Ruby experience

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 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.

Senior Developers

Senior Developers are experienced developers who meet the following requirements:

  1. Technical Skills
    • Write modular, well-tested, and maintainable code
    • Know a domain really well and radiate that knowledge
    • Contribute to one or more complementary projects
    • Take on difficult issues, big or small
  2. Leadership
    • Begin to show architectural perspective
    • Propose new ideas, performing feasibility analyses and scoping the work
  3. Code quality
    • Leave code in substantially better shape than before
    • Fix bugs/regressions quickly
    • Monitor overall code quality/build failures
    • Leave tests in better shape than before: faster, more reliable, more comprehensive, etc.
  4. Communication
    • Provide thorough and timely code feedback for peers
    • Able to communicate clearly on technical topics and present ideas to the rest of the team
    • Keep issues up-to-date with progress
    • Help guide other merge requests to completion
  5. Performance and scalability
    • Excellent at writing production-ready code with little assistance
    • Are able to write complex code that can scale with a significant number of users
    • Are able to fix performance issues on with minimal guidance using our existing tools, and improve those tools where needed


The basics of GitLab development can be found in the developer onboarding document.

The handbook details the complete GitLab Workflow.

Hiring Process

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.

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


Annual Compensation

How did we calculate your compensation?

NYC benchmark $87,337
Rent Index --
Hot Market Adjustment --
Level 1.0
Experience 0.8 to 1.2
Contract Type --
Find out how our calculator works. You are also eligible for stock options and other benefits.