Klarna is one of the largest buy-now-pay-later platforms globally — used by 150K+ merchants and 150M+ consumers. The interview emphasizes payments, fraud detection, and risk assessment at high transaction volume.
Process
Recruiter screen → 60-minute coding phone (DSA medium) → onsite virtual: 2 coding, 1 system design, 1 craft deep-dive, 1 behavioral. Cycle: 4–6 weeks.
What they actually ask
- Design a BNPL approval flow with sub-200ms credit decisions. Interviewers probe how you keep the synchronous checkout path fast: caching bureau pulls, precomputing risk scores, and returning a conservative fallback when a model or data source times out. Be clear about where a real-time decision ends and an async manual-review queue begins.
- Design an installment scheduling and payment-collection system. Expect questions on idempotent retries for failed charges, scheduling the “pay in 4” due dates, and handling partial payments, refunds, and dunning. A favorite edge case: a card that declines on installment 3 of 4 — describe the state machine that drives retries and customer notifications.
- Design fraud detection at checkout. The core tension is blocking fraud without rejecting good customers, all inside a tight latency budget. Talk through useful signals (device fingerprint, velocity checks, account age), serving a model inline, and splitting fast synchronous rules from slower batch scoring.
- Coding: medium DSA, often with financial-correctness framing. This is array, string, and hash-map territory — the kind of ground the core coding patterns cover — not exotic algorithms. The financial-correctness twist means using integer cents instead of floats for money, and watching for rounding, overflow, and off-by-one errors in totals.
- Behavioral: customer focus, regulatory-aware engineering. Bring examples where you balanced a ship date against a compliance or data-privacy requirement, or where you dug into a customer-impacting incident and drove the fix. Structure answers so the tradeoff and your reasoning stay explicit.
Levels and comp (2026)
- SE II: SEK 850K–1.1M total (Stockholm); $145K–$185K (US)
- Senior SE: SEK 1.2M–1.6M / $215K–$285K
- Staff: SEK 1.8M–2.4M / $310K–$410K
- Principal: SEK 2.6M+ / $430K–$570K
Prep priorities
- Be fluent in Java or Kotlin (the bulk of the codebase). You’ll write code in one of these during the phone screen, so pick one and know its standard library cold — collections, streams, null handling. Interviewers notice idiomatic code, not just a passing answer.
- Understand payments protocols, ACH, card networks, and fraud patterns. Know the lifecycle of a transaction: authorization, capture, settlement, refund, and chargeback. Being able to explain why a payment can succeed at auth but fail at capture signals you’ve worked near real money.
- Brush up on regulatory framework: PSD2, FCA rules, US BNPL regs. You don’t need to be a lawyer, but you should know PSD2 mandates strong customer authentication in the EU and that BNPL is moving under tighter US consumer-credit rules. Expect to weave compliance constraints into design answers rather than treating them as an afterthought.
Frequently Asked Questions
Is Klarna remote-friendly?
Hybrid in Stockholm (HQ), Berlin, NYC, London. Many engineering roles fully remote within EU.
How does Klarna compare to Affirm or Afterpay?
Klarna is the global leader; Affirm dominates US; Afterpay (now Block) is Australia-strong. Klarna pays competitively; Stockholm comp lags US peers due to cost of living differences.
What is the engineering culture?
Swedish engineering culture: pragmatic, collaborative, calm pace. Strong work-life balance.
Similar company guides
Prepping for Klarna? Put it to work:
