You search for "AI enablement" jobs because the phrase describes what you have been doing informally: helping colleagues use these tools well. The first advertisement wants a workshop leader. The second, with almost the same title, wants someone who reviews code and ships agents. Which one is the job?
Both are. In the four advertisements I read, the title does not tell you what the job is. The duties do, and they differ enough that a reader suited to one would be a poor fit for another.
This piece reports what four employers advertised on one day. It keeps two things apart throughout: what an advertisement says, quoted, and what I infer from it, labeled as inference.
Four live advertisements from four employers, read from each employer's public job listing on September 21, 2026, and archived as received. They show what these employers advertise. They do not show what the work is like, who gets hired, or what a typical salary is.
The four advertisements
| Employer and title | Where the role sits | Experience asked for |
|---|---|---|
| Nimble Gravity: AI Enablement & Adoption Manager (headed "AI Enablement Lead") | A consultancy; the work is with clients | "5 to 10 years of experience in enablement, training, consulting, organizational adoption, or a related field" |
| Waymo: AI Enablement Lead | An internal data team serving finance, HR, legal and supply chain | "8-10 years of professional experience across data science, data engineering and business intelligence disciplines" |
| Culture Amp: Growth Marketing AI Adoption Specialist | A six-month contract inside one marketing department | "3–5 years of hands-on experience working across marketing and revenue technology tools, building or configuring AI-assisted or automated workflows" |
| GitLab: AI Transformation Owner, CRO | The sales-enablement function | "Several years of experience in enablement, sales operations, or a related GTM function" |
All four were live when I retrieved them. If a link has since gone dead, treat that posting as a historical source; the archived copy is what this piece quotes.
One title, two jobs
Nimble Gravity and Waymo both head the role "AI Enablement Lead".
Nimble Gravity's lead will "lead workshops, deliver training, develop adoption strategies", and must "Hold technical ground solo": "Field specific technical questions about system design, data flow, and failure modes directly, without deferring to 'that's what the technical team is for.'"
Waymo's lead will "Develop and prototype solutions by building proof-of-concepts that leverage large language models (LLMs), agent frameworks, and workflow orchestration tools" and "Provide technical oversight by reviewing code and prompts". It asks for a "BS degree in Computer Science, or a related technical field, or equivalent practical experience" and "Strong proficiency in Python".
Inference: under one heading these are a trainer-consultant role and an engineering lead role. The diagram's three groups are my reading of the duties. No employer uses those labels.
What the advertisements say, and what I infer
| What the advertisements say | What I infer |
|---|---|
| Culture Amp tells its specialist to stay "focused on execution rather than strategy, architecture, or governance work". GitLab's owner must "Influence and lead governance standards for AI tool adoption in the field, including data usage, risk review, tool vetting". Waymo lists "AI governance, enterprise data privacy standards, and security protocols" under "We prefer" | Governance is one role's core duty, another's preference and a third's explicit exclusion. You cannot assume it is part of "adoption" work |
| Nimble Gravity asks for "adoption numbers, engagement rates, time saved, error rates reduced". GitLab asks its owner to "track this adoption (e.g., usage, proficiency, behavior change)". Culture Amp asks for "performance measurement" and work prioritized "by rough effort and impact" | Three of the four want measured results. Each names its own measures |
| The prior experience named is enablement and training (Nimble Gravity), data science and engineering (Waymo), marketing technology (Culture Amp), and sales enablement or operations (GitLab) | Each employer hires from the function the role will serve. Only Nimble Gravity names adoption programs as experience, and it accepts "enterprise software, digital transformation, or AI initiatives" |
| Pay, as each employer states it: Culture Amp "$112,800—$128,900 USD", GitLab "$139,200—$235,200 USD", Waymo "$200,000—$247,000 USD". Nimble Gravity states none | No inference. These are three employers' stated ranges for three different jobs, one of them a fixed-term contract. They do not combine into a salary for a role |
All four ask for practical AI experience
Each advertisement asks you to show hands-on involvement with AI, and each describes it differently.
- Nimble Gravity: "A specific, named example of something you built or configured with generative AI, not just a tool you used. Think: an agent workflow, a rules based guardrail, an automated triage process. 'Used Copilot to draft emails' doesn't meet this bar."
- Waymo: "Mandatory hands-on experience using GenAI tools (vibe-coding) to turn prompts into small prototypes in a constrained environment, then use that artifact to validate requirements."
- Culture Amp: "building or configuring AI-assisted or automated workflows", and then "Document what you build clearly enough that our team can maintain and extend it after the engagement ends."
- GitLab: "Direct experience evaluating, piloting, or deploying AI tools or solutions in a business context, with a solid technical understanding of how they work and where they add value."
Across these four advertisements, employers ask for practical involvement with AI: building or configuring workflows, prototyping, or evaluating, piloting and deploying tools. The evidence you bring should match the responsibility. For one role that might be a working prototype; for another, a documented evaluation or an adoption program.
Check your reading
How to read the next one you find
Mark each responsibility as training and persuading, building and reviewing, or configuring tools inside one department. Use the dominant responsibilities to identify the role's emphasis; some jobs combine these groups.
Is it a duty, a preference, or ruled out? In this sample it was each of those once.
Choose an example that shows your contribution, what you checked and what happened. Include a meaningful measure where you have one.
Waymo separates "You have" from "We prefer". Nimble Gravity marks regulated-industry experience "Strongly preferred, not required" and adds: "If you don't have this but bring deep AI build experience and strong solo executive presence, we still want to hear from you." GitLab says "many successful candidates do not meet every single requirement." These are the employers' words about their own lists. They are not a promise about any application.
How I gathered these
I looked at employers that publish jobs through one job-board vendor, found twelve live titles that matched, chose four from four different employers, and read them on September 21, 2026. Before that, a web search had returned nine indexed postings for the same titles; eight were already withdrawn when I checked the employers' live listings, and I do not know why. This is a small sample from one source. It says nothing about whether these roles are growing or how many exist.
The customer-list guide ends with three counts that show what changed: rows in, rows out, rows deliberately merged. It is an optional first exercise in recording what you did and what you checked. It does not establish readiness for the senior roles above.
