Engineering Manager, Fleet Provisioning Automation

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info. Let's parse the posting. First paragraph: description of CoreWeave (company intro). Might be considered "About the role"? Actually "What You’ll Do" is a section. Then "About The Role". Then "In This Role, You Will" bullet list (but not bullet). Then "Who You Are" (requirements). Then "Wondering if you’re a good fit?" etc. Then "The base salary range for this role is $165,000 to $242,000." Then "In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility)." Then "What We Offer" with benefits list. We need sections: About the role (maybe from "About The Role" paragraph). Responsibilities (from "What You’ll Do" and "In This Role, You Will"). Requirements/Qualifications/Skills (from "Who You Are" and "Wondering if you’re a good fit?" maybe). Benefits (list). Pay (salary range). Schedule? Not mentioned. So we omit Schedule. We must not repeat job title as heading. No Job ID. We need to use

for each section heading. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Learn more at www.coreweave.com." maybe considered boilerplate? It's not navigation but maybe okay to keep? It's not essential; but we can keep as part of company description? Might be considered minor metadata; we could fold into a short

  or drop. Safer to drop. Also remove "Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025." That's substantive? It's company background; maybe keep as part of intro? Not required but could be considered substantive. However we need to preserve ALL substantive information. The intro about CoreWeave is not directly about the role but maybe considered company description; but we can keep as part of "About the role"? Might be okay. But we need to avoid duplication: there is repeated "What We Offer" and later benefits list. We'll include benefits once. We need to ensure we don't include sections with filler like "commensurate with experience". Not present. Let's extract content. Company intro: "CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025." We could put this in a

  under maybe an "About CoreWeave" but not a required heading. Since we only have headings for specific sections, we could just include this as a

  before sections. The instruction: Output ONLY the HTML fragment — no /. So we can start with a

  containing that. Then "What You’ll Do" heading? Actually they have "What You’ll Do" as a heading. Then paragraph: "CoreWeave’s Fleet Provisioning Automation (FPA) team is responsible for the automated provisioning and lifecycle management of CoreWeave’s rapidly growing fleet of hardware nodes and node types. The team streamlines and coordinates node bring-up and configuration, node delivery, health monitoring, and failure-response automation into a cohesive, high-reliability engine of fleet management. This group sits at the intersection of hardware, data center operations, and platform engineering, building the software that keeps our global fleet healthy and ready for customer workloads." That's responsibilities. Could be under "Responsibilities". Then "About The Role" heading with paragraph: "We are seeking an Engineering Manager for the Fleet Provisioning Automation team who can manage and grow our team of developers. This individual will facilitate development by supporting the team in process, communication, and accountability across the team’s domain, and champion reliability and results." Then "In This Role, You Will" with bullet-like sentences: "Lead and grow a team of talented and dedicated Go developers in the US and EU. Provide prioritization, direction, and support to software engineers developing Kubernetes operators and custom resource definitions (CRDs) to automate node provisioning and lifecycle management of CoreWeave’s entire server fleet. Collaborate closely with fleet operations, hardware engineering, and Kubernetes infrastructure teams to design solutions to problems of scale for managed Kubernetes and bare metal deployments and the operation of CoreWeave’s global hardware fleet. Develop a program of onboarding, documentation, enablement, and performance management to help your team members achieve new heights of personal growth and capability. Set the culture and tone for how your team works together — both in how they communicate with and support each other, and in how they enable the rest of CoreWeave." These are duties/responsibilities as well. Could combine under Responsibilities. Then "Who You Are" heading with paragraph: "7+ years of experience in software or infrastructure engineering, including 3+ years in a leadership capacity. Experience guiding teams to create test plans, deployment automation, and supporting tooling that enable safe rollouts and continuous improvement of fleet provisioning services. A background that includes the knowledge and practice of SRE fundamentals, incident management, blameless culture, observability, and change management." Then "Wondering if you’re a good fit? We believe in investing in our people, and value candidates who can bring their own diversified experiences to our teams – even if you aren't a 100% skill or experience match. Here are a few qualities we’ve found compatible with our team. If some of this describes you, we’d love to talk." Then list of qualities: bullet-like sentences: "You believe in the value of automation and will champion practices that drive reliability, reduce the need for manual operations, and drive the adoption of cross-team processes and tooling. You love helping people on their journeys to become their best selves and are comfortable extending your influence to partners, peers, and senior leadership. You’re comfortable building and leading a global team of high-performing, diverse engineers." These are also qualifications/skills. Then salary: "The base salary range for this role is $165,000 to $242,000. The starting salary will be determined based on job-related knowledge, skills, experience, and market location. We strive for both market alignment and internal equity when determining compensation. In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility)." Then "What We Offer" heading with paragraph: "The range we’ve posted represents the typical compensation range for this role. To determine actual compensation, we review the market rate for each candidate which can include a variety of factors. These include qualifications, experience, interview performance, and location. In addition to a competitive salary, we offer a variety of benefits to support your needs. The benefits below reflect our US-based offerings for full-time employees; for roles in other locations, benefits vary and are shared during the hiring process." Then list of benefits: each line preceded by dash. We'll convert to

  • . List: - Medical, dental, and vision insurance - 100% paid for by CoreWeave - Company-paid Life Insurance - Voluntary supplemental life insurance - Short and long-term disability insurance - Flexible Spending Account - Health Savings Account - Tuition Reimbursement - Ability to Participate in Employee Stock Purchase Program (ESPP) - Mental Wellness Benefits through Spring Health - Family-Forming support provided by Carrot - Paid Parental Leave - Flexible, full-service childcare support with Kinside - 401(k) with a generous employer match - Flexible PTO - Catered lunch each day in our office and data center locations - A casual work environment - A work culture focused on innovative disruption We need to keep all. Then after that there is "California Applicants California Consumer Privacy Act Equal Opportunity & Accommodations ..." which is boilerplate EEO etc. Must remove. Also "Export Control Compliance ..." also boilerplate/legal; remove. Thus final HTML: start with company intro

    . Then maybe

    About the Role

    with paragraph(s). Then

    Responsibilities

    with
    • for duties. Could combine "What You’ll Do" and "In This Role, You Will" into list items. Then

      Qualifications

      (or Requirements) with
      • for experience and qualities. Then

        Benefits

        with
        • . Then

          Pay

          with

          containing salary range and details. We must not include Schedule. Check that we don't repeat heading with filler. Let's craft. We need to ensure we don't include any markdown fences. Let's produce:

          CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025.

          About the Role

          We are seeking an Engineering Manager for the Fleet Provisioning Automation team who can manage and grow our team of developers. This individual will facilitate development by supporting the team in process, communication, and accountability across the team’s domain, and champion reliability and results.

          Responsibilities

          • Lead and grow a team of talented and dedicated Go developers in the US and EU.
          • Provide prioritization, direction, and support to software engineers developing Kubernetes operators and custom resource definitions (CRDs) to automate node provisioning and lifecycle management of CoreWeave’s entire server fleet.
          • Collaborate closely with fleet operations, hardware engineering, and Kubernetes infrastructure teams to design solutions to problems of scale for managed Kubernetes and bare metal deployments and the operation of CoreWeave’s global hardware fleet.
          • Develop a program of onboarding, documentation, enablement, and performance management to help your team members achieve new heights of personal growth and capability.
          • Set the culture and tone for how your team works together — both in how they communicate with and support each other, and in how they enable the rest of CoreWeave.
          • The Fleet Provisioning Automation (FPA) team is responsible for the automated provisioning and lifecycle management of CoreWeave’s rapidly growing fleet of hardware nodes and node types. The team streamlines and coordinates node bring-up and configuration, node delivery, health monitoring, and failure-response automation into a cohesive, high-reliability engine of fleet management. This group sits at the intersection of hardware, data center operations, and platform engineering, building the software that keeps our global fleet healthy and ready for customer workloads.

          Qualifications

          • 7+ years of experience in software or infrastructure engineering, including