You're not on the market. That's exactly why we should talk.
The strongest people in this field are employed, well compensated, and not browsing postings. Everything here is built around that, starting with the fact that no conversation obligates you to anything.
Your title probably undersells what you do
Job titles in this field travel badly between companies. People doing genuine model risk management are titled compliance managers in one org and risk leads in the next. People running adversarial testing programs are titled security engineers. People who built an entire AI governance function from nothing are titled whatever the org chart had available at the time.
That gap costs money. It costs it at the offer stage, and it costs it earlier when a company screens you out because their keyword search did not know what you were called.
We can tell you what your actual scope is worth right now — not from a salary survey, but from live US posting data and the offers currently moving in this market.
Four commitments, and we'd rather you hold us to them
Your name doesn't move without your say-so
Not to a client, not to a "we're just gauging interest" conversation, not in an anonymised profile detailed enough to identify you. In a market of a few thousand practitioners, discretion is not a courtesy — it is the entire basis for talking to us at all.
We'll tell you when a role is wrong for you
Including when it is wrong in ways the hiring company has not admitted to itself — a governance role with no authority to stop a launch, a compliance seat that reports three levels below where the decisions get made, a Field CISO title over a job that is actually solutions engineering.
You get the comp read before you need it
What your scope is worth, where the band moves for your specific function, and which parts of your background the market is currently paying a premium for. Useful in your next internal review even if you never take a call with us.
Staying put is a legitimate outcome
Plenty of these conversations end with someone deciding they are in the right seat. That is a good result. This market is small enough that we would rather be the people you call in three years than the one who pushed you into a bad move now.
If your work sits anywhere in here, we should be in contact
Whether or not anything is open right now, and whether you are an individual contributor or running the function. The map is more useful to both of us when it is built ahead of the need.
Policy & Program
Policy ownership, program leadership, the approval gate for AI deployment — analyst through Chief AI Officer.
Model & Enterprise Risk
Model risk management, AI risk assessment, third-party and vendor AI risk, at every level of seniority.
Regulatory Readiness
Regulatory readiness against the state patchwork and customer contracts, from analyst to compliance executive.
Audit & Assurance
Independent testing and attestation. The function this practice is named for, underrepresented everywhere else.
Privacy Engineering
AI privacy engineering, data protection for ML systems, privacy-preserving architecture, at every level.
AI & ML Security
ML security engineering, LLM security architecture, AI red teaming, adversarial testing — plus the Field CISO track.
Trust & Safety
AI trust and safety, misuse monitoring, bias mitigation, alignment. Concentrated at frontier labs.
Data Governance
Training-data provenance, lineage, quality and stewardship for AI systems, at every level.
Advancement is one reason to talk. It is rarely the only one.
Moving up a title is the obvious reason to pick up the phone. It is not the most common one. Here is what usually starts the conversation instead.
The comp read
What your scope is actually worth right now, from live posting data rather than a survey. Useful in a review whether or not you ever take a role.
Equity and upside
Same title, same band, very different equity story. Post-Series-B versus pre-seed versus public changes what the offer is actually worth.
A more technical seat
Moving from a policy-heavy version of this work into one with real technical depth, or the reverse — both are common, and both change what the next five years look like.
A more technical industry
Same function, a company or sector where the AI risk is sharper and the work is closer to the actual model, not three layers of process removed from it.
Culture and authority
A governance seat with no authority to stop a launch looks identical to a strong one on paper. What the role can actually do matters more than the title on it.
A lateral that isn't lateral
Same level, same title, a genuinely different job — moving from compliance-triggered work into the vendor/GTM side, or from IC depth into building a function from zero.
Staying visible, not moving
Plenty of good conversations end with someone staying put, better informed. In a market this small, being known before you need something is worth more than a fast placement.
You're just not sure yet
You don't need a thesis on why you might move. A confidential conversation, off the record, is enough of a reason on its own.
Start with the comp read. Decide about the rest later.
Confidential by default. Nothing moves without your explicit go-ahead.