Key factors at a glance
- Seniority
- Mid
- Experience
- —
- Work mode
- —
- Salary
- Not stated
- Required working language
- English
Must-haves
- Code in Java, JavaScript, or Python
- Understanding of common security vulnerabilities and exploitation
- Ability to explain security risks clearly to other engineers
- Comfortable analyzing unfamiliar systems
- Receptive to feedback
Nice-to-haves
- Computer Science or Engineering degree
- Penetration testing or threat modeling experience
- Security tooling experience
- Bug bounty program participation
- CTF competition participation
How you match
See how your skills match this role — and what to learn to close the gap.
UnlockCompany hiring signal
See whether Klarna Bank AB is scaling up or slowing down, from its posting history.
Original posting
EnglishAbout the role Klarna runs on financial infrastructure that has to hold up against real attackers, not hypothetical ones. As an Engineer within the security track, you'll work on the systems and practices that keep that infrastructure safe - finding weaknesses before someone else does, and building the tools and controls that make the whole engineering organization more secure by default. You'll work closely with engineers across other teams, helping them understand risk in their own systems rather than just handing them a list of findings. What you'll do ● You'll look for vulnerabilities in Klarna's systems and help fix the ones you find. ● You'll build and maintain tools that make it easier for other engineering teams to write secure code. ● You'll review designs and code from other teams with security in mind, and flag risks before they ship. ● You'll help respond when something goes wrong, working through what happened and what needs to change. ● You'll use AI tools as part of your everyday workflow, not as a separate add-on step. Who you are ● You've written code in Java, JavaScript, or Python, whether through a job, an internship, or your own projects. ● You understand common security vulnerabilities and how attackers actually exploit them, not just their names. ● You can explain a security risk to another engineer in terms they can act on, not just flag it and move on. ● You're comfortable digging into a system you didn't build to understand how it works. ● You want regular feedback on your work and you act on it. Bonus points for ● A degree in Computer Science, Engineering, or a related field. ● Experience with penetration testing, threat modeling, or security tooling. ● Participation in bug bounty programs or CTF competitions
Shown in its original English. To apply, continue to the company's own page.