Google·Software Engineer·Onsite - System Design / Architecture
- Design an end-to-end log processing system that ingests logs from many services and supports search and aggregation across the full pipeline.
“This was a beast of a question.”
FAANG / Big Tech
Most of these Google write-ups come from Software Engineers (354), then Machine Learning Engineers (42) and Data Scientists (4). The most reported rounds are the technical phone screen (186), the behavioral / leadership round (106), the onsite coding round (66) and the system design round (33).
405 interview notes · updated Jun 2026
“This was a beast of a question.”
“I started with a doubly linked list plus a hashmap for O(1) join/leave and O(n) traversal, which felt solid.”
“I went straight to greedy and got burned a little.”
“I jumped straight to the hashmap plus heap approach, which works fine at O(n log k).”
“The anagram check part was fine, character frequency maps are pretty standard.”
“Jumped to BFS pretty fast which felt right, model it as a graph where edges exist when getDistance returns something under r.”
“The part that tripped me up was the 'you vs the team' split.”
“I fumbled the opening because I picked an example that was technically true but kind of boring.”
“The problem itself isn't conceptually hard but I kept second-guessing the modulo step.”
“Blanked for a second trying to pick the right story.”
Online Assessment
Data Scientist
Software Engineer
Product Manager
Candidates most often report a technical phone screen (186 write-ups), a behavioral / leadership round (106), an onsite coding round (66) and a system design round (33).
Across 186 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (214 questions), Technical Trade-offs (144) and System Design (47).
Across 106 behavioral / leadership write-ups, the most tagged question topics are Adaptability & Ambiguity (105 questions), Cross-functional Alignment (75) and Stakeholder Management (73).
354 notes
42 notes