← Back to Directory

Google interview notes, page 176 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
Went through the full Google onsite loop for a software engineer role. Three technical rounds plus a behavioral component. The geometry-heavy hard problem in round three was rough but I kept talking the whole time, and the fourth round went really well with a linear time optimization. Waiting to hear back now.
  • Solve a hard algorithmic problem involving geometric concepts.
  • Solve a coding problem and then optimize your solution to run in linear time complexity.
  • Describe specific situations that demonstrate your values and how you handle hypothetical workplace scenarios.

“Not going to sugarcoat it, geometry problems are not my comfort zone.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Google SWE coding round, one question the whole time, interval scheduling. Spent a decent chunk of the session just clarifying the problem before writing a single line, which felt risky but probably saved me from going down the wrong path.
  • Given a set of meetings and a number of available rooms, assign each meeting to a room such that the room with the smallest index is always preferred when multiple rooms are free. Return the room that held the most meetings.

“The two-heap setup is the move here: one min-heap tracking free rooms by index, another tracking busy rooms by end time.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Google for a software engineer role. Just one question but they really sat with it, so come prepared to actually talk through the details.
  • Tell me about a time you went above and beyond what was expected of you. What was the situation, what motivated you to do more, and what effect did it have on the team or product?

“I had a story ready but partway through I realized I was leaning too hard on what I did and not enough on why I did it.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Google behavioral round, one question about leadership and mentorship. Pretty standard but the concrete example requirement tripped me up more than I expected.
  • What makes a good leader or mentor? Walk through a specific example of a leader or mentor who demonstrated those qualities, and describe the effect it had on you or your team.

“I had an answer ready but the 'concrete example' part is where I fumbled a bit.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview, one question about designing for low connectivity. Short session, not much context given beforehand.
  • How would you improve the smartphone experience for users who have limited or no data connectivity?

“My first instinct was to jump straight to offline mode features but that felt too obvious so I tried to reframe around who actually suffers most from this.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE coding round, one question the whole time, a twist on a classic LeetCode problem. The variant flipped the usual objective which tripped me up for a minute before I got my footing.
  • Given a non-negative integer as a string and an integer k, remove exactly k digits so the remaining digits form the largest possible number.

“It's basically the remove-k-digits problem but inverted.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview with a product launch question focused on a digital library. Pretty open-ended, which sounds nice until you're actually sitting there trying to figure out where to start.
  • How would you approach launching a product for a digital library if you were a PM at Google?

“I started with user segmentation which felt right, but I spent way too long on it and barely got to distribution strategy before time was up.”

View Post

Google·Data Scientist·Technical Phone Screen

Jun 2026
Data Scientist interview at Google centered on a meaty product analytics case about Google Meet reliability. One question, but it had a lot of layers: diagnosis, impact quantification, and roadmap trade-offs all bundled together.
  • Enterprise clients are reporting frequent disconnects on Google Meet. Walk through how you'd diagnose the root cause end-to-end, estimate the business impact on enterprise contract renewals, and decide whether to fix the existing bug or build something new.

“This question is sneakily three questions stitched together and I underestimated that going in.”

View Post

Google·Machine Learning Engineer·Technical Phone Screen

Jun 2026
A technical phone screen for an ML Engineer role at Google that was basically one long coding problem about probability-weighted sampling. The question had a lot of layers to it and I didn't expect them to push so hard on the testing angle.
  • Given a list of distinct integers and a corresponding list of probabilities that sum to 1, implement a Python generator that yields values indefinitely according to the given distribution. Your solution should validate inputs, handle floating-point edge cases, and use an efficient sampling approach. Then discuss the time and space trade-offs of your implementation and write unit tests including seeded deterministic checks and statistical distribution verification.

“This one had way more surface area than I expected from a single question.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview with a classic e-commerce metrics drop scenario. One question, pretty open-ended, and I definitely underestimated how structured my answer needed to be.
  • You're a PM at an e-commerce company and sales have dropped 7% over the past few days. How do you figure out what's going on?

“I jumped straight into hypotheses and the interviewer kind of just stared at me.”

View Post