Risk Manager, AWS Risk Management

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the description. We need to extract: - About the role: description of role: "AWS Third-Party Risk Management (TPRM) is seeking a Risk Specialist to join our team within Risk Management Excellence (RMX). In this role, you will serve as a key operator within the TPRM program, responsible for monitoring, assessing, and reporting on risks associated with AWS’s critical third-party ecosystem. You will manage ongoing risk surveillance through the Sentinel platform, produce executive-level risk intelligence reports, support regulatory audits, lead financial viability assessments, and coordinate incident response documentation. This is a highly cross-functional role that partners with AWS service teams, legal, compliance, supply chain, and external vendors to ensure third-party risks are identified, measured, and mitigated. The ideal candidate is a self-starter with strong analytical skills, an eye for process improvement, and comfort navigating ambiguity in a fast-moving cloud infrastructure environment." That's about the role. - Responsibilities: list of duties: bullet points: "You will monitor third-party risk alerts and escalate issues as they arise, ensuring risks are identified and addressed quickly." etc. Let's extract all responsibilities from "Key job responsibilities" paragraph and "A day in the life" maybe also responsibilities but we can include as responsibilities. We need to produce

• for any list of duties/requirements/benefits. - Requirements: Basic Qualifications: "Bachelor's degree or equivalent 3+ years of compliance program management, legal, governance, audit, risk/loss prevention, or equivalent experience Demonstrated understanding of ERM and/or TPRM frameworks" - Preferred Qualifications: "Professional auditing qualification, or similar risk or compliance credentials Experience with SQL and Excel Familiarity with one or more of the following regulatory regimes: DORA, UKCTP, US Federal Banking Agency requirements, or equivalent financial services regulations" - Skills: maybe not explicitly listed; we could infer from responsibilities: analytical skills, process improvement, etc. But we should only include if posting actually states them. The posting mentions "strong analytical skills, an eye for process improvement, and comfort navigating ambiguity". That's in About the role. Could be considered Skills. But we can also include a Skills section if we have explicit list. Might be better to combine into Qualifications? The instruction says use sections like Skills if posting has real specific content. We have some skill mentions. Let's include a Skills section with bullet list: strong analytical skills, eye for process improvement, comfort navigating ambiguity, ability to work cross-functionally, etc. However we must not invent or summarize away detail; we can only include what is explicitly stated. The posting says: "The ideal candidate is a self-starter with strong analytical skills, an eye for process improvement, and comfort navigating ambiguity in a fast-moving cloud infrastructure environment." That's explicit. Also earlier: "You will monitor third-party risk alerts..." etc. Those are responsibilities, not skills. So we can extract those three skill items. - Benefits: The posting includes benefits description: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave." Also mentions sign-on payments and RSUs. So we have benefits content. - Pay: The posting includes salary ranges: "USA, VA, Arlington - 74,200.00 - 129,800.00 USD annually USA, WA, Seattle - 82,700.00 - 129,800.00 USD annually". Also mentions base salary range listed below, sign-on payments and RSUs. So we have pay info. - Schedule: Not mentioned. No schedule info. So we should not include Schedule section. - Also we might include About The Team section? The instruction only lists specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. "About The Team" is not in list, but could be considered part of About the role? Probably we should not create a separate heading for About The Team; we could incorporate that info into About the role or maybe omit. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include About the role (we have). Responsibilities (we have). Requirements (we have). Qualifications (we have preferred qualifications). Skills (we have). Benefits (we have). Pay (we have). Schedule (none -> omit). Also we might need to differentiate between Requirements (basic) and Qualifications (preferred). That's fine. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • Bachelor's degree or equivalent
  • 3+ years of compliance program management, legal, governance, audit, risk/loss prevention, or equivalent experience
  • Demonstrated understanding of ERM and/or TPRM frameworks

  Qualifications

  • Professional auditing qualification, or similar risk or compliance credentials
  • Experience with SQL and Excel
  • Familiarity with one or more of the following regulatory regimes: DORA, UKCTP, US Federal Banking Agency requirements, or equivalent financial services regulations

  Skills

  • Strong analytical skills
  • Eye for process improvement
  • Comfort navigating ambiguity in a fast-moving cloud infrastructure environment
  • Self-starter

  Benefits

  • Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, option for Supplemental life plans)
  • EAP, Mental Health Support, Medical Advice Line
  • Flexible Spending Accounts
  • Adoption and Surrogacy Reimbursement coverage
  • 401(k) matching
  • Paid time off
  • Parental leave
  • Sign-on payments
  • Restricted stock units (RSUs)

  Pay

  Salary ranges: Arlington, VA: $74,200.00 - $129,800.00 USD annually; Seattle, WA: $82,700.00 - $129,800.00 USD annually. Includes base salary, sign-on payments, and RSUs.

  We need to ensure we preserve all substantive information. Let's verify we didn't miss any important details. From description: - Role: monitoring, assessing, reporting on risks associated with AWS’s critical third-party ecosystem. Manage ongoing risk surveillance through Sentinel platform, produce executive-level risk intelligence reports, support regulatory audits, lead financial viability assessments, coordinate incident response documentation. Highly cross-functional role partners with AWS service teams, legal, compliance, supply chain, external vendors. Ideal candidate self-starter with strong analytical skills, eye for process improvement, comfort navigating ambiguity. - Responsibilities list: * monitor third-party risk alerts and escalate issues as they arise, ensuring risks are identified and addressed quickly. * own the monthly risk report from draft through executive distribution, and track key metrics that measure program health. * produce on-demand risk profiles for internal stakeholders using financial intelligence platforms and AI-assisted tooling. * lead financial viability assessments for critical vendors—collecting due diligence reviews, distributing risk surveys, and scoring financial health—while partnering with engineering to automate data collection. * serve as the team’s point of contact for regulatory and customer audits, and document third-party incidents in coordination with security operations. * drive vendor reassessments, process risk nominations for new and existing third parties, and participate in launch reviews for new AWS services. * look for ways to streamline operations through automation, tooling improvements, and well-maintained runbooks. - A day in the life: triaging Sentinel alerts, actioning third-party risk indicators—executing overrides, updating logs, filing tickets. Midday: pulling financial health data for a viability assessment, drafting a risk summary for a stakeholder request, or coordinating audit evidence with a program manager. May join cross-functional call with Legal or Supply Chain on an open incident. Afternoons: updating reassessment trackers, compiling the flash report, or partnering with engineering on an automation that saves the team hours each week. We could incorporate some of these day-in-life details into responsibilities or maybe keep as part of responsibilities. Since we already have responsibilities list covering many, we could add additional bullet points for day-in-life items if not covered. But we must not duplicate. Let's see if any day-in-life items are not already covered: "executing overrides, updating logs, filing tickets" (part of monitoring alerts). "pulling financial health data for a viability assessment" (covered in lead financial viability assessments). "drafting a risk summary for a stakeholder request" (covered in produce on-demand risk profiles). "coordinating audit evidence with a program manager" (covered in serve as point of contact for regulatory and customer audits). "joining a cross-functional call with Legal or Supply Chain on an open incident" (covered in coordinate incident response documentation? maybe not exactly but similar). "updating reassessment trackers" (drive vendor reassessments). "compiling the flash report" (own monthly risk report). "partnering with engineering on an automation that saves the team hours each week" (look for ways to streamline operations through automation). So day-in-life is largely covered. Thus responsibilities list as we have is fine. Now Requirements: Basic Qualifications: "Bachelor's degree or equivalent 3+ years of compliance program management, legal, governance, audit, risk/loss prevention, or equivalent experience Demonstrated understanding of ERM and/or TPRM frameworks". We need to split into bullet points. We should preserve the exact phrasing? Not required but keep substance. We'll output bullet points: - Bachelor's degree or equivalent - 3+ years of compliance program management, legal, governance, audit, risk/loss prevention, or equivalent experience - Demonstrated understanding of ERM and/or TPRM frameworks Now Qualifications (Preferred): list as bullet points. - Professional auditing qualification, or similar risk or compliance credentials - Experience with SQL and Excel - Familiarity with one or more of the following regulatory regimes: DORA, UKCTP, US Federal Banking Agency requirements, or equivalent financial services regulations Now Skills: we have bullet points from ideal candidate description: self-starter, strong analytical skills, eye for process improvement, comfort navigating ambiguity in a fast-moving cloud infrastructure environment. We could also include "ability to work cross-functionally" but not explicitly stated; it's implied but not explicit. Better to stick to explicit. Now Benefits: we need to capture all benefits listed: health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, parental leave. Also sign-on payments and RSUs. Also maybe