← Back to Directory

Google interview notes, page 164 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·Onsite - Multi Round

Jun 2026
Completed a Google software engineer onsite with two coding rounds and a behavioral round. First coding round went smoothly with time to spare for follow-ups, but the second one fell apart on implementation despite having the right algorithm. Still waiting to see how the packet reads overall.
  • Given an interval or line-sweep style problem, explain a brute-force solution and then optimize it. Walk through tradeoffs and handle follow-up modifications.
  • Design and implement a line-sweep algorithm for a given problem, explaining your approach and the tradeoffs before writing the code.
  • Behavioral questions assessing collaboration, adaptability, and culture fit.

“This was the good round.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview, just the one question about improving Drive. Short session, product sense focus, not much else to it.
  • How would you improve Google Drive?

“Familiar product, which actually made it harder.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE interview with a tricky black-box debugging puzzle that pushed well beyond brute force. The core challenge was finding two 'poisoned' test cases using as few calls as possible, and the conversation quickly escalated into algorithm design territory.
  • You have a black-box function that takes a list of test cases and returns pass or fail. Exactly two test cases are 'poisoned': the function only fails when both are present simultaneously. Given the full list, find the two poisoned test cases while minimizing the number of calls to the function. Can you do better than O(n^2)?

“My first instinct was just pair every test case with every other and call it a day.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Google SWE interview with a system design flavored coding question about a restaurant waitlist. More nuanced than a typical LeetCode problem since you had to think carefully about the tradeoffs between data structures rather than just grinding toward a solution.
  • Design a restaurant waitlist data structure supporting three operations: adding a user with a required party size, removing a user by name, and finding the first user in arrival order whose party size fits a given table capacity. The found user stays on the waitlist until explicitly removed. Walk through your data structure choices and the time complexity of each operation.

“I went with a doubly linked list to preserve arrival order plus a hashmap from user to node for O(1) deletes.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Google for a software engineer role. Pretty much a full battery of people-skills questions back to back, no technical stuff at all. Felt like they had a checklist and were just working through it.
  • Tell me about a complex project where you had to resolve conflict between teammates.
  • Describe a time you helped other people.
  • Tell me about a time you had more work than you could handle.
  • How do you decide what to work on first when you have competing priorities?
  • What's something you've learned recently?
  • Tell me about a time you gave feedback to someone. How did they react?
  • What would you do if a colleague took credit for work that the whole team contributed to?

“This one I actually had a decent story for, but I rambled.”

View Post

Google·Software Engineer·Onsite - Product Sense / Strategy

Jun 2026
Interviewed at Google for what seemed like a product or strategy role. One question about Amazon Prime growth data, which felt oddly specific for a Google loop.
  • What drove the sharp growth in Amazon Prime subscribers between 2008 and 2009?

“Wasn't expecting a case about a competitor's subscription product.”

View Post

Google·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Google ML Engineer interview with a graph problem that was pretty much a textbook Dijkstra question, plus a follow-up that added a twist. Nothing too wild but the follow-up is where things got interesting.
  • Given a weighted graph, determine whether a source node can reach a target node, and if so, find the shortest distance between them.
  • Follow-up: how would you modify your approach if the shortest path is required to pass through a specific intermediate node?

“Straight Dijkstra.”

View Post

Google·Data Analyst·Technical Phone Screen

Jun 2026
Interviewed at Google for a data or analytics role, and the main question was about identifying the lowest earning employees from a dataset. Pretty straightforward SQL territory but the details matter.
  • Given an employee dataset with salary information, how would you find the employees with the lowest earnings?

“Went with a basic ORDER BY and LIMIT approach first, then they pushed back asking how I'd handle ties.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google phone screen, algorithms focused. One question the whole time, but it had layers and they kept pushing until I got to the frequency-based optimization. Not a bad experience, just intense for what felt like a simple premise.
  • Design an algorithm to guess an unknown 5-letter word using only a function that checks whether a specific letter appears at a specific position. Start with brute force, then optimize using letter and position frequency data from a dictionary.

“I started with the obvious: just iterate through all 26 letters for each of the 5 positions, call check() each time, done.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview with a classic product design question. Nothing too wild but it took me a minute to find a good angle on it.
  • How would you improve the movie watching experience?

“I went too broad at first, started rattling off features before even defining who the user was.”

View Post