Who Leads AV Compliance When Every City Regulates the Fleet Differently?

The Permit Renewal, the Incident Clock and the Lapsed Certification All Landed on Thursday

A vehicle stopped in an intersection for ninety seconds, which started a reporting clock in one state. A second city wants its quarterly curb-use summary. A remote assistance specialist's certification lapsed five weeks ago, and nobody can say yet whether that person supported a ride afterward. Three obligations, three teams, no single owner of the whole surface. That gap is the job.

An AV compliance lead owns the regulatory obligations of the fleet and of the people who support it, in every jurisdiction it operates in, including the evidence that each obligation was met. The scope is deliberately hybrid. Waymo's 2026 posting paired fleet compliance with operator compliance in one title ¹, and that pairing is the part most hiring managers underestimate, because the vehicle side has engineers already looking at it and the human side usually has nobody.

Four tells separate someone who has done this from someone who has read about it.

The first is that they work from the permit condition itself, not from a summary of it. Ask a candidate how they would confirm the fleet is compliant with a condition in a city they have never worked in. A real answer opens the permit, reads the operative sentence, and asks what artifact would prove it. A performed answer describes a compliance calendar.

The second is that they think in evidence rather than intent. Ask what the company would hand a regulator who asked, with no notice, to see proof that every remote operator on shift last Tuesday was qualified to be. The strong answer names the system of record, who writes to it, how long the retention runs, and what happens when the answer is that a record is missing. The weak answer says the training was done.

The third is that they treat the operator side as in-scope from the first sentence. Qualification, recurrent training, hours, fitness for duty, incident interviewing, and what a remote assistance specialist is permitted to do without escalating are all compliance artifacts. A candidate who talks only about the vehicle has half the job.

The fourth is the negative question, and it is the most useful one to ask. Ask about a time they told an executive that something could not ship yet. Anyone who has held this seat has a story with a date, a specific missing artifact, and a cost. Someone who has only advised will describe a recommendation.

Which Backgrounds Actually Produce an AV Compliance Lead?

The reliable feeders come from industries where an operator's licence to run is conditional and revocable: aviation operations compliance, rail safety, commercial trucking safety directors working under federal motor carrier rules, nuclear operations, and pipeline or maritime regulatory roles. All of them have lived with an inspection they could not prepare for on the day, and all of them already believe that a record which cannot be produced does not exist.

Aviation converts fastest, and for a specific reason. Air operator compliance already spans machine and human in one function: airworthiness on one side, crew qualification, duty limits and training records on the other. That is the same shape as fleet and operator compliance, with a different vehicle. Trucking safety brings the multi-jurisdiction instinct plus a genuinely operational relationship with depots and drivers, which matters more than it sounds when the humans in question sit in a remote assistance room at 2am.

The unexpected feeders are worth more than the obvious ones. Transit agency compliance officers have spent years on service obligations, accessibility requirements and public reporting under municipal scrutiny, which is precisely the political texture of a city AV permit. Clinical trial regulatory affairs people are trained to keep a contemporaneous record that survives an audit years later. Gaming and casino regulatory managers work under per-jurisdiction licences with real revocation risk. Every one of those backgrounds arrives fluent in the habit the role is built on.

What almost nobody arrives with is the technical vocabulary of the driving system. Operational design domain boundaries, disengagement and event definitions, map versioning, fallback behavior. That is teachable in a couple of months and worth budgeting for, and it is the seam where this hire works closest with the geospatial AI engineering lead, since where the vehicle is permitted to drive is both a map fact and a permit fact.

Two profiles interview well and often disappoint. Policy and government affairs candidates are excellent at reading what is coming and frequently uninterested in the filing that is due on the fifteenth. And lawyers who have advised AV clients from outside know the rules without ever having owned the record. Both can be strong hires next to this role. Neither is the role.

Ask How the Candidate Got Burned by a Confident AI Summary of a Rule

Ask how they personally use AI tools in compliance work, then listen for a failure they can date. The answers worth hearing are specific: a model summarized a permit condition or a reporting rule, the summary was confidently wrong about a deadline or a threshold, and the person changed how they work as a result. They can name the rule, name how it fell apart, and name the check they now run every single time.

Good answers share a shape. Someone used a model to diff two cities' permit conditions and then read both source documents to verify every difference it claimed, because the interesting output was the differences it missed. Someone else drafted an incident narrative with an assistant and then pulled the telemetry and the operator log to confirm each sentence before it was filed. A third keeps a running file of cases where a tool asserted a citation that did not exist, which is the closest thing this discipline has to a lab notebook.

The habit underneath all of it is checking a confident claim against something outside the conversation. In compliance the outside thing is almost always a primary source: the permit, the statute, the signed training record, the raw log. That habit is invisible in a resume and hard to fake in front of real work.

So make part of the interview a working session. Give the candidate two real permit condition sets from different jurisdictions, an AI-generated summary of both that contains one wrong deadline you planted, and ninety minutes. Ask for a one-page gap memo: which obligations the current operation cannot evidence today, which artifact would close each gap, and who would own it. You will learn more from that page than from four conversations about regulatory strategy.

One caution about vocabulary. This field rewards fluent talk, and the vocabulary is a weekend of reading away. The transcript of a candidate who has carried a permit through two renewals and one who has followed the industry closely can look nearly identical. Only the work separates them, which is the same reason autonomy boundaries get written down properly only when someone owns them, as with the agent product manager role.

Where Do You Find This Person, and What Actually Closes Them?

Start with the operators visibly hiring the scope, because their people already carry it. Waymo posted an AV Compliance Lead covering fleet and operator compliance in 2026 ¹. Beyond the AV companies themselves, look at commercial trucking and bus fleet safety departments, regional transit agencies running automated shuttle pilots, and the compliance benches at fleet insurers, all of which employ people who own conditional operating authority for a living.

Postings expire, so read that one as evidence the combined scope is real rather than as a vacancy to go and check today. The standards and research venues are the other real pool. SAE's on-road automated driving committee work and the Transportation Research Board's automated vehicle programming both draw the people who read the source documents for pleasure. Those rooms are small, the names repeat, and a warm introduction from one attendee is worth more than a hundred outbound messages.

Look inside first anyway. Depot and fleet operations supervisors who wrote the standard operating procedures, and the person who has been quietly maintaining the remote assistance training matrix in a spreadsheet, are frequently already doing a third of this job with no title and no authority.

What closes this hire is rarely money. It is authority and information. Serious candidates will ask three things: whether they can hold or pause a city launch, who they have to convince to do it, and whether they hear about an incident on day zero or from the second version of the internal summary. Answer all three concretely. If the honest answer is that an executive decides on the day, say so, because they will find out in month two and leave in month six.

The second closing lever is the evidence system. Show them what exists: the record of operator qualification, the retention policy, the incident file from a real event. Strong candidates read a company willing to show its own messy records as one that will let them fix them. The same instinct for who owns a defensible data trail shows up in the AI data partnerships manager hire.

What Should an AV Compliance Lead Cost, and Does the Role Need a Depot Badge?

No wage series covers this title, and no survey found for this piece prices it, so the honest answer stays qualitative. Any single figure quoted for the role today is a guess wearing a benchmark's clothes. Price it against the band used for a senior regulatory affairs manager or a fleet safety director in a regulated transport business.

Then adjust upward for two things: the number of separate jurisdictions in scope, and whether the person carries real authority to hold a launch. Both change the job far more than the title does.

The pressure on that band is real even where the point estimate is not. PwC's 2026 AI Jobs Barometer, analyzing roughly one billion job advertisements, reports an average wage premium of 62 percent for roles demanding AI skills as of 2026 ². Read that as a reason an existing regulatory affairs band will be tested in negotiation, not as a number to put in an offer.

There is a leveling trap worth naming. The category is new enough that scope varies wildly between employers, so a candidate's current title tells you very little. Ask what they were permitted to stop without asking anyone. That answer, not the title, tells you which band applies.

On location, the filings half of the job is genuinely remote. The operator half is not. Qualification, recurrent training and incident interviewing happen where the depots and the remote assistance rooms are, and a compliance lead who has never watched a shift handover writes procedures that the shift quietly works around. Expect a hybrid pattern with regular presence at the operating sites, plus travel to each jurisdiction where a regulator wants a relationship with a person rather than an inbox.

On-premise requirements show up around the evidence itself. Vehicle video, telemetry and operator records can carry data residency and access restrictions, so the constraint is usually the review tooling rather than the person's desk. Scope that before writing an offer rather than after.

One legal note, offered as a flag rather than as advice. In the United States, vehicle-level authority and passenger-service authority frequently sit with different agencies in the same state, and city-level permits add a third set of conditions on top; the rules differ by jurisdiction and were still moving through 2026. Read the operative permit and statute for each place the fleet runs, at the date it runs there, and check with counsel in that jurisdiction rather than reasoning from a summary. The habit of going to the primary source is the whole job, so it should start with the job description.

Read the evidence >