Take end-to-end ownership of GitLab's native Secrets Manager (Rails/Go, OpenBao, RBAC)

Interview for GitLab's Pipeline Security team, owning the native Secrets Manager built on OpenBao toward general availability. Expect Ruby on Rails and Go system-design questions centered on RBAC, GraphQL APIs, Kubernetes/Helm deployment, and a security-first code review mindset — all in a fully async, distributed team.

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 architecture (secure, production-quality code)
Go for targeted components
RBAC design and GraphQL API design
Secrets management / CI/CD pipeline security
Kubernetes deployment (Helm charts) and validation

Common question themes

Design an RBAC model and GraphQL API for a secrets-access feature

How would you secure a CI/CD pipeline against misconfiguration or credential leakage

Walk through your approach to reviewing a merge request with a security-first mindset

Experience with secrets management tools like HashiCorp Vault

How you communicate technical tradeoffs in an async, distributed team

How candidates describe it

Real Senior Backend Engineer (RoR/Go) 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