Software Engineer, Release Engineering at Zapier (L3/L4) — owning CI/CD and delivery infrastructure for every engineer

Zapier is hiring L3/L4 Software Engineers for a new India-timezone Release Engineering team that owns CI/CD pipelines, testing infrastructure, and release orchestration for the whole engineering org. The interview weighs production backend engineering fundamentals against platform-engineering depth — building and improving delivery systems, not just using GitLab CI/Kubernetes/ArgoCD/Terraform as a consumer.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Building/improving CI/CD pipelines and testing infrastructure (not just using them)
Hands-on platform tooling: GitLab CI, Kubernetes, Docker, ArgoCD, Terraform
Production backend/fullstack engineering fundamentals (TypeScript, Node.js, Python or equivalent)
Driving loosely-defined problems to production: design docs, success criteria, rollout, measurement
Systems thinking with downstream engineers as first-class users; defining 'golden paths'
L4: technical leadership, mentoring, cross-team platform dependency coordination

Common question themes

Tell me about a CI/CD pipeline or test suite you diagnosed and fixed — what was the root cause

Describe a release/delivery system you built or significantly improved, and the tools involved

How do you define a 'golden path' for how code gets built and shipped, and drive adoption of it

Walk me through taking an ambiguous platform problem from design doc to production rollout

(L4) Tell me about leading technical design for a project with cross-team dependencies

How do you use AI tools in your engineering workflow, and how do you validate their output

Describe how you'd coordinate an incident response when a release pipeline breaks for the whole org

How candidates describe it

Real Software Engineer interview stories — retold from candidates' public write-ups, with sources.

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

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Zapier interviews