First a recruiter gets in touch with you to talk about the role and the company and you introduce yourself and talk a bit about your professional experience. Then there are 2 technical interviews where the first is just 1 or 2 random Android questions and lots of others about algorithms and data structures. The last technical interview is a one-hour live coding session, again focused on algorithms and data structures. All in all you have to constantly remind yourself that you're not applying to be a university professor instead of an Android engineer

Very old-fashioned interview process. There was a theoretical and a practical part. In the theoretical there were boring questions about equals/hashCode and sealed classes. The stack they are using is very old (no compose/coroutines), they use rxjava and a custom architecture software. The practical part consisted in 2 leetcode exercises. Although I had been told that I could take them offline, the interviewer didn't offer this option.