← Back to Directory

Google interview notes, page 57 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 system design flavor, just one question about building a predictive text algorithm for mobile keyboards. Pretty open-ended and I wasn't totally sure how deep to go on the ML side versus the data structure side.
  • Design an algorithm that predicts the next word or phrase a user is typing on a mobile phone keyboard.

“I started with a trie-based approach for prefix matching and the interviewer seemed fine with it but kept nudging me toward personalization and context.”

View Post

Google·Data Scientist·Technical Phone Screen

May 2026
SQL-heavy screen for a Data Scientist role at Google. One question but it had a real bite to it once you got past the basic aggregation part.
  • Given an email send log, write a SQL query to find the total number of Gmail emails sent per country and return the top five countries by volume. Then extend it to compute month-over-month percentage change in Gmail volume for each country.

“The first part was fine.”

View Post

Google·Product Manager·Onsite - System Design / Architecture

May 2026
Google PM system design round, one big question that sprawled into basically every engineering concept I'd half-studied. Felt like I was building a plane while it was already in the air.
  • Design an internal tool that returns historical currency exchange rates and can handle 10,000 requests per second. Walk through your API design, data model, storage choices, caching strategy, consistency requirements, scalability plan, and how you'd monitor it.

“This question is deceptively wide.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE coding round, one question on BFS-based shortest path finding. Pretty standard graph traversal stuff but there was a follow-up about optimizing graph construction that I wasn't fully ready for.
  • Given a graph as an adjacency list, a start node, and a target node, implement BFS to find the shortest path between them. Also discuss how you'd optimize the graph construction step to avoid a naive approach.

“I got the BFS part down pretty quickly, tracking parents to reconstruct the path at the end.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE coding round, one question, pretty straightforward on the surface but there are a few edge cases worth thinking through.
  • Given a list of strings and a prefix string, return all words from the list that begin with that prefix.

“Case sensitivity tripped me up for a second.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE screen, just a self-intro question from what I can tell. Not much to report.
  • Give a 2-3 minute self-introduction covering your background, recent experience, and why you're interested in this role.

“Pretty standard opener.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a product sense question about mobile apps. Pretty open-ended, which I wasn't fully prepared for.
  • What pain points have you personally encountered using an airline's mobile app, and how would you go about fixing them?

“I rambled for a bit before landing on anything concrete.”

View Post

Google·Software Engineer·Recruiter / HR Screen

May 2026
Recruiter screen for a SWE role at Google, basically just one question about what I'm looking for.
  • What are you looking for in your next opportunity?

“Pretty standard opener.”

View Post

Google·Data Scientist·Onsite - Product Sense / Strategy

May 2026
Big, sprawling product-analytics case for a DS role at Google, centered entirely on Gmail user segmentation. One question but it had like five parts and they expected you to go deep on all of them. The privacy/fairness angle at the end was the part I least prepared for.
  • Gmail wants to build actionable user segments to drive product improvements and lifecycle marketing. How would you design the segmentation scheme, validate it, run experiments to measure lift, and connect it back to the product roadmap? You can only use behavioral metadata and aggregate mailbox state, no email content.

“This was a monster of a question.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

May 2026
Google SWE interview with a big open-ended design question about building something for basically everyone. No coding, just a long conversation about product thinking and how you'd handle scale and inclusion from the start.
  • You're building a product that will be used by essentially all or nearly all users. Walk through how you'd approach problem definition, user research, scope, prioritization, scalability, and accessibility.

“This question is deceptively wide.”

View Post