Senior Backend Engineer (c), Tenant Scale: Git

GitLab GitLab · Enterprise · India · Remote · Platforms Engineering

GitLab is seeking a Senior Backend Engineer for their Tenant Scale: Git team. This role focuses on improving Git and Gitaly for GitLab's platform, contributing to upstream Git, and shaping technical direction. The engineer will work on repository access, performance, and maintainability, collaborating with the open source community and aligning contributions with product needs.

What you'd actually do

  1. Participate in architectural discussions and technical decisions related to Git and Gitaly, helping drive implementation choices that improve correctness, performance, and maintainability.
  2. Contribute features, bug fixes, and performance improvements to upstream Git in line with team and community goals, delivering changes that improve repository access and reliability for users.
  3. Adapt Gitaly to make effective use of Git capabilities, including integrating newly available features to improve scalability, efficiency, and long-term maintainability.
  4. Connect discussions in the open source Git project with GitLab's product direction and engineering work, helping align upstream contributions with product and platform needs.
  5. Scope tasks, estimate effort, and describe implementation plans that support the team's priorities and enable predictable delivery of technical work.

Skills

Required

  • Experience building instrumented, observable software systems.
  • Knowledge of Git internals, including its code and data structures, or practical experience operating Git servers.
  • Experience writing and testing production-quality code in C.
  • Experience contributing to open source projects, including Git or similar systems, and working effectively in public collaboration spaces.
  • Familiarity with Go for backend development and understanding of Linux internals such as processes, memory management, input/output, and filesystems.

Nice to have

  • Interest or experience in large-scale or distributed systems, storage formats, graph theory, or highly available production environments, including transferable backend or infrastructure experience.

What the JD emphasized

  • instrumented, observable software systems
  • Git internals
  • production-quality code in C
  • contributing to open source projects, including Git or similar systems