Distinguished Engineer, Security Architecture - DGX Cloud

What You Will Be Doing:

Set the DGX Cloud Security Bar:
Own the security design standard across DGX Cloud (tenancy, GPU workloads, identity, supply chain, and isolation) and make it concrete. Reference architectures, golden paths, and requirements engineers can actually build against, not a policy library. Hold the Bar by Building:
Embed with engineering teams on real work: join the design, learn the code, help ship the thing rather than grade it afterward. The posture is not "you did this wrong." It is "here are the considerations we need to meet, I will help, let's go to work." Architect the Security Platform:
Drive the multi-year architecture for the common security infrastructure the fleet runs on: hardened baselines and patch SLOs, deploy-time policy and admission control, workload identity, supply-chain provenance through signing and attestation, and detection and response tuned to GPU workloads. Engineer Classes of Risk Out of Existence:
Finding a vulnerability is 4% of the work; building the system where it cannot happen again is the other 96%. You will attack recurring risk at its architectural root, including offensively against our own designs, and feed what you find back into the paved roads, the baselines, and the detections. Grow the Principal Engineering Bench:
Lead a small team of Principal Engineers who report to you and hold the bar across domains. Set their technical direction, hire into the gaps, and grow each of them into deeper scope than they arrived with. Multi-Functional

Collaboration:

Serve as DGX Cloud's primary technical connection into NVIDIA's central security organization, and partner across platform, production engineering, and network security teams. We operate horizontally across vertically organized teams, with influence rather than authority. Communicate Risk Upward:
When something is going to ship below the bar, write down the gap and what closing it would take, and put it in front of the executives who hold the risk pen. We do not block releases ourselves and we do not quietly absorb risk. The bar holds because gaps become visible and owned.

Security Engineering:
Experience (typically 20+ years) across software engineering, infrastructure, and security, with recent depth securing large-scale distributed or cloud platforms. You build systemic solutions rather than performing manual operations or "tool administration." Architecture at Fleet Scale: A proven record owning the security architecture of a large platform end to end, across multi-tenant isolation, identity and access, policy enforcement, supply chain, and detection.

You saw that architecture get built and operated, not shelved. Production-Grade Coding:
Deep enough in the code to stay credible and hands-on. You have written, shipped, and operated production services at scale yourself, and you can read an unfamiliar codebase closely enough to see where its security assumptions break. Emerging Technology:
You form a view early on what is changing under this platform, and you can tell a real shift from a trend. Today that means AI-generated code arriving faster than people can review it, AI-assisted security analysis, and agents acting inside the systems you defend. Tomorrow it will mean something else. Threat Modeling:
The depth to threat model a complex distributed system (the substrate, the orchestration layer, the tenancy boundary) and to tell an architectural gap from a bug. Distributed Systems and Linux Depth:
Cloud-native architecture, container orchestration (Kubernetes), Linux systems security including kernel-level primitives, and the security properties of high-throughput multi-tenant environments. Technical Leadership and Influence:
Build consensus and…