← Back to Directory

Google interview notes, page 62 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·Recruiter / HR Screen

May 2026
Interviewed for a product designer role at Google, just one question about design tools. Not much to report but figured I'd log it anyway.
  • What is your favorite design tool, and why do you prefer it?

“Pretty lightweight question but I still fumbled it a bit.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a single product design question centered on collaborative photo editing. Pretty open-ended, which I wasn't fully prepared for.
  • Design a product similar to Google Docs but for collaborative photo editing. How would you approach it?

“I went straight to features and the interviewer kind of just waited.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a single product design question focused on building something for an older user base. Pretty open-ended and I wasn't totally sure how deep they wanted me to go on the accessibility angle versus the hardware side.
  • How would you design a camera specifically for elderly users?

“I jumped straight into features and had to backtrack once I realized I hadn't defined who 'elderly' even meant.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a single product design question set 100 years out. Futuristic framing made it hard to anchor anything concrete, which I did not handle well.
  • Design an alarm clock for children, set 100 years in the future.

“The century-out framing tripped me up more than I expected.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

May 2026
Google system design round for a software engineering role. The whole session was basically one big question about ad serving, and they kept pushing on follow-ups until I ran out of things to say.
  • Design an ad serving system with a get_ads(k) method that returns the top-k ads ranked by some priority score. Walk through your class design, how you'd maintain the heap on inserts and updates, and what trade-offs you'd make around retrieval complexity.

“I went straight for a max-heap and started talking through Ad and AdStore classes before I'd even pinned down what the scoring function looked like.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google coding screen for a software engineer role. One tree problem, pretty focused session. I spent a decent chunk of time just asking clarifying questions before writing a single line.
  • Given a list of edges representing a tree, write a function that takes two node values as input and returns the distance between them.

“I front-loaded a bunch of clarifying questions before touching the code: can edges repeat, is the input guaranteed to actually form a valid tree, are both nodes guaranteed to exist, what if they're the same node.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE interview with a pretty meaty interval scheduling problem. The question had some real depth to it once you got past the surface read.
  • Given a list of on-call rotations represented as half-open intervals with a person's name and start/end times, produce a consolidated schedule where each output entry is a maximal contiguous time range with the exact set of people on-call during that period. Gaps with nobody on-call should be omitted, and output should be sorted by start time.

“My first instinct was to just sort and merge like a standard interval problem, but that breaks down the second you have overlapping people.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE interview with a graph propagation problem that looked straightforward until the same-timestamp grouping requirement came up. The problem has a few classic solution paths but the tricky part is knowing which constraints actually matter.
  • Given n people and a list of meetings (person a, person b, time t), where person 0 knows a secret and shares it with one other person at time 0, figure out who knows the secret after all meetings. The catch: meetings at the same timestamp must be processed together as a group before moving on.

“The base logic clicked pretty fast for me but I almost missed the grouped-timestamp requirement entirely.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE interview with a sentence similarity problem. Not much context to go on but it was a coding round.
  • Given two sentences, determine whether they are similar to each other.

View Post

Google·DevOps Engineer·Onsite - Multi Round

May 2026
Went through five rounds at Google for an SRE role, covering scripting, Linux internals, troubleshooting, networking, and a culture/values interview. Most rounds went well but the scripting round was shaky, and now I'm waiting on the hiring committee with my recruiter trying to build the case.
  • Write a script to solve a given problem, then extend it to handle a more complex follow-up case.
  • Describe how Linux handles a specific internal process or subsystem (e.g. memory management, process scheduling, or I/O).
  • Walk through how you would troubleshoot a production issue from symptom to root cause.
  • Explain how you would diagnose or resolve a networking problem in a distributed system.
  • Tell me about a situation where you had to navigate ambiguity or conflict on a team, and how you handled it.

“Got through the main part fine, code worked, no major issues.”

View Post