← Back to Directory

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

Apr 2026
Behavioral round at Google for a software engineer role. One question, lots of follow-ups. Left feeling like I'd either nailed it or completely rambled my way through.
  • Walk me through a recent project you found both challenging and interesting. What were the hardest problems, how did you diagnose and fix them, what trade-offs did you make around scope, timeline, quality, or cost, and what was the measurable outcome?

“The base question felt fine but the follow-ups stacked fast.”

View Post

Google·Software Engineer·Recruiter / HR Screen

Apr 2026
Went through a Google SWE screen that included at least one motivational question about why Google specifically. Pretty standard stuff but worth thinking through before you go in.
  • Why do you want to work at Google specifically, and why are you making this move now?

“I had an answer prepped but it still felt a bit hollow when I said it out loud.”

View Post

Google·Business Analyst·Onsite - Product Sense / Strategy

Apr 2026
Got a market sizing question at Google, pretty standard case interview stuff but I fumbled the structure more than I'd like to admit.
  • Estimate the number of people who frequently visit bars.

“I jumped straight into US population and started segmenting by age, which felt right, but then I got tangled up trying to define 'frequently' and wasted like two minutes debating whether that meant weekly or monthly.”

View Post

Google·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Google ML engineer interview that went deep on regularization. More of a breadth-plus-depth combo than I expected, covering everything from the classics to stuff like mixup and label smoothing that I hadn't touched in a while.
  • Walk through the regularization techniques you know and explain when you'd actually use each one.
  • What are the practical differences between L1 and L2 regularization, and how do those differences affect the model you end up with?
  • How does dropout work as a regularizer, and what are the failure modes or pitfalls when using it?
  • Can you explain how normalization layers act as implicit regularizers during training?
  • How do label smoothing and mixup work, and what problems are they solving compared to standard training?
  • Where do Bayesian priors fit into the regularization story, and how do they connect to L2 regularization specifically?
  • How does ensembling reduce variance, and when would you choose it over other regularization approaches?

“This started as a broad opener but they kept pulling on threads.”

View Post

Google·Data Scientist·Technical Phone Screen

Apr 2026
Went through a technical screen for a DS role at Google and got hit with a pretty deep stats question about Simpson's paradox. Not a light conversation, they wanted the full picture: math, causality, and practical fixes.
  • Define Simpson's paradox and build a concrete numeric example where a treatment looks better in every subgroup but worse in the aggregate. Walk through the algebra of how weighted averaging reverses the trend, connect it to confounding and causal graphs, describe remedies like stratification and regression adjustment, and explain when the aggregate vs. the subgroup-conditioned estimate is actually the right answer.

“This one wrecked me a little.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Google SWE coding round with two problems back to back. The second one had follow-ups that kept escalating and I felt like I was barely keeping up by the end.
  • You're given a text file where each line has some raw string data. Parse each line to extract a user ID and a numeric value, then store the results in a way that's efficient to query later.
  • Given several people's calendars, each represented as a list of days they're free, find all days where every person is available. Follow-ups: (a) generalize to days where at least P out of N people are free, and (b) given an integer X, find all consecutive windows of X days where the availability condition holds.

“Pretty standard parsing problem.”

View Post

Google·Software Engineer·Online Assessment (OA)

Apr 2026
Google SWE online assessment, 90 minutes, two coding problems. The first was a string processing task and the second was a feature rollout evaluator with dependency resolution. An AI assistant was apparently available but your code still had to pass the unit tests, which felt like a weird middle ground.
  • Implement a function that processes an email string in fixed-size chunks, computes a checksum for each chunk using character weights, and uses that checksum to index into a verification string, returning the concatenation of all selected characters.
  • Given a feature rollout system with user attributes and feature rules, implement an evaluator that checks country eligibility, platform version eligibility, and dependency satisfaction in the correct order, returning a structured decision with a reason string.
  • Parse a dependency file where each line maps a feature name to a comma-separated list of dependencies, and correctly handle whitespace trimming and empty dependency lists.
  • Handle cycle detection in a feature dependency graph where cycles can involve two features or longer chains, and format the cycle reason string to show the full path including the repeated node.

“The character weight mapping tripped me up a bit.”

View Post

Google·Software Engineer·Onsite - Product Sense / Strategy

Apr 2026
Google Cloud PM interview with a product prioritization question. Not much context to go on but it's the kind of open-ended strategy question that can go sideways fast if you don't anchor your reasoning early.
  • As a PM for Google Cloud, which product area would you prioritize for development and why?

“This one has a lot of surface area and that's the problem.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Interviewed at Google for what seemed like a product or hardware strategy role. One question, pretty out there, and I'm still not sure I gave a good answer.
  • How would you justify building a robotic refrigerator for Google?

“I kind of froze for a second because it sounds absurd but then realized that's probably the point.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google SWE interview with a data structure design question that seems deceptively simple until you think about the efficiency constraint on findLargest.
  • Design a class with two operations: insert(num) to add a number, and findLargest(k) to return the (k+1)-th largest value using 0-based indexing. For example, after inserting 3, 3, and 2, findLargest(0) should return 3, findLargest(1) should return 3, and findLargest(2) should return 2. The findLargest operation should be as efficient as possible.

“My first instinct was a sorted list and just index from the end.”

View Post