Senior Manager, Infrastructure Operations and Compliance

We need to output HTML fragment with sections: About the role (maybe "Position Overview" or "About Us"? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We need to preserve all substantive info, remove boilerplate like About Us (mission statement) maybe not needed? The "About Us" is generic fluff; we can drop it as boilerplate? It's not specific to role. The instructions: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" might be considered boilerplate but it's about company mission; not sure if we should keep. The role description includes "Position Overview". We'll treat that as "About the role". We'll include sections: About the role (Position Overview), Responsibilities (What You'll Do), Requirements (Required Experience), Qualifications (Preferred Qualifications), Benefits, Pay (Compensation). Possibly Schedule not present. Also maybe "Reporting Structure" could be part of About the role? Not a standard heading; we could include as part of About the role or maybe omit. The instruction: prefer few substantive sections over many thin ones. We could combine Reporting Structure into About the role. Also "Equity" maybe part of Compensation? Could include under Compensation. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we need list items. For requirements list. For preferred qualifications list. For benefits list. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. We need to remove duplicated lines. Ensure we don't repeat. Let's extract content. First, Position Overview paragraph: "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." That's the overview. Next "What You'll Do" with subsections: Team Leadership, Unified Decommissioning Lifecycle, Maintain Team Operational Accountability, DCSC Compliance & Access Control Accountability, Automation & Operational Efficiency. Each has bullet points (some paragraphs). We need to extract each bullet as list items. Let's parse: 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. Now "Who You Are" paragraphs describing desired traits. This could be part of Requirements or Qualifications? It's more like "Who You Are" describing ideal candidate. Could be part of Requirements or Qualifications. We'll treat as Requirements (maybe combine with Required Experience). But we have separate Required Experience and Preferred Qualifications sections later. We need to preserve all substantive info. So we need to include the "Who You Are" paragraphs as part of Requirements or maybe as a separate section like "Qualifications"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put "Who You Are" under Requirements (or Qualifications). Since there is also a "Required Experience" and "Preferred Qualifications". We could treat Required Experience as Requirements, and Preferred Qualifications as Qualifications. The "Who You Are" could be part of Requirements as well (maybe merge). But to avoid duplication, we could incorporate its content into Requirements section as prose (

  ) and then list Required Experience as bullet list. Similarly, "Reporting Structure" could be a short paragraph under About the role. Compensation section: includes "Compensation may be adjusted depending on work location. For Colorado based hires: Estimated annual salary of $156,000 - $215,000. Washington (Kirkland), and Washington D.C. based hires: Estimated annual salary of $182,000 - $251,000." Also "Equity This role is eligible to participate in Cloudflare's equity plan." So we need to include that. Benefits section: list of benefits as given. We must not include boilerplate like "About Us" mission, "Available Locations: Austin SeattleDenverAtlanta Washington DCApplication Deadline: December 16, 2026" maybe we should keep location and deadline? The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. Location and deadline could be minor metadata; we could include as a short p under About the role or maybe drop. The instruction says preserve ALL substantive information; location and deadline are substantive? They are details about the job. Might be worth keeping. But they said "fold minor metadata into a short

  or drop it." Location and deadline could be considered minor metadata. I'd include them as a short p after the overview. We must not include sections like "Schedule" if not present. No schedule info. We must not include "Skills" heading unless there is specific skills list; we have some skills in Required Experience etc. Could combine. We need to output only HTML fragment, no /, no markdown. Let's construct:

  About the role

  [overview paragraph]

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

  Reporting Structure: This role reports to the Director, Infrastructure Operations (AMER) and is part of the broader Infrastructure Operations leadership team.

  Then Responsibilities:

  Responsibilities

  • 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
  • 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
  • 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.
  • 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