Google Senior Software Engineer Interview Experience
Google · Senior · Software Engineer
It was basically the most by-the-book Google loop possible: shortest path in a DAG, minimum meeting rooms, then a news feed design where they kept pushing on fanout, storage, and ranking.
Interview process
It felt pretty classic Google. I had a phone screen with behavioral and coding, then an onsite with two coding rounds and one system design round. The technical side was straightforward and very standard, and the two coding problems I remember were shortest path in a DAG and minimum meeting rooms. For system design, they had me design a news feed and then pushed on scale, fanout, storage, and ranking. Nothing about the loop felt unusual.
Interview rounds · 2
- 1
Phone screen
BehavioralData Structures & AlgorithmsI had a phone screen that mixed behavioral with coding, but the part I remember most was the behavioral side. They asked about conflict, leadership, mentorship, and project details.
- Q1. Tell me about a conflict you handled.
- Q2. Tell me about a time you showed leadership.
- Q3. Tell me about your mentorship experience.
- Q4. Walk me through a project in detail.
- 2
Final / onsite round
Data Structures & AlgorithmsSystem DesignMy onsite was two coding rounds and one system design round. It was pretty straightforward and by the book, with standard LeetCode-style questions plus a news feed design.
- Q1. Find the shortest path in a directed acyclic graph.
- Q2. Minimum meeting rooms.
Q3. Design a news feed.
Follow-up questions- How would you handle scale?
- How would you think about fanout?
- What storage choices would you make?
- How would ranking work?
Tips from the candidate
I would practice talking through test cases really clearly, because they cared a lot about that in the coding rounds. It did not seem like it was only about getting to an answer fast.
Company culture
The people I met seemed like they genuinely enjoyed the work culture, and the vibe I got was good WLB.