Google Senior SWE — build eye-tracking perception software for Android XR devices

This role is on Google's Android XR / XR Perception team, writing compute-constrained perception software (eye tracking specifically called out) that runs at high frame rate and bandwidth on mobile XR devices. The bar is senior: 5+ years of software development, 3+ years shipping/maintaining production software, 1+ year of design/architecture, plus required computer vision/AR experience, with eye-tracking-on-XR-devices and camera sensor pipeline experience called out as strongly preferred. Expect deep technical discussion on embedded/on-device ML perception systems, performance-constrained software design, and cross-team collaboration, alongside Google's standard coding and system design loop.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Standard Google SWE loop: recruiter screen, phone screen(s) with coding, then onsite virtual loop of 4-5 rounds covering coding/algorithms, system design, a domain-specific (perception/CV) technical round, and Googleyness/leadership, followed by Hiring Committee review.

What this interview tests

Perception software for compute-constrained, high-frame-rate Android devices
Computer vision / AR / eye-tracking domain experience
Camera sensor pipelines and data flow on Android devices
Architecture/design documentation and cross-team technical communication
Code review practices and engineering process improvement
Collaboration with ML engineers to productionize perception models on-device

Common question themes

Design a perception pipeline that must hit a real-time frame budget on constrained hardware

Describe hands-on experience with eye tracking, gaze, or camera sensor pipelines

Tell me about a design doc you wrote that shaped how your team built a system

How do you approach code review to improve team practices, not just catch bugs

Describe collaborating with ML/research engineers to get a model running efficiently on-device

A time you diagnosed and fixed a performance bottleneck in resource-constrained software

How candidates describe it

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

Bloomberg · Senior Software EngineerOffer

Bloomberg Senior Software Engineer Interview: Five Rounds, Offer

A Senior Software Engineer candidate applied to Bloomberg's London office through the company's careers site and, after an initial screen, went through five separate on-site conversations covering coding, system design, a recruiter chat, and a hiring-manager round, ultimately accepting an offer.

Interviewed October 2022 · London, United Kingdom

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

All Google interviews