Candidates applying for Software Developer roles take an average of 30 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Klarna overall takes an average of 28 days.
Common stages of the interview process at Klarna as a Software Developer according to 2 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at Klarna
Interview
The tech challenge and behavior interviews were both interesting exercises but both interviewers seemed to think they were holding up gauntlets for a prize rather than having a conversation with an equal. The behavior one especially went 15 mins longer than scheduled and most of the questioning by the interviewer, leaving hardly any time for them to answer my questions. But what really irked me was the guy conducting the interview by connecting through a tv in a meeting room, while he sat on the far end. He could clearly observe me in minute detail while it was pretty hard vice versa. Talk about power plays.
Interview questions [1]
Question 1
Standard questions about current and past job experiences
I applied online. The process took 6 weeks. I interviewed at Klarna (Estocolmo, ) in Nov 2019
Interview
The most thorough recruiting process I've experienced so far. However, as all steps were highly relevant, the feedback clear and transparent, and the recruitment representative unusually engaged and supportive throughout the whole process, for me this was more of a motivating quality marker than anything else.
The process took 2 weeks. I interviewed at Klarna (New York, NY)
Interview
1. Pattern based logical multi choice test
Its a simple multi choice test based on patterns. There are 18 questions and 15 min. Unsure why its taken.
2. Coding test
Three simple coding problems with no time limit.
3. Another coding test with an engineer.
This one is of average difficulty. The interviewer also asks about your current work experience.
4. System design problem
This was a bit weird. First, the interviewer(who, for the test, pretends to be a product owner) asks to build a throw away prototype of the given problem statement and later asks to build a production level service for the same problem. This causes a bit of a confusion as there might be a difference in opinion between the interviewer and you on what components are considered in prototyping phase and what are for the production service. For eg, the interviewer might ask you to skip testing or authentication components in prototyping phase but you might thinks its a must-have even in prototyping phase. This grey area between prototype and production service design was confusing for me.
5. Two bar raisers
The hiring manager was responsive and helpful too.