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 approx. 2 weeks or take a technical interview; after that you have to go through a 2hrs 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 (45mins) tech interview. Then, a few days later I took the 2hrs-long interview: excluding language issues (the two people that interviewed me were not very good at speaking English), the interview looked very similar to a university exam. They were expecting 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 recycler views work and they focused especially on very small details (such as how one can reuse the same view pool in multiple recycler views; 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.