Core DevOps builds continuous Integration, continuous deployment, planning, and source control experiences. These are among the most mature, highest traffic, and most deeply interconnected systems at GitLab. They carry years of accumulated architectural decisions, they sit in the critical path of our customers’ own delivery pipelines, and they are being reshaped by the shift toward AI native development. The job is to raise their quality, converge them onto a coherent go-forward architecture, and retire accumulated risk, all without interrupting the millions of users and Fortune 100 organizations who depend on them.
GitLab is pursuing a set of company-wide engineering goals: large gains in developer productivity, measurably higher quality in what we ship, and engineering practices reshaped around AI and agentic workflows. Core DevOps is where much of that strategy has to land, because these are the services our own engineers and our customers depend on daily. In this role you will bring that strategy into Core DevOps in a form that works for long lived production systems, and carry what you learn here back out to the rest of engineering.
What You’ll Do
Set and continuously refine the go forward technical direction for CI, CD, Plan, and source code experiences, aligned against the horizontal architectural initiatives.
Work directly with the VP of Engineering as her technical counterpart on planning, technical investment, and where the group’s engineering effort should go.
Translate GitLab’s company-wide productivity, quality, and AI native engineering goals into concrete technical direction for Core DevOps, and turn into iterable roadmaps, partnering broadly across the org.
Define what good means in measurable terms for these services, including availability, latency at p95 and p99, pipeline success rate, test reliability, data correctness, and defect escape rate, then hold designs and implementations to it.
Maintain a clear and current picture of systemic technical risk across the group, including single points of failure, unowned critical paths, brittle coupling between CI/CD and Plan, scaling limits, and past decisions that now constrain the roadmap. Drive a prioritized plan to retire it.
Lead the hardest design decisions hands on, writing code, prototypes, and proofs of concept where a design argument needs evidence behind it.
Drive convergence on shared patterns, libraries, and paved paths, reducing how many different ways the same problem gets solved across the group.
Design migration paths that let large, long lived systems change underneath users without breaking them, using incremental cutover, dual run, measurable rollback, and deprecation with clear timelines.
Adopt the platform capabilities coming from GitLab’s AI organization and the company’s productivity initiatives into Core DevOps, feed this group’s requirements back into them, and help prove what works on systems of this scale and maturity.
Serve as the escalation point for complex or contested technical decisions across the group, including those where no single team owns the outcome.
Review significant designs and merge requests in the group’s critical paths, and use review to teach rather than only to gate.
Ensure designs hold across GitLab.com, GitLab Dedicated, and Self-Managed deployments, and respect multi-tenant, compliance, and data governance boundaries in each.
Partner with Infrastructure, Security, and SRE so Core DevOps services are observable and debuggable, and so failure modes degrade gracefully instead of cascading.
Make architectural constraints and opportunities clear to Product in roadmap terms, so that technical investment and product ambition get planned together instead of traded off late.
Write clear, opinionated design documents, architecture narratives, and decision records that let teams across the group make aligned decisions independently.
Grow Principal and Staff Engineers across Core DevOps, raise the bar on design rigor and technical writing, and contribute to the technical hiring bar for senior individual contributors.
Participate in the Incident Management on-call rotation to help meet availability goals for GitLab.com, and complete Interview Training to participate in hiring as a technical interviewer or panel member.
What You’ll Bring
10+ years of software engineering experience, including 4+ years in a Staff, Principal, or equivalent senior technical leadership role.
Deep expertise in AI and ML systems, including large language models, agentic frameworks, and autonomous workflow design at production scale.
Proven track record of leading hands-on technical experimentation, including defining evaluation frameworks, running benchmarks, and translating findings into scalable architecture decisions.
Strong background in scalable, multi-tenant distributed systems, including service decomposition, fault tolerance, observability, and operational resilience.
Experience designing and implementing human-in-the-loop controls, safety guardrails, and responsible AI practices for production systems.
Experience mentoring senior engineers and influencing technical direction across multiple teams or divisions without direct authority.
Ability to work effectively in a fully remote, globally distributed organization with excellent written and asynchronous communication skills.
The base salary range for this role’s listed level is currently for residents of the United States only. This range is intended to reflect the role’s base salary rate in locations throughout the US. Grade level and salary ranges are determined through interviews and a review of education, experience, knowledge, skills, abilities of the applicant, equity with other team members, alignment with market data, and geographic location. The base salary range does not include any bonuses, equity, or benefits. See more information on our benefits and equity. Sales roles are also eligible for incentive pay targeted at up to 100% of the offered base salary.
United States Salary Range
$250,000—$349,000 USD
How GitLab Supports Full-Time Employees
Benefits to support your health, finances, and well-being
Flexible Paid Time Off
Team Member Resource Groups
Equity Compensation & Employee Stock Purchase Plan
Growth and Development Fund
Parental Leave
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.
