Primary record

Project Manager, Software Operations

Nuro Indexed employerMountain View, California (HQ) · Nuro HQ - Mountain View, CA
Source-hosted applyChecked 3h agoContract
Apply at Nuro

Nuro receives this application through Greenhouse. Babu Careers does not claim delivery.

Workplace

On-site

Employment

Contract

Published

Aug 12, 2026

Closes

No date supplied

The role

Who We Are

Nuro believes self-driving vehicles are the most immediate and profound opportunity for AI to drive positive change in the physical world. Safer streets, more time for what matters, and easier access to the world around us, that’s why we’re building a universal autonomy platform: self-driving for all roads and all rides.

Founded in 2016, Nuro is a physical AI company developing Level 4 autonomous driving technology for a wide range of vehicles, use cases, and markets. Powered by the Nuro Driver™, our universal autonomy platform enables the global mobility ecosystem to deploy autonomy at scale, from robotaxis and logistics fleets to personal vehicles.

With years of real-world deployment experience and a flexible, partner-led business model, Nuro is working toward a future where millions of autonomous vehicles powered by our technology help make everyday life safer, easier, and more connected. Nuro has raised over $2B in capital from Uber, NVIDIA, Google, Softbank, Fidelity, T. Rowe Price, and other leading investors.

About the Team

The Software Operations team is at the heart of how Nuro's autonomy software gets built right. We own QC, tool testing, and bug reproduction across labeling workflows, and we care deeply about the craft of doing that work well. You'll sit inside the team, learn the work firsthand, and help build the systems that make quality achievable at scale.

You'll report directly to the Head of Software Operations with real access, real context, and a genuine mandate to make things better.

About the Role

We're looking for someone who can walk into a working system, figure out where it's actually breaking, and build the case for how to fix it, without being told where to look.

Give you a workflow and a few weeks, and you'll come back with a theory of what's wrong, evidence for it, and a specific recommendation, not

Requirements

Department: Software Operations