Tesla started charging real passengers for rides in its Cybercab on September 3, in Austin, Texas. It's a two-seat vehicle with no steering wheel, no brake pedal, no gas pedal, and no mirrors. Tesla notified federal regulators it had certified those vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards. But regulators opened a federal audit into that certification the same day.
The audit is real, and the paperwork behind it is public. NHTSA's Office of Defects Investigation logged it as AQ26002, an Audit Query covering an estimated population of 1,000 Cybercab vehicles. The field that should stop any hiring manager mid-scroll is "Prompted By": not a crash report, not a driver complaint — "Public Information." NHTSA opened this case because it saw Tesla's own launch announcement.
The agency's stated goal is to "examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues," and specifically "the extent to which Tesla's certification depended on determinations that certain FMVSS are inapplicable to the Cybercab."
"NHTSA fully supports the safe development and deployment of automated vehicles. But as the federal regulator, we need to ensure that all of our laws are followed."
— Jonathan Morrison, Administrator, NHTSA, TechCrunch
Most federal safety standards assume a human is sitting in the driver's seat. That's why they specify pedals and mirrors in the first place. Tesla's certification rests on the argument that a car with no driver's seat doesn't have to meet standards written for one. NHTSA wants to see the technical work behind that argument, not just the conclusion.
That's a compliance-engineering question, not an autonomy question, and it's worth separating from the marketing pitch. "No steering wheel" doesn't mean no human touches the ride. Tesla unredacted 17 Robotaxi crash narratives in May, and three collisions now on the public record (two from that disclosure, one reported later out of Houston) happened with a remote operator driving the car when it hit something: one drove a Robotaxi "up the curb and made contact with a metal fence" at roughly 8 mph after the automated system got stuck; another drove one into "a temporary barricade for a construction site" at about 9 mph after a safety monitor requested help; a third, in Houston, "made contact with a hidden tree stump" while recovering a stuck car from a dead-end residential road. Tesla itself has said remote operation "enables Tesla to promptly move a vehicle that may be in a compromising position" without waiting for a person to physically reach it. Fair enough — but that's a person, employed by Tesla, driving the car from somewhere else, on a system whose entire public pitch is that no person is driving.
This isn't Tesla's only open case with NHTSA this year. In March, the agency escalated a separate probe into Tesla's Full Self-Driving software to an Engineering Analysis (the last step before a recall decision) covering more than 3.2 million vehicles, after finding the camera-based system failed to detect degraded visibility from glare, dust, or fog and didn't alert the driver until just before a crash. NHTSA said as many as nine crashes may be tied to the issue, including one fatal crash. Tesla's own analysis conceded its proposed fix would only have addressed three of the nine. Read next to the Cybercab audit, the pattern isn't "one bad launch." It's a regulator that has spent 2026 asking Tesla to show its work on self-certified safety claims.
Here's the part that belongs on a hiring plan, not just a compliance memo. Removing a visible point of human control (a steering wheel, a manual approval step, a human reviewer in a workflow) doesn't remove the need for someone who can explain, in writing, to a regulator or an auditor, exactly why that removal is safe. That's a specific skill set: functional-safety and regulatory-affairs engineers who build and defend a certification record before anyone asks for one, not after. Career-placement firm Elevation Proving Grounds, aggregating LinkedIn Talent Solutions and Indeed Hiring Lab listings, counted more than 41,000 active U.S. openings across core autonomous-vehicle engineering roles as of June 2026. Those openings skew toward the perception and motion-planning work that ships a demo, not the compliance work that survives an audit.
You don't need to be building a robotaxi for this to apply. Any company shipping an automation claim — "no human needed to approve this," "the AI handles it end to end" — is one regulator's question or one plaintiff's discovery request away from needing someone who can produce the technical record behind that claim on short notice. NHTSA didn't wait for Tesla's Cybercab to hurt anyone; it opened the file on launch day. Treat that as a preview of the question you'll get asked next, not a Tesla story, and you hire for this role on a plan instead of a deadline.
VC5 Consulting places the functional-safety and regulatory-affairs engineers who can defend an automated system's certification before a regulator asks for it — not the week after. If your product removed a human checkpoint and nobody on staff owns proving that was safe, let's talk.