Staff Backend Engineer, GitLab

• Cross-Team Technical Leadership: A sustained record of technical leadership across more than one team or a broad product area
• Deep Architecture Experience: Deep backend architecture and production experience in complex applications, services, or platforms, including scaling or governing APIs, service platforms, data systems, modular monoliths, or shared backend components
• Modularization in Production: Experience modernizing a monolith or legacy backend architecture in production, and with modular architecture such as bounded contexts, package encapsulation, ports and adapters, service extraction, event-driven boundaries, or an equivalent approach
• Influence Without Authority: A strong ability to create alignment through clear written proposals and decision records, so decisions are documented, understood, and adopted without constant escalation
• Product Judgment: The ability to balance customer outcomes, delivery speed, technical health, reliability, and long-term platform investment
• Mentorship: Experience mentoring engineers and shaping standards through code review, documentation, and example
• Agentic AI Leadership: Production experience with AI-assisted or agentic engineering workflows, including the ability to evaluate and improve how a team adopts them

Desirable

• As a Staff Backend Engineer, you will provide technical leadership across your team and adjacent teams, solving the highest-scope and most complex problems in your area. You will lead large, cross-cutting backend initiatives, drive our modular architecture strategy, and define the standards that let teams move faster without compromising quality, security, reliability, or operability
• This is a technical leadership role that combines deep backend expertise, systems judgment, product judgment, and influence across organizational boundaries. You will work with Product, Frontend, Infrastructure, Security, Data, Engineering Managers, and engineers across product groups, bringing subject matter expertise, and you will do it without relying on formal authority
• Leverage: Your work multiplies across teams. The platforms, standards, and architectural decisions you lead determine how quickly everyone else can ship
• Genuinely Hard Problems: You’ll lead the modernization of a large monolith toward modular, reusable, appropriately independent systems — at the scale of a platform used by millions of users
• Influence Without Bureaucracy: You’ll shape technical direction across teams through clear written proposals and decision records, and partner with Product and Engineering leadership on platform roadmap and investment trade-offs
• Frontier AI Work: You’ll lead adoption of AI-assisted and agentic engineering workflows and define the review, quality, security, and privacy guardrails that make them safe to rely on
• Autonomy: You’ll thrive in our remote-first, asynchronous organization, where clear written communication and self-direction are the pillars of success
• Lead Cross-Cutting Initiatives: Lead the technical design and delivery of large backend initiatives that span teams, and identify and remove systemic bottlenecks across product and infrastructure groups
• Own Architecture Strategy: Drive modular backend, service, data, and platform architecture. Lead modernization of the monolith and legacy backends toward modular, reusable, and appropriately independently operated systems — while preventing fragmentation and service sprawl
• Set the Standards: Define and improve standards for APIs, contracts, compatibility, schema evolution, testing, security, performance, observability, operability, and maintainability — plus the build, test, deploy, release, rollback, and production-readiness practices needed to operate modular features safely
• Establish Shared Patterns: Create the patterns for dependency management, data ownership, eventing, failure isolation, service maturity, and operational documentation. Establish Go service patterns and Kubernetes operating practices where they matter to our production estate, and guide Rust adoption where it solves a real systems, security, performance, or supply-chain problem
• Own What You Build in Production: Take part in on-call and incident response for the systems your teams own, act as a technical escalation point during complex incidents, and turn what you learn into architectural and operational improvements that prevent recurrence
• Influence and Partner: Shape technical direction across teams without formal authority, and partner with Product and Engineering leadership on platform-level roadmap decisions and investment trade-offs
• Grow Engineers: Mentor Senior and Intermediate engineers, shepherd technical debt reduction and reusable patterns that improve throughput, and raise the technical capability of the wider team
• Lead AI Adoption: Lead team-level adoption of AI-assisted and agentic workflows, including the quality, security, privacy, and operational guardrails, and help engineers direct, validate, reject, and course-correct agent output