Google interview notes, page 215 of 215

FAANG / Big Tech

Most of these Google write-ups come from Software Engineers (1,167), then Product Managers (686) and Data Scientists (125). The most reported rounds are the product sense round (667), the technical phone screen (660), the behavioral / leadership round (252) and the onsite coding round (214).

2146 interview notes · updated Oct 2026

Google·Software Engineer·Onsite - Multi Round

Sep 2026

Did my Google SWE intern loop and came out of it genuinely unsure how to feel. Round one was rough in patches but round two went well enough that the interviewer said they'd support me, so now I'm just waiting and overthinking it.

Solve a medium-difficulty coding problem that involves handling two distinct conditions, one simpler and one harder, where the harder case can be reduced to the simpler one.
Solve a medium-difficulty coding problem, then modify your solution to handle a follow-up variant of the original problem.

“This is where things got messy.”

View Post

Google·Software Engineer·Technical Phone Screen

Oct 2026

First technical screen for a Google SWE internship. OOP and data structures, medium difficulty, with three follow-ups back to back. Went reasonably well but nerves were a factor and a small bug at the end left things feeling unfinished.

Design a solution to an OOP-based problem involving data structures, then extend your solution through multiple follow-up constraints.

“Hadn't touched OOP in about a year and the interviewer read the whole thing out loud instead of pasting it, so the first few minutes were rough just trying to hold all the pieces in my head.”

View Post

Google·Software Engineer·Technical Phone Screen

Oct 2026

Google SWE intern technical screen, one coding question with three follow-ups, OOP and data structures focus. Went reasonably well but ended with a small bug I couldn't squash before time ran out, so I'm sitting here wondering if that cost me.

Design and implement an OOP-based solution to a data structure problem, then extend it through multiple follow-up constraints.

“The interviewer read the whole thing out loud instead of sharing it on screen, which threw me off more than I expected.”

View Post

Google·Software Engineer·Technical Phone Screen

Oct 2026

Did a two-round Google SWE intern interview and felt pretty good about the first one, then completely fell apart on the second. The second round was graph-based and I struggled badly enough that I actually told the interviewer I thought I'd bombed it, which I'm now second-guessing.

A graph-based algorithmic problem (specific problem not disclosed).

“Couldn't get through it cleanly.”

View Post

Google·Software Engineer·Technical Phone Screen

Oct 2026

Phone screen at Google for a software engineering role that threw me completely off with a file-based string problem I had no prep for. Spent most of the call fumbling through hints and never actually wrote any code, which still stings.

Given a 4GB file, find the minimum length of a substring that does not appear anywhere in the file.

“My first instinct was brute force with hashing and the interviewer basically shut that down immediately.”

View Post

Google·Software Engineer·Technical Phone Screen

Oct 2026

Two rounds for a Google SWE intern role, both went faster than expected. The second round got weird toward the end with a problem that turned into a collaborative back-and-forth, which left me unsure whether that was a good sign or a bad one.

Solve a combinatorics-based problem (non-standard, not a typical leetcode-style prompt).
Given a tree with a specific structural property, solve the core problem and then construct a tree that satisfies that same property.

“Finished with time to spare and got a trivial follow-up that was basically one line added to my solution.”

View Post