Klarna software engineer candidates report a reasoning test, practical coding, system design and behavioral rounds. Timelines and communication varied widely across experiences, so plan for delays.
$125K
Avg. Base Comp
$165K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describing Klarna's software engineer interviews most often mention an early abstract reasoning test, followed by coding, system design and behavioral conversations. Some describe it as an IQ-style test focused on pattern recognition. It mainly works as a filter, so get comfortable with the format before you sit it.
The coding stage often looks more practical than a typical algorithm screen. Candidates report pair programming on a project outline sent in advance, making changes to an existing code repository, and finishing semi-ready code tasks sent a day before. Others mention a take-home assessment that an interviewer then walked through with them, two easy Kattis problems, and a two-sum variant. Practice reading unfamiliar code, refactoring and explaining trade-offs aloud.
System design questions appear to vary by team and level. Reported prompts include microservices with databases and message queues, a producer-consumer messaging problem, and a ticketing SaaS platform. A lead-level candidate faced payments-domain questions and recommends preparing on payments systems. The common thread is explaining your reasoning and design choices rather than reciting a textbook answer.
Behavioral rounds reportedly cover Klarna's leadership principles, why you want to join or change jobs, and your past experiences. One senior candidate said feedback on this stage, about not showing enough senior-level experience, affected their outcome. Bring concrete examples that match your level.
Timing and closure were inconsistent. Reported experiences range from several weeks to four months, and several candidates describe long gaps or no final response. Ask your recruiter for next steps and get any offer details in writing.
Synthesized from 10 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Klarna process.
I interviewed for a mid-level Software Engineer role at Klarna in early 2025, and while the technical rounds themselves went smoothly, the overall experience left me frustrated and skeptical about the organization.
The process consisted of multiple rounds spread over several months. There was a home coding assessment that I had to complete first—a coding challenge that the interviewer then walked through with me in detail, asking questions about my approach and reasoning. Beyond that came a behavioral interview focused on why I wanted to join Klarna, along with a design-focused conversation. The interviewers I spoke with during these technical and design rounds were genuinely nice and the conversations felt collaborative rather than adversarial. The technical bar seemed reasonable; the interviews tested problem-solving fundamentals and your ability to articulate your thinking, which is fair for the level.
What really threw me was the recruiter experience. My recruiter changed partway through the process, and the transition was jarring. The new recruiter made an odd comment about their predecessor, who apparently had left. More than that, they made some unprofessional remarks with gender undertones that genuinely caught me off guard. Coming from someone senior in the organization, it made me question what the actual culture was like beyond the interview room.
I cleared all the interviews and was told the process was complete—even congratulated on passing. But then came the letdown. They said they didn't have a fitting position available, but assured me that new roles would open up in a month or two and I'd be first in line. Sure enough, positions got posted online a month later. I never heard from them. The whole thing felt disorganized and broken, which was disappointing because the technical part was actually fine.
Prep tip from this candidate
Technical preparation here should focus on coding fundamentals and design thinking—the interviews test your problem-solving approach carefully, so be ready to articulate your logic at every step. But also go in with realistic expectations about communication and follow-through; reports suggest organizational dysfunction in the hiring pipeline, so clarify timelines and next steps explicitly in writing if you advance.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Klarna
Design a reporting pipeline for a major tech company using only open-source tools under strict budget constraints.
| Question | |
|---|---|
| Decreasing Tech Debt | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Payments Received | |
| Monthly Customer Report | |
| Total Spent on Products | |
| Top 3 Users | |
| Comments Histogram | |
| Random SQL Sample | |
| String Shift | |
| Get Top N Frequent Words | |
| Find the First Non-Repeating Character in a String | |
| Upsell Transactions | |
| Google Maps Improvement | |
| Prime to N | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Bagging vs Boosting | |
| Longest Streak Users | |
| Duplicate Rows | |
| Last Transaction | |
| Like Tracker |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter conversation covering background, role fit and expectations. One account puts it at 30 minutes. One candidate waited nearly a month to hear back before this stage began, so timing may vary.
Several candidates describe an abstract reasoning or IQ-style test early in the process, with one noting a focus on pattern recognition. It is described as fairly straightforward but works as a filter, so get familiar with the format beforehand.
Reports describe coding that leans practical. Examples include pair programming on a project outline sent in advance, changing an existing repository, semi-ready tasks sent a day before, a take-home assessment, and easy Kattis problems. One candidate reports a two-sum variant instead. Expect the format to vary by role and team.
Candidates report architecture discussions rather than whiteboard coding. Prompts mentioned include microservices with databases and message queues, a producer-consumer messaging design, a ticketing platform, and payments-domain questions at lead level. Interviewers reportedly want your opinions, examples and reasoning.
Candidates report behavioral questions about leadership principles, motivation for joining or changing jobs, and past experiences. One lead-level candidate describes a staff engineer round that doubled as a culture fit interview, followed by a team fit round. Outcomes varied: some candidates report offers, while others report no vacancy, a different offer or no response.
