Senior Backend Engineer (Ruby), AI Catalog: External Agents at GitLab
Closed
GitLab is hiring a remote Senior Backend Engineer (Ruby), AI Catalog: External Agents to build secure Ruby backend integrations and AI-powered developer workflows. The listing covers Remote, United Kingdom.
Search jobs by company: GitLab
Save job — free account Saved jobs
Create a free application profile — Keep your skills and projects in a reusable profile. Private by default; you choose when to share. Apply for this job directly with the employer.
By continuing, you agree to processing needed to manage your account and profile. Privacy policy
This opening is not confirmed as active. Check the employer source before applying.
Role overview
GitLab’s AI Engineering organisation builds AI-powered capabilities into its DevSecOps platform. These Senior Backend Engineer roles work on Ruby backend systems that connect external agents, AI coding workflows and event-driven automation to GitLab.
Responsibilities
- Design, build and maintain secure, tested and performant Ruby backend integrations and services.
- Connect GitLab agents with external tools and providers such as Slack, Claude Code, Codex and other workflow systems.
- Build event and trigger capabilities that respond to pushes, issues, merge requests, CI/CD results, deployments and third-party events.
- Define APIs, permissions, contracts and architectural patterns for exposing AI functionality safely.
- Collaborate with product, UX, frontend and AI engineering teams to deliver end-to-end features.
- Improve observability, test coverage and production reliability, and participate in incident response when required.
Qualifications
- Strong professional experience building production Ruby on Rails backends and APIs.
- Experience integrating external systems, event-driven workflows, webhooks or tool-calling interfaces.
- Understanding of secure API design, permissions, testing, performance and backward compatibility.
- Ability to work across a large monolith and adjacent services while making pragmatic architectural decisions.
- Experience with AI-assisted or agentic software systems is valuable, as is familiarity with developer tools and CI/CD.
- Strong written communication and ability to collaborate in a remote, async-first team.
Technology in this role
- Python: familiarity with Python backends or Vue frontends is a .
- SQL: • Strong SQL skills and familiarity with relational databases such as PostgreSQL, including efficient queries and data .
- Ruby on Rails: Strong professional experience building production Ruby on Rails backends and .
- Ruby: These Senior Backend Engineer roles work on Ruby backend systems that connect external agents, AI coding workflows and event-driven automation to .
- PostgreSQL: • Strong SQL skills and familiarity with relational databases such as PostgreSQL, including efficient queries and data .
- CI/CD: Build event and trigger capabilities that respond to pushes, issues, merge requests, CI/CD results, deployments and third-party .
- CAN: Our Talent Acquisition team can help answer any questions about location after starting the recruiting .
- GraphQL: • Design, implement, and review GraphQL and REST application programming interfaces (APIs) and related backend logic, with clear contracts for frontend .
- Rails: Strong professional experience building production Ruby on Rails backends and .
Role-specific candidate guide
Preparation notes based on the employer’s stated responsibilities and qualifications.
Understanding the scope. This Senior Backend Engineer (Ruby), AI Catalog: External Agents 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: “GitLab’s AI Engineering organisation builds AI-powered capabilities into its DevSecOps platform. These Senior Backend Engineer roles work on Ruby backend systems that connect external agents, AI coding workflows and…” 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 AI and data 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 “Design, build and maintain secure, tested and performant Ruby backend integrations and services.”; “Connect GitLab agents with external tools and providers such as Slack, Claude Code, Codex and other workflow systems.”; “Build event and trigger capabilities that respond to pushes, issues, merge requests, CI/CD results, deployments and third-party events.”. 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 preparing your application.
How to read the requirements. The listed qualifications include “Strong professional experience building production Ruby on Rails backends and APIs.”; “Experience integrating external systems, event-driven workflows, webhooks or tool-calling interfaces.”; “Understanding of secure API design, permissions, testing, performance and backward compatibility.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement.
Benefits
- Equity Compensation & Employee Stock Purchase Plan
About GitLab
GitLab is a remote-first DevSecOps platform company. Its AI Engineering teams connect AI agents, coding workflows and lifecycle events to software delivery.
Employer websiteHow to apply
Check the original posting to confirm the role is still open before applying.
Check employer postingSource checked: 2026-11-08
Browse job categories
Related jobs
- Backend Engineer (Ruby), AI Engineering: Agent Observability at GitLab — GitLab
- Senior Backend Engineer (Ruby), AI Engineering: AI Coding at GitLab — GitLab
- Staff Backend Engineer (Ruby), AI Engineering: DAP Repository Flows at GitLab — GitLab
- Senior Backend Engineer, External Security at Horizon3 — Horizon3
- QA Engineer, Voice AI Agents at Arbiter — Arbiter
- Senior Backend Engineer, AI Engineering: Chat at GitLab — GitLab
