Lead Engineer
bOverview /b pIn this role you will own and improve systems that handle real-money transactions for millions of users. You’ll work across domains in a hands-on capacity, shaping architecture and decisions that impact reliability and business outcomes. You’ll mentor peers and elevate engineering practices while embedding AI as a working method, not just a demo. This is a growth-focused opportunity at Klarna to push the boundaries of banking-scale engineering and influence multiple teams as the business evolves. You’ll be central to delivering robust, compliant financial systems and driving cross-team collaboration. /p bResponsabilità /bulliMake defensible technical decisions and justify trade-offs /liliEnsure designs align with broader architecture and reliability concerns /liliDesign for regulated banking constraints (reliability, auditability, controls)
/liliMentor engineers and raise technical standards across teams /liliAct as a multiplier to elevate teams and domains /liliSet standards for AI usage in everyday practice /li /ul bRequisiti fondamentali /bulliProven experience building and operating high-scale, reliable systems /liliExperience in Java, JavaScript, or Python environments /liliAbility to articulate trade-offs and non-taken paths /liliStrong communication to both technical and non-technical audiences /liliLeadership through impact, not title, with ability to drive initiatives across teams /liliComfort with ambiguity and cross-team collaboration without formal authority /li /ulullicross-functional collaboration /liliclear communication /liliproblem-solving under pressure /liliJava /liliJavaScript /liliPython /li /ul
/liliMentor engineers and raise technical standards across teams /liliAct as a multiplier to elevate teams and domains /liliSet standards for AI usage in everyday practice /li /ul bRequisiti fondamentali /bulliProven experience building and operating high-scale, reliable systems /liliExperience in Java, JavaScript, or Python environments /liliAbility to articulate trade-offs and non-taken paths /liliStrong communication to both technical and non-technical audiences /liliLeadership through impact, not title, with ability to drive initiatives across teams /liliComfort with ambiguity and cross-team collaboration without formal authority /li /ulullicross-functional collaboration /liliclear communication /liliproblem-solving under pressure /liliJava /liliJavaScript /liliPython /li /ul