Senior Manager, Infrastructure Operations and Compliance
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections with those headings only if content exists.
We have content: Position Overview (description of role). That could go under "About the role". Also "What You'll Do" is responsibilities. "Who You Are" maybe qualifications/requirements. There's "Required Experience" and "Preferred Qualifications". Also "Reporting Structure" maybe not needed. "Compensation" includes pay ranges for specific locations. "Equity" maybe part of compensation but not required. "Benefits" section present. "Schedule" not mentioned; no schedule info. So we should not include Schedule heading.
We need to include Pay section if posting actually states them. Yes compensation includes salary ranges for Colorado, Washington (Kirkland), and Washington D.C. So we can include Pay section with that info.
Benefits section: we have benefits description. Should include.
Qualifications: maybe combine Required Experience and Preferred Qualifications under Qualifications? Or separate Requirements and Qualifications? The instruction lists both Requirements and Qualifications as possible headings. We need to decide what to put where. Typically Requirements = required experience; Qualifications = preferred qualifications. We'll follow that.
Skills: maybe we can extract skills from responsibilities? Not explicit. Could omit if no specific skills listed. Better to omit Skills section if no explicit skills.
About the role: we can use Position Overview paragraph.
Responsibilities: "What You'll Do" bullet points (though they are paragraphs with bold headings). We need to convert to - . The content includes multiple sub-sections: Team Leadership, Unified Decommissioning Lifecycle, Maintain Team Operational Accountability, DCSC Compliance & Access Control Accountability, Automation & Operational Efficiency. Each has details. We'll make each as
- maybe with internal
or
? The instruction: Use - for any list of duties/requirements/benefits, and
for prose. So we can treat each duty as
- containing prose (maybe with
). We'll keep it simple: each duty as
- with the text.
Requirements: Required Experience bullet points (list). We'll make
- .
Qualifications: Preferred Qualifications bullet points.
Benefits: list of benefits (Health & Welfare Benefits, Financial Benefits, Time Off). We'll make
- .
Pay: compensation ranges. We'll put as
maybe.
We must not include boilerplate like "Available Locations: Austin SeattleDenverAtlanta Washington DCApplication Deadline: December 16, 2026". That's metadata; we should fold minor metadata into a short
or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short
for locations and deadline maybe. But not required to include; we can drop. Safer to drop as it's minor metadata.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from sections we include.
Let's extract content precisely.
About Us: we may not need to include as it's company description; but could be part of About the role? The instruction says use headings like About the role. The About Us is not about the role but company. Might be considered not needed. However we could include it under About the role as background. But risk of adding content not explicitly under a heading. The instruction: "include a section ONLY when the posting has real, specific content for it". The posting has "About Us" which is specific content about company. Could map to About the role? Not exactly. Safer to omit About Us entirely? But then we lose substantive info about company mission. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit About Us, we lose that info. However maybe we can incorporate it into About the role section as a brief description. The instruction does not forbid adding content under a heading that is not exactly matching; we just need to use those headings for sections. So we can put the About Us paragraph under
About the role
as prose. That would preserve it.
Thus About the role will contain the About Us paragraph plus Position Overview? Might be too much but okay.
Let's craft:
About the role
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.
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.
Now Responsibilities: "What You'll Do" with subheadings. We'll create - each subheading as a list item, with its details as
inside.
Let's extract each:
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 maybe
inside.
Now Requirements: Required Experience bullet points.
Extract:
- 7+ years in infrastructure operations, data center operations, network operations, or a closely related field, with at least 3 years in a people management role
- Demonstrated experience managing managers and holding multiple teams accountable to operational SLAs simultaneously
- Direct experience with physical data center operations including hardware lifecycle management, decommissioning, colocation vendor management, or break-fix operations
- Familiarity with compliance frameworks relevant to physical infrastructure: SOC 2, ISO 27001, FedRAMP, or equivalent — at an operational (not auditor) level
- Strong program management instincts: comfortable running complex, multi-workstream initiatives with dependencies across teams, vendors, and time zones
- Proven track record of driving operational efficiency through process redesign or automation
or
- ? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can treat each duty as
- containing prose (maybe with
). We'll keep it simple: each duty as
- with the text.
Requirements: Required Experience bullet points (list). We'll make
- .
Qualifications: Preferred Qualifications bullet points.
Benefits: list of benefits (Health & Welfare Benefits, Financial Benefits, Time Off). We'll make
- .
Pay: compensation ranges. We'll put as
maybe. We must not include boilerplate like "Available Locations: Austin SeattleDenverAtlanta Washington DCApplication Deadline: December 16, 2026". That's metadata; we should fold minor metadata into a short
or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short
for locations and deadline maybe. But not required to include; we can drop. Safer to drop as it's minor metadata. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from sections we include. Let's extract content precisely. About Us: we may not need to include as it's company description; but could be part of About the role? The instruction says use headings like About the role. The About Us is not about the role but company. Might be considered not needed. However we could include it under About the role as background. But risk of adding content not explicitly under a heading. The instruction: "include a section ONLY when the posting has real, specific content for it". The posting has "About Us" which is specific content about company. Could map to About the role? Not exactly. Safer to omit About Us entirely? But then we lose substantive info about company mission. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit About Us, we lose that info. However maybe we can incorporate it into About the role section as a brief description. The instruction does not forbid adding content under a heading that is not exactly matching; we just need to use those headings for sections. So we can put the About Us paragraph under
About the role
as prose. That would preserve it. Thus About the role will contain the About Us paragraph plus Position Overview? Might be too much but okay. Let's craft:About the role
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.
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.
Now Responsibilities: "What You'll Do" with subheadings. We'll create- each subheading as a list item, with its details as
inside. Let's extract each: 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 maybe
inside. Now Requirements: Required Experience bullet points. Extract: - 7+ years in infrastructure operations, data center operations, network operations, or a closely related field, with at least 3 years in a people management role - Demonstrated experience managing managers and holding multiple teams accountable to operational SLAs simultaneously - Direct experience with physical data center operations including hardware lifecycle management, decommissioning, colocation vendor management, or break-fix operations - Familiarity with compliance frameworks relevant to physical infrastructure: SOC 2, ISO 27001, FedRAMP, or equivalent — at an operational (not auditor) level - Strong program management instincts: comfortable running complex, multi-workstream initiatives with dependencies across teams, vendors, and time zones - Proven track record of driving operational efficiency through process redesign or automation
- each subheading as a list item, with its details as
- .
Pay: compensation ranges. We'll put as
- .
Qualifications: Preferred Qualifications bullet points.
Benefits: list of benefits (Health & Welfare Benefits, Financial Benefits, Time Off). We'll make