"Interview Process The interview process at Kraken was refreshingly straightforward and well-structured. It consisted of three clear stages: 1. Take-Home Technical Challenge (Python/Django) Estimated to take 3-4 hours, with no strict deadline Clear problem statement around processing energy industry flow files Purposefully vague requirements to assess problem-solving approach Instructions to list "what you didn't have time to complete" if not finished within the timeframe Challenge closely resembled actual work you would do in the role Freedom to implement and document my solution as I saw fit 2. Technical Discussion (1 hour) In-depth discussion of my implementation choices Questions about my approach to the problem Opportunity to explain my technical decisions and tradeoffs Conversational rather than interrogative 3. Team Fit Interview (1 hour) Met with the manager and a team member Behavioral questions and scenario discussions Cultural fit assessment Plenty of time for my questions about the team and company What Set This Process Apart What I appreciated most was Kraken's transparency about their process. They explicitly mentioned that the take-home challenge was intentionally vague to see how candidates approach ambiguous problems - reflecting real-world scenarios. My extensive documentation, assumptions, and detailed README were well-received. The interviews felt genuinely conversational rather than one-sided interrogations. The team encouraged me to interview them as much as they interviewed me, which provided great insight into their work culture and processes. I shared many laughs with the interviewers, and their sincerity when answering my questions about company processes was refreshing. They seemed genuinely interested in finding the right fit rather than just technical skills. Tips for Candidates Document your take-home challenge thoroughly (this helped me tremendously!) Take the time to add docstrings, comments, and detailed explanations in your README It took me a couple more hours than the suggested timeframe, but the extra documentation effort was well worth it Explain your assumptions and approach in detail Prepare thoughtful questions about the team and company Be ready to discuss your problem-solving process, not just your solution Approach the conversation as a two-way street Overall, this was one of the most straightforward and enjoyable interview processes I've experienced. The team at Kraken clearly values transparency, problem-solving capabilities, and cultural fit beyond just technical skills."

HR phone screen, followed by take-home assessment. If the team approves of the assessment, next is a technical interview with other engineers focused around the assessment. Last is a soft-skills/culture fit interview with the hiring manager.

Interview Process The interview process at Kraken was refreshingly straightforward and well-structured. It consisted of three clear stages: 1. Take-Home Technical Challenge (Python/Django) Estimated to take 3-4 hours, with no strict deadline Clear problem statement around processing energy industry flow files Purposefully vague requirements to assess problem-solving approach Instructions to list "what you didn't have time to complete" if not finished within the timeframe Challenge closely resembled actual work you would do in the role Freedom to implement and document my solution as I saw fit 2. Technical Discussion (1 hour) In-depth discussion of my implementation choices Questions about my approach to the problem Opportunity to explain my technical decisions and tradeoffs Conversational rather than interrogative 3. Team Fit Interview (1 hour) Met with the manager and a team member Behavioral questions and scenario discussions Cultural fit assessment Plenty of time for my questions about the team and company What Set This Process Apart What I appreciated most was Kraken's transparency about their process. They explicitly mentioned that the take-home challenge was intentionally vague to see how candidates approach ambiguous problems - reflecting real-world scenarios. My extensive documentation, assumptions, and detailed README were well-received. The interviews felt genuinely conversational rather than one-sided interrogations. The team encouraged me to interview them as much as they interviewed me, which provided great insight into their work culture and processes. I shared many laughs with the interviewers, and their sincerity when answering my questions about company processes was refreshing. They seemed genuinely interested in finding the right fit rather than just technical skills. Tips for Candidates Document your take-home challenge thoroughly (this helped me tremendously!) Take the time to add docstrings, comments, and detailed explanations in your README It took me a couple more hours than the suggested timeframe, but the extra documentation effort was well worth it Explain your assumptions and approach in detail Prepare thoughtful questions about the team and company Be ready to discuss your problem-solving process, not just your solution Approach the conversation as a two-way street Overall, this was one of the most straightforward and enjoyable interview processes I've experienced. The team at Kraken clearly values transparency, problem-solving capabilities, and cultural fit beyond just technical skills.