The Humans Behind Tesla's 'Driverless' Robotaxi

Say “full self-driving” and most people picture the same thing: a car gliding through a city while the AI handles everything. Then look at what’s actually happening in Austin, where Tesla’s Robotaxi pilot has been running since June 2025. The crashes piling up have surfaced an awkward detail. Those “driverless” cars are, in many moments, being steered by humans sitting in an office hundreds of miles away.

The people filling in the gaps

When Tesla launched the Austin pilot, Musk framed it as the beginning of the driverless era. The reality on the ground is messier.

Every Robotaxi rides with a “safety monitor” in the passenger seat. Behind that, there’s a separate job category Tesla itself advertises: teleoperator. These employees watch live feeds from the cars and take over remotely when the vehicle hits an edge case — reversing out of a tight alley, navigating around a construction zone, or just getting unstuck.

Tesla has posted listings for “Teleoperation Software Engineer” roles on its careers page. That’s a strange hire for a company whose CEO keeps insisting the AI handles everything.

What the crash reports actually ask

A pattern has emerged in the recent incident coverage. When a Robotaxi drifts into the wrong lane or behaves erratically near a pedestrian, investigators are no longer asking “was the car in autonomous mode?” The first question now is “was a remote operator engaged at the time?”

That single shift reopens the entire autonomous-vehicle liability debate from scratch. If a human was effectively driving via fiber-optic cable, is this even a self-driving crash? Or is it just a remote-driving crash with extra steps?

Waymo has run teleoperators for years, but draws a hard line: their remote staff don’t drive the car. They answer questions the car asks — the vehicle pauses, asks “what should I do next?”, and a human suggests “go right.” Tesla’s setup, based on what’s leaking out of investigations, looks closer to direct remote control. That’s a different beast, both technically and legally.

The weight of “FSD”

Here’s the part that deserves more attention. Tesla has spent years selling consumers a software package called Full Self-Driving — at one point priced near $10,000 per car. The same company, when running its own commercial robotaxi fleet, decided it needed human teleoperators on payroll.

The implication writes itself. Tesla doesn’t trust FSD alone to operate safely on city streets. If it did, those expensive remote staff wouldn’t exist. NHTSA’s recent information request to Tesla zeroes in on exactly this point: what is the precise scope of human intervention in your system? When the regulator has to ask, the marketing has clearly outrun the engineering.

The industry’s convenient gray zone

Tesla isn’t alone in blurring this line. The entire AV industry plays both sides — pitching investors on autonomy percentages while pointing to human oversight whenever something goes wrong. It’s a useful ambiguity, right up until someone gets hurt.

The standards just aren’t there. How many vehicles can one teleoperator monitor at once? What happens when the cellular link drops mid-maneuver? Who’s liable when a 500-millisecond latency turns into a collision? Nobody has a clean answer, and the cars are already on the road.

What were we actually buying?

Remember Musk’s long-running pitch that your Tesla would earn Uber money while you slept? That economic model rests entirely on real autonomy. If every robotaxi requires a backstop of remote human labor, the unit economics fall apart. Labor costs were supposed to be the variable that got eliminated, not relocated to a building in California.

Autonomous driving isn’t a fantasy. But a meaningful chunk of what gets sold as “autonomous” today is propped up by invisible human labor — workers in headsets, watching screens, ready to grab a virtual wheel. Next time you see a Robotaxi ad, it’s worth asking where the real driver is sitting.