I interviewed for a JavaScript engineer position at Klarna's Berlin office. Klarna's interview process consisted of the following stages:

1. Two different tests: a) A logic test involving images where candidates predict the next image in a sequence (multiple choice). b) A JavaScript coding test with three questions (unlimited time).

2. Two interviews in the second round: a) A technical skills interview featuring a live coding algorithmic exercise in JavaScript (45 minutes). b) An attitude interview (30 minutes).

3. A final interview comprising three rounds: a) A 15-minute logic test (identical to stage 1(a), where you guess the next image pattern in a multiple-choice series). b) A 30-minute discussion with a Senior Engineering Manager. c) A 90-minute architecture interview.

The HR's attitude from day one was very condescending and showed no respect for the candidate's efforts or time. If you believe the least you can expect in any interview is respect for your time, please read on to understand why I am sharing this.

After I spent a weekend completing stage 1 interviews, I received feedback over the next few days that I had cleared it. When I discussed scheduling the next interview with HR, they stated that the development team had no time to conduct interviews for the next 1.5 months at my preferred time slots because they were already interviewing other candidates. I tried to be flexible, as I had already invested time and effort in completing the coding exercise. However, the HR said they would only book a slot if they could find one with the interviewers and that I was free to interview elsewhere, as Klarna could not guarantee anything. This was unbelievable to hear, especially after being fully flexible with them regarding timings. I continued to follow up and request absolutely any 3-hour slot during a weekday. Luckily (according to HR), I secured a slot in 1.5 weeks, solely for the stage 2 round.

Stage 2 was cleared, and then they scheduled the final round.

Stage 3 (the last round) went extremely well. With nearly 9 years of experience, I was already comfortable with architecture discussions. I also built a sample pseudo-service and demonstrated how it could be production-ready.

After four days of follow-up, HR responded saying that all feedback was extremely positive and the interviewers liked my candidature. However, they stated I had scored a bit low on their logic test involving images (where I had to predict the next image in a multiple-choice format). They did not provide my score but explicitly said that the five technical rounds were perfectly fine, but the one logical image pattern test was not strong enough, leading to the rejection of my candidature.

I have absolutely no problem with job application rejections, as it is part of the process. However, providing an illogical reason for rejection and placing no importance on technical tests, even with positive feedback, while focusing solely on image recognition, made me feel they wanted to reject me for any impractical reason. After almost a month of interviews, this is what it boiled down to.

I was very disappointed by the vague reason given for my rejection and felt I had wasted over a month interviewing for a company that was not only condescending from the start but also rejected me after all my efforts for what felt like a stupid game, instead of focusing on coding, technical skills, or personal experience. I would have greatly appreciated any feedback on the technical tests, but according to them, that part was satisfactory.

Any candidate who aspires not only to join a good company but also one that is respectful, honest, credible, and values important aspects of the interview process should not waste their time interviewing with this company. The chances are high that you will be very frustrated by their interview handling and possibly rejected for an absolutely vague reason, despite your efforts and positive interviews and feedback.

Logical image recognition pattern MCQ,

3 JavaScript home coding challenges,

and peer-to-peer coding algorithm challenges in JavaScript.