Staff Backend Engineer, Architecture Engineering: Nonlinear Productivity at GitLab

Role overview

Staff Backend Engineer, Architecture Engineering: Nonlinear Productivity at GitLab, retained from the employer source record. Verify current availability on the official posting before applying.

Responsibilities

• Set the technical direction for the team's agentic systems, from how agents are orchestrated to where a step should stay human-owned, and defend those calls once they're tested against real code.
• Discover and prioritize sources of friction across GitLab's SDLC, driving the fix — agentic, process-based, or both — from a rough hypothesis through to a shipped, measured result.
• Work across any part of GitLab's codebase as the problem requires, since this team operates like a small, generalist group rather than one scoped to a single service.
• How GitLab Supports Full-Time Employees

Qualifications

• Ability to work autonomously in unfamiliar codebases and drive solutions from discovery through completion.
• Strong distributed systems and computer science fundamentals, including coordination, consistency, idempotency, rate limiting, failure modes, and degradation under load.
• Proficiency in Go, Rust, or Python, with the ability to read and modify code in the others.
• A track record of delivering results from unclear or incomplete requirements — able to take a complex, loosely specified problem and decompose it into a concrete proposal of small, shippable steps.
• A history of unblocking and enabling teammates — through design reviews, technical writing, or mentoring — and of engaging regularly with other teams to find where collaboration actually pays off.
• 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.

Technology in this role

• Python: Proficiency in Go, Rust, or Python, with the ability to read and modify code in the .
• Go: Proficiency in Go, Rust, or Python, with the ability to read and modify code in the .
• Rust: Proficiency in Go, Rust, or Python, with the ability to read and modify code in the .
• LLM: • Experience building reliable agentic or large language model (LLM)-based systems, including multi-step orchestration, tool use, guardrails, and .
• CAN: Our Talent Acquisition team can help answer any questions about location after starting the recruiting .

Role-specific candidate guide

Preparation notes based on the employer’s stated responsibilities and qualifications.

Understanding the scope. This Staff Backend Engineer, Architecture Engineering: Nonlinear Productivity position at GitLab is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “Staff Backend Engineer, Architecture Engineering: Nonlinear Productivity at GitLab, retained from the employer source record. Verify current availability on the official posting before applying.” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the software engineering area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Set the technical direction for the team's agentic systems, from how agents are orchestrated to where a step should stay human-owned, and defend those calls once they're tested against real code.”; “Discover and prioritize sources of friction across GitLab's SDLC, driving the fix — agentic, process-based, or both — from a rough hypothesis through to a shipped, measured result.”; “Work across any part of GitLab's codebase as the problem requires, since this team operates like a small, generalist group rather than one scoped to a single service.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before.

Benefits

• Equity Compensation & Employee Stock Purchase Plan

About GitLab

Nonlinear Productivity — shortened internally to "NLP," with no relation to natural language processing — is one of GitLab's newest teams: a strategic incubation group that reports into AI Platform leadership under the direct sponsorship of the CTO. It's split into a US group (this role) and an India-based group working the same charter; the two sync on roadmap and tooling a few times a week but otherwise run day to day on their own. Solutions that prove out internally are the team's path to a monetized, customer-facing GitLab offering.

It's a good fit for engineers who want technical ownership of something with no existing playbook, and a hand in defining a brand-new part of GitLab from its first commit.

Browse job categories

Related jobs

• Senior Backend Engineer, Architecture Engineering: Nonlinear Productivity at GitLab — GitLab
• Senior Software Engineer (Backend) at TeamSnap — TeamSnap
• Staff Backend Engineer, User Safety at Reddit — Reddit
• Senior Backend Engineer, External Security at Horizon3 — Horizon3
• Senior Backend Engineer, Agent Experience at Grab — Grab
• Senior Backend Software Engineer, Agent Experience at Grab — Grab