Ship production LLM-powered features for Google's Commerce/Shopping platform serving over a billion shopping queries a day

Google Commerce is hiring a software engineer to design, build, test, and deploy software for the shopping experiences that serve over a billion queries a day, spanning inspiration through checkout. The JD explicitly requires production experience deploying LLM-based systems and ML/Generative AI exposure, layered on Google's standard 2-year SWE bar - expect Google's typical coding + system design + googleyness/leadership loop.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Google's well-known hiring process typically includes a phone screen with coding, followed by an onsite loop of coding, system design/architecture, and Googleyness/leadership interviews.

What this interview tests

Data structures & algorithms (Google's standard coding bar)
Production experience deploying LLM-based systems; ML/Generative AI quality evaluation
System design for high-traffic consumer commerce features (search, recommendations, checkout)
Code review practices and design-review leadership
Debugging/triaging production issues across hardware, network, and service layers

Common question themes

Coding: solve a data structures/algorithms problem and discuss complexity trade-offs

Describe an LLM-based feature you shipped to production - how did you evaluate and improve its quality?

System design: design a component of a high-scale shopping experience (e.g., product search or checkout)

How do you conduct a code review - what do you look for in style, testability, and efficiency?

Walk through triaging a production issue: how do you isolate whether it's a hardware, network, or service problem?

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