Software Technical Program Manager, Systems Engineering

Nuro Nuro · Robotics · Mountain View, CA · Software TPM

Nuro is seeking a Systems Engineering TPM to own the technical substance of how they validate autonomy. This role involves defining scenario sets, structuring fault injection campaigns, and ensuring simulation coverage is meaningful and systematically growing. The TPM will work embedded with Autonomy, Simulation, and Systems Engineering teams to drive technical rigor in the validation program, ensuring traceability between requirements and evidence.

What you'd actually do

  1. Own the technical framework for measuring validation coverage: what counts as covered, where the gaps are, and what engineering decisions close them.
  2. Drive the technical design of large-scale simulation campaigns - scenario selection, variation strategies, metrics definition, and results interpretation.
  3. 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.
  4. Maintain traceability between autonomy system requirements, scenario/test definitions, and validation evidence — ensuring the coverage story is coherent and audit-ready.
  5. Apply systems engineering principles to structure validation logic: interface dependencies, assumption documentation, and V&V coverage mapping.

Skills

Required

  • 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.

Nice to have

  • 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.

What the JD emphasized

  • technical substance
  • technical rigor
  • technical design
  • technical strategy
  • technical collaboration
  • technical bridge
  • technical problems
  • technical execution