Build the backend that lets AI agents operate across GitLab's software delivery lifecycle

GitLab's new Agent Tools team is building the systems — including GitLab's MCP server — that let AI agents interact with the full software delivery lifecycle, not just code generation. This Intermediate Backend Engineer role works in Ruby on Rails across GitLab's monolith, shipping GraphQL/REST APIs at the intersection of GitLab's core platform and its AI strategy.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Ruby on Rails backend development in a large, mature monolith
Designing REST/GraphQL APIs for scalability and backward compatibility
Building interfaces (e.g., MCP server) for AI agents to interact with a platform
Automated testing discipline (RSpec) in a fast-moving feature area
Production troubleshooting and Tier 2 on-call ownership
Practical, daily use of AI tooling in one's own engineering workflow

Common question themes

Walk through a Rails feature you built involving background jobs or data models

How would you design an API contract meant to be called by an AI agent, not just a human client

Tell me about a production incident you triaged and root-caused

How do you use AI tools day-to-day in your own engineering work

Describe your approach to test coverage (RSpec) on a fast-iterating feature

How do you collaborate effectively async across timezones

How candidates describe it

Real Backend Engineer (Ruby) interview stories — retold from candidates' public write-ups, with sources.

Google · Backend Software EngineerNo offer

Google Backend Engineer Interview Experience: Bangalore Onsite (Rejected)

A rejected Google Backend Engineer candidate in Bangalore recounts a recruiter screen, a gating elimination round, and a three-round onsite loop covering trees, tries, scheduling, and graph problems.

Interviewed April 2021 · Bangalore, India

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

View the original posting

All GitLab interviews