Classic process: phone interview with a bunch of general Java questions, then onsite.

Before the interview, I had already seen a bunch of red flags on Glassdoor, but did not pay too much attention (recent reviews + a bunch of consecutive reviews in May from current employees to improve their rating). My overall experience was pretty bad.

The interview process was really scripted (so scripted, some of them asked me to solve the same puzzle twice). Even if you can feel the experience of senior people, their knowledge about Android architecture and patterns was not that good (they did not know RxJava, for instance). It turned out they used a bunch of third parties in their app, and the most interesting algorithms were not home-made.

On three onsite interviews, two went well. The last one was a disaster. The interviewer was not capable of understanding solutions other than his own and was really confused by any other way of tackling a problem. At the end, when I asked about the next step in their process, he told me it was the final one that day and they usually do not need any onsite to make a decision. He then said in my case, they would make a decision quickly.

Unfortunately for him, it turned out they wanted me to come back onsite. Sounds like someone made his mind too quickly...

I then politely accepted to come back, but they took a week to just get back to me, whereas I was already passing final interviews with other companies in the meantime. Hence, I aborted the process.

I eventually figured out their office manager was in charge of the lobby/snacks/catering and people team too...

TL;DR - If you want to work for a social network, go work for Facebook. Engineering will be better.

ListView & RecyclerView / general Android architecture

Binary trees operations

Basic HashMap implementation