Own the kernel and user-space GPU driver stack for Pixel devices

This role sits on Pixel's GPU driver team within Google's Platforms and Devices org, sharing ownership of the kernel GPU driver and user-space graphics driver stack. Responsibilities span developing new GPU features, performance tuning, silicon bring-up, and debugging low-level issues across in-market and future Pixel devices. Requires a bachelor's degree or equivalent plus 2 years each in low-level systems programming (C/C++) and embedded operating systems, with experience writing low-level graphics API code.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Low-level systems programming in C/C++
Embedded operating systems and kernel-level driver development
GPU graphics/compute driver stack (kernel + user-space)
Low-level graphics APIs: OpenGL ES, Vulkan, OpenCL
Silicon bring-up and hardware/software debugging
Designing general solutions vs. device-specific workarounds

Common question themes

Debug a hardware/software boundary issue found only on real silicon

Design or explain a piece of the GPU driver stack (kernel driver vs user-space)

Data structures and algorithms in a systems-programming context

Diagnosing a performance bottleneck in a GPU-accelerated application

A time you generalized a solution instead of shipping a device-specific workaround

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