Applied by referral and was contacted almost immediately by a recruiter.

Set up a Google Hangouts phone screen, and then set up an on-site at their Venice HQ.

The phone screen was 1 hour, and the on-site was the usual all-day multiple interview process. The recruiters were friendly and extremely prompt.

The female engineers who interviewed me were absolutely fantastic. They made the interviews interactive, were open to different/new ideas, and were generally welcoming. The male engineers who interviewed me were aggressive, rude (on phone texting, checking emails right next to me, and not willing to change or explore new ideas), and most importantly, not willing to collaborate.

Throughout my interview, I had recruiters and engineers consistently talk down about the Android client (a huge red flag).

Overall, it reeked of an engineering culture that is youthful and trying to find its way. I would be careful to work here, simply because a toxic culture cannot be fixed from the ground up, and most importantly, it impedes the time for learning.

I was able to implement each answer correctly with unit tests in the allotted time but was denied.

I ended up taking another offer at a larger company in the Bay Area and would not have accepted their offer if it had been given, due to what I perceived to be a very hostile workplace.

Easy interview, though. Just use MVC architecture in your answers (engineers didn't know MVP/RxJava patterns).

1. Implement a stack.

   • After asking about constraints, I was given: Implement a stack of fixed length.
   • Must execute and write unit tests. 1B. Now, use the stack you created to create a stack of variable length.
   • Extend the stack and implement a next pointer, essentially a linked list extension.

2. Write an app that accepts deep links and displays the last path on the screen (a word bank app).

3. Design Battleships and write functional unit tests.

4. Write an app that mimics network-based search functionality.

   • You can append "-whatever" to the word and mock the network layer.
   • Wrote this as an MVP with an interface between my presenter and data layer.
   • Implemented the interface to just do thread.sleep then hit callback.
   • Write unit tests.
   • Used RxJava's debounce for the TextView (interviewer didn't know RxJava, so I had to implement a debounce function extending a Handler instead so he could understand).