Skip to content
OpenAI

Systems Software Engineer, Security, First Party Hardware

San FranciscoHybrid · United States
FullTime · Scaling
POSTED 8 JUNVERIFIED 3H AGO
Apply Ask
Role
166 days opentrue age
Past the 47d median close
Posted 8 Jun · n=195
Payats field
$230k–385kposted
▲ +50% vs market median $205k
$158k$407k
Market p25–p75
$158k–$263k
OpenAI p25–p75
$309k–$407kn=8
H-1B median · Security
$330k
SF Bay Area · n=177 · 365d to 19 Nov
CompanyOpenAI →
851open roles
Opened · 30d
+200
Closed · 30d
−150
Signal
● Steady+50 net
21d of snapshots · 30d window
Market
4,189open · Security
Opened · 7d
+48011% of open
All security
8,317open
All tracked boards · live 22 Nov · n=4,189
Visa
210H-1B LCAs · FY26
Median wage
$260k
UK licensed sponsor
✓Worker (A rating)
LCAs FY26 · n=210 · to 2026-06-30
RustC++

About the Team

OpenAI’s Hardware organization develops AI-native silicon and system-level solutions for the unique demands of advanced AI workloads. Building on efforts like Jalapeño, the team is developing future generations of AI-native silicon and tightly integrated systems to power the next generation of frontier models. By co-designing chips, systems, tools, and methodologies, the team helps deliver faster, more efficient, and production-ready hardware for OpenAI’s supercomputing platform.

About the Role

We're seeking a Security Engineer to join our First-Party Hardware team. In this role, you will own the end-to-end security foundation for OpenAI's first-party AI hardware systems, working across hardware security, embedded security, system security, and practical deployment at data center scale.

You will partner with silicon, hardware, firmware, infrastructure, manufacturing, operations, and security teams to define and deliver system-level device trust. This includes boot integrity, device identity, provisioning, attestation, management-plane security, storage encryption, debug controls, firmware update and recovery, RMA, and decommissioning. You will be accountable for turning threat models into requirements, requirements into implementation, and implementation into validation evidence that can support launch decisions.

Location: San Francisco, CA (Hybrid: 3 days/week onsite)

Relocation assistance available.

In this role, you will

Own security requirements, threat models, validation strategy, and launch-readiness evidence for first-party hardware platforms from early design through production deployment.

Design and review secure boot, measured boot, roots of trust, platform firmware resilience, firmware signing, recovery, and anti-rollback strategies across heterogeneous devices.

Own device identity, provisioning, enrollment, attestation, certificate lifecycle, and key-management requirements across manufacturing and data center bring-up.

Harden management interfaces and operational access paths across BMCs, hosts, accelerators, switches, and service tooling, including TLS/mTLS, Redfish, gNMI, SSH, syslog, and break-glass workflows.

Drive security requirements for manufacturing, supply chain, firmware/image signing, storage encryption, RMA, repair, and decommissioning processes.

Build and drive validation for security-critical hardware and firmware behavior, including debug lockout, lifecycle transitions, update paths, attestation evidence, and recovery flows.

Partner with vendors and contract manufacturers to turn security requirements into concrete deliverables, test evidence, and launch gates.

Drive end-to-end closure across design, implementation, manufacturing readiness, deployment readiness, fleet operations, and incident response when security issues arise.

Investigate hardware and firmware security issues, assess exploitability and operational risk, and drive durable fixes with engineering owners.

You might thrive in this role if you have

7+ years of hands-on experience, or exceptional accomplishments demonstrating equivalent expertise, in hardware security, embedded security, firmware security, platform security, or low-level systems security.

Experience shipping or securing real hardware platforms, embedded devices, servers, accelerators, networking systems, BMCs, bootloaders, BIOS/UEFI, RTOS, kernels, or firmware update systems.

Deep familiarity with secure boot, measured boot, TPMs, hardware roots of trust, device attestation, key provisioning, debug interfaces, firmware signing, recovery, or lifecycle-state design.

Strong applied-cryptography judgment for secure boot, attestation, TLS/mTLS, key storage, certificate lifecycle, storage encryption, and long-range transitions such as post-quantum readiness.

Ability to read and write systems code in C, C++, or Rust and to use that skill to review, prototype, test, or debug security-critical behavior.

Comfort with hardware-software interfaces such as SPI, I2C, SMBus, PCIe, UART, JTAG, SWD, GPIOs, TPMs, and board-level debug tools.

Source · OpenAIFirst seen 3 NovOriginal ↗