Intermediate Backend (Ruby or Go) Engineer, Gitlab Delivery - Operate New

Other Jobs To Apply

No other job posts for this day.

GitLab is an open-core software company that develops the most comprehensive AI-powered DevSecOps Platform, used by more than 100,000 organizations. Our mission is to enable everyone to contribute to and co-create the software that powers our world. When everyone can contribute, consumers become contributors, significantly accelerating human progress. Our platform unites teams and organizations, breaking down barriers and redefining what's possible in software development. Thanks to products like Duo Enterprise and Duo Agent Platform, customers get AI benefits at every stage of the SDLC.

The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. Co-create the future with us as we build technology that transforms how the world develops software.

Backend Engineer, GitLab Delivery - Operate

An overview of this role

As a Backend Engineer, your work within the GitLab Operate team will focus on delivering and supporting GitLab for self-managed customers. This role centers on the infrastructure, tooling, and automation that power GitLab deployments via Omnibus, GitLab Helm Charts, the GitLab Environment Toolkit (GET), and the GitLab Operator.

The GitLab Operate team serves as a critical bridge between GitLab engineering and our self-managed customers, ensuring our products are easily deployable, secure, and scalable across a range of environments. You’ll work on production-grade tooling and collaborate with engineering teams to ensure GitLab’s features are consistently delivered and operable across supported platforms.

Some interesting links about the team and role:

  • Our primary projects
  • Our work with the community
  • Our Demo videos

What you’ll do

  • Omnibus GitLab: Maintain and evolve the GitLab Omnibus package to ensure it reliably integrates all GitLab components and can be deployed in self-managed environments.
  • Kubernetes Charts: Contribute to the development and maintenance of GitLab Helm Charts, enabling scalable and production-ready GitLab deployments on Kubernetes.
  • GitLab Environment Toolkit (GET): Enhance and support the toolkit used to deploy validated GitLab reference architectures for enterprise and internal use cases.
  • GitLab Operator: Support the GitLab Operator project to enable Kubernetes-native lifecycle management for GitLab deployments.
  • Installation and Upgrade Experience: Ensure a consistent and reliable experience for installing, upgrading, and operating GitLab across all supported platforms.
  • Security Collaboration: Partner with Security to address vulnerabilities in the deployment stack and ensure secure defaults and configurations.
  • Automation & CI/CD: Build and maintain automation pipelines for validating and testing deployment tools across Omnibus, Charts, GET, and the Operator.
  • Cross-Team Integration: Work closely with Distribution Engineers, SREs, Release Managers, and Development teams to ensure smooth integration of new features into our deployment methods.
  • Documentation & Enablement: Create and maintain user-focused documentation that enables self-managed customers to confidently deploy and operate GitLab.
  • Reliability: Ensure all supported deployment methods are well-tested and meet GitLab’s standards for quality, reliability, and performance.

What you’ll bring

  • Production experience working with Kubernetes and Helm
  • Professional proficiency in Ruby, Go and strong Bash scripting skills
  • Experience with Terraform and infrastructure as code workflows
  • Practical experience working with databases, especially PostgreSQL
  • Understanding of secure, scalable, and supportable deployment practices
  • Experience collaborating in large codebases and across distributed teams
  • Ability to write clear, user-facing documentation and implementation guides
  • Experience with major cloud providers (e.g., GCP, AWS, Azure)
  • Knowledge of service scaling and rollout strategies
  • Knowledge of Observability tools (Prometheus, Grafana, etc)

About the team

The Operate team is part of GitLab Delivery and focuses on delivering GitLab to self-managed users through supported and validated tooling. This includes maintaining and evolving the GitLab Omnibus package, Helm Charts, GitLab Operator, and the GitLab Environment Toolkit (GET). We partner with SRE, Release, Security, and Development teams to ensure GitLab is easily deployable, supportable, and production-ready in diverse environments. Our work directly supports GitLab’s commitment to reliability and flexibility for small business through enterprise scale, self-managed installations.

How GitLab will support you

  • Benefits to support your health, finances, and well-being
  • All remote, asynchronous work environment
  • Flexible Paid Time Off
  • Team Member Resource Groups
  • Equity Compensation & Employee Stock Purchase Plan
  • Growth and development budget
  • Parental leave
  • Home office support

Please note that we welcome interest from candidates with varying levels of experience; many successful candidates do not meet every single requirement. Additionally, studies have shown that people from underrepresented groups are less likely to apply to a job unless they meet every single qualification. If you're excited about this role, please apply and allow our recruiters to assess your application.

Country Hiring Guidelines: GitLab hires new team members in countries around the world. All of our roles are remote, however some roles may carry specific location-based eligibility requirements. Our Talent Acquisition team can help answer any questions about location after starting the recruiting process.

Privacy Policy: Please review our Recruitment Privacy Policy. Your privacy is important to us.

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, regardless of race, color, religion, ancestry, sex (including pregnancy, lactation, sexual orientation, gender identity, or gender expression), national origin, age, citizenship, marital status, mental or physical disability, genetic information (including family medical history), discharge status from the military, protected veteran status (which includes disabled veterans, recently separated veterans, active duty wartime or campaign badge veterans, and Armed Forces service medal veterans), or any other basis protected by law. GitLab will not tolerate discrimination or harassment based on any of these characteristics. See also GitLab’s EEO Policy and EEO is the Law. If you have a disability or special need that requires accommodation, please let us know during the recruiting process.

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...