Recruiter screen - Standard questions around past experiences, role, and expectations.
IQ test - This was new to me but pretty easy, I must say.
HM round - Behavioral scenarios about your past experiences.
Onsite: Coding - Not LeetCode style, mostly around practical stuff like making changes to a code repo they ask you to modify.
System design - Not generic, like "design a WhatsApp messenger." It's specific to Klarna use cases, so I'd say prepare a bit on payments domain-related questions.
Staff engineer round - This is more of a culture fit round; very technically in-depth and challenging.
I liked my interactions overall; everyone was very positive. Even if I didn't get some things right, they steered me in the right direction. I passed the onsite, but the role was put on hold while awaiting the TeamFit round. However, by then, I had accepted an offer already, so I had to withdraw. But I would have strongly considered it otherwise.
Recruiter screen - Standard questions around past experiences, role, and expectations.
IQ test - This was new to me but pretty easy, I must say.
HM round - Behavioral scenarios about your past experiences.
Onsite: Coding - Not LeetCode style, mostly around practical stuff like making changes to a code repo they ask you to modify.
System design - Not generic like "design a WhatsApp messenger," but specific to Klarna use cases. I'd say prepare a bit on payments domain-related questions.
Staff engineer round - This is more of a culture fit round, very technically in-depth and challenging.
If you cleared onsite, then Teamfit round.
The following metrics were computed from 1 interview experience for the Klarna Lead Software Engineer role in Spain.
Klarna's interview process for their Lead Software Engineer roles in Spain is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Klarna's Lead Software Engineer interview process in Spain.