Two stages: One interview with HR, mostly about past and current experiences. Some yes/no questions about my knowledge of some tools. The second stage is comprised of one architectural interview and a code challenge. The code challenge is more of a practical style as opposed to the LeetCode style. There are none of the typical recruitment questions. Just the architecture challenge and the code challenge. I think I've failed to pass the code challenge, though no feedback was given to me when I asked. I've made the mistake of going for a clean architecture, isolating external data structures from internal ones. That took some precious time and when the time was up, my solution wasn't yet working - though it was very close. Not sure if the main problem was the unfinished product or the fact they deemed it over-engineered. The most interesting part is that during the code challenge, you are supposed to stop sharing your screen, turn off your camera and mute your microphone. Overall, the interview was quite pleasant and I thought I had nailed it. These are good-intended people stuck with a binary approach when it comes to recruiting software developers. Shame, I think it must be a really nice place to work. Keep it simple, avoid any abstractions, let the external API leak into your code and you should be fine.