Uber's AV Chief Leaves Nov 16. His Fleet Ops Team Has No One to Follow

If you're hiring robotaxi fleet operators, the usual move after an executive departure doesn't work at Uber this time. Normally you'd track the exec and wait for him to rebuild his team somewhere else. Sarfraz Maredia, who runs Uber's autonomous mobility and delivery unit, leaves on Nov 16 for a top role outside transportation, so there's no team-building to wait for. The people worth calling are the operators who worked under him, and you have until the two internal leads splitting his job finish deciding who reports to whom.

Why following the executive is the wrong play here

When an executive leaves the industry, nobody pulls his team after him. That means you aren't competing with their old boss. You're competing with other outside recruiters, and the race lasts until the reorg settles.

The usual case for poaching a team after an executive leaves goes like this. The leader joins a competitor, waits out his non-solicit, and then hires his best lieutenants. Recruiters who follow the exec are betting on that sequence. It doesn't apply to Maredia. He has spent more than 12 years at Uber and is moving to a company in an unrelated industry that he hasn't named publicly. He won't be building a robotaxi ops team, so his people have no one to rejoin.

His portfolio is being split between two people:

• Samarth Kejriwal, senior director of driverless vehicle operations
• Aaron Emrich, head of autonomous delivery

Underneath them sit the five workstreams Maredia ran. Each one maps to a team a robotaxi or robotics company needs to build:

1. Charging
2. Fleet tooling and management
3. Data collection
4. In-vehicle experience
5. Remote assistance

Until Kejriwal and Emrich decide who reports to whom, everyone in those teams has three questions they can't answer: who their manager will be, what their scope will be, and whether their role survives. The company-wide restructuring adds pressure. Uber plans to cut the number of managers by 20% at every level and move many of them into individual-contributor roles. Someone leading a small charging pod today may be an IC by the time the reorg settles.

People who leave this unit already go to startups. Guy Peterson, who ran business development for autonomous partnerships, became chief business officer at Also, Rivian's bike spinoff. Lando Juarez, who led legal for the unit, left for Bedrock Robotics in June. Uber AV people are already listening to robotics and mobility companies.

How big is the Uber AV talent pool?

In Refolk's index of professional profiles, 128 US profiles have both "Uber" and "autonomous" in their headline. Only 69 US profiles anywhere use "autonomous vehicle fleet operations" in their headline. That makes Uber's AV-labeled pool about 1.9 times the size of the entire US fleet-ops headline pool.

1.9x

In a sample of 25 from the Uber pool, 21 still work at Uber. Their titles include Head of Product, Global Head of Safety, and Head of Autonomous Delivery Operations, all in Autonomous Mobility & Delivery. The other four have already left, for Rivian, Waymo, DoorDash, and one other company. Competitors have started picking from this group, but most of it is still in place.

A note on layoffs: Uber's cuts were company-wide. They totaled about 3,300 jobs, roughly 10% of staff, taking Uber from about 34,000 corporate employees to just under 30,000. What's specific to the AV unit is the leadership split and the reorg that follows it. That matters for your outreach. People facing a reorg are open to talking, but they aren't desperate, and your message should reflect that.

The 1% remote rule sorts the pool for you

Uber now says only about 1% of employees can keep working remotely, and jobs will be concentrated in New York and San Francisco. That makes AV staff living outside those cities the easiest group to recruit, because for most of them, staying at Uber now means relocating.

About 24% of the Uber-AV sample in Refolk's index lives outside the two hubs, in DC, Seattle, Pittsburgh, and Phoenix. Most of these people now have to move or leave, and the rule hits all of them at the same time.

Pittsburgh and Phoenix are also AV hubs with local employers already in place. So you can offer a Pittsburgh or Phoenix fleet-tooling lead a new job without asking them to relocate, which Uber can no longer offer.

Prioritize in this order:

• Staff outside the hubs in AV cities (Pittsburgh, Phoenix). Strongest push, and local employers can absorb them.
• Staff outside the hubs elsewhere (DC, Seattle). Strong push, and remote-friendly startups win here.
• Bay Area staff on teams whose lead is unclear. The push depends on how Kejriwal and Emrich divide reporting lines.
• NYC staff. Weakest push, since they already sit in a hub.

Why keyword search finds zero remote assistance people

When I searched Refolk's index for US profiles with "remote assistance" or "teleoperations" in the headline, I got zero results. Uber lists remote assistance as one of the unit's core workstreams, so the people are there. Their headlines just don't contain those words.

0

Teleoperations is a job function, not a job title. Remote assistance people put titles like "Fleet Response" or plain "Operations" in their headlines. A Boolean string built on the function returns nothing. A string built on a generic title like "Operations" buries you in rideshare ops people who have never worked with a driverless vehicle.

What works instead:

• Search by employer and team name. Use "Uber" plus "Autonomous Mobility & Delivery" or "AV" in the experience section, not the headline.
• Use adjacent title words. "Fleet response" or "operations lead," with an Uber AV team filter.
• Read experience descriptions for the work itself. Look for phrases like "remote guidance," "vehicle assistance," or "operator tooling."
• Look at former Uber AV staff at partners and competitors. The four who already left, to Waymo, Rivian, DoorDash, and one other firm, show where the next ones are likely to go.

This is the problem Refolk is built for. You describe the person in plain English, including the work their title leaves out, and get a ranked shortlist, so you aren't guessing which job-function word they happened to use.

Austin and Atlanta: Waymo's 2028 launch is a dated trigger

Uber's Austin and Atlanta depot and fleet staff have a specific reason to look now. Waymo has told Uber it will launch the Waymo app in both cities in January 2028, alongside its existing deployment with Uber.

Under the original deal, Uber had exclusive rights to service Waymo's fleet in Austin and Atlanta, handling everything from rider logistics to vehicle maintenance. Ending exclusivity doesn't end the contract, which runs through at least May 2028. But anyone running depot operations in those cities can see that their main fleet partner will soon have its own front door.

They're also in the right part of the country. In Refolk's index, most of the US "AV fleet operations" headline pool lives outside the Bay Area: LA, Houston, Dallas, Atlanta, Arizona, Tennessee. If you're hiring fleet ops in the Sun Belt, Uber's Austin and Atlanta staff are local, experienced on a Waymo fleet, and facing a known date.

Hire them in clusters, not one at a time

Fleet ops talent is so thin that a team of 3 to 5 people who already work together is worth more than five strong hires from five different companies. They bring a shared playbook with them, and that's the hard part to rebuild from scratch.

The 69-person US fleet-ops headline pool in Refolk's index is spread across about a dozen employers, and no company holds much of it:

• Zoox: 3
• PlusAI: 2
• Aurora: 2
• NVIDIA, Tesla, Transdev, AVOMO, and a stealth robotics startup: 1 each

No competitor has a deep bench, so everyone hiring for this function starts close to zero. Uber's AV pool is the largest concentration of this experience I can find, and Zoox, Aurora, and PlusAI are the likeliest companies to bid against you.

When nobody has a deep bench, the company that hires a working pod first gets its fleet-ops function running first.

A practical sequence for robotaxi fleet operations recruiting:

1. Map the unit by sub-team. Sort the 128 into charging, fleet tooling, data collection, in-vehicle experience, and remote assistance. Refolk does this when you ask for the sub-team by name, which beats tagging a spreadsheet row by row.
2. Flag who sits outside SF and NY. That's the roughly 24% your first wave goes to.
3. Find the pod leads. Look for managers of small teams. Uber has already cut "micro-teams" with one or two reports nearly in half, and with managers being cut 20% at every level, the remaining small-team leads are the likeliest to be converted to ICs.
4. Contact the lead first, then the pod. One conversation about scope and charter opens three or four more.
5. Time it to the reorg, not to Nov 16. Maredia's last day matters less than the day Kejriwal and Emrich announce reporting lines. Reach people before that announcement, while the uncertainty is real.

In the message, talk about scope, not the departing exec. Maredia's farewell memo says Uber's focus will increasingly be "on scaling AVs in more cities and achieving higher supply density in those markets," and Uber is pushing to offer service in as many as 15 cities worldwide by the end of 2026. These people know what city launches demand. "Your org is being split in two" is gossip. "You'd own fleet tooling for our next three city launches, from wherever you live" is an offer, and it targets the two things Uber's reorg just made uncertain: what they own and where they work.

FAQ

When should I contact Uber's AV operations staff?

Now, and before Kejriwal and Emrich finalize reporting lines. Maredia leaves Nov 16, but the real trigger is the moment people learn who their manager is and whether they're still a manager. Once that's settled, most of the uncertainty goes away, and a lot of the openness goes with it. Staff outside SF and NY facing the 1% remote rule will stay reachable longer, because the relocation question doesn't go away.

Is Uber laying off its autonomous team?

Uber is cutting about 3,300 jobs company-wide, roughly 10% of staff, and reducing managers by 20% at every level. What's specific to the AV unit is a leadership split: Maredia's portfolio is being divided between Samarth Kejriwal and Aaron Emrich, and his farewell memo says Uber will keep scaling AVs to more cities. Treat these people as passive candidates in flux, not as laid-off job seekers.

Who else is trying to hire autonomous vehicle operations engineers from Uber?

Expect Zoox, Aurora, and PlusAI, which are the largest employers of AV fleet-ops people in Refolk's index, plus robotics and mobility startups. Former Uber AV staff have already gone to Rivian, Waymo, DoorDash, Also, and Bedrock Robotics, so those companies know the pool too. No single employer holds more than three of the 69 US fleet-ops headline profiles, so every bidder is trying to build the same bench.

What titles should I search for Uber's remote assistance team?

Not "remote assistance" or "teleoperations," because those return zero US headlines in Refolk's index. Search "Fleet Response" or plain "Operations," combined with Uber's Autonomous Mobility & Delivery team in the experience section. Better still, describe the work in plain English and let the search match experience descriptions instead of headline keywords.