← Back to Directory

Google interview notes, page 180 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

Jun 2026
Google SWE interview with a calendar scheduling problem that looks straightforward until you start thinking about overlapping busy intervals, merging, and edge cases. Clean algorithmic problem but there's more to it than a first glance suggests.
  • Given a working window and a list of per-participant busy intervals, find all maximal time slots where every participant is simultaneously free and the slot is at least a given minimum duration long. Intervals are half-open and may overlap or be out of order.

“My first instinct was to iterate per-person and intersect free windows, which works but gets messy fast when intervals overlap within a single person's schedule.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE interview with a graph connectivity problem that looks like a Union-Find warmup until unfriend events show up and suddenly you're having a very different conversation.
  • Given N people (IDs 0 to N-1) and a list of timestamped logs where each log records a 'friend' or 'unfriend' action between two people, find the earliest timestamp at which all N people are connected in a single group transitively. Return -1 if they never all connect.

“Started with Union-Find, felt good about it, then they asked about the unfriend events and I kind of froze.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at Google focused on Google Web Answers. Two questions, both connected, and the second one about publisher implications is where things got uncomfortable for me.
  • If you were the PM for Google Web Answers, what metrics would you prioritize?
  • What would the implications be for site publishers if Google Web Answers succeeded? Would they be happy with your product?

“I went straight to user-facing stuff: query satisfaction, zero-click rate, answer accuracy.”

View Post

Google·Machine Learning Engineer·Technical Phone Screen

Jun 2026
One ML/AI round at Google for an MLE role. The recruiter had me pick a specialization going in, but the actual interview ignored that completely and just went off my resume the whole time.
  • Could your research projects be applied to any Google products, and if so, how would that work?

“This was the closer and it's the one I keep replaying.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE interview, second round. A tree traversal coding problem that looked simple on the surface but turned into a longer conversation about implementation choices than I expected.
  • Given two APIs, one that returns the children paths of a directory and one that deletes a file, implement a function that deletes an entire directory recursively.

“The core algorithm is just DFS, so I got through the implementation pretty fast.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview, one question about sunsetting Gmail. Pretty short session but the question itself took a while to unpack.
  • You're a PM at Google. How would you go about sunsetting Gmail?

“My first instinct was to panic a little because Gmail has like 2 billion users, so the stakes feel absurd.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview, one question about improving a core product. Pretty stripped down as far as interview reports go, but the question itself is a classic and worth thinking through.
  • How would you improve Gmail?

“Classic product sense question and I still fumbled the scoping part.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Got a product strategy question at Google about Tesla's autopilot pricing. Pretty focused session, just the one case.
  • Tesla currently charges a one-time upfront fee for its autopilot feature. Would you recommend switching to a subscription model instead?

“I went straight to the revenue math and kind of forgot to anchor on the customer side first.”

View Post

Google·Technical Program Manager·Onsite - System Design / Architecture

Jun 2026
Google TPM system design round, one meaty question about data center fault handling. Pretty open-ended and I spent the first few minutes just trying to figure out what scope they actually wanted.
  • Design a technical system that automatically detects and replaces faulty hardware components in a data center.

“I jumped straight into fault detection and kind of ignored the replacement logistics side for too long.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Google SWE coding round with a graph/shortest-path problem that had two parts. The second part is where things get interesting and a bit tricky.
  • You're given a graph of delivery stops, a start, an end, and a list of dangerous stops. First, find the shortest path that avoids all dangerous stops entirely, returning -1 if none exists. Second, find the shortest path that passes through the fewest dangerous stops possible.

“Part one felt manageable, just run Dijkstra and skip any dangerous node during traversal.”

View Post