NVIDIA Networking product security team is looking for an outstanding technical security architect with hands-on experience to help us improve the security posture of NVIDIA networking products. In this role you will partner with firmware, hardware, and architecture teams on the security architecture, to reduce risk, threats, and vulnerabilities while driving new security features that affect millions of devices all over the world!

What you'll be doing:

• Be involved in the security architecture of NVIDIA Networking firmware — trust boundaries, privilege separation between firmware domains, device identity and key storage, secure boot and chain of trust, and secure update and anti-rollback flows.
• Perform security threat modeling of firmware and embedded subsystems across NVIDIA Networking products.
• Analyze complex firmware and hardware/firmware interactions to identify security weaknesses, including boot flows, privileged execution environments, and host- and network-facing management interfaces.
• Define security features and mitigations spanning the full device lifecycle — provisioning, attestation, debug authorization, runtime hardening, and field update. Guide the engineering teams throughout the implementation.
• Translate threat models into actionable security requirements and architectural decisions, and review designs and implementations against them.
• Partner with hardware and ASIC architects to specify the security primitives firmware depends on, and define how they are used across the product line.
• Drive secure development practices for firmware — memory-safe coding patterns in C, static analysis, and fuzzing of firmware-exposed interfaces — and make sure development processes meet security and coding standards.

What we need to see:

• Academic degree in computer science, electrical engineering, or related field (or equivalent experience).
• Demonstrated experience of 8+ years in product security, firmware security, or security research, including hands-on work with embedded or firmware codebases.
• Experience defining security policy models — authorization schemes, RBAC, and administrative role separation — including how policy is expressed, enforced, and administered in production.
• Familiarity with applied cryptography (including secure boot, code signing, and attestation), threat modeling, common attack vectors, and mitigation techniques.
• Ability to work independently, and collaboratively in a constantly evolving environment.