A CTO’s field guide to the 2026 AI job title theater, with a companion reference guide covering all 40 roles.
I have been a CTO for most of my adult life. I have hired, fired, onboarded, mentored, and occasionally been forced to explain to finance why a “Senior Applied Generative AI Engineer II” and a “Staff LLM Engineer” should sit in the same comp band. What I can tell you, after twenty years in this circus, is that the AI job title situation in 2026 is the worst naming disaster the industry has produced since we decided “DevOps” was a person rather than a practice.
Let me give you the tour. In a single week last month I saw open roles for: AI Engineer, Applied AI Engineer, AI Software Engineer, Generative AI Engineer, GenAI Engineer, LLM Engineer, Prompt Engineer, Context Engineer, Agent Engineer, Agentic AI Engineer, RAG Engineer, AI Systems Engineer, AI Platform Engineer, AI Infrastructure Engineer, AI Reliability Engineer, Model Deployment Engineer, LLMOps Engineer, AI Ops Engineer, AIOps Engineer, AI Evaluator, Evals Engineer, AI Red Teamer, AI Alignment Engineer, AI Safety Engineer, Model Behavior Engineer, AI Trainer, Forward-Deployed Engineer, AI Solutions Architect, AI Product Manager, AI Strategist, Chief AI Officer, Head of AI, AI-Native Developer, AI-Augmented Engineer, and my personal favorite, “Builder.” Boris Cherny from Anthropic actually predicted on Lenny’s Podcast that the title “software engineer” would disappear and be replaced by “builder,” because calling it a quarter to noon on Wednesday clearly wasn’t stupid enough.
Here is the dirty secret. Most of these titles describe the same three jobs.
Job 1: Someone who builds product features using an API somebody else trained. That is 80% of the market. Call them AI Engineer, Applied AI Engineer, GenAI Engineer, LLM Engineer, Prompt Engineer, RAG Engineer, or AI Software Engineer. The work is indistinguishable. They write Python or TypeScript, call OpenAI or Anthropic, stuff retrieval in front of it, write evals, and try to get the thing to stop hallucinating in production. Levels.fyi pegs median total comp for an “AI Software Engineer” at $245K and an “AI Engineer” at $159K. Same human. Different line on the org chart. $86K gap.
Job 2: Someone who trains or fine-tunes models. Your actual ML Engineer, ML Research Engineer, or Research Scientist. Median around $265K, PhD common, older discipline.
Job 3: Someone who keeps the AI plumbing from catching fire. MLOps, LLMOps, AI Platform, AI Infrastructure, AI Reliability. Pick your poison. Median around $161K.
Everything else is branding.
The 10 titles worth hiring for
These are the roles that describe actual, differentiated work. If your job description matches one of these, great. If it doesn’t, you are probably restating one of these in more expensive language.
| Title | Median TC | Verdict | What they really do |
|---|---|---|---|
| AI Engineer | $159K to $245K | Fastest-growing role in US | Builds product features on top of LLM APIs |
| LLM Engineer | $210K to $450K | Real specialization, real premium | Productionizes LLMs end-to-end, including fine-tuning |
| Machine Learning Engineer | $265K | The stable anchor role | Actually trains models from data |
| Research Engineer (frontier labs) | $350K to $1.4M+ | Dominant title inside AI labs | Research plus engineering, one role at OpenAI, Anthropic, DeepMind |
| AI Infrastructure Engineer | $220K to $600K+ | Hot, compute is the bottleneck | Runs the GPU cluster and serving stack |
| MLOps / LLMOps Engineer | $161K to $240K | Stable, underpaid for what it is | Keeps models and prompts from breaking in production |
| AI Product Manager | $180K to $260K+ | Every product org needs one | Owns the cost/quality/latency triangle |
| Forward-Deployed Engineer | $238K to $700K | Hot and potentially oversold | Enterprise customer-embedded, writes production code |
| Evals Engineer | $160K to $400K+ | The most under-valued title on this list | Designs how you actually know if the AI is good |
| Chief AI Officer | $352K to $1M+ | New but real C-suite seat | Owns AI strategy, risk, and governance |
If you hire cleanly across those ten, you cover roughly 95% of the legitimate work happening in AI right now. Everything else in the reference guide is either a variant of these, a niche specialization, or marketing.
The 10 titles that are mostly theater
These are the ones I would push back on if they showed up in a req template. Some are real work under a dressed-up label. Some are skills masquerading as jobs. Some are vendor sales moves wearing an engineering uniform.
| Title | Why it’s theater | What it actually is |
|---|---|---|
| “Builder” | Cherny’s prediction for end of 2026, not a real title | Marketing for “engineer who uses AI” |
| Vibe Coder | Collins Word of the Year. Meme. | Someone who accepts all AI diffs without reading |
| Vibe Engineer | Willison himself called the name “stupid” | A workflow, not a title |
| AI-Native / AI-Augmented Developer | Not a title, a skill | Will be “Software Engineer” in 18 months |
| Prompt Engineer | Peaked 2023, now absorbed into AI Engineer | Narrow slice of what context engineers do |
| GenAI Engineer | Branding variant of AI Engineer | Consulting firms preferred label |
| RAG Engineer | Too narrow to survive | Skill inside AI Engineer |
| Context Engineer (at consulting shops) | Cognizant hired 1,000 with a vendor that sells “ContextFabric” | Senior Consultant with a new title |
| AI Strategist | Squishy advisory label | Consulting rebrand |
| AIOps Engineer (legacy sense) | Naming collision with agent ops | IT ops with ML features |
Context Engineer deserves a note. The underlying discipline is legitimate. Karpathy endorsed the framing in 2025, and the work (retrieval, memory, tool design, governance of what an agent sees) is real. But Cognizant’s August 29, 2025 announcement of one thousand Context Engineer hires, in partnership with Workfabric AI which happens to sell a product called ContextFabric, is a marketing stunt wearing an engineering hat. In-house teams at AI labs do context engineering. They just don’t hire for the title.
“Prompt Engineer” had the same arc in reverse. In 2023 it was supposedly the future of work. Two years later, Glassdoor has the median at $129K, ZipRecruiter has it at $63K, and most serious roles have been quietly rebadged to “AI Engineer” because nobody wanted to be the one who told investors they were hiring English majors to whisper at ChatGPT.
Then there is the Forward-Deployed Engineer, which isn’t theater but deserves a warning label. Palantir invented the role over a decade ago. In 2025 every AI lab decided they needed them too. FT reported FDE postings jumped over 800% between January and September 2025. Gergely Orosz then pointed out the funny part: developers do not actually want the job. High pressure, customer-facing, seen as less prestigious than “real” engineering, and devs who take it often quit within weeks when they figure out it is consulting with a nicer title. Palantir pays an average $238K TC. OpenAI and Anthropic pushed the bands to $350K to $550K. For that money you get to fly to Fortune 500 HQs and babysit their RAG pilots. Some job.
And “vibe coder.” Andrej Karpathy coined it on February 2, 2025. Eight months later Simon Willison countered with “vibe engineering” to rescue the term. Willison himself wrote that the name is “stupid” but he wanted the gatekeeping. Fine. But now we have a generation of LinkedIn headlines that read “AI-Native Vibe Engineer | Builder | Forward-Deployed Agentic Context Architect” and my eyes physically hurt.
The cost of the theater
The naming mess has a direct price. When a company calls the same job three different things across three req IDs, recruiters over-pay the shiniest one by 20 to 40 percent. I have seen a fintech pay $260K for an “LLM Engineer” while paying $180K for an “AI Engineer” doing the exact same RAG work two floors away, because the first req was approved by a VP who read one Substack about LangChain.
The title inflation also signals to the market. Once “AI Engineer” becomes the generic label, every niche reinvents itself as a different kind of engineer to escape the pay gravity. This is how you get “Principal Agentic Context Engineer” as a real LinkedIn title. It pays better than AI Engineer because HR has no benchmark for it.
What is actually going to happen
Most of these titles will collapse into “AI Engineer” over the next 18 months. The prestige labels will survive only at frontier labs where the work is genuinely different. What will emerge in their place are two roles nobody is talking about yet, and they matter more than anything on the current list.
The first is the AI Delivery Engineer
Not an orchestrator, not a conductor. Someone who owns the full arc from vague business intent to shipped outcome, using AI as the primary production tool. They refine the story description. They decide what technology to reach for. They guide the AI through generation with different levels of automation depending on the risk of the task. They review output, iterate, and ship.
This is not a project manager. This is not a prompt engineer. This is the person who turns “we need a customer-facing quote calculator that handles these edge cases” into a working thing, with the AI doing most of the typing and the human doing all of the thinking. In most small and mid-sized companies, this role absorbs what today is split across engineer, PM, and tech lead. By 2027 I expect the AI Delivery Engineer to be the most common engineering title in companies under 200 people.
The second is the Verification Engineer
This role does two jobs at once. They are a QA tester in the traditional sense, running the system end-to-end and hunting for broken edge cases. But they are also the keeper of a domain knowledge base that lets them verify the AI actually built the right thing for the business, not just something that runs.
They check the business logic. They confirm the flow handles the regulatory case, the currency conversion, the off-hours billing exception, the thing that matters to this specific company and no other. This role only makes sense in larger organizations and in anything where a wrong answer has real consequences. Fintech. Healthcare. Industrial control. Legal. Payments. For low-risk code, the AI will self-check or auto-accept. For anything that touches money, safety, or compliance, a human Verification Engineer signs off. The knowledge base they maintain is the product. The checking is the salary.
Neither of these roles is a rebrand. Both replace real work that today is scattered across tickets nobody owns.
Practical advice
If you are a hiring manager reading this, do two things. First, standardize on two engineering titles for the current wave (ML Engineer and AI Engineer) and put specialization in the JD, not the title. Second, start mapping which of your existing roles are quietly becoming AI Delivery Engineer or Verification Engineer roles. The people already doing that work are the ones you cannot afford to lose.
If you are a candidate, stop collecting titles like Pokémon. Nobody senior is impressed. The best engineer I hired last year had “Software Engineer” on her LinkedIn and shipped three production LLM systems. The worst candidate I rejected was a “Principal Agentic GenAI Forward-Deployed Context Architect” whose GitHub was three forks of a LangChain tutorial.
The models are smart. The titles are stupid. The next generation of titles will not be the ones on the LinkedIn trending list right now. They will be the ones that name work that did not exist before AI made it possible.
For the full breakdown of all 40 titles, comp ranges, differentiators, growth trends, and my recommended HR standardization framework, see the companion AI Job Title Reference Guide 2026.
Final Words
I wrote this partly as a reference for HR teams drowning in req templates, and partly because I am tired of seeing the same three jobs dressed up in thirty-five costumes. Agree? Disagree? Think I got the predictions wrong and you have a better name than AI Delivery Engineer or Verification Engineer? Tell me.
I post regularly on LinkedIn (linkedin.com/in/ivanturkovic), X (x.com/ithora), and Threads (threads.com/@ithora). If you want to talk about how to actually structure your AI engineering org, or you’re thinking about fractional CTO work, reach out at ivanturkovic.com/contact or book a call directly at cal.eu/ivan-turkovic/30min.
What title is your company using for the job that used to be “software engineer,” and what do they actually do all day? I genuinely want to know.
If this post made you think, you'll probably like the next one. I write about what's actually changing in software engineering, not what LinkedIn wants you to believe. No spam, unsubscribe anytime.