Google engineer building self-serve data pipelines and infrastructure for the Payments (Google Pay) data platform

This role sits on Google's Payments team, building and evolving the core data infrastructure — the 'Golden Data Pipeline' (GDP) — that underpins consumer payments products like Autofill, tap-to-pay, and Google Pay, focused on data reliability, scalability, and compliance for product and analyst teams. Minimum qualifications ask for 2 years of software development experience with large-scale data processing and distributed systems, putting this at a mid-level IC bar.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Google's standard SWE loop: phone screen(s) with coding, followed by onsite rounds covering coding, system/data design, and Googleyness/leadership behavioral interviews, per Google's well-known public process.

What this interview tests

Distributed data pipeline design and large-scale data processing
Data reliability, scalability, and compliance in a payments context
End-to-end ownership: scoping ambiguous problems into solutions
Cross-functional collaboration with PMs, data scientists, analysts
Identifying and resolving technical debt in existing systems

Common question themes

Design a self-serve data pipeline/platform for analysts and product teams

General coding/algorithms round in C++, Java, Python, or Go

How to ensure data reliability and compliance for sensitive (payments) data

A time you took a technical problem from ideation through to a delivered solution

Working with non-engineering stakeholders (PM, data scientist) to define data requirements

Googleyness/behavioral: navigating ambiguity, driving without authority

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