SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
GitLab is seeking a Senior Backend Engineer to join the newly established Platform Readiness team. This role focuses on building internal developer tooling that embeds platform readiness intelligence into GitLab's software development lifecycle, enabling features to ship successfully across four distinct deployment platforms: Self-Managed, Dedicated, Dedicated for Government, and GitLab.com.
You will architect and evolve systems that automate the evaluation of platform readiness requirements and surface risks early in development. Currently, developers discover platform compatibility issues late, triggering costly rework and delays. Your work will transform this from manual, ad-hoc assessments to intelligent, agentic automation.
Key responsibilities include:
- Contributing to agentic workflows on the Duo Agent Platform, designing and implementing the Core Agentic Workflow and Requirements Agent for automated platform readiness evaluation
- Evolving the platform requirements knowledge base through schema design, validation tooling, and CI systems
- Building integration surfaces in issues, merge requests, design documents, and CI/CD pipelines to enable feature teams to engage with Platform Readiness
- Partnering with platform teams (Infrastructure, Security, Data) to translate expertise into structured requirements and validation logic
- Designing quality control feedback loops to surface assessment errors and improve accuracy
- Mentoring other engineers on agentic-workflow standards and human-AI collaboration principles
- Contributing to technical documentation and architectural decision records
Required experience includes 5+ years of software engineering with at least 2+ years in backend, platform, or developer-facing tooling. Strong proficiency in TypeScript/Node, Python, or Golang is essential. You should have shipped developer-facing tooling where the primary user is another engineer, understand GitLab-style development workflows (issues, epics, merge requests, CI/CD), and have experience with structured content systems, schemas, or validation tooling.
