Google·Software Engineer·Onsite - System Design / Architecture
- Design a group chat application.
“I started with the basics, WebSocket connections, message storage, delivery guarantees, and the interviewer kept pushing on scale.”
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 started with the basics, WebSocket connections, message storage, delivery guarantees, and the interviewer kept pushing on scale.”
“Wide open prompt with zero constraints, which sounds like a gift until you're sitting there trying to figure out where to even start.”
“The transitive part is what makes this click as a Union-Find problem.”
“The part that tripped me up was the 'committed to it anyway' angle.”
“I picked Maps pretty fast and felt good about it until the follow-up came.”
“I started by trying to figure out what method we're even talking about, network transfer vs physical drives on a truck, because the answer is wildly different.”
“The tricky part isn't knowing yourself, it's knowing what profile they're screening for.”
“I started by asking clarifying questions about the hotel tier and guest profile, which felt right.”
“Classic question but I still fumbled it a bit.”
“I spent the first few minutes just trying to scope it because 'Google' is enormous and an experimentation platform could mean a hundred different things.”