Software Technical Program Manager, Systems

Who We Are Nuro is a self-driving technology company on a mission to make autonomy accessible to all. Founded in 2016, Nuro is building the world’s most scalable driver, combining cutting-edge AI with automotive-grade hardware. Nuro licenses its core technology, the Nuro Driver™, to support a wide range of applications, from robotaxis and commercial fleets to personally owned vehicles. With technology proven over years of self-driving deployments, Nuro gives the automakers and mobility platforms a clear path to AVs at commercial scale, empowering a safer, richer, and more connected future. About the Role Nuro's autonomous vehicle platform has to work - not just in the easy cases, but in the hard ones. The ones we design for, simulate at scale, and deliberately break to understand. We're looking for a Systems Engineering TPM who owns the technical substance of how we validate autonomy: what we test, why we test it, and whether our coverage actually means something. This is not a planning or scheduling role. You'll work embedded with Autonomy, Simulation, and Systems Engineering teams to drive the technical rigor behind our validation program — defining scene sets, structuring fault injection campaigns, and ensuring our simulation coverage is meaningful, traceable, and systematically growing. The program infrastructure is owned elsewhere; your job is to make sure what's inside it is technically sound. About the Work Scenario Coverage Strategy Understanding the taxonomy of challenging scene sets used for autonomy validation - ensuring coverage spans safety-critical, edge-case, and adversarial scenarios grounded in real-world operational data and systems requirements. Own the technical framework for measuring validation coverage: what counts as covered, where the gaps are, and what engineering decisions close them. Partner with systems engineers to translate system-level requirements and failure modes into concrete, testable scenario definitions. Large-Scale Simulation Drive the technical design of large-scale simulation campaigns - scenario selection, variation strategies, metrics definition, and results interpretation. Work with simulation and infrastructure teams to ensure campaign design maximizes signal: the right scenarios, run at the right fidelity, with results that feed actionable engineering decisions. Identify when simulation results are inconclusive or misleading and drive the engineering conversation to resolve it. Fault Injection Unhealthy Autonomy Own the technical strategy for fault injection and degraded-mode validation - defining what failure conditions matter, how they're induced, and what acceptable autonomy behavior looks like under each. Collaborate with Systems Engineering, Controls, and HW teams to build fault injection test matrices grounded in FMEA and systems-level failure mode analysis. Ensure unhealthy autonomy behaviors surfaced through fault injection are technically understood, root-caused, and tied back to requirements or safety goals. Requirements Traceability Systems Engineering Maintain traceability between autonomy system requirements, scenario/test definitions, and validation evidence — ensuring the coverage story is coherent and audit-ready. Apply systems engineering principles to structure validation logic: interface dependencies, assumption documentation, and VV coverage mapping. Serve as the technical bridge between systems development and validation execution — translating what the system is supposed to do into how we know it does it. Technical Collaboration Domain Expertise Be the person in the room who understands both the autonomy stack and the validation methodology well enough to push back, ask the hard questions, and spot coverage gaps others miss. Partner closely with the Systems Validation TPM — who owns planning, timelines, and scope gates — to ensure technical execution stays aligned with program commitments without duplicating that function. Communicate ... (truncated, view full listing at source)