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.”
354 Software Engineers have shared notes from their Google interviews, with the questions they were asked in each round. That is 87% of the 405 Google interview notes on Screna AI.
354 Software Engineer interview notes
“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.”
“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.”
“Picked a school project team thinking it would come across as more genuine than just listing a job.”