Klarna contacted me directly via my personal email regarding this position. They found me on LinkedIn. The position was located in Berlin.
The interview steps were:
Google Hangout with HR: This introductory call covered Klarna and the position. HR also asked about my personal background, such as my location, openness to new opportunities, and motivations for considering this role. I was also informed about the entire interview process and its stages.
Online Test (Logical Reasoning and Code Challenge):
Google Hangout for Technical Review: This was a 1-hour call focusing on Java and your technical background. I shared my screen and completed another algorithm code challenge during this session.
Google Hangout for Character Stage: A 30-minute interview with the VP of Engineering, covering both behavioral and technical questions.
Onsite Interview: I was not invited to this stage.
Following stage 4, I received a rejection. HR informed me that while I was a strong fit, they decided not to proceed with me for the final step because I was a candidate requiring relocation to Berlin.
Klarna was aware from the beginning of the interview process that I required relocation. However, they chose to use this information as a rejection reason after stage 4. If relocation had been a deal-breaker, they could have stopped the process before it began. Instead, they proceeded with the interviews, wasting my time and effort.
Have you ever been a part of a project which failed, and what was your role in there?
The following metrics were computed from 1 interview experience for the Klarna Java Software Engineer role in Berlin, Germany.
Klarna's interview process for their Java Software Engineer roles in Berlin, Germany is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Klarna's Java Software Engineer interview process in Berlin, Germany.