Google Software Engineer Interview

Google · L3 Software EngineerOffer

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

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

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

Google · L3 Software EngineerNo offer

A second-attempt candidate cleared Google's phone screen and moved to a four-round technical onsite plus a behavioral round in Seattle. Rounds covered binary search, tree traversal, a trie-based word game, and grid BFS; the candidate identified the first onsite round, a binary-search counting problem, as the likely reason the loop ended without an offer.

Interviewed September 2019 · Seattle, WA

Google · L3 Software EngineerOffer

A candidate describes an accelerated, referral-adjacent path to a Google L3 Software Engineer offer in Bangalore: a phone screen, five virtual onsite interviews, hiring-manager calls, and reflections on how they prepared.

Interviewed August 2020 · Bangalore, India

Google · L3 Software EngineerOffer

A candidate walks through a full Google onsite loop for an L3 role, covering a behavioral round, an Android-focused system design discussion, and three separate coding rounds, and reflects on why the final level landed below what they had hoped for.

Interviewed October 2019 · Not specified

Google · L4 Software Engineer, Google CloudOffer

A referred candidate interviewed for an L4 software engineer role on a Google Cloud team in Bangalore, going through a phone screen, three onsite coding rounds (the third left unfinished), and a culture conversation, only to have the hiring committee offer L3 instead of L4; the candidate obtained the compensation letter and declined the next day because the pay was below their current salary.

Interviewed 2021 · Bangalore, India

Google · L4 Software EngineerOffer

A four-year FAANG+ engineer in India ran parallel interview pipelines with Google, Microsoft, Amazon, and Uber over about six months, closing with offers from Google (L4), Microsoft (L62), and Amazon (L5), and a rejection from Uber.

Interviewed January 2021 · Not specified

Google · L4 Software EngineerOffer

A backend engineer with several years at another large tech company describes preparing for and clearing Google's L4 loop in India, after an earlier attempt had ended at the phone screen stage.

Interviewed November 2024 · India

Google · L5 Software EngineerOffer

A senior software engineer with eight years of experience went through a Google L5 loop as part of a multi-company search that also produced offers from Bloomberg and Facebook. Google waived the phone screen and moved straight to a virtual onsite of three coding rounds, a system design round, and a Googlyness round; the panel then asked for two additional coding rounds and another system design round before the process concluded in an offer.

Interviewed 2021 · Not specified

Google · Software Engineer, SDE 1Outcome unknown

A candidate who interviewed with both Microsoft and Google around the same time shares the Google SDE 1 onsite loop: a word-transformation reachability problem in one round, and a two-part round covering a grid typing-distance optimization and a set-outlier detection problem. No final outcome for the Google process was stated.

Interviewed May 2020 · Not specified

Google · Software EngineerOffer

A candidate with a nontraditional, security-and-cryptography-leaning background skipped Google's phone screen at the recruiter's suggestion and went straight to a single-day virtual onsite in March 2020, covering four coding rounds and one behavioral round. Despite Google's reputation for a slow process, the candidate heard back with a pass within two days, cleared the Hiring Committee, and received an initial offer of about $280k per year in total compensation.

Interviewed March 2020 · Remote (virtual interview due to COVID-19)

Google · Software EngineerOutcome unknown

A self-taught full-stack engineer running a wide 2020 job search got into Google's pipeline through a recruiter's cold LinkedIn message and went straight to a five-interview virtual onsite, skipping a phone screen. Feedback was mostly positive except for one round built around Dijkstra's algorithm, which the candidate had not specifically prepared for. That mixed result sent the packet to a hiring committee, which asked for two more interviews before deciding — interviews that never happened because the candidate accepted a competing offer first.

Interviewed 2020 · Remote

Google · Backend Software EngineerNo offer

A rejected Google Backend Engineer candidate in Bangalore recounts a recruiter screen, a gating elimination round, and a three-round onsite loop covering trees, tries, scheduling, and graph problems.

Interviewed April 2021 · Bangalore, India