Google Software Engineer Interview Experience — An L4 Loop Downleveled to L3

Google·Software Engineer·Aug 2026
OnsiteTechnical ScreenIn progressmedium

I recently interviewed for Google L4 R1 and R2. After the interviews, I was downleveled to L3.

Round 1

Coding: Given a file system containing directories and files, where each file has a size and each directory contains files or another directory, calculate the total entity size for a given ID that may identify either a directory or a file. It was somewhat like a wrapped version of LeetCode 339.

The follow-up was to check whether it was a valid file system. I have forgotten the specific requirements, but the implementation was somewhat like LeetCode 261.

Behavioral questions: Regular behavioral questions.

Three days later, I passed and scheduled R2.

Round 2, MTV onsite

Coding 1: An object-oriented design problem for a bookshelf containing a bookmark. It needed to support CRUD operations for books and maintain the bookmark's position.

Coding 2: LeetCode 674 plus LeetCode 3738.

One week later, I was told that the feedback was positive and that my packet would be sent to the hiring committee. Another week later, I was told that the hiring committee had approved L3, and I started team matching.

Published

Curated and edited by PracHub

Practice the questions from this interview

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Google
Role
Software Engineer
Rounds
Technical Screen → Onsite
Outcome
In progress
Difficulty
medium
Interview date
Aug 2026
Questions from this interview
4 questions

Real Google interview experiences

First-hand reports from Google candidates — the rounds, the questions they were asked, and how it went.

All 127 Google interview experiences