I was referred by a friend who was in the interview process. I had a quick chat with the hiring manager and then scheduled the phone screen. The phone screen was an hour long and focused on fundamental data structure and algorithm understanding. Two hours after the phone screen, I was invited to come on site.
The on-site interview was pretty standard: four one-hour interviews that covered overall system design, Android-specific topics, and general data structures/algorithms. I hadn't been feeling well that day, and by the end of the day, I was dragging pretty badly. My final interview was pretty rough, but that was nobody's fault.
The only complaint I have is that finding the lobby could certainly be easier. It's tucked back in a group of unmarked bungalows. Perhaps if they had someone standing out on the street or on the boardwalk to meet you, it would make that a bit easier.
General understanding of data structures - be familiar with:
The following metrics were computed from 2 interview experiences for the Snap Android Software Engineer role in Venice, California.
Snap's interview process for their Android Software Engineer roles in Venice, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Snap's Android Software Engineer interview process in Venice, California.