Sprains, pain, and whiplash: Waymo and Zoox test drivers are getting hurt as robotaxis scale

Sprains, pain, and whiplash: Waymo and Zoox test drivers are getting hurt as robotaxis scale Sean O'Kane 7:36 AM PDT · August 27, 2026 The rapid scaling of robotaxis over the last two years has come with a hidden human cost.

Test drivers for Waymo and Zoox sustained more than two dozen injuries in 2024 and 2025 from hard braking or other sudden movements made by the autonomous vehicles, according to a TechCrunch review of data submitted to the Occupational Safety and Health Administration.

These test drivers, who put autonomous vehicles through their paces on public roads, have suffered sprains, strains, whiplash, and more, according to OSHA data and interviews with former and current workers. Some have been sidelined for weeks or months.

Transdev, which employs and manages Waymo’s test drivers, reported 16 injuries tied to Waymo depot locations in three cities that were caused by the autonomous software braking hard or swerving suddenly. Zoox reported as many as eight worker injuries linked to hard braking.

Other autonomous vehicle companies do not appear in the dataset, though it’s possible they’re exempt. The Zoox and Waymo injuries appear because the companies classify themselves as taxi, limo, or transit services, which OSHA subjects to greater disclosure because they’re “higher-hazard” industries. OSHA also only requires establishments with 100 or more employees in these industries to make this information public, meaning test drivers in newer cities where operations haven’t scaled may have been injured on the job without appearing in this dataset.

TechCrunch was unable to learn whether Waymo or Transdev logged any new injuries in 2026. OSHA does not require companies to submit annual data until the following year as part of the agency’s Injury Tracking Application.

In Zoox’s case, injuries are still happening, according to sources who spoke to TechCrunch on condition of anonymity.

Two current and three former Zoox contractors told TechCrunch that the company’s test fleet vehicles — modified Toyota Highlander SUVs equipped with its self-driving system — were still braking hard and abruptly as recently as July. Three of those contractors said workers are still getting hurt. The workers were granted anonymity to discuss private operations.

Zoox declined to answer specific questions about the injuries it reported last year or the claims contractors made to TechCrunch about the continued hard-braking issues. The company said it follows necessary reporting requirements and takes injuries seriously.

Zoox also said hard-braking incidents are sometimes unavoidable and that the injuries reported last year represent a small percentage of the millions of miles its test fleet traveled.

Waymo also declined to answer questions about the injuries reported to OSHA.

“The safety of our riders, road users, and team is of paramount importance,” Waymo told TechCrunch. “As part of the process of responsibly deploying fully autonomous vehicles, we have driven tens of millions of miles with human operators behind the wheel. This is part of our ongoing validation process and learnings from these trips are integrated into the service.”

While Waymo has spent more than a decade developing its self-driving cars, it wasn’t until 2025 that it really started to scale. The company started offering rides in new cities and began mapping and testing in others, growing its commercial fleet to more than 1,500 vehicles by May 2025. Today, that fleet is more than 3,500 vehicles.

Waymo doesn’t break out how many vehicles it uses just for testing. But the amount of autonomous vehicle testing almost certainly increased as the company expanded its service areas and started to familiarize itself with entirely new locations.

Transdev reported five Waymo test driver injuries in 2024 across San Francisco, Los Angeles, and Phoenix. One was related to hard braking, while the other four were related to erratic vehicle behavior.

In one case, a test driver reported that the car “suddenly backed up” while parking itself and “whipped the steering wheel,” catching his left hand and bending it "to the point he heard a crack in his wrist." The employee spent more than two months away from work as a result.

The number of injuries jumped to 11 in those three markets in 2025, and hard braking was the cause of nearly all of them. Last September, a test driver in Phoenix wound up having to spend 157 days away from work after their vehicle “made an exaggerated breaking [sic] event without any obstruction.” At least two other injury reports specifically mention that the hard braking happened for no apparent reason.

The only injury report from 2025 that offers a reason for a hard-braking event involved an incident that happened in August in Los Angeles. The employee reported that “some kids were playing in the pathway.” The Waymo robotaxi stopped hard enough that the worker spent 175 days away from their job.

The Zoox contractors said hard braking — or “brake jabs,” as they are referred to internally — can happen multiple times on a single test drive, sometimes in the same location. They can happen at any speed, though higher-velocity braking incidents typically take a harsher toll on the body, the workers said.

The braking often happens when the autonomous driving system detects — or mistakenly detects — debris of some kind on the road, they said.

The scariest incidents, the contractors said, are when a test vehicle experiences a “nogo” — internal code for an entire system shutdown that often leads to a brake jab.

“You could be going 45 miles per hour and the car will enact a nogo, and suddenly you’re being whipped forward in the middle of the street, in traffic, and you need to be able to take over quickly,” one said.

This behavior shows up repeatedly in the injury reports Zoox submitted to OSHA.

On January 5, 2025, a Zoox test vehicle was driving autonomously in San Francisco when it abruptly slammed on the brakes. Th...

Indexed and credited by AIPROPX. Originating outlet: TechCrunch. Open at source →