Senior Manager, Infrastructure Operations and Compliance

We need to output HTML fragment with sections for headings where content exists. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must include sections only if real specific content. We need to parse the posting: It includes About Us (company description), Position Overview, What You'll Do (with subsections), Who You Are, Required Experience, Preferred Qualifications, Reporting Structure, Compensation, Equity, Benefits, What Makes Cloudflare Special? Also Available Locations and Application Deadline (metadata). We should maybe include a short paragraph for metadata (Available Locations, Application Deadline) as a

. Not as heading. We must not create sections like Pay/Schedule/Benefits unless posting actually states them. Compensation is stated (salary ranges). So we can have a Compensation section with

Compensation

and then

with the salary ranges. Equity: mention eligibility to participate in equity plan. Benefits: described. So we can have Benefits section. Schedule: not mentioned. So omit. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Must not omit details. Must not create placeholder sections. We need to decide which sections to include: About Us (company description) maybe as

  About Us

  . Position Overview maybe as

  Position Overview

  . What You'll Do could be a heading with subpoints; but we could break into subheadings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those standard headings, but we can also use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those standard headings where applicable. But we can also use other headings if needed? The examples are just examples; they didn't forbid other headings. However to be safe, we can map content to those standard headings: About the role (maybe Position Overview), Responsibilities (What You'll Do), Requirements (Required Experience), Qualifications (Preferred Qualifications), Skills (maybe not separate), Benefits, Pay (Compensation). Schedule omitted. We also have About Us (company description) maybe not a standard heading but could be "About the role"? Actually About Us is about company, not role. Could be omitted? But we need to preserve all substantive information. Could include as a

  without heading? 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. So we can still use

  for About Us if we want. Probably fine. We need to avoid repeating job title as heading. Not needed. We need to remove cookie/navigation/legal/EEO etc. Not present. We need to output only HTML fragment. Let's craft:

  About Us

  At Cloudflare, we are on a mission to help build a better Internet. Today the company runs one of the world’s largest networks that powers millions of websites and other Internet properties for customers ranging from individual bloggers to SMBs to Fortune 500 companies. Cloudflare protects and accelerates any Internet application online without adding hardware, installing software, or changing a line of code. Internet properties powered by Cloudflare all have web traffic routed through its intelligent global network, which gets smarter with every request. As a result, they see significant improvement in performance and a decrease in spam and other attacks. Cloudflare was named to Entrepreneur Magazine’s Top Company Cultures list and ranked among the World’s Most Innovative Companies by Fast Company. At Cloudflare, we’re not looking for people who wait for a polished roadmap; we’re looking for the builders who see the cracks in the Internet that everyone else has simply learned to live with. We value candidates who have the instinct to spot a "normalized" problem and the AI-native curiosity to create a solution using the latest tools. Our culture is built on iteration, leveraging AI to ship faster today to make it better tomorrow, while ensuring that every improvement, no matter how small, is shared across the team to lift everyone up. If you’re the type of person who values curiosity over bureaucracy, and that AI is a partner in solving tough problems to keep the Internet moving forward, you’ll fit right in.

  Then maybe a short paragraph for metadata: Available Locations: Austin SeattleDenverAtlanta Washington DC Application Deadline: December 16, 2026. We'll combine.

  Available Locations: Austin, Seattle, Denver, Atlanta, Washington DC. Application Deadline: December 16, 2026.

  Then Position Overview.

  Position Overview

  Cloudflare is looking for a Senior Manager to lead a unified Infrastructure Operations function spanning physical network reliability, operational security, and global regulatory compliance across 750+ data center sites in 125+ countries. The leader in this role ensures 24x7 operational availability of Cloudflare's network infrastructure through incident response, hardware break-fix, circuit management, and physical hardware lifecycle operations. This leader also owns physical access control policy and administration, periodic access reviews, and evidence-based compliance delivery across SOC 2 Type II, ISO 27001, FedRAMP, ISMAP, and IRAP. You will lead two teams, setting organizational direction, building talent, and being accountable for outcomes across the full lifecycle of Cloudflare's physical infrastructure: from how hardware is deployed and maintained, to how access is controlled and reviewed, to how assets are securely retired and evidenced for audit. The breadth of this scope demands a leader who can hold the org-level tensions, speed versus rigor, global scale versus precise detail, partner dependency versus uncompromising standards, without losing either end. You will bring credibility across both dimensions of this role. On the infrastructure side, a strong grasp of data center colocation environments, network architecture, and hardware operations as well as the judgment to lead managers and teams who live in that world every day. On the compliance side, the organizational instinct to maintain audit readiness continuously, not just at cycle time, and the stakeholder fluency to navigate relationships with GRC, government auditors, and strategic global partners. Above all, you will bring a bias toward building smarter processes, better tooling, and AI-assisted operations that multiply your team's capacity as Cloudflare's footprint continues to grow.

  Then Responsibilities (What You'll Do). We'll break into sub-sections maybe using
  • for each bullet. We need to preserve all details. The "What You'll Do" includes several bullet-like paragraphs: Team Leadership, Unified Decommissioning Lifecycle, Maintain Team Operational Accountability, DCSC Compliance & Access Control Accountability, Automation & Operational Efficiency. We can make each as a
  • with internal paragraphs? Probably each
  • can contain

    for prose. But we need to keep details. Simplify: For each major heading, we can have

    ? But instruction only mentions

    . Could use

    for each subsection? Might be okay but could be many sections. They said prefer a few substantive sections over many thin ones. So maybe we keep one Responsibilities section with a

    where each
    • contains the detailed prose. Let's extract each subsection content: Team Leadership: - Lead two teams, the Operations team and the Security and Compliance team. - Set goals, develop talent, and build a culture of operational excellence and compliance-consciousness across both functions - Hold both teams to shared SLAs and quality standards, balancing the urgency of 24x7 incident response with the rigor of compliance audit cycles - Serve as the escalation point for cross-team issues, complex vendor negotiations, and decisions that touch both operational and regulatory domains Unified Decommissioning Lifecycle: - Own the end-to-end DECOM process as a single, governed workflow: physical collections and unracking, secure asset destruction with CoD issuance (ITAD vendor management), serial number verification, compliance evidence filing, and records closure - Eliminate the current handoff gap between Maintain's physical operations and DCSC's compliance oversight building a single, auditable pipeline from "decom triggered" to "evidence archived”. - Drive ITAD vendor relationships, escalation paths, and contractual SLAs for asset destruction across all regions (APAC, EMEA, NASA, South America) - Maintain audit-readiness of decommissioning records for SOC 2, ISO 27001, PCI DSS, and FedRAMP control requirements Maintain Team Operational Accountability: - Accountable for 24x7 incident response coverage across all Cloudflare locations: carrier outages, DC facility issues, hardware degradation, and power/temperature events. - Oversee hardware break-fix operations including coordination with Metro Technicians, third-party repair vendors and remote contractors. - Drive maturity in circuit decommissioning, RMA management, and physical collections processes - Ensure on-call schedules, handover protocols, and incident SLAs are consistently met across APAC, EMEA, and NASA shifts. DCSC Compliance & Access Control Accountability: - Accountable for quarterly and monthly access review cycles (QAR/MAR) across 750+ global data center sites covering SOC 2 Type II, ISO 27001, FedRAMP Moderate/High, ISMAP, and IRAP frameworks - Own the physical access provisioning and deprovisioning function, including SLA adherence and ACL integrity - Serve as the senior owner of the team’s automation initiatives - Maintain executive-level relationships with GRC leads across all active compliance frameworks; be the accountable voice for DCSC's control obligations in audit conversations - Represent DCSC at Monthly Business Reviews and executive infrastructure health checks Automation & Operational Efficiency: - Drive a meaningful reduction in manual operational burden across both teams identifying and prioritizing automation opportunities in access reviews, decommissioning evidence collection, portal data extraction, and incident triage - Sponsor and guide the development of internal tooling (DCSC Portal, automation scripts, AI-assisted workflows) that multiplies team capacity without proportional headcount growth - Evaluate and adopt AI tooling for repetitive operational tasks, documentation acceleration, root-cause analysis, and compliance evidence generation. We'll put each as
    • with line breaks maybe
      or

      . Use

      inside

    • for readability. Now Who You Are section: Could be

      Who You Are

      with paragraphs. Required Experience:

      Required Experience

      with
      • each bullet. Preferred Qualifications:

        Preferred Qualifications

        with
        • . Reporting Structure:

          Reporting Structure

          with

          . Compensation:

          Compensation

          with

          containing salary ranges. Equity: maybe

          Equity

          with

          . Benefits:

          Benefits

          with
          • for each benefit category. What Makes Cloudflare Special?: maybe

            What Makes Cloudflare Special?

            with

            (truncated? The text cuts off at "technology already u". It seems incomplete. We should preserve as given, but it's incomplete; we should not invent. We'll include the text as is, but note it's cut off. We'll include exactly what's provided: "We’re not just a highly ambitious, large-scale technology company. We’re a highly ambitious, large-scale technology company with a soul. Fundamental to our mission to help build a better Internet is protecting the free and open Internet. Project Galileo: Since