Senior Hardware Engineer, Server Infrastructure
CoreWeave · New York, NY · 2 wk ago
HybridEngineeringFull-time
We need to output HTML fragment with sections for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. We must not repeat job title. Must include only sections with real specific content. Must not include boilerplate like EEO, legal, etc. Must preserve all substantive info.
We need to parse the posting.
First, there is an introductory paragraph about CoreWeave (company description). That is not part of role specifics; but we might include as part of About the role? The instruction: "use . Ensure we don't lose any detail.
Let's extract content.
About The Role paragraph:
"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. Engineering work includes automation across the hardware lifecycle, hardware and firmware management services, monitoring and alerting, and qualification and bring-up of new platforms. Operational support includes acting as a senior point of contact for hardware escalations, driving deep root-cause analysis across hardware and firmware, and working quality and RMA issues through to resolution with server vendors and OEMs. Both engineering and operational support are core responsibilities. You will support the systems you build and use what you learn from production failures to improve automation, telemetry, and platform design. You will work closely with data center operations teams, hardware technicians, and engineering teams to bring new regions online and keep existing infrastructure healthy."
That's the About the role content.
What You’ll Do (Responsibilities) list:
- 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.
That's responsibilities.
Who You Are (Requirements) 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.
That's required.
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.
That's preferred.
What We Offer (Benefits) 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
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." No actual numbers, so we cannot include Pay.
Also "In addition to a competitive salary, we offer a variety of benefits to support your needs." That's generic but we already have benefits list.
We must not include boilerplate like "California Applicants California Consumer Privacy Act Equal Opportunity & Accommodations" etc. So we strip those.
Now produce HTML fragment:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. The posting includes: - About The Role (a paragraph describing role). That's content for About the role. - What You’ll Do (list of duties). That's Responsibilities. - Who You Are (list of qualifications/requirements). That's Requirements/Qualifications/Skills? It includes "Deep understanding of server hardware..." etc. Those are requirements. Also "Preferred Qualifications" separate list. - There's a "Wondering if You’re a Good Fit?" section (more traits). Could be considered part of Requirements or Skills but maybe we can incorporate into Requirements. - What We Offer includes benefits and compensation description. It mentions "The range we’ve posted represents the typical compensation range for this role." No actual numbers given. It says "To determine actual compensation, we review the market rate...". No specific pay range given. So we cannot create a Pay section because no specific numbers. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated: list of benefits. So we can include Benefits section. Pay section not included because no specific range. Schedule not mentioned. Thus we will have sections: About the role, Responsibilities, Requirements (maybe combine Who You Are and Preferred Qualifications?), Qualifications (maybe separate?), Skills (maybe we can treat Preferred Qualifications as Skills? But we need to avoid thin sections. Better to have Requirements (including both required and preferred) and maybe Skills separate if there is distinct skill list. The posting includes "Proficiency in Ansible or Python..." etc under Who You Are (required). Then "Preferred Qualifications" list. Could treat Required as Requirements, Preferred as Qualifications or Skills. But we need to avoid duplication. Let's decide: - About the role: paragraph. - Responsibilities: list from "What You’ll Do". - Requirements: list from "Who You Are" (required). - Qualifications: list from "Preferred Qualifications". - Benefits: list from "What We Offer". We could also include Skills section but maybe not needed as we have Requirements and Qualifications. The instruction says prefer few substantive sections over many thin ones. Having 5 sections is okay if each has substantive content. Could we combine Requirements and Qualifications into one? But they are distinct: required vs preferred. Might be better to keep both. We must not include boilerplate like EEO, legal, etc. So we strip those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet point as is, maybe as
About the role
... paragraph ...
Responsibilities
- ... each bullet ...
Requirements
- ... each required bullet ...
Qualifications
- ... each preferred bullet ...
Benefits
- ... each benefit bullet ...