4 rounds. heres what i remember: 1. coding: LC 239 sliding window maximum. got optimal but ran out of time on follow up 2. coding: LC 994 rotting oranges variant. solved in 20 min 3. system design: design google photos. froze on the ML ranking pipeline part. interviewer had to hand-hold me through it 4. behavioral: googliness. talked about a conflict with a PM. felt ok pretty sure im getting rejected. the system design was rough. 3 yoe btw

Google L4 onsite - got destroyed

c89b6673

4 rounds.

c99b3ec5

LC 239 is medium-hard. if you got optimal thats fine even without the follow up. system design at L4 they dont expect you to nail the ML part. you might be fine

dc2c957f

i had the exact same google photos question last month. the trick is to separate the storage layer from the serving layer and hand-wave the ML ranking as a separate microservice. they just want to see you can scope

64b5b221

3 yoe going for L4 is standard. even if you get rejected, the feedback is valuable. google lets you retry in 6 months