← Back to Directory

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

Apr 2026
Interviewed for a TPM role at Google and got a question about picking up unfamiliar technology, which sounds simple but actually took me a second to figure out what angle they were going for.
  • If you were handed a technology you'd never worked with before, how would you approach learning it, and how would you know when you'd actually learned it well enough?

“The second part of this question tripped me up more than the first.”

View Post

Google·Business Analyst·Technical Phone Screen

Apr 2026
Got a market sizing question at Google, pretty standard stuff but I always freeze up when the numbers start piling on top of each other.
  • Estimate the number of millennial homeowners in the US.

“I started with total US population, carved out the millennial age bracket, then tried to apply a homeownership rate.”

View Post

Google·Software Engineer·Onsite - Product Sense / Strategy

Apr 2026
Interviewed for a product designer role at Google and got a classic hardware-meets-UX prompt. Pretty open-ended, which was either a gift or a trap depending on how you look at it.
  • Design a remote control for a toy car.

“I spent the first minute or two trying to figure out who the user actually is, kid versus parent versus both, because that completely changes the form factor and the controls.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral screen at Google for a SWE role. Pretty short, one question about adaptability and that was the gist of it.
  • How open are you to adapting to changes?

“Felt like a warmup question but I still fumbled it a bit.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Google for a SWE role, just the one question about pushing through resistance on an idea you believed in.
  • Tell me about a time you moved forward with an idea even though others pushed back on it.

“I had a story ready for this but it felt thin once I started telling it.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Got a product sense question at Google for a PM role, focused on handling a real-world quality failure. Short post, single question, not much else to go on.
  • A bug or product defect is silently affecting customers in the field and you're seeing it show up in return rates and support volume. How do you handle it?

“This one made me realize I jumped straight to 'fix the bug' mode instead of thinking about the customer impact loop first.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Interviewed for a data engineer role at Google, got a SQL/analytics problem centered on monthly customer transactions. Pretty standard technical screen but the scope of the question left some room to go deeper than I expected.
  • Write a query to analyze monthly customer transactions, covering aggregation, trends, or anomalies across time periods.

“Spent the first couple minutes just making sure I understood what 'analyze' meant here because that word can mean a lot of things.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Interviewed at Google, got asked about the future of microwaves. Still not entirely sure what role this was for.
  • What do you think the future of microwaves looks like?

“Blanked for a second because I kept waiting for the real question.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google SWE coding round, just one question on binary tree diameter. Pretty standard but I second-guessed myself more than I should have.
  • Given the root of a binary tree, find the length of the tree's diameter.

“I knew the trick was that the diameter doesn't have to pass through the root, which I almost forgot until I started drawing it out.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Google for a software engineer role. They focused on conflict, a major challenge you'd faced, and working under tight deadlines. Pretty standard BQ territory but Google tends to push for specifics so vague answers won't cut it.
  • Tell me about a time you had a conflict with a teammate or colleague. How did you handle it?
  • Describe a significant technical or professional challenge you faced and how you worked through it.
  • Can you give an example of a time you had to deliver something under a very tight deadline?

“I had an answer ready but halfway through I realized I was making myself sound way too right and the other person way too wrong.”

View Post