Systems Software Engineer, Security, First Party Hardware

OpenAI OpenAI · AI Frontier · San Francisco, CA · Scaling

This role focuses on the end-to-end security foundation for OpenAI's first-party AI hardware systems, covering hardware security, embedded security, system security, and deployment at data center scale. Responsibilities include defining and delivering system-level device trust, from boot integrity to decommissioning, and translating threat models into requirements and validation evidence. The role requires extensive experience in hardware and embedded security, with a strong understanding of applied cryptography and systems programming.

What you'd actually do

  1. Own security requirements, threat models, validation strategy, and launch-readiness evidence for first-party hardware platforms from early design through production deployment.
  2. Design and review secure boot, measured boot, roots of trust, platform firmware resilience, firmware signing, recovery, and anti-rollback strategies across heterogeneous devices.
  3. Own device identity, provisioning, enrollment, attestation, certificate lifecycle, and key-management requirements across manufacturing and data center bring-up.
  4. 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.
  5. Drive security requirements for manufacturing, supply chain, firmware/image signing, storage encryption, RMA, repair, and decommissioning processes.

Skills

Required

  • hardware security
  • embedded security
  • firmware security
  • platform security
  • low-level systems security
  • shipping or securing real hardware platforms
  • embedded devices
  • servers
  • accelerators
  • networking systems
  • BMC
  • bootloaders
  • BIOS/UEFI
  • RTOS
  • kernels
  • firmware update systems
  • secure boot
  • measured boot
  • TPMs
  • hardware roots of trust
  • device attestation
  • key provisioning
  • debug interfaces
  • firmware signing
  • recovery
  • lifecycle-state design
  • applied cryptography
  • TLS/mTLS
  • key storage
  • certificate lifecycle
  • storage encryption
  • post-quantum readiness
  • systems code in C, C++, or Rust
  • hardware-software interfaces
  • SPI
  • I2C
  • SMBus
  • PCIe
  • UART
  • JTAG
  • SWD
  • GPIOs
  • board-level debug tools
  • driving security improvements
  • owning broad, ambiguous security programs end to end
  • translating risk into technical requirements
  • validation plans
  • accountable engineering decisions
  • clear written and verbal communication

What the JD emphasized

  • end-to-end security foundation
  • system-level device trust
  • security requirements
  • threat models
  • validation strategy
  • launch-readiness evidence
  • secure boot
  • measured boot
  • roots of trust
  • firmware signing
  • device identity
  • provisioning
  • enrollment
  • attestation
  • certificate lifecycle
  • key-management
  • manufacturing
  • data center bring-up
  • management interfaces
  • operational access paths
  • firmware/image signing
  • storage encryption
  • RMA
  • repair
  • decommissioning processes
  • security-critical hardware
  • firmware behavior
  • debug lockout
  • lifecycle transitions
  • update paths
  • recovery flows
  • security requirements into concrete deliverables
  • test evidence
  • launch gates
  • end-to-end closure
  • design
  • implementation
  • manufacturing readiness
  • deployment readiness
  • fleet operations
  • incident response
  • hardware and firmware security issues
  • exploitability
  • operational risk
  • durable fixes