← Back to Directory

Google interview notes, page 149 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·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Google ML Engineer interview, domain-specific AI/ML round focused on agent systems. Started with a project deep dive then moved into a diagnostic question about agent performance. Pretty technical throughout.
  • Walk me through a project you've worked on involving AI agents.
  • If an agent isn't performing well, how would you go about diagnosing what's wrong?

“I was working on agents at the time so this felt like home turf.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Google for a software engineer role. The whole thing was one big question about building a task scheduling system, and it went pretty deep pretty fast.
  • Design a task scheduling system that supports task dependencies, persistent storage, scheduling policies, and long-running tasks. Cover data models, APIs, execution engine, fault tolerance, backpressure, worker heartbeats, and stuck task handling. Also discuss scaling, multi-tenant isolation, and observability.

“This is a monster of a question and I did not pace myself well.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Went through a product strategy question at Google centered on Waymo. Just the one question but it branched out in a lot of directions fast.
  • How would you decide whether to show ads on Waymo self-driving cars?

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

View Post

Google·Software Engineer·Hiring Manager Screen

Jun 2026
Google EM interview, one question about communicating roadmap and mission to the team. Pretty standard leadership screen but it made me think harder than I expected about how I actually do this day to day.
  • How would you communicate a project's roadmap and mission to your team?

“I rambled a bit about all-hands and docs before landing on something more concrete about connecting individual work to the bigger picture.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE interview with a system design/coding hybrid question about managing multiple user timers on top of a single underlying timer API. Pretty tricky constraint-based problem that forced you to think carefully about data structures and edge cases rather than just slapping a heap on it and calling it done.
  • You have a Timer class with access to only one underlying system timer at a time. Implement setNewTimer(timestamp) so that multiple user timers can be outstanding simultaneously, with handleTimer() firing correctly for each expired timer. Discuss data structures, complexity, and edge cases like duplicate timestamps and overrides.

“My first instinct was a min-heap keyed on timestamp, which is the right call, but I fumbled explaining why you need to reschedule the system timer every time setNewTimer is called with something earlier than the current head.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview with a single scenario question about a product launch that's showing bad signals a month out. Pretty stressful question to sit with, no real right answer.
  • Your team is a month away from launching a strategic app. Internal feedback and metrics (including CSAT) are below target. What do you do?

“I went straight to 'delay the launch' and the interviewer just kind of waited, like they wanted more.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Google SWE coding round, one algorithmic problem about range queries on parity patterns. Pretty clean problem once you see the prefix sum trick, but I spent way too long trying to brute force it before the hint clicked.
  • Given an integer array and a set of range queries [l, r], determine for each query whether the subarray has strictly alternating parity between adjacent elements. Preprocess the array so every query can be answered in O(1).

“My first instinct was to just iterate through each query range and check adjacent pairs, which is obviously too slow when there are a lot of queries.”

View Post

Google·Product Manager·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Google for a PM role. Just the one question from what I can tell, but it was a meaty one that took up most of the time.
  • Tell me about a time you took on an entrepreneurial initiative, either at work or in your personal life.

“I had a story ready but it felt a bit thin under pressure.”

View Post

Google·Software Engineer·Hiring Manager Screen

Jun 2026
Interviewed for a solutions architect role at Google, just the one question I can remember clearly. Pretty standard stuff but it still tripped me up a bit.
  • How do you measure the success of a project?

“I fumbled around with some generic answer about deadlines and stakeholder satisfaction.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at Google with a market entry and operations case question. Pretty classic structure but the second part about kiosk ratios threw me off a bit.
  • A major Canadian grocery chain wants to open its first location in Montreal. Should they do it, and if so, what should the ratio of self-checkout kiosks to traditional cashier lanes be?

“Two-part question and I spent way too long on the first part.”

View Post