1. 1-hour programming interview. The task was to complete a simple screen in an Android project, write a unit-test for it, then discuss ConcurrentHashMap as a separate task; 2. 1-hour system design interview. The task was to architect a system to assign ATM refilling tasks to workers. Draw everything; 3. Up to 3 45-min team fit interviews. A team fit is not an informal conversation – you're still being asked management and system design questions, and the interviewers have a list of skills they mark +/- Every interview has pre- and post-call with your recruiter.

The process was quick even during Holidays period. After submitting my test I received a rejection email with the following content: Quite good architecture and DI. Good unit tests and UI test. Good work with offline mode. What can be better: 1) Use DiffUtil instead of calling notifyDatasetChanged(), right now you are reloading the whole list 2) When i select currency - it doubled on top. And in that case sometimes it's shows not identical rates for them both (it's seems strange) 3) UI test didn't pass 4) No unsubscribe on configuration changes - it can cause crash 5) Selected currency not stored after configuration changes. I don't understand how they reject a senior developer who has a quite good architecture, DI and Unit tests just because of minor bugs! I believe the judgment wasn't objective enough.