Google L5 interview experience

Overview

Google is one of the most sought-after employers for software engineers worldwide, and its interview process is widely regarded as a benchmark for technical hiring in the industry. The company hires across multiple levels, with L5 and L6 representing senior software engineer tracks that require strong algorithmic thinking, system design skills, and demonstrated leadership. This experience outlines a candidate's journey through the Google L5 interview loop, from the initial recruiter conversation through to the final feedback call.

Interview Process

The candidate applied to a Google Software Engineer role through the company's careers page in November, primarily to assess whether the profile aligned with the L5 or L6 level. A recruiter followed up two weeks later with details of the interview loop.

The structure consisted of a single phone screen, followed by five virtual onsite rounds spread across two days. The onsite comprised three coding rounds, one system design round, and one Googleyness and Leadership round. After the initial recruiter call, the candidate received an emailed topic list covering arrays, graphs, dynamic programming, stacks, queues, Dijkstra's algorithm, and knapsack problems. The recruiter noted that the expectations centred on medium to hard problems solved in roughly 15 to 20 minutes, with correct syntax and edge cases handled.

Three weeks after the onsite, the recruiter delivered the final feedback: system design and behavioural performance were strong, while the coding rounds did not meet the bar. The candidate was told they could reapply after a year.

Technical Rounds

Phone Screen

The phone screen followed Google's well-known format of coding in a Google Doc, with no IDE, no autocomplete, and no ability to execute code. While the candidate had prepared for this environment, the experience of writing solutions in a plain document remained somewhat jarring despite prior practice. The round is a distinctive element of Google's process and is rarely used by other major technology companies.

Coding Round 1

The first onsite coding round was similar in style to a LeetCode medium difficulty problem. The candidate encountered a brief moment of being stuck, at which point the interviewer offered a hint, though the candidate ultimately resolved the issue independently.

Coding Round 2

The second coding round centred on a geometry problem. The candidate initially overcomplicated the solution by attempting coordinate transforms, when a basic trigonometric approach would have sufficed. The error was identified roughly ten minutes before the end of the round, allowing a pivot, but this came at the cost of time that should have been spent on edge cases. Following this round, the candidate expected negative feedback.