Google·Software Engineer·Onsite - System Design / Architecture
- Design a web crawler from scratch.
“I jumped straight into the URL frontier and crawl scheduling before even clarifying scope, which I think hurt me.”
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
“I jumped straight into the URL frontier and crawl scheduling before even clarifying scope, which I think hurt me.”
“Weakest part of my behavioral prep by far.”
“I went straight to user empathy and started talking about willingness to pay, which felt right but I probably skipped over the obvious stuff like checking if it's a niche product with no substitutes.”
“Read that back a few times before answering.”
“Felt like a curveball coming from Google.”
“I knew this one but still fumbled the initial setup.”
“I started with market segmentation which felt right but I probably spent too long on it before getting to actual recommendations.”
“slice_sample() with prop=0.5 is the clean answer and I got there, but I initially started talking about sample_n() out of habit before catching myself.”
“Threw me a bit because it's so far from anything tech.”
“I had a story ready but halfway through I could tell it wasn't landing.”