Project Manager, Software Operations

Start free →

Or apply yourself on the official page →

About 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 a request for more direction. The procedures, rubrics, and taxonomy you'll touch are downstream of that investigation. They're how your findings get made permanent; they are not the job itself. You'll spend real time inside the in-house team's workflow. Your job there isn't to absorb and wait, it's to notice what nobody else has flagged, form a working theory of why it's happening, and test that theory against the actual work before you propose anything. Sometimes the right answer isn't a better rubric or a cleaner taxonomy at all; it's realizing the current one is solving the wrong problem. You'll also keep our offshore QC vendor team calibrated to whatever standard your investigation lands on. This role is a great fit if you get energized by finding the thing nobody's noticed yet and making an evidence-backed case for fixing it, even when that case meets resistance. If you'd rather build your own read on a problem than follow someone else's checklist, want your work tied directly to a product that matters, and thrive with autonomy and a direct line to leadership, this is the role for you. This is not a good fit if you do your best work with a defined process to execute against. That's a different, valuable skill, but it's not this role. About the Work: Finding What's Actually Wrong • Spend real time in the workflow and form your own read on where it breaks, not just where you're told to look • Build a working theory, then go test it against real cases before you propose anything • Be willing to conclude that the rubric, the taxonomy, or the process itself is the actual problem Making the Case • Turn what you find into a specific, evidence-backed recommendation, not a vague observation • Defend that recommendation when someone pushes back, and update it fast when the pushback is right • Report findings and recommendations to the Head of Software Operations on a regular cade

View the official posting →