Kraken Software Developer interview questions

Interview was really fast and the responses for each step were coming within 1-2 days. The technical challenge required me to use a specific technology I wasn't that used to, but it was still doable. I was asked to do the project for 5 or so hours and just write what I would have done if I had more time. Since it required me to learn many new things I took more time with it, but I could still submit it within around 5 days. Each interview had a very friendly atmosphere and I was in contact with HR in between in case I had any follow up questions.

I interviewed specifically for the Kraken Flex department. It's a four stage interview process, which I did fully remotely. I applied online with CV and cover letter, the recruiter contacted me a couple of days later. It was two and a half weeks from my application online to offer from Kraken. First stage was initial screening call with a recruiter, standard questions about your experience, why you're interested in the role / working at kraken, and what your salary expectations are. Second stage is a take-home task (mine was in python), there is no time limit but the recruiter asks you to let them know when they can expect it to be retuned. Third stage is an informal style technical interview with two engineers about your experience and discussion on subjects like cloud systems, test-driven development, and best practises. Fourth stage is a system design interview, they give you the scenario the day before so you can be familiar with it, and then the interview is white boarding solutions online with two engineers, and they will ask you about trade-offs for decisions and introduce other considerations to discuss. Note: this was the most fun system design interview I've ever done, it was really great to familiarise myself with the scenario in advance, so that on the day I could focus on discussing the different approaches to the solution rather than trying to quickly read/understand the problem. It really allowed us to jump straight in to the white boarding and left lots of time of discussing the system design.