Drimva

42dot

Sr. Staff Firmware Security Architect (Domain Security — Secure Boot, OTA & Vehicle Cybersecurity)

$189K–$267K

Sunnyvale, United States · Senior Staff · Full-time · Posted Oct 7, 2026

Experience
15+ years in embedded or firmware engineering, including at least 6 years owning embedded or product security.

About the job

Own the end-to-end firmware security architecture for a software-defined vehicle platform, from secure boot and OTA updates through cybersecurity assurance and release approval.

What you'll do

  • Define secure boot, Uptane OTA, hardware-root-of-trust, key-management, isolation, diagnostics, and in-vehicle communication security designs.
  • Produce cybersecurity analyses and regulatory evidence, coordinate safety–security engineering, and review implementations, tests, and releases.
  • Establish vulnerability response and supplier security requirements; work with cloud and infrastructure teams on fleet interfaces.

What they ask for

  • Personally owned a production secure-boot or chain-of-trust design on MCU-class silicon; Linux-only experience is insufficient.
  • Practitioner-level applied cryptography, HSM or secure-element programming, and manufacturing key provisioning; hands-on TUF/Uptane or equivalent signed-metadata update security.
  • Authored a TARA, cybersecurity concept, or cybersecurity case and responded to assessor or OEM questions; working familiarity with UNECE R155/R156.
  • C proficiency to review boot and update code, linker scripts, memory maps, and HSM API usage; strong technical writing.

Nice to have

  • Uptane standards or community involvement; ISO 26262 or safety–security co-engineering experience.
  • Experience with NXP S32K3/HSE_B, post-quantum firmware signatures, in-vehicle communication security, or assessor engagement.

Pay

$189,240 - $266,760 (currency and whether base salary or total pay not stated)

Tools

C, TUF, Uptane, python-tuf, go-tuf, NXP HSE/CSEc/SHE+, Infineon AURIX HSM, NXP S32K3

Model-written summary · the original posting is authoritative

First seen Oct 29, 2026 · Last verified Nov 5, 2026 (UTC)