There were 3 steps: 1. an online test about using and understanding algorithms- this is a pretty easy step 2. a pair programming session - 4 tasks this one took 2 hours, 4 tasks to do and explain every step down to the lowest level the 4 task were to complete the code samples regarding: cache implementation (with race conditions), download resource (if not already in cache), serialisation and lastly uikit (some things regarding autolayout in code and uitablesviews) - this step is the real technical step, it has a medium difficulty but it’s hard because it’s live action also the guy was really helpful, if you were stuck always here to help, bonus points revolut 3. final step - discussing with one of the heads of mobile engineering - 30 minutes this one was the mont intimidating, the interviewer had ADHD, always moving and hard to follow he asked questions about testing, pull requests, code guidelines and hardest things to develop on ui and business personally this was the hardest interview of all, i felt i lost the position on this step, but thank god I haven’t.

I was contacted on LinkedIn regarding the position, and we scheduled an interview. It turned out to be a strange experience—I could tell from the start that I wouldn’t progress, as they were clearly looking for highly passionate, tailored answers. For example, when asked why I wanted to join, giving a general response like seeking a new environment seemed to immediately disqualify candidates—that’s what I realized during the process. (They need someone who exaggerates with his answers)