Mid
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.
Step into this interview
Free · a live voice mock calibrated to this exact role
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
Related interviews
Senior
Software Engineer, Serverless Networking, Infrastructure
Staff
Staff Software Engineer, Mobile (Android), YouTube
Associate
Software Engineer
Airbnb
Senior
Senior Software Engineer, Service Tools
Figma
Senior
Software Engineer, Developer Experience (Build Systems)
Coinbase
Mid