Drimva

NVIDIA

Senior Security Engineer, RTOS and Virtualization

$184K–$356K

US, CA, Santa Clara +4 · Senior · Full-time · Posted Sep 29, 2026

Location
US, CA, Santa Clara
US, TX, Austin
US, OR, Hillsboro
US, Remote
US, WA, Redmond
Experience
8+ years of hands-on experience.
Education
BSEE/ BSCS degree or equivalent experience.

About the job

Leads security engineering for RTOS, hypervisor, and embedded virtualization technologies used in automotive systems, from architecture and implementation through verification.

What you'll do

  • Lead security engineering across design, implementation, review, and verification; collaborate on CPU and SoC security architecture.
  • Build defensive features, perform threat modeling and automotive TARA, and connect risks and mitigations to standards and evidence.
  • Review low-level code, investigate vulnerabilities, build fuzzing and security test infrastructure, and drive fixes into production.

What they ask for

  • Hands-on experience in systems, embedded, platform, product, or automotive security.
  • BSEE/ BSCS degree or equivalent experience.
  • Experience securing RTOS, hypervisor, kernel, firmware, boot, driver, or other privileged software; strong C/C++ skills.
  • Experience with security analysis and remediation, CPU/SoC security concepts, and familiarity with relevant automotive cybersecurity, safety, or process standards.

Nice to have

  • Drove adoption of Rust, Ada/SPARK, formal methods, or other memory-safe and analyzable systems approaches; built capability-based or ownership-based security models.
  • Built security automation, fuzzing infrastructure, review agents, or AI-assisted tools used by engineering teams.

Pay

184,000 USD - 287,500 USD base salary (Level 4); 224,000 USD - 356,500 USD base salary (Level 5)

Tools

RTOS, hypervisor, C/C++, MMU/SMMU, IOMMU, Rust, Ada/SPARK

AI focus

The role may involve building AI-assisted tools for engineering teams; NVIDIA also states that it uses AI tools in recruiting.

Model-written summary · the original posting is authoritative

First seen Oct 16, 2026 · Last verified Nov 4, 2026 (UTC)