← Back to Directory

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

May 2026
Google SWE behavioral round. One question, but it had a lot of layers to it and I don't think I fully landed the conflict resolution piece.
  • Tell me about a time a teammate took credit for work that was mostly yours. How did you handle it, what did you say to them or your manager, and what did you change about how you document ownership afterward?

“I had a real story for this but I fumbled the middle section.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a single product design question about building a competitor to Ticketmaster. Pretty open-ended, which I wasn't fully prepared for.
  • How would you design an online ticketing platform to compete with Ticketmaster?

“I spent the first few minutes just listing features and the interviewer kind of waited patiently until I stopped.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview, product sense round, one question about designing a car for seniors. Pretty open-ended and I wasn't totally sure how deep to go on the accessibility angle versus the tech angle.
  • How would you design a car specifically for elderly users?

“I started with user segmentation which felt right, breaking seniors into early-retired active folks versus those with more physical limitations.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE coding round, one problem the whole time. Pretty focused session, the kind where you can tell they want to see how deep you go on a single thing rather than rushing through a bunch of questions.
  • You're given two arrays and an integer k. Delete elements from the second array so that its first k elements (after deletion) have no values in common with the first k elements of the first array. Return the minimum number of deletions needed, or the resulting array.

“My first instinct was to just iterate both arrays and compare, which is obviously slow.”

View Post

Google·Software Engineer·Onsite - Multi Round

May 2026
Went through Google's early career software engineering process in the US and it was harder than expected. Four rounds total, two behavioral and two technical, and the technical side had some genuinely tricky moments. Ended up rejected, but leaving notes here for anyone prepping.
  • Given a code environment with a filesystem and a readme, identify and fix any issues in a data processing workflow.
  • Solve a constrained directed graph problem, given a vague input data structure.

“This one threw me completely.”

View Post

Google·Product Manager·Onsite - Behavioral / Leadership

May 2026
Went through a Google PM interview that was pretty much one big behavioral question about roadmap decisions. Nothing too surprising but it made me realize how much I ramble when I don't have a concrete example ready.
  • Describe a time you had to make a tough trade-off decision on a product roadmap.

“I fumbled the opening because I picked an example that was too safe.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a security role at Google, got asked a classic networking question that sounds easy but really isn't if you go deep enough.
  • Walk me through what happens, at a technical level, when you type a URL into a browser and hit enter.

“Security context changes this question a lot.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a SWE role at Google, just one question about a past project. Pretty standard stuff, nothing that knocked me sideways.
  • Walk me through a project you've worked on.

“I rambled a bit picking which project to talk about, which probably burned 30 seconds of goodwill right at the start.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

May 2026
Google system design screen focused on video streaming infrastructure. One question but it had enough depth to keep me busy for the whole session.
  • How would you reduce bandwidth consumption in a video streaming application, and what technical metrics would you track to measure success?

“I started with adaptive bitrate streaming and the interviewer seemed fine with that, but then I got a bit lost when they pushed on the metrics side.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Interviewed for a PM role at Google and got hit with the classic 'improve your favorite product' question. Short loop, product sense focused.
  • How would you improve your favorite product?

“Picked a product I actually use every day thinking that'd make it easier.”

View Post