Build the AI-powered test infrastructure that ships Pixel devices faster

Google's Platforms and Devices org is hiring a software engineer to build and own cross-device test infrastructure for Pixel, applying ML/AI to automate testing and speed up release cycles. Expect coding, ML infrastructure, and system-design depth across desktop, mobile, and device environments.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Google SWE loop: phone screen with coding, then onsite/virtual onsite rounds mixing coding (DS&A), a Googleyness/leadership behavioral, and a domain round on ML infra or test systems.

What this interview tests

Test infrastructure design at scale
ML infrastructure (deployment, evaluation, optimization, data processing)
Cross-device/platform debugging (hardware, network, service)
Data structures & algorithms
Code review and engineering best practices

Common question themes

Design a scalable test system for a new cross-device feature

Where would you apply ML/AI to reduce manual test triage

Debug a flaky test failure across hardware and service layers

Data structures/algorithms coding problem

Experience with ML infra: model deployment or evaluation pipeline

How you balance speed vs. test coverage in fast release cycles

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