Senior Engineer, DevOps

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. The posting includes "About The Role" and then "What You'll Do" (responsibilities), "What We're Looking For" (requirements/qualifications/skills), "Nice to Have" (maybe skills). Also salary range given: Los Angeles Salary Range $144,000 - $180,000 USD. Benefits: mention "For information about our benefits, please visit https://benefitsatfanatics.com/". No explicit benefits list, but we have a link. Should we include Benefits section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The benefits link is specific content? It's a pointer to benefits page, not a list. Might be considered not specific enough. However they said "For information about our benefits, please visit ..." That's not a list of benefits. Probably we should not create Benefits section because no specific benefits listed. Pay: we have salary range, so include Pay section. Schedule: not mentioned. So omit Schedule. We need headings:

for each section. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. The job title is Senior Engineer, DevOps. Not include. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the About Us description? The instruction: "About Us" is part of posting but maybe not needed? The sections we need to output: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The "About Us" is not one of those headings; but we might include it as prose under About the role? Actually "About The Role" is a heading we should use as

  About the role

  . The content under that heading includes description of role. The "About Us" preceding that is company overview; not required to include? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should include the About Us content somewhere. Where? It could be placed before the About the role heading as a

  maybe. Since we cannot add arbitrary headings not in list, we can just put it as a

  before the first heading. That's allowed: output only HTML fragment, we can have paragraphs and headings. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use

  for section headings (list). It doesn't say we cannot have other headings, but better to stick to those. We can include About Us as a

  without heading. Thus structure:

  About Us Fanatics is building a leading global digital sports platform.... (the whole About Us paragraph). Then

  About the role

  then content: maybe a

  summarizing the role description? The posting includes "About The Role We're looking for a Senior Engineer, DevOps to join the Live & Collect Infrastructure team in Los Angeles. You'll design, build, and operate the cloud foundation that powers Fanatics' Live & Collect platforms across AWS and GCP. This is a hands-on role for someone who enjoys solving hard infrastructure problems at scale, applying AI/ML tooling to infrastructure and operations, mentoring other engineers, and championing DevOps maturity across the org." That's prose; we can put in

  . Then Responsibilities: heading

  Responsibilities

  then
  • items from "What You'll Do". Need to preserve each bullet. Then Requirements/Qualifications/Skills: The posting has "What We're Looking For" (requirements) and "Nice to Have". We could combine into Requirements and Skills sections. But we need to decide: The instruction: prefer a few substantive sections over many thin ones. Could make one section "Requirements" containing both required and nice-to-have? But we have separate headings possible: Requirements, Qualifications, Skills. Might be overlapping. Better to have Requirements (mandatory) and Skills (nice-to-have). Qualifications maybe education. Let's parse: What We're Looking For list: - 5+ years of experience in cloud engineering, infrastructure, or SRE roles, with production experience in both AWS and GCP. - Strong background with infrastructure-as-code (Terraform preferred) and container orchestration (Kubernetes). - Hands-on database administration and tuning experience with Cloud Spanner, AWS RDS, and PostgreSQL (performance tuning, replication, backup/recovery, capacity planning). - Experience with CI/CD tooling and modern DevOps automation practices. - Familiarity with AI/ML-powered tooling for infrastructure automation, monitoring, or operations (e.g., AIOps platforms, LLM-based automation, copilots for infra/ops workflows). - Solid scripting/programming ability (Python, Go, or similar) for automation and tooling. - Demonstrated experience operating and troubleshooting large-scale, distributed, high-availability systems. - Comfortable carrying on-call responsibilities and driving incidents to resolution under pressure. - Strong communication skills and experience mentoring other engineers. - Bachelor's degree in Computer Science, Engineering, or equivalent practical experience. Nice to Have: - Experience supporting live events, auctions, or other high-traffic consumer platforms. - Hands-on experience building or integrating AI/ML pipelines or infrastructure for AI workloads. - Relevant cloud certifications (AWS or GCP). - Familiarity with cost optimization and FinOps practices across multi-cloud environments. We could map: Requirements = the mandatory list; Skills = nice-to-have (maybe also include technical skills). Qualifications could be education (Bachelor's degree). But we already have education in mandatory list. Could put education under Qualifications. However to avoid duplication, maybe we just have Requirements (including education) and Skills (nice-to-have). The instruction says prefer few substantive sections over many thin ones. So maybe just two sections: Requirements and Skills. But we also need About the role and Responsibilities. Pay section. Thus sections: About the role, Responsibilities, Requirements, Skills, Pay. We must not include Benefits or Schedule. Now format. We need to preserve all substantive information: include About Us paragraph, About the role paragraph, responsibilities bullets, requirements bullets, skills bullets, pay range. Also include the note about salary range being base pay only etc. That's part of Pay section. Should we include that prose? Yes. Also include the link for benefits? Not including Benefits section, but we could mention benefits link in About Us? Not needed. We must not include boilerplate like "Ensure your Fanatics job offer is legitimate..." etc. Remove that. Also remove "By submitting your application, you agree to our terms of service..." etc. Also remove "The salary range represents base pay only..." but that is part of Pay; we should keep it as it's substantive about pay. Keep. Now craft HTML. Start with

    About Us ...

    (the whole About Us paragraph). Ensure we keep line breaks? Not needed. Then

    About the role

    ...

    Then

    Responsibilities

    • ... each bullet. Then

      Requirements

      • ... each mandatory bullet. Then

        Skills

        • ... each nice-to-have bullet. Then

          Pay

          ... salary range sentence plus note about base pay only etc.

          Make sure not to include any extra headings. Now write the content exactly as in posting, preserving details. About Us paragraph: "Fanatics is building a leading global digital sports platform. We ignite the passions of global sports fans and maximize the presence and reach for our hundreds of sports partners globally by offering products and services across Fanatics Commerce, Fanatics Collectibles, and Fanatics Betting & Gaming, allowing sports fans to Buy, Collect, and Bet. Through the Fanatics platform, sports fans can buy licensed fan gear, jerseys, lifestyle and streetwear products, headwear, and hardgoods; collect physical and digital trading cards, sports memorabilia, and other digital assets; and bet as the company builds its Sportsbook and iGaming platform. Fanatics has an established database of over 100 million global sports fans; a global partner network with approximately 900 sports properties, including major national and international professional sports leagues, players associations, teams, colleges, college conferences and retail partners, 2,500 athletes and celebrities, and 200 exclusive athletes; and over 2,000 retail locations, including its Lids retail stores. Our more than 22,000 employees are committed to relentlessly enhancing the fan experience and delighting sports fans globally. Fanatics Collectibles is a new company operating at the intersection of collectibles, culture, and technology. Backed by world-class investors, operators, and sports & entertainment partners, we are building the global leader in next-generation collectibles. As part of the broader Fanatics ecosystem, we leverage a digital sports platform that spans over 900 sports properties and engages more than 81 million fans. Together, we are reimagining every part of the collectibles experience for fans, partners, and creators." That's long but we keep. About the role paragraph: "We're looking for a Senior Engineer, DevOps to join the Live & Collect Infrastructure team in Los Angeles. You'll design, build, and operate the cloud foundation that powers Fanatics' Live & Collect platforms across AWS and GCP. This is a hands-on role for someone who enjoys solving hard infrastructure problems at scale, applying AI/ML tooling to infrastructure and operations, mentoring other engineers, and championing DevOps maturity across the org." Now responsibilities bullets (from "What You'll Do"): - Design, build, and maintain scalable, resilient infrastructure across AWS and GCP using infrastructure-as-code (Terraform). - Own core cloud platform services — Kubernetes, networking, and CI/CD pipelines. - Evaluate and integrate AI-assisted tooling (e.g., LLM-based automation, AIOps, intelligent monitoring) to improve infrastructure efficiency and operations. - Partner with product and platform engineering teams to architect cloud solutions that support high-traffic, high-availability Live & Collect systems. - Administer and tune managed and self-hosted databases (Cloud Spanner, AWS RDS, PostgreSQL), including performance tuning, capacity planning, backup/recovery, and query optimization. - Drive reliability and cost-efficiency initiatives across multi-cloud environments. - Champion DevOps best practices, scalable infrastructure patterns, and observability standards across engineering teams. - Mentor engineers on cloud architecture, automation, and operational excellence. - Participate in an on-call rotation, responding to and resolving production incidents to meet SLAs. - Contribute to security hardening, compliance, and disaster-recovery planning for cloud infrastructure. Make sure to preserve punctuation and em dashes etc. Now Requirements bullets (mandatory): - 5+ years of experience in cloud engineering, infrastructure, or SRE roles, with production experience in both AWS and GCP. - Strong background with infrastructure-as-code (Terraform preferred) and container orchestration (Kubernetes). - Hands-on database administration and tuning experience with Cloud Spanner, AWS RDS, and PostgreSQL (performance tuning, replication, backup/recovery, capacity planning). - Experience with CI/CD tooling and modern DevOps automation practices. - Familiarity with AI/ML-powered tooling for infrastructure automation, monitoring, or operations (e.g., AIOps platforms, LLM-based automation, copilots for infra/ops workflows). - Solid scripting/programming ability (Python, Go, or similar) for automation and tooling. - Demonstrated experience operating and troubleshooting large-scale, distributed, high-availability systems. - Comfortable carrying