I recently interviewed with Fastned and wanted to share my experience with the process. Overall, it was quite thorough and involved multiple steps, each providing a unique challenge. Step 1: Initial HR Interview The process began with a standard HR interview. This was fairly typical, with questions about my background and experience, similar to what you would expect in any HR screening. Step 2: Home Assessment Next, I was given a home assessment to complete within 10 days. This was a challenging task, but I managed to not only meet but exceed the requirements by providing a comprehensive visual presentation. Step 3: My efforts were well-received, and the subsequent conversation with two engineers (a junior engineer and a team lead) went very well. Both were professional and supportive. Step 4: Behavioral/Cultural Interview I was invited for an in-person behavioral and cultural interview with the Head of Engineering: This was my favorite part of the process. The discussion was engaging, and I felt a strong alignment with the company's values ​​and culture. Step 5: Coffee Chat with the Director of Product; and Engineering The final step was a 30-minute coffee chat with the Director of Product Engineering. I had expected this to be a more relaxed, informal discussion about my motivations and fit for the company. However, just before this meeting, I received an unexpected call from HR asking why I had left my previous positions, which added a layer of stress to what I thought would be a casual conversation. Unfortunately, this last step did not go as planned. The feedback I received was that I did not answer questions to the core, and the overall impression was disappointing. I believe this was influenced by the sudden HR questioning right before the interview, which threw me off balance. Reflections and Concerns Reflecting on the entire process, there were a couple of key issues: Kotlin Experience: Despite mentioning during the initial HR interview that I had learned Kotlin in my spare time but did not have professional experience with it, this seemed to become a significant point of concern later in the process. The job description mentioned Kotlin and/or Java, but it became clear that professional experience with Kotlin was a crucial requirement. This misalignment in expectations was frustrating. Timing of HR Questions: The decision to ask about my previous job departures right before the final interview added unnecessary stress. This information should have been clarified earlier in the process to avoid affecting my performance during the critical final step. Conclusion Fastned is undoubtedly a good company with warm and professional people. However, the interview process seemed to place disproportionate weight on the final coffee chat, despite the extensive prior steps. After investing significant time and energy, It was disappointing to be judged primarily on the last 30 minutes of interaction. I hope this feedback is helpful for both candidates preparing for interviews and for Fastned to refine their interview process for future candidates.