Rack Integration Operations Engineer

We need to output HTML fragment with sections: About the role (maybe "About The Department"? Actually headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have content: About Us (company description) maybe not needed? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need to map content to these headings. We have "About The Department" and "Role Summary". Could treat as "About the role". Also "Key Responsibilities". Then "Qualifications Requirements" and "Desirable / Bonus Qualifications". Also maybe "What Makes Cloudflare Special?" could be something like "Benefits"? Not exactly benefits but could be "Benefits". However we should only include sections if posting has real specific content. The posting does not mention explicit Benefits, Pay, Schedule. So we should not create those sections. Also "Skills" maybe not explicit separate; qualifications cover skills. Could we include a Skills section? Probably not needed. Thus we will output sections: About the role (combining About Us? Actually About the role likely includes role summary and department). Responsibilities (Key Responsibilities). Qualifications (including Requirements and Desirable/Bonus). Possibly also a separate Skills? Not needed. We need to preserve all substantive information, not invent or summarize away detail. Use

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

  for prose. We need to remove boilerplate: cookie/navigation/legal/EEO etc. At end there is EEO statement, accommodation info, etc. Must remove those. Also remove duplicated lines. We need to keep all substantive info: About Us description? Might be considered company overview, not required but could be part of About the role? The instruction: "About Us" maybe not needed as a heading; but we could incorporate into About the role as prose. However we must not invent headings. We can just put it in a

  under About the role. We need to ensure we don't include the EEO statement etc. Let's extract substantive sections: - About Us: description of Cloudflare mission, network, etc. Keep. - About The Department: description of Infrastructure Engineering team, Hardware Integration group. - Role Summary: description of Rack Integration Operations Engineer role. - Key Responsibilities: bullet list (multiple sub-sections: Engineering & Quality Review, Materials & Logistics Operations Support, Partner & Program Management, AI Innovation & Process Automation). Each has sub-bullets. - Qualifications Requirements: list of requirements (Vendor & Manufacturing Experience, Hardware & BOM Proficiency, Program Management Discipline, Applied AI & Automation Skills, Cross-Functional Collaboration). - Desirable / Bonus Qualifications: list (Background in data center infrastructure hardware..., Experience writing lightweight scripts..., Familiarity with global hardware supply chain...). - What Makes Cloudflare Special?: description of projects (Galileo, Athenian, 1.1.1.1) and privacy commitment. Could be considered "Benefits"? Not exactly but it's about company culture/values. Could be placed under a section like "About Cloudflare" but not in allowed headings. However we could treat as part of "About the role" or maybe as a separate section "About Cloudflare"? Not allowed headings. The instruction says use headings from list; we can only emit those headings if we have content. We could put this under "About the role" as prose, but it's not about the role. However we could also create a section "About Cloudflare" but not allowed. Better to incorporate into "About the role" as additional context? Might be okay. But we must not create headings like "Benefits" unless posting actually states them. It does not list benefits like health insurance etc. So we skip Benefits, Pay, Schedule. Thus final HTML:

  About the role

  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.

  About The Department: The Infrastructure Engineering team builds and scales Cloudflare’s global network, ensuring high availability, security, and performance across hundreds of cities worldwide. Within Infrastructure Operations, the Hardware Integration group acts as the bridge between engineering designs and physical deployment, overseeing key third-party manufacturing partnerships, hardware quality, and supply chain logistics to keep our expanding footprint running seamlessly.

  Role Summary: As a Rack Integration Operations Engineer, you will serve as a technical quality gatekeeper and operational partner across Cloudflare's hardware build programs. Working collaboratively within the Infrastructure Engineering and Strategy teams, you will bridge the gap between engineering specifications and external contract manufacturing partners. In this role, you will ensure Bill of Materials (BOM) accuracy, optimize materials planning, track partner performance, and actively modernise internal operations by building light, AI-enabled automations to streamline repetitive workflows.

  Responsibilities

  • Engineering & Quality Review
    • Ensure BOM Accuracy: Review and validate complex BOMs prior to release to integration partners, proactively identifying part substitutions, spec mismatches, and potential build blockers.
    • Bridge Engineering & Production: Partner closely with hardware design engineers to resolve design change requests (DCRs) and BOM discrepancies throughout the build lifecycle.
    • Maintain Technical Quality Standards: Leverage functional expertise across rack-level power, networking, server, and firmware architectures to evaluate build compliance against Cloudflare specifications.
  • Materials & Logistics Operations Support
    • Support Materials Planning: Contribute to demand forecasting and materials planning for rack build programs, aligning partner capacity with component lead times.
    • Coordinate Supply Chain Logistics: Oversee inbound and outbound logistics for components and finished racks between partners and Cloudflare sites through to final shipment.
  • Partner & Program Management
    • Drive Partner Execution: Serve as an operational point of contact for external hardware integration partners regarding build progress, scheduling, and issue resolution.
    • Track SLAs & Quality Metrics: Contribute to vendor scorecards and KPI tracking across build quality, on-time delivery, and cost efficiency; lead root-cause analyses for recurring defects.
    • Maintain Program Visibility: Track hardware build cycles in Jira, leading documentation, status check-ins, and project closeouts alongside cross-functional teammates.
  • AI Innovation & Process Automation
    • Automate Operational Workflows: Identify manual, repetitive tasks across BOM reviews, reporting, and partner tracking, using AI tools and LLM prompt engineering to streamline processes.
    • Analyze Performance Data: Evaluate spend, build timelines, and quality trends using AI-assisted analysis tools to surface actionable operational insights.
    • Build Shared Tooling: Develop, document, and maintain sustainable, lightweight automation scripts and workflows for adoption across the broader team.

  Qualifications

  • Vendor & Manufacturing Experience: Professional background managing hardware vendor or contract manufacturing (EMS/ODM) relationships, including BOM validation, quality tracking, and schedule management.
  • Hardware & BOM Proficiency: Practical ability to evaluate rack-level technical specifications (power distribution, networking, server hardware, firmware) to ensure manufacturing compliance.
  • Program Management Discipline: Hands-on experience managing operational workflows in Jira, with a track record of tracking and reporting on team KPIs and SLAs.
  • Applied AI & Automation Skills: Practical experience using AI tools or LLMs to automate concrete workflows, optimize reporting, or perform data analysis.
  • Cross-Functional Collaboration: Strong written and verbal communication skills, with a track record of working effectively across engineering, procurement, supply chain, and external partner teams.

  Desirable / Bonus Qualifications

  • Background in data center infrastructure hardware (servers, network switches, rPDUs, enterprise cabling).
  • Experience writing lightweight scripts (Python, Google Apps Script, or similar) paired with AI developer tools.
  • Familiarity with global hardware supply chain and logistics operations.
  We might also include "What Makes Cloudflare Special?" as a paragraph under About the role or maybe as a separate section "About Cloudflare". Since not in allowed headings, we could add a

  after About the role describing that. Let's add a paragraph after the role summary: "What Makes Cloudflare Special? ..." as prose. Thus after Role Summary paragraph, add another

  with that content. Let's extract that content: "What Makes Cloudflare Special? 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 2014, we've equipped more than 2,400 journalism and civil society organizations in 111 countries with powerful tools to defend themselves against attacks that would otherwise censor their work, technology already used by Cloudflare’s enterprise customers--at no cost. Athenian Project: In 2017, we created the Athenian Project to ensure that state and local governments have the highest level of protection and reliability for free, so that their constituents have access to election information and voter registration. Since the project, we've provided services to more than 425 local government election websites in 33 states. 1.1.1.1: We released 1.1.1.1 to help fix the foundation of the Internet by building a faster, more secure and privacy-centric public DNS resolver. This is available publicly for everyone to use - it is the first consumer-focused service Cloudflare has ever released. Here’s the deal - we don’t store client IP addresses never, ever. We will continue to abide by our privacy commitment and ensure that no user data is sold to advertisers or used to target consumers. Sound like something you’d like to be a part of? We’d love to hear from you!" We should remove the invitation to apply? That's maybe boilerplate but it's part of the special section. It's not a call to action? It's encouraging to apply. Might be considered application instruction? It's not exactly instruction to apply, but it's encouraging. The instruction says remove application instructions. This is more like a