The interview process is quite long.

First, there's a normal interview with a recruiter. Then, you can choose between building a quite complex app in approximately 2 weeks or taking a technical interview. After that, you have to go through a 2-hour technical interview with two engineers.

Because I have another job, I did not develop the app and chose the short tech interview. It consisted of multiple questions around Java collections, multi-threading with Kotlin, and the Android Activity lifecycle. They were looking for notions, instead of actual development experience, but it seemed OK for a very short (45 minutes) tech interview.

Then, a few days later, I took the 2-hour-long interview. Excluding language issues (the two people who interviewed me were not very good at speaking English), the interview looked very similar to a university exam. They expected you to know by heart a lot of things that you don't usually touch when doing the actual job. They asked me about how Kotlin code is compiled, how RecyclerViews work, and they focused especially on very small details (such as how one can reuse the same ViewPool in multiple RecyclerViews; I had never had to do that, so I didn't know).

My suggestion for anybody looking to get a job here would be to read multiple books on Java, Kotlin, and the Android ecosystem, temporarily forgetting about the actual things you need in the real world.

How would you make a property thread-safe in Kotlin?

Having 3 activities, one of which is transparent, describe the lifecycle.

How would you reuse the same view pool from one RecyclerView into another one?

How does the Kotlin compiler work?

How would you build an animator that enlarges the width of a button?

How would you build a system that asks data from an API and also supports caching?