← Back to Directory

Google interview notes, page 140 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 - Behavioral / Leadership

Jun 2026
Behavioral round at Google for a software engineer role. Just one question but it had some weight to it.
  • Tell me about a project or decision you wish you had handled differently. What went wrong, what would you change, and how did it shape the way you work now?

“I had a story ready but it came out too polished and I could tell they wanted something messier and more real.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Google SWE coding round, basically a calculator problem that sounds easy until you actually have to handle all the garbage edge cases they throw at you. Spent a lot of time at the whiteboard before writing a single line.
  • Implement a string expression evaluator that handles non-negative integers and the operators +, -, *, / with correct operator precedence, plus edge cases like empty input, whitespace-only strings, trailing operators, and division by zero.

“The base problem is basically a known leetcode question but they layered on a bunch of extras.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Had a PM interview at Google that basically came down to one product metrics question about BART. Short session, not a lot of back-and-forth, left feeling like I probably could've gone deeper.
  • How would you define and measure success metrics for BART (the transit system)?

“I started with ridership and on-time performance, which felt obvious the moment I said it out loud.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE interview with a graph problem that started straightforward and then got a follow-up twist that actually wasn't as bad as I expected.
  • Given a weighted graph with non-negative edge weights, a start node S and a target node T, determine if T is reachable from S and if so return the shortest distance. Return -1 if not reachable.
  • Follow-up: now there's a mandatory waypoint node K that the path must pass through. Find the shortest path from S to T that goes through K, or return -1 if no such path exists.

“Classic Dijkstra setup.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google product design interview, one question about building a VR product for people with disabilities. Pretty open-ended, which sounds fun until you're actually sitting there trying to figure out where to start.
  • Design a virtual reality product for people with disabilities.

“I spent too long trying to pick the 'right' disability to focus on instead of just picking one and going deep.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE coding round, one dynamic programming problem. Pretty standard stuff but it's the kind of question where you either see it immediately or you don't.
  • Given an array of non-negative integers where each value represents money in a house, find the maximum amount you can collect without taking from two consecutive houses.

“Classic DP problem and I knew it, which was both good and bad.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Interviewed for an EM role at Google, got asked the classic leadership style question. Not much else to report.
  • How would you describe your leadership style?

“Blanked for a second on this one, which is embarrassing given how often it comes up.”

View Post

Google·Product Manager·Onsite - Behavioral / Leadership

Jun 2026
Google PM behavioral round, pretty focused on self-awareness and how you handle being wrong. Two questions, both variations on the same theme really, one broad and one with a bunch of follow-ups that dig into the specifics.
  • Tell me about a time you made a mistake.
  • Describe a situation where you were completely convinced you were right about something as a PM, but turned out to be wrong. Walk me through when you realized it, what you did next, who you told, how they reacted, and what you took away from it.

“Thought I had a solid story ready but the follow-up silence after I finished felt long.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google coding interview for a software engineer role, centered on a text wrapping problem that looked straightforward but had a bunch of edge cases hiding in it. The kind of question where you think you're done and then they ask about one more thing.
  • Given a string of text and a maximum line width (in characters), calculate how many lines are needed to display the text. You must wrap only at whitespace boundaries, respect explicit newline characters, and handle leading, trailing, and extra internal whitespace. Also discuss what happens when a single word is longer than the max width.

“I started okay, got the basic word-wrapping loop down pretty fast.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google interview with a geometry/math puzzle that turned into a surprisingly deep design discussion. The question sounds like a brain teaser but they really wanted to see how you reason through tradeoffs and generalize solutions.
  • Given a square, divide it into N regions of equal area. Walk through multiple approaches, discuss constraints on cut shapes, and explain how your strategy handles arbitrary values of N including odd ones.

“I started with parallel slices because that felt obvious, N vertical cuts, done.”

View Post