Careers page adds 58 autonomy and fleet-operations roles, 19 referencing driverless operation or remote assistance
Waymo's binding constraint moves from autonomy to operating policy and permits
The company's careers page listed 58 open roles this week in autonomy deployment and fleet operations, of which 19 reference driverless operation or remote assistance policy explicitly. Twenty-two are located in cities where paid autonomous service is already operating, and nine are located in the city targeted for the first international launch. Eleven roles are at staff level or above. Seven are cross-listed with the simulation organization. One posting for a deployment engineering lead lists reporting to the unit's co-chief executive and describes the role as owning the operating policy rather than the software. A recruiter post referenced a reorganization of the deployment organization effective at the start of the following calendar quarter.
Nineteen of fifty-eight roles on operating policy rather than perception software, with the lead role owning 'the operating policy rather than the software', indicates the binding constraint in the autonomous program is now regulatory and operational rather than algorithmic.
Nobody hires nineteen people to write the rulebook for a system that is not about to matter. That posting is dated the week they opened three cities, which means the policy jobs were approved before the launches were announced.
- 58 autonomy deployment roles, 19 referencing driverless operation or remote assistance
- Lead role owns operating policy rather than software
- 31 of 58 roles sited in operating or imminent-launch cities
- Deployment organization reorganization effective next quarter