← Back to Directory

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

Jun 2026
PM interview at Google, just the one question about Google Calendar. Pretty standard product metrics territory but it's deceptively open-ended once you start pulling on the thread.
  • How would you measure the success of Google Calendar?

“I went straight to DAU and event creation volume and then kind of stalled.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Google for a software engineer role, just the one question about going beyond your job description. Pretty standard but I fumbled it more than I expected.
  • Tell me about a time you took on responsibilities that were outside your defined role.

“I had a decent story ready but I kept second-guessing whether it was impressive enough for Google.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE interview with a pretty gnarly low-level math problem and a follow-up LC problem. The coding round pushed into bit manipulation territory which I wasn't expecting from what looked like a simple multiplication question.
  • Implement a product(int a, int b) function that returns a * b using only the operators +, ++, --, %, and >>. Write both a recursive and an iterative version, handle negatives and zero, and discuss the time complexity.
  • Follow-up: given a positive integer n, find the minimum number of operations to reduce it to 1, where each operation is either divide by 2 (if even), or add 1 or subtract 1 (if odd).

“The basic iterative version came to me fast, just add a to itself b times.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Got a Google SWE coding question involving task scheduling on a 24-hour wraparound timeline. The tricky part was that tasks could span midnight and even run longer than a full day, which made the naive interval overlap approach break down pretty fast.
  • Given a list of tasks defined by a start time (in minutes, 0 to 1439) and a duration (which can exceed 1440 minutes), find the minimum number of servers needed so no two tasks run simultaneously on the same server. Tasks wrap around the 24-hour cycle and run continuously.

“The wraparound is what gets you.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE coding round, one question on meeting room scheduling. Pretty standard interval problem but the edge cases are where things get interesting.
  • Given a list of meeting time intervals [start, end], find the minimum number of conference rooms needed so no two overlapping meetings share a room.

“I went with a min-heap on end times, which clicks once you realize you only care whether the earliest-ending meeting has freed up by the time the next one starts.”

View Post

Google·Product Manager·Onsite - Cross-functional / Panel

Jun 2026
Google PM interview, one question about handling messy stakeholder situations with no clear north star. Pretty standard for this type of role but still tricky to answer well under pressure.
  • How would you manage a project where stakeholders have conflicting opinions and the goal itself isn't well defined?

“I fumbled the opening a bit because I went straight into 'align on a shared goal' which felt too textbook.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Google SWE interview that went deep into sequence problems. The follow-up extension was the real test and I was not fully prepared for how far they'd push it.
  • Given N subsequences, determine whether they can all be subsequences of a single common parent sequence. If yes, construct or describe such a parent.

“This is the generalized version of a two-subsequence problem and it's a lot nastier.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Interviewed for a product designer role at Google, got one behavioral question about handling pushback from leadership. Pretty standard but it's the kind of thing that trips you up if you haven't thought it through beforehand.
  • How would you handle pushback from upper management on a project you're leading?

“I fumbled the opener a bit, started talking about 'aligning stakeholders' which felt too buzzwordy even as I was saying it.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE coding round, one algorithmic problem about merging intervals. Pretty standard stuff on the surface but the problem statement was dressed up in a space theme which threw me off a bit at first.
  • Given a list of pairs where each pair defines the center and radius of a planet's gravitational zone, return the ranges of positions that are safe to travel through (i.e., outside all gravitational zones).

“Took me a minute to strip away the space theming and realize this was just a merge intervals problem.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google product strategy interview with a classic market entry question. Not much context to go on but the question itself is a solid case.
  • Should Google enter the ridesharing market?

“This one looks straightforward but there's a lot to unpack.”

View Post