Status: 5 yrs exp
Position: L5 at google
Location: Seattle, WA
Date: Oct 12, 2021

Technical phone screen in 2020 (1 hour):

• Algorithm question

Onsite (5 rounds - 45 mins each):

Overall, the interview duration of 45 mins felt very short.

1. System Design - Scoreboard for a game
   This went bad. My preparation fell short. (self eval: No hire)
2. Coding round 1 - low-level design with maps and doubly linked lists
   Made a silly mistake in an inequality that was core logic, fixed it quickly after the interviewer hinted. (self eval: strong Hire)
3. Coding round 2 - Graph, compression,Trie-like
   I wrote complicated code that failed one edge case but I identified and mentioned how to easily fix it in the end. He sounded impressed with the unique solution but said it was incomplete. (self eval: Weak Hire)
4. Behavioral round
5. Coding round 3 - a hard variant of overlapping intervals
   I explained a possible solution for the hard variant and worked through an example for the proposed logic. The interviewer suggested solving the sub-problem of overlapping intervals since time was limited. I wrote working code for the sub-problem. I didn't have time left for the big problem. (self eval: Strong/Weak Hire)

Result:
The recruiter called to mention L5 Reject but they wanted to do 2 additional rounds to determine L4.

Any hints on how to prepare best for the 2 additional rounds and what to watch out for.
Any tips appreciated on what they would be looking for in those 2 extra rounds?