The AI Operator Map: AI Jobs Sort on a Different Axis

A while back a message landed in my LinkedIn inbox. A recruiter at an AI-specialist firm here in Australia: they were placing AI talent with clients across the country, my profile had stood out, would I be keen for a chat. I said yes, but honestly not for the role. I wanted to know what demand for AI people actually looks like in this market, straight from the people who sit behind the job ads.

Which is how that call turned into two interviews running at once. They were measuring me against their ladder, three tiers from hands-on operator to executive, AUD $70k to $250k and up. I was trying to read the market off them: what problems are companies actually hiring people to solve?

But my question wasn’t anywhere on their ladder. Hire two people at the same tier and you can get two completely different jobs: one automating internal workflows, one building products on LLMs. Different experience required, different evidence to show. The ladder had no row for that distinction. The call ended and I still didn’t have my answer.

So I went and checked myself: job postings, salary guides, national statistics. Every number in this piece carries its source and its definition; the stage is the Australian market, and global surveys are marked as such. You’ll see why by the end.

The names the market uses collapse into five

Strip away the titles, group by “what problem does this person solve”, and you get five functions. Not an industry standard — a grouping I built from the postings and the surveys.

Five rows and the map would be done, except the moment you search by title, the table starts coming apart.

Titles churn. Functions persist.

It isn’t just titles — the credentials around them churn too. This year’s evidence alone:

• Microsoft retired the Power Automate RPA developer certification (PL-500) in June 2026 and put a new agent certification (AB-100) in its place. The credential name swapped; the automation function underneath didn’t move.
• “Chief AI Revenue Officer” circulates in content everywhere. I could not find a single person who actually holds the title.
• Forward Deployed Engineer postings grew 729% in a year on Indeed’s data, and the role sits across two functions, Application and Architecture, so it fits no single cell.
• One Melbourne government posting for an AI Enablement Lead bundles the AI roadmap, responsible-AI governance, and the organisational learning program into one hire.
• In IAPP’s survey, 68% of privacy professionals have taken on AI governance as a second hat.

So the unit is the function, not the title. In the postings, small organisations bundle several functions into one person, and the bigger the company, the more each function gets its own team. Adoption itself tracks size too: per the Australian Bureau of Statistics’ 2024–25 business survey, 35% of large businesses use AI, 22% of mid-sized, and 11% of small and micro businesses.

Tools track company size as well. n8n, the center of gravity of YouTube automation content, didn’t make the grid of the 2026 Gartner Magic Quadrant for iPaaS at all (a mention in the text, no more), while the leaders are Boomi, Workato, SAP, Salesforce, and Microsoft. Half the companies running self-hosted n8n have 2 to 10 employees (Bloomberry’s certificate-log scan of self-hosted instances; cloud customers aren’t captured). n8n is inside big companies too; what splits isn’t presence but the procurement and production-approval layer. Why the tools YouTube teaches and the tools companies actually buy differ this much deserves its own piece, so just one line here: enterprise vendors don’t pay YouTubers affiliate commissions. SMB tools do. n8n pays 30% of referred cloud-subscription revenue for twelve months.

“Can’t I just learn whatever and go?”

I wish. The failure data says it’s not that simple.

Quoted failure rates for enterprise AI run anywhere from 30% to 95%, and they measure different things in different units, so they can’t be lined up on one scale. Pull out any single number and you almost certainly distort it.

If you’ve seen “95% of AI projects fail” somewhere, it comes from the bottom row: a preliminary report, not a peer-reviewed study, built on 52 interviews plus 153 conference surveys and a review of 300-odd public initiatives. The real limits are its six-month window and interview-attested outcomes, and the same report found that roughly 83% of generic chatbot pilots succeed. This is why every number in this series carries its source and its definition.

Where the surveys do overlap, despite their different bars, is an observation: in McKinsey’s, BCG’s, and MIT’s data alike, the successful minority defined the outcome before building and redesigned the workflow instead of laying a tool on top. Correlation, not proven cause, but the direction is consistent. My reading: this market is short on people who know what to measure.

And AI skills already carry a price. Australian job ads asking for AI skills grew little for four years, then doubled from 20,000 to 41,000 in a single year, and those ads carry an average 62% wage premium (PwC AI Jobs Barometer, Australia 2026; by industry it ranges 8–59%). Demand is growing, but which size of organisation you join changes the tools you’ll meet and the evidence you’ll be asked to show.

Each function has its own evidence

That’s why the last column of this map is evidence, not tools.

If some terms in the table are unfamiliar, that’s fine. What an eval harness is, how you measure behaviour change: each function’s installment will unpack them one at a time.

Evidence isn’t something you can batch up later. Build with measurement attached from step one and it accumulates alongside the work itself. Which function, measuring what, and how — those are the cells this series fills in.

If you’re weighing up your AI career right now, pick the problem you want to solve, not the title. The experience you build solving it becomes the foundation for everything after.

Next up: Automation.