Design and ship features for Google Wallet's Android platform at consumer scale

Software Engineer role on Google's Payments/Wallet team in Singapore, owning end-to-end design and delivery of features on Google Wallet's Android app and platform — the credential 'file system' behind tap-to-pay, Autofill, and Google Pay — with deep integration into Google Play Services and the Android platform itself. Requires 2 years of Java/Kotlin plus 2 years of Android app development.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Standard Google SWE process: recruiter screen, coding phone screens, then an onsite loop of coding, system/Android design, and Googleyness/leadership plus team matching.

What this interview tests

Java/Kotlin and Android application development
End-to-end feature ownership from design to deployment
Integration with Google Play Services and the Android platform
Designing platform abstractions/APIs for internal and external integrators
Collaboration with Product Managers and UX
Payments domain awareness: NFC, contactless, digital credentials (preferred, not required)

Common question themes

Coding problem in Java or Kotlin

Design an Android feature end-to-end for a payments/credentials app

How would you design an API for third-party integrators onto a platform

Discuss Android app architecture choices (lifecycle, secure storage, background work)

Cross-functional collaboration with PM/UX and across time zones

Googleyness/behavioral questions on ambiguity and ownership

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