← Back to Directory

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

Apr 2026
Google PM interview with a product design question that sounds fun until you actually try to answer it. The driverless car angle adds a layer of complexity that I wasn't fully prepared for.
  • Design a ride-hailing app similar to Uber, built specifically for Google's autonomous vehicles, targeting kids under 16 as the primary users.

“I went straight into features and completely forgot to anchor on the user first.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google SWE interview that was basically a maze problem session. The base case was straightforward but the follow-up with the block conversion rule is where things got interesting and I think I almost went down the wrong path before catching myself.
  • Given an m x n grid where each cell is either free or blocked, find whether a path exists from the top-left to the bottom-right and return the length of the shortest such path.
  • Follow-up: you can convert at most one blocked cell into a free cell during traversal. Find the shortest path under this new rule.

“Standard BFS with a visited set, nothing too tricky.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Product sense round at Google for a PM role. One question, pretty open-ended, and I spent the first few minutes just trying to figure out what angle they actually wanted.
  • Design a bike-sharing or bike access program for Google's Mountain View campus.

“I jumped straight into features, which was probably the wrong move.”

View Post

Google·Software Engineer·Onsite - Multi Round

Apr 2026
Went through a coding round and a behavioral round for a software engineer role at Google in Seattle. The coding problem got solved but the follow-up ran out of time, and the behavioral side felt pretty solid. Sitting here not sure if it was enough.
  • Solve a coding problem and walk through the time and space complexity of your solution, including a follow-up variant of the problem.
  • Behavioral questions covering past work situations, with the interviewer asking follow-ups on specific scenarios.

“Got through the main problem fine and nailed the complexity breakdown.”

View Post

Google·Software Engineer·Onsite - Multi Round

Apr 2026
Went through two rounds of Google SWE interviews after 14 previous rejections at other companies. Round 1 was two back-to-back coding problems, Round 2 added a Googleyness and Leadership section plus another coding problem. Ended with an offer after HC approval.
  • Given a block of text describing a combinatorics-style problem, implement a solution and then optimize it.
  • Given a weighted graph problem, find the optimal path using an appropriate traversal algorithm.
  • Describe a time you dealt with a conflict within your team.
  • Tell me about a time you worked under a tight or unreasonable deadline.
  • How do you handle situations with significant ambiguity or unclear requirements?
  • A hypothetical scenario with a constraint that gets progressively tightened across multiple follow-ups. What's your principled approach?
  • Implement a solution using two hash maps, then analyze the space complexity and extend the solution to handle duplicate values.

“Panicked when I saw the wall of text.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a product design question focused on accessibility and underserved demographics. Pretty open-ended, which sounds nice until you're sitting there trying to figure out where to even start.
  • How would you design a supermarket specifically for elderly customers?

“I spent the first minute just listing accessibility features like wider aisles and bigger fonts, which felt shallow pretty fast.”

View Post

Google·Product Manager·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Google for a PM role. Just one question but it took up most of the time, which I wasn't expecting.
  • Tell me about a time you took initiative before anyone else did.

“I had a decent story but I think I buried the lead.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google technical phone screen, probably for a software engineering role. One question, but it had layers I didn't fully appreciate until after I hung up.
  • Print every positive integer from 1 up to 10^1000 minus 1, where numbers can have up to 1000 decimal digits. You can't use built-in big integer types, so how do you represent and increment these numbers, and what do you say when they ask why you can't actually run this?

“My first instinct was to reach for a bignum library and I had to stop myself.”

View Post

Google·Software Engineer·Recruiter / HR Screen

Apr 2026
Interviewed for a security engineer role at Google, just one question from what was shared here.
  • What draws you to cybersecurity as a field?

“Pretty standard opener but I still fumbled it a bit.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a classic infrastructure/product trade-off question. Short and focused, one question that sounds deceptively simple but has a lot of layers depending on how deep you go.
  • If you're building an app that needs to serve millions of users, would you run the ML model on the server or on the user's device? Walk through your reasoning.

“I started with latency and cost tradeoffs, which felt right, but I kept second-guessing myself mid-answer.”

View Post