Security Engineer, Firmware Security

Core Weave is The Essential Cloud for AI™. Built for pioneers by pioneers, Core Weave 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, Core Weave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, Core Weave became a publicly traded company (Nasdaq: CRWV) in March 2025.

Learn more at

The Security Engineering organization at Core Weave is responsible for keeping the Core Weave Cloud secure by design—from our data centers and GPU fleets all the way up to the platform layers that power our customers’ AI workloads. The Firmware Security function sits at the intersection of hardware, platform engineering, and infrastructure security, ensuring that the low-level software that runs on our servers, GPUs, and networking gear is trustworthy, up to date, and resilient to compromise.

This team defines and enforces the standards for secure firmware across our global fleet, builds the tooling to validate and attest device state at scale, and partners closely with data center operations and engineering teams to roll out changes safely. If you’re excited about securing BMCs, BIOS/UEFI, GPU and NIC firmware in massive AI clusters, this is the team to join.

As a Staff Firmware Security Engineer, you will be the technical lead for firmware security across Core Weave’s infrastructure. You’ll design and drive the strategy for secure boot, firmware signing, attestation, and fleet‑wide governance of firmware across servers, GPUs, and critical infrastructure devices. You’ll work hands‑on with engineering teams, hardware vendors, and data center technicians to identify risks, ship durable controls, and respond to emerging threats in the firmware and hardware ecosystem.

Your work will directly influence how securely we operate some of the largest GPU fleets in the world.

• Define the end‑to‑end firmware security architecture for Core Weave’s server, GPU, and networking platforms, including root‑of‑trust, secure boot, and attestation flows.
• Design and implement secure boot and measured boot strategies across host, BMC, and accelerator firmware, leveraging TPM/TPM2 and hardware roots of trust.
• Build and maintain tooling and automation to inventory firmware, validate signatures and policies, manage firmware SBOMs, and enforce version baselines across large fleets.
• Partner with platform, infrastructure, and data center engineering teams to design safe rollout mechanisms for firmware updates, including canarying, rollback strategies, and blast‑radius controls.
• Perform threat modeling, design reviews, and code reviews for firmware‑related components and low‑level platform software, identifying and mitigating security risks early in the lifecycle.
• Lead deep‑dive investigations into firmware vulnerabilities and anomalous device behavior, coordinating incident response and remediation across cross‑functional teams.
• Engage with hardware and OEM partners (e.g., server, GPU, and NIC vendors) to influence their security roadmaps, validate security features, and integrate vendor tooling into Core Weave’s controls.
• Collaborate with Security Engineering peers to integrate firmware security signals into telemetry, detection, and SIEM pipelines for continuous monitoring.
• Establish standards, best practices, and documentation for firmware security, and mentor engineers across the organization in building secure‑by‑default infrastructure.

• 8+ years of experience in security engineering, platform security, or systems/firmware engineering, including substantial work with server or device firmware.
• Deep understanding of firmware and platform security concepts, including secure/verified boot, measured boot, roots of trust, and attestation (e.g., TPM‑based or vendor‑specific solutions).
• Hands‑on experience with server and BMC ecosystems (e.g., UEFI/BIOS, BMC/Redfish/IPMI, bootloaders) and how they interact with operating systems and hypervisors.
• Strong Linux systems…