Google L4 Software Engineer Interview Experience — Sunnyvale Onsite, No Hire Despite Optimal Solutions

Google·Software Engineer·Jun 2026
OnsiteRejectedeasy

I got a bad feeling at the onsite from the start, and sure enough, in the end I got a no hire even though I got optimal solutions on both questions plus the follow-ups. The stated reason was lack of communication. I feel like I got screwed, because the whole time I clarified everything first and then talked while I wrote, and the phone screen had explicitly said my communication was outstanding.

One round was a DFS question wrapped in an OOD design, which was fairly easy. The only real catch was that you have to handle possible cycles. You design a class that stores a database and does string replacement, replacing all the variable names inside, but you also have to handle variable names that are nested inside other variable names.

Another round was a variation of LeetCode 243. The follow-up was to write a class implementing a few specific methods, for example checking whether two words are anagrams and so on. Not complicated.

A week later I got a call from the recruiter saying lack of communication. They didn't give any more specific feedback, and said they were moving on.

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
Onsite
Outcome
Rejected
Difficulty
easy
Interview date
Jun 2026
Questions from this interview
2 questions

Real Google interview experiences

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

All 153 Google interview experiences