Two titles have started appearing in the same job specifications, often interchangeably. They are not the same thing, and the difference matters more than it first appears, because it determines what you are actually hiring for.
The short version: the AI-Native CTO redesigns the company around intelligence. The Agentic CTO focuses more specifically on redesigning work around agency.
What the Agentic CTO is for
Agency begins when software can act. A chatbot responds. An agent pursues an outcome: it interprets a goal, makes a plan, uses tools, completes steps, checks progress and escalates when human judgment is required.
Building that safely inside a company is a genuine specialisation. It requires deciding which workflows are suitable for delegation, setting boundaries on what an agent may recommend, prepare, execute or approve, giving it trusted and permission-aware context, and standing up the evaluation and observability needed to know whether it is doing the job.
That is a deep body of work. An organisation moving seriously from copilots to agents will need someone who understands it properly.
Why it is a specialisation and not the whole job
The difficulty is one of scope.
An Agentic CTO, defined narrowly, is accountable for how work gets delegated to software. That is a substantial mandate, but it sits inside a larger one.
The AI-Native CTO carries the broader accountability across product, platforms, engineering, data, risk, talent and business strategy. Agent design is one of seven responsibilities in that role, alongside reimagining the product, building the intelligence architecture, redesigning software delivery, protecting the company, changing the talent model and translating technology into enterprise value.
A company that hires only for agency tends to end up with capable agents attached to a product strategy nobody revisited, running on a knowledge layer nobody designed, staffed by an organisation nobody redesigned. The agents work. The company does not change.
The dependency runs one way
Every serious Agentic CTO should be AI-native. The reverse is not required.
You cannot design agents well without understanding where intelligence belongs in the product, how the knowledge architecture is assembled, what the engineering organisation can actually sustain, and what the risk appetite is. Agency sits on top of all of that.
But a CTO can be genuinely AI-native — redesigning the product around what models make possible, rebuilding the delivery system, changing how the organisation learns — while deliberately holding back on autonomous action, because the risk profile does not yet justify it.
That is not a gap in their capability. It is a decision, and often the right one.
What this means for hiring
If you are writing the role now, the practical question is which problem is in front of you.
If the organisation has a clear AI strategy, a product direction it believes in, foundations that hold, and a specific set of workflows it wants to delegate to software, then agentic depth is the scarce skill and you should hire for it.
If the organisation has pilots, enthusiasm, a board asking questions and no shared view of where AI creates value, then agency is not the problem. Direction is. Hiring an agent specialist into that situation produces a well-engineered answer to a question nobody has settled.
Most organisations I speak to are in the second position and describing themselves as though they were in the first.
The durable category
Titles follow capability, and capability follows what the business needs over time.
Agentic leadership is one of the most important emerging capabilities in technology, and it will stay important. But it describes a specialisation within a role rather than a replacement for it.
AI-Native CTO is the more durable category, because it names the full accountability: what the company builds, how it is built, who builds it, what it costs, what it risks and what it is worth. Agency is one of the levers inside that mandate, not the mandate itself.
When the current wave of titles settles, that is the distinction I expect to survive.