Synced from Greenhouse · Aug 13

Director of Engineering

GitLabBangalore, IndiaPosted Aug 13, 2026
Director of EngineeringExecutive
Apply now - freeSave & get alerts

Mirrored from GitLab's own Greenhouse careers system · refreshed hourly

229
Other open GitLab roles
Aug 13
Posted
Greenhouse
Applicant system
Job descriptionReq 8696826002

GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 50 million registered users and more than 50% of the Fortune 100* trust GitLab to ship better, more secure software faster.

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.

*Fortune 500® is a registered trademark of Fortune Media IP Limited, used under license. Claim based on GitLab data. Fortune 100 refers to the top 20% ranked companies in the 2025 Fortune 500 list, published in June 2025. Fortune and Fortune Media IP Limited are not affiliated with, and do not endorse products or services of GitLab.

Overview of the Role

GitLab.com is being rebuilt as a horizontally scalable cluster. Two primitives make that possible: Organizations, the tenant boundary that makes a customer's data a single addressable, portable unit, and Cells, independent GitLab instances that host those Organizations and can be provisioned on demand across clouds and regions.

The target is a 100x increase in headroom for GitLab.com, delivered without customers ever seeing a cell. Same domain, same URLs, same product — a substrate underneath that scales by adding capacity rather than by negotiating with a single database.

The boundary we are building is worth more than the scale it unlocks. An isolated Organization can guarantee where its data lives and what travels with it. That turns data residency, regional control, in-region AI and search compute, and enforceable tenant-level policy into product capabilities rather than deployment exceptions. It is the foundation for a class of enterprise and regulated-market offerings that a shared-instance architecture cannot support.

We are hiring a Director of Engineering in India to lead this charter. You will build and run the engineering organization that takes Cells from first production migrations to the default way GitLab.com operates.

What you will do

  • Delivery of the Cells and Organizations roadmap — cell provisioning and lifecycle, the routing and topology layer, organization data migration tooling, and feature parity across the platform.
  • Migration execution. Cohort-based movement of customer Organizations onto cells with zero data loss, verified rollback, and no downtime outside the tenant in flight.
  • A multi-cloud, multi-region cell footprint and the architectural decisions that govern what stays cell-local and what crosses boundaries.
  • The engineering organization. Hire, level, and develop managers and senior ICs across several teams. Set the technical bar and the operating cadence.
  • Cross-functional leadership. This charter touches nearly every product group at GitLab. You will drive commitments and sequencing with peer engineering leaders, Product, Infrastructure, and Security — much of it asynchronously, across time zones, in public issues and merge requests.

How success is measured

  • Customer Organizations running on cells in production, migrated cleanly and on schedule.
  • Availability and latency improvements attributable to isolation and load distribution.
  • Infrastructure cost per unit of capacity trending down as the footprint grows.
  • Throughput and retention of the teams you build.

What you will bring

Engineering leadership at director scale

  • Experience leading multiple teams through managers (roughly 25–60 engineers), including hiring and developing managers.
  • A track record of shipping multi-quarter infrastructure programs with hard external dependencies — the kind where the hardest problem is sequencing across ten teams, not writing the code.
  • Comfort operating as a peer to VPs and staff-plus engineers: you can hold an architectural position on technical merit and change it when the evidence changes.
  • Strong written communication. GitLab is remote and asynchronous by default; influence here is exercised in documents.

Distributed systems depth

  • You have built and operated large-scale distributed systems in production — multi-tenant SaaS, sharded or cell-based architectures, control planes, or data platforms at comparable scale.
  • Working fluency in relational database scaling (partitioning, sharding, replication), data migration at scale, and request routing.
  • Real operational experience: incident command, capacity planning, and designing for blast-radius containment.
  • Cloud infrastructure at depth on at least one major provider, ideally more than one.

AI-native engineering

  • You understand what agentic access patterns do to a platform's read volume, concurrency, and authorization model, and you design for that rather than retrofitting it.
  • You use AI tooling in your own engineering practice and have raised the bar for it across a team.

How GitLab Supports Full-Time Employees

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.

View original posting on Greenhouse

What applying to GitLab usually looks like

Based on publicly available information, candidates applying through greenhouse typically begin with an online application and resume submission, sometimes accompanied by optional screening questions. GitLab's process, like many companies using this ATS, may include multiple stages such as an initial recruiter conversation, one or more interviews with hiring managers or team members, and potentially a skills-based or take-home exercise depending on the role. Communication is usually managed through automated status updates within the platform, and response times vary based on the position and volume of applicants. Candidates can generally expect the process to be structured but may experience variability in pacing. It is commonly advisable to prepare for both behavioral and role-specific technical questions, and to ensure application materials clearly reflect relevant skills, since greenhouse-based processes often emphasize structured evaluation criteria across candidates.

Based on publicly available information. LandEarly does not verify interview process details.

Land this one early - before the req fills.

LandEarly tailors your resume and screening answers to each posting, submits within minutes of a role going live, and tracks every application in one place.

Free to start · No credit card · Cancel anytime

Keep exploring

What this role pays, where else it is open, and how to write the application.

Director of Engineering
GitLab · Bangalore, India
Apply