← Back to Directory

Google interview notes, page 49 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·Hiring Manager Screen

Apr 2026
Interviewed for a PM role at Google, basically one question about what makes a good product manager. Not much to go on but here's what I remember.
  • What makes a good product manager?

“Classic opener that I somehow still fumbled.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a single product design question about expanding Maps coverage to unmapped areas. Pretty open-ended, which I wasn't fully prepared for.
  • How would you design a solution to bring unmapped places onto Google Maps?

“I jumped straight into crowdsourcing and local guides without really thinking through who actually suffers most from missing map data.”

View Post

Google·Data Scientist·Technical Phone Screen

Apr 2026
Went through a technical screen for a DS role at Google that went pretty deep into OLS inference. One question but it had like four sub-parts and felt like a grad school exam more than an interview.
  • In OLS regression, walk through how you'd test whether a single feature is statistically relevant: set up the hypothesis test and t-statistic with its exact standard error formula and degrees of freedom, explain why the test statistic actually follows a t-distribution under classical assumptions, give intuition for why using an estimated sigma makes things noisier than a Z-test, and describe how heteroskedasticity or clustered data changes the test and the reference distribution.

“This wrecked me a little.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google product design interview, one question about reimagining a city park. Pretty open-ended and I wasn't totally sure what angle they wanted.
  • How would you redesign the city park experience?

“I went straight into user segments, which felt right, but I think I spent too long on it and rushed the actual design part.”

View Post

Google·Technical Program Manager·Hiring Manager Screen

Apr 2026
TPM interview at Google with a scenario-based question about project overlap. Just the one question from what I can tell, but it packed a lot into it.
  • You're six months into a twelve-month project and you discover in a meeting that another team has been building the same thing. What do you do?

“I went straight to 'set up a sync meeting' which felt right but I think I skipped over the part where you actually figure out how much overlap there really is before doing anything.”

View Post

Google·Product Manager·Onsite - Behavioral / Leadership

Apr 2026
Google PM interview, one behavioral question about user research driving product direction. Not much else to go on but it's a classic they seem to love asking.
  • Tell me about a time when a user insight caused you to significantly change the direction of a product you were working on.

“I had a decent story ready but fumbled the 'changed the product' part.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a classic market sizing question. Pretty standard stuff but the pressure of doing it live made me second-guess every assumption I had.
  • How many restaurants are there in San Francisco?

“I started with population and tried to work down from there, something like residents per household, meals eaten out per week, average restaurant capacity and turnover.”

View Post

Google·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Google MLE coding round, one graph problem with a follow-up that actually made things interesting. Pretty standard overall but the follow-up caught me off guard in a good way.
  • Given a social network, find all friends of a given user. Follow-up: how would your solution change if users can also unfriend each other?

“The base problem was a graph traversal thing, BFS to find connected nodes.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview, product sense round. Just one question but it did enough damage on its own.
  • Pick your favorite product and propose three enhancements to it.

“I panicked a little choosing the product because I wanted something I could actually speak to deeply, not just something that sounded impressive.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Google SWE coding round, one question the whole time. The skyline problem. I'd seen it before but not practiced it enough to feel clean under pressure.
  • Given a list of rectangular buildings each defined by a left edge, right edge, and height, compute the skyline as a sorted list of key points where the visible height changes.

“I knew this problem.”

View Post