← Back to Directory

Google interview notes, page 116 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·Product Manager·Onsite - Product Sense / Strategy

May 2026
PM interview for the Pixel team at Google, one question about justifying a budget phone launch. Pretty classic product strategy framing but with enough specifics to make you actually think.
  • You're a PM on the Pixel team. What would justify launching an affordable entry-level Pixel phone?

“I went straight to market share and new user acquisition, which felt right but I kind of ignored the brand risk angle until they pushed back.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

May 2026
Google SWE interview focused on permutations. Not much to go on but it was a coding round and the topic was classic algorithmic territory.
  • Generate all permutations of a given array or string.

“Permutations is one of those problems where you either know the recursive backtracking pattern cold or you're drawing blanks on a whiteboard.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Product sense round at Google for a PM role. One question, straightforward on the surface but it opens up fast once you start pulling at it.
  • You've received user feedback that Yelp's restaurant recommendations feel too generic and not personalized. How would you approach this problem?

“I jumped straight to solutions and had to walk it back.”

View Post

Google·Machine Learning Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Google for an ML Engineer role. Just one question but they really sat in it with you, lots of follow-ups about specifics.
  • Tell me about a time you improved a process rather than a product outcome. Walk through what the original process looked like, what was painful about it, how you spotted the opportunity, what you proposed and pushed through, how you got people on board, and what the measurable impact was on velocity, quality, or morale.

“This one tripped me up more than I expected.”

View Post

Google·Product Manager·Onsite - Behavioral / Leadership

May 2026
Went through a behavioral round for a PM role at Google, and it was pretty much what you'd expect: leadership principle territory, one question about creativity.
  • Can you tell me about a time you did something creative?

“I fumbled this more than I expected.”

View Post

Google·Software Engineer·Hiring Manager Screen

May 2026
Interviewed at Google and got hit with a budget overrun scenario. Pretty short experience to write up, but the question itself made me think more than I expected.
  • If a project you're managing goes over budget, what do you do?

“I fumbled this a bit.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE coding round, one algorithmic problem about grouping two-digit integers by their digit composition. Pretty focused session, just the one problem with some back-and-forth on the approach.
  • Given an array of two-digit integers (10-99), group numbers that share the same digits regardless of order. Return the size of the largest such group. For example, 12, 21, and any other permutation of those digits belong together.

“The example they gave makes it click pretty fast: 12 and 21 are the same group, 34 and 43 are the same group.”

View Post

Google·Machine Learning Engineer·Technical Phone Screen

May 2026
Google ML interview, one question about batch vs real-time prediction tradeoffs. Short and focused, felt more like a screen than a deep dive.
  • Give an example of a use case that suits batch processing, and another that requires real-time predictions.

“I went with product recommendations for batch (run nightly, serve from a cache) and fraud detection for real-time.”

View Post

Google·Software Engineer·Onsite - Multi Round

May 2026
Google onsite at Mountain View, two coding rounds back to back. First one went really well, second was rougher but not a disaster. Still waiting to hear back and genuinely not sure which way it goes.
  • Find the shortest path in a graph using BFS, then solve two follow-up variations with additional constraints.
  • Given a binary tree, find the maximum path sum (or a problem of similar structure and difficulty).

“This went about as well as an interview can go.”

View Post

Google·Machine Learning Engineer·Technical Phone Screen

May 2026
Interviewed for an ML engineer role at Google, pretty standard technical screen with at least one project deep-dive question.
  • Walk me through a machine learning project you've worked on.

“Picked a project I knew well but probably over-explained the data pipeline and ran out of time before getting to model evaluation, which is usually what they actually care about.”

View Post