← Back to Directory

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

May 2026
Behavioral round at Google for an ML Engineer role. Just one question but they really wanted to dig into the specifics of how you handle interpersonal friction at work, not just the happy ending version.
  • Tell me about a time your work was blocked by a dependency on a colleague. How did you handle it, and what happened to the relationship afterward?

“I had a decent story ready but I fumbled the middle part where they want to hear about the actual unblocking attempts.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Google, just one question but they really sat in it with you. The whole conversation was about conflict with senior folks, which I thought would be quick but ended up being a 20-minute deep dive.
  • Tell me about a time you had a significant disagreement with a senior engineer, tech lead, or manager. How did you handle it, and what happened?

“I went in thinking I'd tell a clean story about a technical disagreement where I turned out to be right.”

View Post

Google·Software Engineer·Recruiter / HR Screen

May 2026
Behavioral screen at Google for a SWE role, pretty short, just one question about what drives you.
  • What are you passionate about?

“Stumbled on this more than I expected.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a product sense case about X-ray analysis software. Single question, fairly focused, but it pushed into territory I wasn't fully prepped for around technical constraints versus user experience tradeoffs.
  • You're the PM for an X-ray analysis software product. Users are complaining about slow result processing times. How do you address this?

“I went straight to solutions which was probably the wrong move.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google coding interview, one question about binary strings. Pretty algorithmic, felt like a dynamic programming setup once I stopped overthinking it.
  • Given a number N, find all N-digit binary strings that contain no two consecutive 1s.

“Took me a minute to see the structure.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Got a conceptual compression question at Google that sounds deceptively simple but has a lot of moving parts if you actually think it through.
  • Why can a video file be compressed to a much smaller relative size compared to a still image?

“I started talking about codecs and then kind of wandered into bitrate territory before remembering the actual key point: temporal redundancy.”

View Post

Google·Technical Program Manager·Onsite - System Design / Architecture

May 2026
Google TPM interview with one big infrastructure question that sounds deceptively simple but opens up into a rabbit hole fast.
  • How would you plan and execute an upgrade across 5000 servers?

“I went straight to the technical side, talking about rolling updates and batch sizing, and only realized halfway through that they probably wanted to hear about coordination, stakeholder communication, and rollback planning just as much.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Interviewed at Google for what seemed like a software engineering role. Two questions, one on Android internals and one on backend design. Short session but not easy.
  • Walk me through how an Android application works under the hood.
  • Design the backend system architecture for a large-scale application.

“I started with the Activity lifecycle and kind of just...”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

May 2026
Google SWE coding round with a string matching problem that looked deceptively simple but had some tricky edge cases to think through.
  • Given a dictionary of words and a 'jammed' input string (where any character in a word may be repeated consecutively any number of times), return all dictionary words that could have produced the jammed string.

“My first instinct was to just regex it, like collapse consecutive duplicate characters in the jammed string and compare.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

May 2026
Interviewed at Google, looks like a system design or technical round based on the question. Not much context to go on but the one question they asked was actually pretty interesting to think through.
  • How does communication between Mars and Earth work?

“This is the kind of question where you either freeze or you lean in.”

View Post