Senior Software Engineer, Embedded Product Security

Job description

Job responsibilities

• Own the signed boot chain across compute generations: firmware and bootloader signing, UEFI Secure Boot key hierarchies, signed kernel and initrd, and full-disk encryption with automated unlock.
• Own signing key management and the infrastructure behind it: HSM-backed keys, separation of development and production trust roots, key rotation, and build-time enforcement that the right keys sign the right artifacts.
• Define and implement the platform’s hardening postures, spanning network exposure and firewall policy, privilege and sudo restriction, serial console and USB lockdown, and the difference between a locked-down fielded…
• Drive vulnerability management for the fielded fleet: track CVEs (Common Vulnerabilities and Exposures) against our kernel and userspace, own the patching strategy for hardware approaching vendor end-of-life, and keep…
• Partner with our product security organization to turn security requirements into shippable implementations, act as our team’s security liaison, and support program-specific accreditation efforts.

Job requirements

• 4+ years of professional software engineering with a security focus on Linux or embedded systems.
• Hands-on experience implementing a secure boot chain: code signing, chain of trust, UEFI Secure Boot or an equivalent vendor secure boot implementation.
• Practical cryptographic engineering skills: PKI and certificate hierarchies, HSM or PKCS#11-backed signing, key lifecycle management, and full-disk encryption.
• Strong Linux internals knowledge, particularly in patching, boot flow, kernel and initrd, systemd, privilege boundaries, and filesystem and device access control.
• Proficiency in C or Rust, plus the ability to work fluently in shell.
• Practical hardening and vulnerability-management experience on real systems: attack-surface reduction, CVE triage on a deployed fleet, and live patching strategies that don’t break the product.
• Ability to explain a security decision to engineers who need to implement it, and to a program stakeholder who needs to accept the residual risk.
• US person status required. Active US Secret clearance, or a previously granted Secret clearance eligible for reactivation.