Kraken Software Engineer Interview Questions
& Process

Applied via Indeed, the whole thing took about a month. First, I had a good chat with a recruiter who laid out the plan. We talked about the company, the team, pay, and why I wanted to join. Second was a take-home test: a Django command-line app to parse files. They wanted to see how I'd handle an unclear task and build something scalable, making sure to document my assumptions. Third, we dove deeper into the take-home task, discussing my methods, choices, and the trade-offs. They asked how the app could be expanded. The last stage was all about my technical skills and the broader Python/Django world, including how we work. Got the offer super fast after that, like 30 minutes! My recruiter, Brad, was awesome and really helpful.

The hiring process is very straightforward: first, a video call with HR. Then, a technical test to do at home (3-4h) in Python, Django. Next, a video call with 2 engineers to discuss the technical test and possible improvements. Finally, a video call with 2 people from the team for team fit. Everyone I met during these interviews was very kind. The process is transparent and very fast, with feedback the day after each interview, taking up to 1 week maximum. I also received a document explaining the entire process, which was a pleasant surprise compared to other companies where the process can be unclear and long. Frankly, this type of human process is very refreshing, thank you to the Talent Acquisition team. Plus, the Talent Acquisition Specialist was great, very attentive and responsive.

The interview process was a terrible experience and a complete waste of my time. It started with an initial HR call, followed by a code challenge. That's when things really went downhill. They advised me to spend no more than 3-4 hours on the challenge, encouraging me to document any incomplete tasks and stating that the goal wasn't to fulfill all requirements but to progress as far as possible. I adhered to this timeframe and completed all requirements, adding testing and documentation, all within 4 hours. A week later, I received a rejection letter with nonsensical feedback on the code challenge. They claimed I hadn't completed the requirements, made only one commit, or failed to include sample files, none of which were true and were easily verifiable. They also criticized the code for not being 100% tested and for having brief documentation, despite the 4-hour limit and their encouragement not to finish everything! It seemed like they either swapped my code with someone else's or didn't review it at all. I responded with proof and screenshots demonstrating that all requirements were met and working. They conceded I was correct on 'some' points but still insisted I hadn't implemented the 'search' feature, ignoring my demonstration. They then stated I was being discarded for other, unsubstantiated reasons. This is unbelievable. I decided to stop wasting my time with them. Thankfully, the challenge only took 4 hours of my free time, which I regret, but it could have been worse. Other reviews mention 5-6 hour time limits for the same test.