About the job
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.
Responsibilities
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.
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.
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.
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 V&V 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.
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 complex validation logic and coverage gaps clearly to engineering leads and senior stakeholders.
Qualifications
Minimum
4–6 years in systems engineering, autonomy validation, or a technically-focused TPM role in autonomous vehicles, robotics, or aerospace.
Deep familiarity with scenario-based testing, coverage-driven validation, or autonomy stack evaluation.
Strong systems engineering fundamentals: requirements traceability, V&V methodology, interface management, failure mode analysis.
Ability to engage technically with autonomy, simulation, and hardware engineers — not just coordinate between them.
Comfortable owning ambiguous technical problems and driving them to structured, defensible conclusions.
Preferred
Experience designing or executing large-scale simulation campaigns, including scenario variation strategies and results analysis.
Familiarity with SOTIF (ISO 21448), UL 4600, or safety-of-the-intended-functionality concepts as they apply to autonomy validation.
Background in ODD (Operational Design Domain) analysis, scenario taxonomy development, or safety case construction.
Experience with simulation platforms such as CARLA, LGSVL, or proprietary AV sim environments.