Security Risk Management Lead
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We have content for About the role (intro), Responsibilities (What You'll Do), Requirements/Qualifications (What We Look For), Benefits, Pay (Base Pay Grade etc). No Schedule info. So we should not include Schedule heading. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. The posting includes some legal bits at end: "We’re committed to providing an inclusive interview process..." and "By clicking 'Submit Application'...". Those are boilerplate/application instructions; we should remove them. Also remove "Please note that visa sponsorship is not available for this position." Might be considered metadata but not boilerplate? It's a condition; maybe keep? It's not a heading; could be folded into a short p. But it's not essential? It's a condition; we can keep as a short p under maybe About the role? But better to keep as a p under About the role or maybe separate? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short p for visa sponsorship note. Also "Remote-first with flexibility built in" etc is about work arrangement; could be part of About the role or maybe a separate section? Not a defined heading; we could incorporate into About the role. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep details like responsibilities list, requirements list, benefits list, pay ranges. We must use
- for any list of duties/requirements/benefits. Use
for prose. We must not create sections with filler like "commensurate with experience". In What We Look For there is "BA or BS degree ... or commensurate experience". That's a phrase; we should not create a section heading for that; but it's inside a list item maybe. We can keep it as part of a list item; it's not a heading. It's okay. We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits, so include those. We must not include Schedule. Thus sections: About the role (intro paragraph maybe plus remote-first note), Responsibilities (What You'll Do), Requirements (What We Look For), Benefits, Pay. We need to ensure we don't duplicate content. Let's extract About the role: first paragraph: "At Affirm, we exist for the moments that matter—giving people a clear, predictable way to pay over time, with no hidden fees, no surprises, and no tradeoffs on what matters most. Affirm values security as being critical to the company’s continued success. Our mission is to cultivate a culture of security at Affirm, enabling the company to succeed in building honest financial products. The Security Risk Management team is evolving beyond traditional governance, risk, and compliance; we are building an engineering driven program that designs, automates, and scales the controls, workflows, and tooling that protect Affirm and our customers. The ideal candidate will design, develop, configure, and implement solutions to complex technical and business problems across the Security Third Party Program and the broader Security Risk Management program. They are equally comfortable shaping policy and shipping automation using modern tooling (Python, Cursor, Claude, and other agentic coding platforms) to replace manual GRC work with scalable, code-defined workflows. They will operate as a subject matter expert, interface with business and engineering stakeholders, and play a key role in transforming Security Risk Management from a compliance oriented function into a security engineering discipline." Then after that there is "What You'll Do" list. We could also include remote-first note: "Remote-first with flexibility built in Affirm is proud to be a remote-first company. Most roles can be done from almost anywhere within the country of employment. Some positions may occasionally require in-person work at an Affirm office, and a few are office-based due to the nature of the work. All new hires will be invited to attend an in-person onboarding experience." This is substantive; we could include in About the role as a paragraph. We also have visa sponsorship note: "Please note that visa sponsorship is not available for this position." Could be a short p. Now Responsibilities: list items under "What You'll Do". Need to capture each bullet. Let's extract bullets: - Lead and mature Affirm's Security Third Party Program, including the design, implementation, and continuous improvement of processes, controls, and operational workflows - Build and maintain automation that replaces manual GRC tasks: intake, triage, evidence collection, control validation, tracking, escalations, and reporting, using either Python, low code platforms, and agentic coding tools (Cursor, Claude, etc.) - Design and operate workflow orchestration and integrations across systems like ticketing, GRC platforms, vendor management tools, identity providers, and cloud control planes - Partner closely with Procurement, Legal, Engineering, IT, Compliance, Privacy, and business stakeholders to assess and manage security risk across third party relationships - Translate ambiguous business and security requirements into practical, scalable program solutions and decision frameworks - Identify opportunities to automate manual processes across the program and prototype solutions yourself rather than waiting on an engineering backlog - Drive program operational excellence by establishing repeatable processes, service-level expectations, metrics, and reporting for third party security risk management - Evaluate third party security controls, cloud architectures (AWS/GCP), integration patterns, and risk posture, and provide clear recommendations to stakeholders and leadership - Conduct light threat models on high risk integrations and partner with Security SMEs for deeper diligence - Manage and prioritize a portfolio of complex security risk reviews and initiatives simultaneously, balancing business enablement with risk reduction - Partner with technical teams to implement or optimize systems and tools that support program automation and workflow orchestration - Develop dashboards, reporting mechanisms, and program insights (SQL, BI tools, or custom tooling) that improve visibility into risk trends, bottlenecks, and program performance - Act as a trusted advisor and SME on third party security risk management, helping stakeholders make informed, risk based decisions - Contribute to the broader Security Risk Management strategy by identifying opportunities to scale, simplify, and strengthen security governance processes through engineering Now Requirements/Qualifications: "What We Look For". List: - 5+ years of experience in Information Security, Risk Management, Engineering and/or relevant roles - Hands-on experience using agentic coding tools (Cursor, Claude Code, Copilot, etc.) and a working knowledge of Python; you don't need to be a software engineer, but you should be fluent enough to read, modify, and run scripts, build automations, and ship small tools end-to-end - Familiarity with cloud environments (AWS, GCP, or Azure) — IAM, logging, common services, and the security risks/controls that apply to cloud-deployed third parties and integrations - Excellent written and verbal communications skills - Experience engineering solutions via Python, Claude, Cursor or other agentic coding tooling - Experience with industry based information security & control frameworks (NIST Cyber Security Framework, ISO 2700x, SOC1&2(SSAE18), PCI DSS, NIST-800-53, FFIEC Cybersecurity Assessment Tool, SANS Top 20, etc.) - BA or BS degree in Information Security, Cyber Security, Computer Science or related field or commensurate experience - Attention to detail and experience with security practices and security tooling - Demonstrated ability to drive projects towards completion - Ability to understand and communicate technical issues to non-technical teams - Professional certification in Information Security or Risk Management (such as CISSP, CISM, CISA, CRISC, etc.) is a plus Now Benefits: list under "Benefits Designed For You". Bullets: - Health coverage at no cost: We cover 100% of premiums for employees and their dependents. - Spending stipends: Monthly stipends support your tech setup, and the ability to choose health and wellness options that are right for you. - Time to recharge: Flexible time off and generous holiday calendars help you rest when you need to. - Own a piece of what you build: Our employee stock purchase plan (ESPP) lets you buy Affirm stock at a discount. - We’re committed to providing an inclusive interview process, including accommodations for candidates with disabilities. If you need support, we’re happy to help. (This is more boilerplate but it's part of benefits? Actually it's a statement about interview process; could be considered boilerplate but it's not navigation/legal/EEO? It's about accommodations; might be okay to keep but it's more about process. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is about accommodations for candidates with disabilities; could be considered EEO? It's about providing accommodations, which is EEO-related. Might be considered boilerplate; safer to remove. Also the line "For positions based in San Francisco or Los Angeles: Affirm considers qualified applicants with arrest and conviction records, as required by law." That's also EEO/legal; remove. Also "By clicking "Submit Application," you acknowledge that you have read Affirm's Global Candidate Privacy Notice and consent to the use of your personal information as described." That's application instruction/legal; remove. Thus benefits list should include the first four bullet points. Possibly also the spending stipends line includes two parts: tech setup and health and wellness options. Keep as is. Now Pay: we have Base Pay Grade - L Equity Grade - 5 etc. Then description: "Employees new to Affirm typically come in at the start of the pay range. Affirm focuses on providing a simple and transparent pay structure which is based on a variety of factors, including location, experience and job-related skills. Base pay is part of a total compensation package that may include equity rewards, monthly stipends for health, wellness and tech spending, and benefits (including 100% subsidized medical coverage, dental and vision for you and your dependents.) USA Pacific base pay range (CA, WA, NY, NJ, CT) per year: $165,000 - $225,000 USA Sapphire base pay range (all other U.S. states) per year: $146,000 - $206,000 Please note that visa sponsorship is not available for this position." We should include pay details: base pay ranges, mention equity grade, etc. Also note visa sponsorship not available (we already have that as metadata). We can include that as a short p under Pay or About the role. Probably under Pay as a note. We must not create Schedule section. Now construct HTML:
About the role
At Affirm, we exist for the moments that matter—giving people a clear, predictable way to pay over time, with no hidden fees, no surprises, and no tradeoffs on what matters most. Affirm values security as being critical to the company’s continued success. Our mission is to cultivate a culture of security at Affirm, enabling the company to succeed in building honest financial products. The Security Risk Management team is evolving beyond traditional governance, risk, and compliance; we are building an engineering driven program that designs, automates, and scales the controls, workflows, and tooling that protect Affirm and our customers. The ideal candidate will design, develop, configure, and implement solutions to complex technical and business problems across the Security Third Party Program and the broader Security Risk Management program. They are equally comfortable shaping policy and shipping automation using modern tooling (Python, Cursor, Claude, and other agentic coding platforms) to replace manual GRC work with scalable, code-defined workflows. They will operate as a subject matter expert, interface with business and engineering stakeholders, and play a key role in