Infrastructure Manager, XCM

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate like EEO, legal, etc. Also remove application instructions, navigation, cookie, etc. We need to parse the description. First paragraph: "Amazon's Cross Channel Marketing team (XCM) is seeking a Infrastructure Manager to own the systems behind our content platforms, serving marketing, campaign, creative, design, and production. This includes a dedicated AWS environment supporting petabyte-scale storage across multiple tiers, high-performance shared filespace supporting creative production, and the compute and automation that keep it running. This role administers those systems, automates their operation, and extends them to support new integrations with the third-party platforms our teams depend on. The work spans storage lifecycle, backup, recovery, and continuity planning, identity and access management, and the single sign-on and credential lifecycle behind every third-party platform in the estate. This role automates that administration wherever it can, and maintains the ownership, monitoring, and support structures that keep these systems supportable as the environment grows. It also helps shepherd new tools through Amazon security review and keeps tools already in use compliant as requirements change. We are looking for a hands-on administrator who thinks in systems and would rather automate an operational burden than absorb it. Curiosity about AI as a working tool is expected, both in applying it to infrastructure automation and in judging where it belongs. Understanding the pace and scale at which marketing and production teams work matters as much as infrastructure depth. Ambiguity is constant here: inherited systems, incomplete documentation, and dependencies that sit with vendors and internal security, identity, and tech partners." That's about the role. So we can put that under

About the role

with

. Next: "Key job responsibilities" bullet list: - Manages the AWS environment behind our content platforms, and evolves it as new workloads and integrations arrive - Designs storage tiering and lifecycle policy across petabyte-scale content and multiple systems, determining what lives where and why - Owns high-performance shared storage, backup, and archive across creative production and digital asset management - Automates administration of these systems so the environment scales without adding manual work - Maintains identity, access, and security compliance across the third-party platform estate, including single sign-on, credential lifecycle, and platform security review - Establishes and maintains operational standards for these systems, covering ownership records, monitoring, alerting, and support processes - Builds and secures the infrastructure new integrations run on, including credential storage and access paths for AI and third-party services - Represents our content platform systems to other XCM technology teams, partners across Amazon, and third-party providers, so integrations are well designed and ownership is clearly defined These go under

Responsibilities

with

• . Next: "About The Team" includes a link. That's not a section we need? It says "Find out more about XCM here: https://www.amazon.jobs/content/en/teams/international-stores/xcm". That's not substantive content for a section; we can ignore. Next: "Basic Qualifications" list: - 4+ years of site reliability engineering (SRE), systems engineering, systems administration, DevOps, security administration, or network administration experience - Experience using AWS services - Experience in any of the following: Python, Java, Perl, PHP, Ruby, Bash, Shell or equivalent - Bachelor's degree in Systems Engineering, Computer Science, or related field or relevant work experience - Experience implementing repeatable processes and driving automation or standardization - Experience directly working with cloud hosting technologies (AWS, Azure, etc.) - Direct ownership over live production cloud environment, including storage at scale, lifecycle, and compute - Experience supporting creative, marketing or media teams and their system needs These are qualifications. Could be under

  Requirements

  or

  Qualifications

  . The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where each piece goes. Basic Qualifications likely go under Requirements. Preferred Qualifications go under Qualifications (or Skills?). Let's map: - Requirements: basic qualifications (must-have) - Qualifications: preferred qualifications (nice-to-have) - Skills: maybe list specific technical skills like programming languages, AWS, etc. But we already have those in requirements. Could also separate out skills like "Python, Java, etc." but we can keep them in Requirements. We need to avoid thin sections. Let's see if we have enough for Skills: maybe we can extract specific skills: "Python, Java, Perl, PHP, Ruby, Bash, Shell", "AWS services", "SSO across platforms including federated identity, SAML or OIDC integrations and certificate rotation", "high-performance shared storage for media production, such as LucidLink, Qumulo, or Isilon", "secrets management and secure credential exchange between systems, including AI and model API access". Those are from Preferred Qualifications. Thus we could have:

  Requirements

  with
  of basic qualifications.

  Qualifications

  with
  of preferred qualifications.

  Skills

  maybe not needed if we already covered. But we could combine preferred qualifications into Qualifications and maybe not have Skills. The instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Schedule not present (no schedule info). Benefits we have info: "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 mention sign-on payments and RSUs. That's benefits. So we can include Benefits. Pay: we have salary ranges for three locations: Santa Monica, New York, Seattle. That's pay info. So we can include Pay. Schedule: none. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not include empty sections. Now we need to format. We must not include Job ID, no navigation, no EEO boilerplate, no legal, no application instructions, no link to team maybe? The "About The Team" link is not substantive; we can drop. We need to preserve all substantive information. So we need to include the salary ranges and benefits details exactly as given. We need to ensure we don't include any boilerplate like "Amazon is an equal opportunity employer..." etc. Remove that. Also remove Los Angeles County specifics? That's part of job duties? It includes some legal stuff about criminal history etc. That's likely boilerplate/legal; we should remove. Also remove "If you have a disability..." accommodation link. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Our inclusive culture empowers Amazonians..." maybe that's fluff but could be considered boilerplate; but it's not required to keep. Safer to remove. We need to keep the description of role, responsibilities, qualifications, benefits, pay. Now craft HTML. We'll start with

  About the role

  ...

  Make sure to preserve line breaks? Not needed. Now Responsibilities:

  Responsibilities

  • ...
  ...
  Requirements:

  Requirements

  ...
  Qualifications:

  Qualifications

  ...
  Benefits:

  Benefits

  ... maybe we can list items as
  • but the description is a sentence. Could keep as

    . But instruction: Use

    • for any list of duties/requirements/benefits, and

      for prose. Benefits is a list of items; we can make

      • each benefit. Pay:

        Pay

        ... maybe we can list each location as

      • . Use list. Now ensure we don't repeat any info. Let's extract exact text. About the role paragraph: We'll copy the first paragraph exactly as given, but we may need to trim trailing spaces. First paragraph: "Amazon's Cross Channel Marketing team (XCM) is seeking a Infrastructure Manager to own the systems behind our content platforms, serving marketing, campaign, creative, design, and production. This includes a dedicated AWS environment supporting petabyte-scale storage across multiple tiers, high-performance shared filespace supporting creative production, and the compute and automation that keep it running. This role administers those systems, automates their operation, and extends them to support new integrations with the third-party platforms our teams depend on. The work spans storage lifecycle, backup, recovery, and continuity planning, identity and access management, and the single sign-on and credential lifecycle behind every third-party platform in the estate. This role automates that administration wherever it can, and maintains the ownership, monitoring, and support structures that keep these systems supportable as the environment grows. It also helps shepherd new tools through Amazon security review and keeps tools already in use compliant as requirements change. We are looking for a hands-on administrator who thinks in systems and would rather automate an operational burden than absorb it. Curiosity about AI as a working tool is expected, both in applying it to infrastructure automation and in judging where it belongs. Understanding the pace and scale at which marketing and production teams work matters as much as infrastructure depth. Ambiguity is constant here: inherited systems, incomplete documentation, and dependencies that sit with vendors and internal security, identity, and tech partners." Now Responsibilities list items exactly as given: - Manages the AWS environment behind our content platforms, and evolves it as new workloads and integrations arrive - Designs storage tiering and lifecycle policy across petabyte-scale content and multiple systems, determining what lives where and why - Owns high-performance shared storage, backup, and archive across creative production and digital asset management - Automates administration of these systems so the environment scales without adding manual work - Maintains identity, access, and security compliance across the third-party platform estate, including single sign-on, credential lifecycle, and platform security review - Establishes and maintains operational standards for these systems, covering ownership records, monitoring, alerting, and support processes - Builds and secures the infrastructure new integrations run on, including credential storage and access paths for AI and third-party services - Represents our content platform systems to other XCM technology teams, partners across Amazon, and third-party providers, so integrations are well designed and ownership is clearly defined Now Requirements (Basic Qualifications) list: - 4+ years of site reliability engineering (SRE), systems engineering, systems administration, DevOps, security administration, or network administration experience - Experience using AWS services - Experience in any of the following: Python, Java, Perl, PHP, Ruby, Bash, Shell or equivalent - Bachelor's degree in Systems Engineering, Computer Science, or related field or relevant work experience - Experience implementing repeatable processes and driving automation or standardization - Experience directly working with cloud hosting technologies (AWS, Azure, etc.) - Direct ownership over live production cloud environment, including storage at scale, lifecycle, and compute - Experience supporting creative, marketing or media teams and their system needs Now Qualifications (Preferred Qualifications) list: - Experience and understanding of the workflow within a marketing, production, or creative department or company - Experience with multimedia content creation, or experience implementing a cloud-based technology solution - Experience with owning SSO across platforms including federated identity, SAML or OIDC integrations and certificate rotation - Experience with high-performance shared storage for media production, such as LucidLink, Qumulo, or Isilon - Familiar