Chief Information Security Officer - Klarna Bank USA

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: Intro paragraph: "Klarna, briefly At Klarna, we're building an everyday finance network, helping over 120 million consumers across 26 countries save time and money, and worry less about their finances. Working here means taking on problems most companies never get to solve, and being hands-on enough that the interesting part of the work lands with you, not someone else — you'll build with AI, not watch it happen. This is the stretch zone. Come find out what you're capable of." That's a paragraph about company; could be included maybe as a

before sections. Then "About The Role" heading content: paragraphs about Klarna Bank USA regulated entity, role description. Then "What You'll Do": list of duties (multiple sentences). Should be turned into

• items. Then "Who You Are": list of qualifications/experience. Could be Requirements or Qualifications. We need to decide sections: About the role (maybe combine intro and About The Role?), Responsibilities (What You'll Do), Requirements (Who You Are), maybe Qualifications (maybe same as Requirements). But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role (including description), Responsibilities (What You'll Do), Requirements (Who You Are). Possibly also Skills? The "Who You Are" includes skills and experience. Could treat as Requirements. Benefits, Pay, Schedule: Not present except mention "Final compensation will be based on the candidate's qualifications, skills, and experience." That's not specific numbers, it's vague; we should not create Pay section because it's not specific. Benefits not mentioned. Schedule: mention "This position is based in Utah, or requires frequent business travel to Utah if you're based elsewhere in the U.S. Working together: we value co-located teams; most teams currently meet in the office 2–3 days per week, and this varies by team and can change over time." That's schedule info (office days). Could be considered Schedule section. It's specific: 2-3 days per week office. So we can include Schedule. Also location: Utah base or travel. Could be part of Schedule or maybe a separate note. But we can include location in Schedule or maybe a short p. We must not include filler like "commensurate with experience". The compensation line is vague but not filler like "commensurate with experience"? It says "Final compensation will be based on the candidate's qualifications, skills, and experience." That's somewhat generic but still substantive? It's not a specific number or range, but it's still info about compensation determination. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The compensation line is not a specific number but it's stating that compensation will be based on qualifications etc. That's not a placeholder like "commensurate with experience"? It's similar but maybe considered filler. Safer to not create Pay section because it's not a specific figure. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about compensation (final compensation will be based on...). That is a statement about pay, albeit not specific. Might be considered stating them. But the instruction also says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The line "Final compensation will be based on the candidate's qualifications, skills, and experience." is somewhat generic but not exactly those placeholders. However it's still vague. I'd lean to not include Pay section to avoid risk. Schedule: we have specific office days 2-3 days per week. That's specific enough. So we can create Schedule section with that info. Benefits: none. Thus sections: About the role, Responsibilities, Requirements (or Qualifications). We'll choose About the role, Responsibilities, Requirements. We need to use

  for each section heading. Inside sections, use

  for prose,

  • for lists. We must preserve all substantive information. Let's extract content. About the role: The paragraph after "About The Role": "Klarna Bank USA operates as a regulated U.S. banking entity, which means its information security program answers not just to internal risk committees but to banking regulators and supervisory examination teams. As Chief Information Security Officer, Klarna Bank USA, you'll own that program end to end — the bank's cyber risk, its regulatory relationships, and how well it draws on Klarna's global Security organization without duplicating it. You'll be part of Klarna's global Security organization and report to the Group CISO. For matters relating to the U.S. bank entity, you'll also have a direct reporting and governance relationship with the Klarna Bank USA Chief Risk Officer." That's prose. Responsibilities: "What You'll Do" bullet points (though they are sentences separated by periods). We'll split into list items. List: - Own the information security and cybersecurity program for Klarna Bank USA — governance, strategy, policies and standards; risk assessments and control oversight; and security requirements for products, services, and material technology changes. - Lead identity and access security, cloud, infrastructure, and application security, data protection, and vulnerability and exposure management, along with security monitoring, detection, and response across the bank's environment. - Own incident management and cyber resilience, third-party and intra-group technology risk, security testing and assurance, and security awareness and training, and report on all of it to the Board and senior management. - Represent Klarna Bank USA to regulators and supervisory teams on information security and cybersecurity matters, and lead security-related regulatory examinations, reviews, and information requests. - Turn regulatory observations and commitments into effective, sustainable control improvements, and keep the bank in continuous examination readiness rather than treating compliance as a periodic exercise. - Connect Klarna Bank USA to the security capabilities Klarna operates group-wide, establishing clear accountability across entity and group boundaries and closing any gaps that are specific to the U.S. bank. - Advise the Klarna Bank USA CRO, CEO, Board, and Group CISO on the bank's cyber risk profile, turning security concerns into concrete recommendations and escalating material issues as they arise. - Move between Board-level discussions, regulatory meetings, architecture reviews, and significant security incidents, staying close to the substance of what you're accountable for. That's 8 items. Requirements/Who You Are: list of qualifications. Paragraph: "You've worked in cybersecurity, information security, or technology risk within U.S. banking or another regulated financial institution, and you've led or materially owned an information security program there — a background in a de novo bank, industrial bank, fintech, or bank charter process is especially relevant here." Then separate sentences: - You've worked directly with U.S. banking regulators and regulatory examination teams, and you know what supervisory engagement looks like from the inside. - You've presented cybersecurity risk to Boards, executive management, and regulators, and you can move between governance conversations and detailed technical discussions with the same audience. - You understand modern cloud infrastructure, software engineering, and technology platforms well enough to assess the risk in them yourself. - You've operated in an environment where important technology or control capabilities are owned by a parent company, affiliate, or shared service, and you know how to build clear accountability across that boundary. - You can tell which risks are material and which are theoretical, and you act on that distinction instead of treating every finding the same way. - You take ownership of problems proactively, build relationships across organizational boundaries without relying on hierarchy, and form your views from evidence rather than from what worked at your last organization. Also there is a line: "Things you should know before applying" then bullet points: - This position is based in Utah, or requires frequent business travel to Utah if you're based elsewhere in the U.S. - Working together: we value co-located teams; most teams currently meet in the office 2–3 days per week, and this varies by team and can change over time. - Non-obvious backgrounds are welcome. Diversity of skills, perspectives and backgrounds is how we create, innovate, and disrupt like no other. - Final compensation will be based on the candidate's qualifications, skills, and experience. We need to decide where to put these. The location and schedule could go under Schedule section. The "Non-obvious backgrounds are welcome..." is a statement about diversity; could be part of About the role or maybe a separate section but we don't have a specific heading for Diversity. Could incorporate into About the role as a paragraph. The compensation line we decided maybe not to include as Pay section; but we could include it as a short p under About the role or Requirements? It's about compensation; maybe better to omit as it's vague. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit compensation line, we are summarizing away detail. However the instruction also says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state something about compensation, albeit vague. Should we include a Pay section with that line? The line is not a specific number but it's still stating something about compensation. The instruction about filler/placeholder text includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". The line "Final compensation will be based on the candidate's qualifications, skills, and experience." is somewhat similar to "commensurate with experience" but not exactly those words. It's still vague but maybe acceptable. However the instruction says never emit a heading followed by filler/placeholder text. If we create a Pay section with that line, it's not filler like those examples, but it's still vague. I'd lean to include a Pay section with that line as a

    . It's substantive in that it states how compensation is determined. It's not a placeholder like "commensurate with experience" but it's similar. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about compensation, so we can create Pay section. The content is not filler like those examples. So we will include Pay section with that sentence. Schedule: we have location and office days. Could combine location and schedule. We'll put schedule info: "This position is based in Utah, or requires frequent business travel to Utah if you're based elsewhere in the U.S. Working together: we value co-located teams; most teams currently meet in the office 2–3 days per week, and this varies by team and can change over time." That's specific enough. Now the "Non-obvious backgrounds are welcome. Diversity of skills, perspectives and backgrounds is how we create, innovate, and disrupt like no other." This is a statement about diversity/inclusion. Could be included in About the role as a paragraph, or maybe a separate section but we don't have a heading for Diversity. We'll add it to About the role after the initial description. Now we need to ensure we don't repeat job title as heading. Not include. We need to output only HTML fragment. Let's structure:

    Klarna, briefly At Klarna, we're building an everyday finance network, helping over 120 million consumers across 26 countries save time and money, and worry less about their finances. Working here means taking on problems most companies never get to solve, and being hands-on enough that the interesting part of the work lands with you, not someone else — you'll build with AI, not watch it happen. This is the stretch zone. Come find out what you're capable of.

    About the role

    Klarna Bank USA operates as a regulated U.S