Senior Hardware Engineer, Server Infrastructure

We need to output HTML fragment with sections: About the role, Responsibilities (What You’ll Do), Requirements/Qualifications (Who You Are, Preferred Qualifications maybe), Benefits (What We Offer). Also maybe Pay? Not present. Schedule? Not present. So include sections with actual content. We must not repeat job title. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove sections like "Wondering if You’re a Good Fit?" maybe considered filler? It's more like motivational but could be considered part of "Who You Are"? Might be considered not substantive? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The "Wondering if You’re a Good Fit?" contains statements like "You enjoy solving problems..." which are somewhat generic but still content. Might be considered part of "Who You Are" but could be separate? Safer to incorporate into Who You Are or maybe omit as it's somewhat fluff. However it's still substantive? It's more about fit. Could be considered part of "Who You Are". I'd include it within Who You Are as additional bullet points. We need to use

for section headings. Use

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

  for prose. We need to preserve all substantive information. So we need to capture the responsibilities list (What You’ll Do) as bullet points. Also "Who You Are" list of qualifications. Also "Preferred Qualifications" list. Also benefits list. We need to avoid duplication: The responsibilities list includes many bullet-like sentences separated by periods. We'll convert each sentence into

• . Ensure we keep all details. Let's extract responsibilities: - Design and develop server hardware infrastructure to support CoreWeave’s high-performance workloads. - Automate all aspects of the server hardware lifecycle, from provisioning and configuration through firmware management, monitoring, and decommissioning. - Develop and maintain hardware and firmware management services that ensure reliability at scale. - Develop and implement monitoring and alerting for server hardware health, improving alert quality to support reliable on-call response. - Serve as a senior point of contact for hardware escalations, performing deep troubleshooting and root-cause analysis across hardware and firmware to drive long-term fixes. - Participate in an on-call rotation for hardware escalations and improve the runbooks, alerts, and tooling that make the rotation sustainable. - Collaborate with cross-functional teams to define hardware requirements, specifications, and system architecture. - Work with server vendors and OEMs to evaluate, qualify, and deploy new platforms and resolve firmware, quality, and RMA issues. - Support new data center region bring-up and hardware qualification. - Analyze hardware system performance, identify bottlenecks, and implement improvements to efficiency and resilience. - Establish and continuously refine processes for internal hardware testing, deployment, and performance optimization. - Create and maintain accurate documentation of hardware designs, specifications, test procedures, and results. - Support data center operations teams and hardware technicians with troubleshooting guidance, runbooks, and training so common issues can be resolved without engineering escalation. - Turn recurring production failures into automation, better telemetry, and improvements to platform design and vendor solutions. - Communicate status, trade-offs, and risks clearly to engineering, operations, and customer-facing stakeholders, including during active incidents. Now "Who You Are" list: - Deep understanding of server hardware, components, and management technologies. - Proficiency in Ansible or Python, with hands-on experience programmatically interacting with server BMCs using Redfish or IPMI; Redfish preferred. - Experience collaborating with hardware vendors and OEMs to evaluate, qualify, and deploy server solutions. - Demonstrated experience supporting and troubleshooting production infrastructure, participating in on-call or escalation rotations, and driving incidents through to root-cause resolution. - Comfort with both building and automating systems and supporting infrastructure already in production. - Proven ability to stay current with technologies and trends in server and data center hardware. - Strong interest in automation and infrastructure scalability, with a commitment to continuous improvement. - Excellent technical documentation skills and attention to detail. - Strong analytical and problem-solving abilities, with a bias toward systematic, data-driven decisions. - Excellent written and verbal communication skills in English, with the ability to work effectively with technical teams and cross-functional stakeholders. Preferred Qualifications list: - Experience bringing up new data center regions or standing up infrastructure in a new geography. - Experience with GPU platforms and rack-scale systems such as NVIDIA GB200 or GB300. - Experience with BMC technologies and management interfaces such as Redfish or IPMI at fleet scale. - Experience with firmware lifecycle management or hardware qualification programs in large-scale environments. - Strong Linux systems administration and debugging skills at fleet scale. - Familiarity with Kubernetes-based services, observability tools such as Prometheus and Grafana, and distributed production environments. - Experience designing alerting, runbooks, and self-service tooling that enable operations teams to resolve common hardware failures without engineering escalation. - Experience supporting external customers or partners in a technical troubleshooting capacity. Benefits list (What We Offer): - 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 Also there is a line: "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." This is about Pay but no actual numbers. Since we should not create Pay section unless posting actually states them (specific numbers). It does not state a range, just says typical compensation range but no numbers. So we should not include Pay section. Schedule: none. Now we need to output HTML fragment with headings: About the role, Responsibilities, Requirements (maybe combine Who You Are and Preferred Qualifications?), Benefits. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (prose), Responsibilities (ul), Requirements (ul) maybe combine Who You Are and Preferred Qualifications? Could separate into Requirements and Preferred Qualifications but both are qualifications. Might be better to have Requirements (Who You Are) and Preferred Qualifications (Preferred Qualifications). But we need to avoid thin sections; but both have substantive content. Could combine into one Requirements section with two sublists? But instruction says use

  • for any list. Could have one
    with all items, but then we lose distinction. Might be okay to have two sections: Requirements and Preferred Qualifications. Both are substantive. Also we need About the role prose: The paragraph(s) before responsibilities: "CoreWeave is seeking a highly skilled and motivated engineer to join our Hardware Engineering team. In this role, you will help design, develop, and optimize our server hardware infrastructure. You’ll collaborate closely with cross-functional teams, external vendors, and key stakeholders to deliver performant, reliable, and scalable hardware solutions that power CoreWeave’s rapidly growing infrastructure. You will own server hardware from provisioning through decommission. This hands-on role combines engineering and operational support." That's prose. We should not include duplicated lines. Ensure we don't include boilerplate like "Learn more at www.coreweave.com." That's maybe okay to keep? It's not boilerplate? It's a link but could be considered navigation? It's just a URL. Might be okay to keep but it's not substantive about role. Might be considered filler. Safer to omit. Also remove "Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025." That's company info, maybe not needed for role. Could be omitted as not substantive to role. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Company background may be considered not substantive to role? It's generic. Might be okay to keep but it's not about role. I'd omit to keep focused. Now produce HTML:

    About the role

    CoreWeave is seeking a highly skilled and motivated engineer to join our Hardware Engineering team. In this role, you will help design, develop, and optimize our server hardware infrastructure. You’ll collaborate closely with cross-functional teams, external vendors, and key stakeholders to deliver performant, reliable, and scalable hardware solutions that power CoreWeave’s rapidly growing infrastructure. You will own server hardware from provisioning through decommission. This hands-on role combines engineering and operational support.

    Responsibilities

    • Design and develop server hardware infrastructure to support CoreWeave’s high-performance workloads.
    • Automate all aspects of the server hardware lifecycle, from provisioning and configuration through firmware management, monitoring, and decommissioning.
    • Develop and maintain hardware and firmware management services that ensure reliability at scale.
    • Develop and implement monitoring and alerting for server hardware health, improving alert quality to support reliable on-call response.
    • Serve as a senior point of contact for hardware escalations, performing deep troubleshooting and root-cause analysis across hardware and firmware to drive long-term fixes.
    • Participate in an on-call rotation for hardware escalations and improve the runbooks, alerts, and tooling that make the rotation sustainable.
    • Collaborate with cross-functional teams to define hardware requirements, specifications, and system architecture.
    • Work with server vendors and OEMs to evaluate, qualify, and deploy new platforms and resolve firmware, quality, and RMA issues.
    • Support new data center region bring-up and hardware qualification.
    • Analyze hardware system performance, identify bottlenecks, and implement improvements to efficiency and resilience.
    • Establish and continuously refine processes for internal hardware testing, deployment, and performance optimization.
    • Create and maintain accurate documentation of hardware designs, specifications, test procedures, and results.
    • Support data center operations teams and hardware technicians with troubleshooting guidance, runbooks, and training so common issues can be resolved without engineering escalation.
    • Turn recurring production failures into automation, better telemetry, and improvements to platform design and vendor solutions.
    • Communicate status, trade-offs, and risks clearly to engineering, operations, and customer-facing stakeholders, including during active incidents.

    Requirements

    • Deep understanding of server hardware, components, and management technologies.
    • Proficiency in Ansible or Python, with hands-on experience programmatically interacting with server BMCs using Redfish or IPMI; Redfish preferred.
    • Experience collaborating with hardware vendors and OEMs to evaluate, qualify, and deploy server solutions.
    • Demonstrated experience supporting and troubleshooting production infrastructure, participating in on-call or escalation rotations, and driving incidents through to root-cause resolution.
    • Comfort with both building and automating systems and supporting infrastructure already in production.
    • Proven ability to stay current with technologies and trends in server and data center hardware.
    • Strong interest in automation and infrastructure scalability, with a commitment to continuous improvement.
    • Excellent technical documentation skills and attention to detail.
    • Strong analytical and problem-solving abilities, with a bias toward systematic, data-driven decisions.
    • Excellent