← Back to Directory

Google interview notes, page 66 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·Technical Phone Screen

May 2026
Google SWE interview with a classic array problem. Nothing too wild but the pressure of it being Google makes even straightforward questions feel heavier than they should.
  • Given an array of integers and a target value, find whether any combination of elements sums to that target.

“Went with two pointers after sorting, which works for pairs but I fumbled when they pushed on subsets.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google product design interview, just one question about designing an ATM specifically for airports. Sparse on details but the constraint made it more interesting than a generic ATM prompt.
  • How would you design an ATM specifically for airport environments?

“The airport constraint is the whole thing here.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Google for a software engineer role. Just one question but they really sat with it, wanted the full story not just a quick resolution.
  • Tell me about a time you and a teammate disagreed on a technical or product decision. What was the disagreement, how did you work through it, and what happened?

“I had a decent story ready but I think I spent too long on the setup and not enough on how we actually resolved it.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a product analytics question that sounds deceptively open-ended until you realize how much ground you're expected to cover.
  • Name three software or hardware products you've started using in the last three months. The interviewer picks one and asks you to walk through how you'd track user engagement with it, including what factors the company should weigh.

“The part that tripped me up was the 'last three months' constraint.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

May 2026
Google SWE coding round with a hard backtracking problem. The variant twist on a classic LC problem made it feel less like rote prep and more like they wanted to see if you actually understood what was happening under the hood.
  • Given a string of digits and a target integer, insert +, -, or * operators between any adjacent digits (without reordering or skipping digits) so the resulting expression evaluates to the target. Return all valid expressions. Numbers in the expression cannot have leading zeros except for a standalone '0'.

“The leading zero constraint is where I tripped up first.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

May 2026
Coding round for a Gemini team SWE role at Google. One meaty algorithmic problem that looked like a histogram variant but had enough wrinkles to trip you up if you hadn't seen the recursive painter pattern before.
  • Given N adjacent fence planks each with a height, find the minimum number of paint-roller operations to cover the entire fence. Each operation costs 1 and is either a full vertical stroke on one plank, or a horizontal stroke across a contiguous range of planks at some height h (only valid if every plank in that range is at least h tall).

“I recognized the histogram shape pretty fast but got stuck translating that into the recursion.”

View Post

Google·Software Engineer·Onsite - Product Sense / Strategy

May 2026
Product design interview at Google for a designer role, one question about designing a UI for a doctor-facing consultation app. Pretty open-ended, which I wasn't fully prepared for.
  • Design the UI for a consultation app intended for doctors.

“I jumped straight into screens without spending enough time on the user.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE interview with a grid-based combinatorics problem. The question looked like a puzzle at first glance but turned into a pretty involved backtracking exercise once you started thinking about the constraints.
  • Given a 3x3 keypad lock screen with 9 keys, count the number of valid unlock patterns of length k where m <= k <= n. A valid pattern uses distinct keys connected in sequence, and if a line between two consecutive keys passes through another key, that key must have already been visited.

“The 'passing through' constraint is where I stumbled.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Interviewed at Google for a product role and got hit with a delivery operations case out of nowhere. Not a lot of context to go on, but it was a solid problem-solving exercise.
  • You're running a food delivery platform and delivery times have been increasing. How do you diagnose and address this?

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

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a single product design question about building a birthday celebration app. Pretty open-ended and I wasn't totally sure how deep they wanted me to go on the social vs. utility angle.
  • How would you design a mobile app focused on celebrating birthdays?

“I went straight to user segments, which in hindsight was fine but I probably spent too long on personas before getting to the actual product.”

View Post