← Back to Directory

Google interview notes, page 86 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 - Behavioral / Leadership

May 2026
Google PM interview, got asked the classic engineering disagreement question. Not much else to report but it's the kind of question that sounds easy until you actually have to answer it live.
  • Tell me about a time you disagreed with an Engineering team member or team.

“I had a story ready but it came out way more passive than I intended.”

View Post

Google·Data Scientist·Technical Phone Screen

May 2026
Got a statistics concept question at Google for a DS role. Just one question but it required a pretty thorough answer covering definition, mechanism, and a worked example.
  • What is Simpson's paradox, and how can data imbalance or confounding variables produce it? Walk through a concrete example.

“I knew the textbook definition but fumbled when they pushed for a real example.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a product design question about reimagining the gas station experience. Pretty open-ended, which I was not fully prepared for.
  • How would you redesign the gas station experience?

“I went straight to EVs and charging infrastructure which felt obvious in retrospect, like half the room probably said the same thing.”

View Post

Google·Software Engineer·Onsite - Product Sense / Strategy

May 2026
Interviewed for a product design role at Google and got hit with a classic critique question about one of their own flagship products. Short session, not much to it, but the question itself has some real depth if you let it.
  • Critique Google Maps. What works, what doesn't, and how would you improve it?

“I went in thinking I'd nail this because I use Maps every day.”

View Post

Google·Technical Program Manager·Onsite - Behavioral / Leadership

May 2026
Google TPM behavioral round, one question about process improvement. Pretty stripped down as far as interviews go.
  • Tell me about a broken process at your organization and what you did to fix it.

“I went with a cross-team release coordination mess that had been causing delays for months.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Coding round at Google for a software engineer role. Pretty manageable, the main problem was basically Meeting Rooms II dressed up in a taxi dispatch scenario.
  • Given a list of taxi ride requests each with a start and end time, find the minimum number of taxis needed to serve all rides without overlap.

“Classic interval scheduling problem underneath the story.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

May 2026
Google SWE coding round, basically one classic combinatorics problem the whole time. Clean enough problem but the follow-up pressure on complexity made me second-guess myself more than I should have.
  • Given an array of unique integers, return all possible subsets (the power set) without duplicate subsets.

“I went with backtracking, include or exclude each element as you recurse down.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE interview focused almost entirely on word frequency problems, starting from a basic array version and escalating into stream processing and then a tricky non-repeating words variant. The problem kept mutating in ways I didn't fully anticipate.
  • Given an array of words and an integer k, return both the k most frequent and k least frequent distinct words. How do you handle ties?
  • Design a data structure for an unbounded word stream that supports ingesting words one at a time and querying the top-k or bottom-k most frequent words seen so far. What are the time and space tradeoffs?
  • Extend your stream design to also return the first k or last k words that are currently non-repeating, meaning words with a frequency of exactly 1, ordered by when they arrived in the stream.

“The tie-breaking part is what tripped me up a bit.”

View Post

Google·Software Engineer·Hiring Manager Screen

May 2026
Interviewed for a BA role at Google, one question about diagnosing a conversion drop. Short but the kind of question that sounds easy until you're actually in it.
  • Walk me through how you diagnosed a drop in conversion rate.

“I jumped straight into funnel analysis and forgot to first clarify what baseline we were comparing against.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with two questions, one classic estimation and one that felt more like a trick than a real product question. Pretty short session overall but the second question threw me off more than I expected.
  • Estimate the total number of potholes across the continental United States.
  • Should Google take on the responsibility of fixing all the potholes in the US?

“Went with a top-down approach: US road miles, average pothole density per mile by road type, weighted by urban vs rural split.”

View Post