Senior Backend Engineer, Platform Readiness

About the role

GitLab features must ship successfully across four distinct deployment platforms—Self-Managed, Dedicated, Dedicated for Government, and GitLab.com. Today, developers routinely discover platform compatibility issues late in development, triggering costly rework, delays, and emergency escalations. The Platform Readiness team is building an internal developer tooling capability that embeds platform readiness intelligence directly into GitLab's software development lifecycle to solve this problem.

As a Senior Backend Engineer on the newly established Platform Readiness team, you'll architect and evolve the systems that enable features to ship successfully across all platforms by automating the evaluation of platform readiness requirements and surfacing risks early. You'll be a technical anchor for the team, driving the evolution of platform readiness from manual, ad-hoc assessments toward intelligent, agentic automation. Your work will directly impact GitLab's ability to ship features faster while dramatically reducing the risk of platform-readiness gaps and the operational burden of cross-platform validation.

You'll receive onboarding and technical guidance from other engineers and team leadership as you establish the technical direction for the Platform Readiness team.

What you'll do

• Contribute to the Platform Readiness team's agentic workflows on the Duo Agent Platform: design, implement, and evolve the Core Agentic Workflow (currently published to the AI Catalog as a DAP flow) and the Requirements Agent, enabling automated evaluation of platform readiness assessments against platform requirements
• Evolve the platform requirements knowledge base: contribute to schema design, validation tooling, and CI systems that power the agentic workflow; ensure the schema captures the full scope of platform readiness concerns across all four platforms and domains
• Build integration surfaces that enable feature teams to engage the Platform Readiness team where they already work: issues, merge requests, design documents, and CI/CD pipelines
• Partner with platform teams (Infrastructure, Security, Data) to translate their expertise into structured platform requirements, domain skills, and validation logic without requiring specific domain knowledge
• Contribute to the quality control feedback loop: design systems that surface assessment errors, missed gaps, and content drift back to the governance process