← Back to Directory

Google interview notes, page 29 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·Technical Phone Screen

Apr 2026
Security engineer screen at Google, one technical question about Windows internals. Pretty focused session, no fluff.
  • How does malware achieve persistence on Windows machines?

“This is the kind of question where you can go wide or deep and it's genuinely hard to know which they want.”

View Post

Google·Machine Learning Engineer·Recruiter / HR Screen

Apr 2026
Recruiter screen for an ML engineer role at Google. Not much to report, just the usual opener to kick things off.
  • How did you first find out about this position?

View Post

Google·Product Manager·Onsite - Behavioral / Leadership

Apr 2026
Interviewed for a PM role at Google and got hit with an ethics scenario question. Pretty standard behavioral round but it made me think harder than I expected.
  • If you found out a colleague was doing something unethical, what would you do?

“I went straight to 'I'd escalate to my manager' and the interviewer just kind of waited, so I kept talking and dug myself into a weird hole about company policy.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google SWE coding round, one problem, tree traversal. Pretty standard stuff but I fumbled around more than I should have before landing on the right approach.
  • Given a binary tree, return the node values visible from the right side (i.e., the rightmost node at each level).

“I knew it was a level-order traversal thing pretty quickly, but I wasted maybe two minutes half-explaining DFS before catching myself.”

View Post

Google·Software Engineer·Onsite - Product Sense / Strategy

Apr 2026
Google business analyst interview with a market sizing question about grocery delivery. Pretty standard case format but the specifics tripped me up more than I expected.
  • How would you estimate the market opportunity for a grocery delivery service launching in a new city?

“I went straight for a top-down approach and started throwing out population numbers, which felt okay at first.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Round 2 at Google for a software engineer role. The coding question was a parser problem that escalated quickly into variadic argument support. Not a bad round but definitely not a comfortable one either.
  • Write a function that evaluates a nested expression string like 'add(2, mul(3, pow(4, 5)))' supporting addition, subtraction, multiplication, division, and exponentiation.
  • Extend your solution to support variadic arguments, e.g., 'add(1, 2, 3, mul(4, 5, 6))' where functions can take any number of arguments.

“I went with a tokenizer feeding into a recursive descent parser which felt right and the interviewer seemed fine with the direction.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
PM role interview at Google, one product strategy question framed as a historical scenario. Pretty lean on details but the question itself was meaty enough to chew on for a while.
  • You're a PM at Uber in 2015. How do you decide whether to roll out cash payments as an option for riders?

“This one pulled me in two directions at once.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Google system design round for a software engineering role. The whole session was basically one big question about designing a server pool manager at scale, and it went deep fast.
  • Design a service to manage a large pool of roughly 100,000 server nodes, where each node can satisfy multiple instance types. The service needs a getServer(reqNumOfServer, instanceTypes[]) API to allocate servers matching the requested types, and a returnServer(ids[]) API to release them. Walk through your data structures, indexing strategy, how you'd minimize fragmentation, handle concurrency and starvation, and what happens when nodes fail.

“This one sprawled in every direction.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google SWE coding round, one algorithmic problem the whole session. Not the hardest thing I've seen but I fumbled the setup before getting to the clean solution.
  • Given an array of two-digit integers (each between 10 and 99), find the largest subset where every number in the subset shares at least one common digit. Return the size of that subset.

“I overcomplicated this at first.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google data science or analytics interview, single question about experimental design. Pretty conceptual but it has real teeth if you haven't thought carefully about when A/B testing breaks down.
  • Describe a situation where an A/B test would not be appropriate. What type of test would you run instead, and why?

“I started rattling off the obvious cases like network effects and small sample sizes, but then blanked a bit on what to actually propose as alternatives.”

View Post