← All jobs

Senior Backend Engineer, Ruby, Spec-Driven Development at GitLab

Confirmed open

GitLab is hiring a remote Senior Ruby Backend Engineer to build agentic intent-to-code workflows using Rails, Python, PostgreSQL and GitLab Duo. The listing covers Remote, United Kingdom.

GitLab logoGitLab
Location
Remote
Work arrangement
remote
Technologies
Python

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.

Role overview

GitLab’s Plan: Spec-Driven Development team is building an intent-to-code loop: agentic workflows that turn a stated intent into a refined work item, implementation plan and verified mergeable code.

This senior backend role owns early backend work across flows, APIs, data models and evaluation systems for a high-visibility AI product.

Responsibilities

  • Build backend features for agentic intent-to-code workflows using Ruby on Rails, Python and PostgreSQL.
  • Design APIs, data models and evaluation systems for AI-generated plans and code.
  • Integrate GitLab Duo Agent Platform, large-language-model APIs and the AI gateway.
  • Lead major features from unclear problem definition through release and public-beta learning.
  • Collaborate with product, design and users, mentor engineers and influence technical direction.
  • Improve reliability, security, observability and test coverage for AI-powered workflows.

Qualifications

  • Strong professional experience building production Ruby on Rails backends and APIs.
  • Experience with Python, PostgreSQL, data modelling and distributed application design.
  • Practical experience with AI, LLM APIs, agentic workflows or automated developer tooling.
  • Ability to evaluate non-deterministic outputs and design safe, reliable product behaviour.
  • Ability to lead ambiguous work, communicate clearly and collaborate in a distributed async-first team.
  • Interest in software development lifecycle automation and developer productivity.

Technology in this role

  • Python: Build backend features for agentic intent-to-code workflows using Ruby on Rails, Python and .
  • Ruby on Rails: Build backend features for agentic intent-to-code workflows using Ruby on Rails, Python and .
  • Ruby: Build backend features for agentic intent-to-code workflows using Ruby on Rails, Python and .
  • PostgreSQL: Build backend features for agentic intent-to-code workflows using Ruby on Rails, Python and .
  • LLM: Practical experience with AI, LLM APIs, agentic workflows or automated developer .
  • CAN: Our Talent Acquisition team can help answer any questions about location after starting the recruiting .
  • GraphQL: • Use Ruby on Rails and Python to build reliable production systems, with PostgreSQL, GraphQL, representational state transfer, GitLab Duo Agent Platform, large language model application programming interfaces, and an artificial intelligence .
  • Rails: Build backend features for agentic intent-to-code workflows using Ruby on Rails, Python and .

Role-specific candidate guide

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

Understanding the scope. This Senior Backend Engineer (Ruby), Plan: Spec-Driven Development 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 Plan: Spec-Driven Development team is building an intent-to-code loop: agentic workflows that turn a stated intent into a refined work item, implementation plan and verified mergeable code.” 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 “Build backend features for agentic intent-to-code workflows using Ruby on Rails, Python and PostgreSQL.”; “Design APIs, data models and evaluation systems for AI-generated plans and code.”; “Integrate GitLab Duo Agent Platform, large-language-model APIs and the AI gateway.”. 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 with Python, PostgreSQL, data modelling and distributed application design.”; “Practical experience with AI, LLM APIs, agentic workflows or automated developer tooling.”. 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 you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.

Technology and working evidence. The technology terms associated with this listing are Python. Treat this as a set of posting-derived signals, not a guarantee that every tool.

Benefits

  • Equity Compensation & Employee Stock Purchase Plan

About GitLab

GitLab is a remote-first DevSecOps platform company. The Plan team builds AI-powered workflows that help turn intent into software changes.

Employer website

How to apply

Review the original posting and apply through the employer’s careers page.

View source and apply

Source checked: 2026-10-13

Browse job categories

Related jobs