Build the build/test infrastructure that Android Developer Tools engineers ship libraries through

Software Engineer role on Google's Android Developer Tools infrastructure team in Cambridge, MA, building the internal tooling, build systems (Bazel), and CI/CD infrastructure that lets Android tooling teams ship libraries with API compatibility, documentation, and non-flaky tests. Requires 2 years in Kotlin or Go plus 1 year with Bazel-style build systems.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Standard Google SWE process: recruiter screen, 1-2 coding phone screens, then an onsite loop of coding, Googleyness/leadership, and a team-matching conversation.

What this interview tests

Build systems: Bazel (required), plus Gradle/Maven familiarity
Kotlin or Go programming proficiency
Data structures and algorithms
CI/CD system design and maintenance
API compatibility and test flakiness / code health practices
Cross-team collaboration (including external partners like JetBrains)

Common question themes

Coding problem in Kotlin or Go covering data structures/algorithms

Design or debug a build system rule/target in Bazel

How would you detect and eliminate flaky tests across a large codebase

Describe partnering with another team (or external vendor) to land a feature

How do you maintain API compatibility across library releases

Googleyness/behavioral: ambiguity, collaboration in small nimble teams

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 Google Software Engineer interviews

All Google interviews