The process began with a recruiter who provided a great deal of useful detail about what to expect. The initial "phone screen" was conducted on-site, which I believe helped me perform my best.

It included warm-up questions about previous work and Android specifics, followed by two not-terribly-difficult coding challenges.

The on-site full-day interview consisted of six 45-minute sessions:

• One session was for lunch.
• One session was with an interviewing trainee, which was coding-focused.
• Two sessions were primarily focused on coding, similar to the phone screen.
• One session covered a series of behavioral questions (classic inquiries like, "What's something valuable you once learned from a supervisor?" – requiring me to dust off old memories).
• One session focused on design.

The design interview seemed frustratingly aimless. While I felt I was able to give good answers, this was the only interview where I received negative feedback. The feedback was too vague to make sense of, leading me to suspect poorly communicated expectations.

Otherwise, the whole experience was quite positive.

NDA. Coding questions were non-trivial but straightforward enough to easily tackle two in the half-hour period allotted each time.