Build customer-facing serverless networking infrastructure handling millions of packets per second at Google Cloud

This role is on Google Cloud's Serverless Networking team, building highly scalable, customer-facing connectivity and security infrastructure across all layers of the stack. It requires 5 years of software development experience, 3 years building large-scale infrastructure/distributed systems/networks, and at least 1 year of software design and architecture experience — squarely a senior IC role with real ownership over service-to-service communication models.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Large-scale distributed systems and networking infrastructure
Serverless connectivity and security architecture
Service-to-service communication models at scale
Design reviews and technology tradeoff decisions
Code review and engineering best practices

Common question themes

Describe a large-scale infrastructure or networking system you built and its bottlenecks

Walk through a design review you led — what alternatives did you consider

How do you approach code review and enforcing best practices across a team

Tell me about triaging and resolving a production issue affecting network/service quality

How would you reason about reliability vs. simplicity tradeoffs in serverless networking

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