Telecom companies spent years treating AI as an efficiency layer around customer support and analytics. That changed once carriers began deploying AI inside network operations, infrastructure planning, enterprise products, and service delivery.
The CIO role expanded with it, and many carriers discovered their existing leadership structure was built for a different mandate than the one carriers are running today.
The telecommunications AI-native CIO is not a future hire. Carriers are running these searches now, and the gap between what boards expect and what the candidate market can deliver is wider than most leadership teams anticipate when they open the process.
In many telecom AI-native builder searches, the disconnect appears after boards realize the operational mandate is broader than the role they initially defined.
Why Carriers Are Upgrading the Telecom AI CIO Role
For years, many telecom CIO mandates centered on internal systems transformation. Cloud migration, vendor consolidation, cybersecurity modernization, and enterprise platform upgrades dominated the role. Boards evaluated CIOs on infrastructure reliability and operational discipline.
That scorecard now includes operational AI outcomes alongside those fundamentals.
AI systems are moving into areas that directly affect operational performance at scale. Carriers are already deploying AI in production environments across:
- network optimization
- customer service automation
- field service coordination
- fraud detection
- enterprise AI offerings
- predictive infrastructure maintenance
The CIO increasingly sits at the center of those initiatives because telecom environments run infrastructure where operational data volumes are among the largest of any industry.
Telecom boards are recognizing that AI transformation cannot be isolated inside innovation groups or temporary task forces. The carriers already deploying AI into live operational systems are seeing the gap widen quickly between experimental AI programs and measurable operating impact. The search no longer focuses only on someone who can modernize enterprise IT. The mandate now includes operational AI leadership across systems where downtime and service failures cost money and customers immediately.
I often hear carrier boards describe this as a technology upgrade. The executives who are actually driving results inside these organizations treat it as an operational transformation with technology as the execution vehicle.
The Agentic AI Use Cases Driving Telecom Hiring Decisions
At large carriers, many AI initiatives have already moved from pilots into live operational environments. The use cases driving hiring decisions include:
Network operations
AI systems now identify service degradation patterns before outages occur and automate parts of network optimization. In large telecom environments, small reductions in downtime or maintenance delays affect revenue directly.
Customer support automation
AI agents manage high-frequency support interactions across billing, device activation, connectivity troubleshooting, and enterprise service management, escalating technical problems and reducing pressure on human teams.
Field service coordination
AI-assisted dispatch systems are being used to improve technician routing and maintenance scheduling, reducing operational costs for carriers managing large regional or international networks.
Fraud detection
AI models integrated into real-time detection systems identify account compromise and payment abuse, increasingly important as telecom companies expand digital services and enterprise offerings.
Enterprise AI products
Carriers are building AI-powered offerings for enterprise customers, creating new revenue streams that sit directly inside the CIO's technology mandate.
The CIO is expected to coordinate these efforts across infrastructure, data governance, cybersecurity, and vendor ecosystems simultaneously. Leaders with credible operational AI deployment experience at carrier scale remain hard to find, which is why these searches have become harder to close than boards expect when they open them.
What Carrier AI Appointments Signal to Boards
Recent telecom leadership appointments share a pattern that boards running this search should study closely. The title on the org chart has changed. More importantly, so has the mandate behind it.
AT&T: Andy Markus, Chief Data and AI Officer
AT&T has been unusually transparent about its AI leadership approach. Andy Markus, Chief Data and AI Officer, has made agentic AI the explicit centerpiece of AT&T's technology strategy. His framing is direct: AT&T is moving AI from the information economy into the action economy. Agents, which AT&T calls autonomous assistants, do not just generate content. They plan and execute tasks from beginning to end.
AT&T evaluates all potential agentic AI use cases through the Generative AI Transformation Office, which assesses value for customers and the business before prioritizing deployment. Markus has stated publicly that the result is a two-times return on investment from generative AI initiatives, with free cash flow impact as one of the primary measures of success.
AT&T has been testing and rolling out a network-based, customer-facing agentic AI tool. The digital receptionist is built directly into the network infrastructure, which means it requires no device download and continues to function even when a customer is out of cellular range. AT&T has described it as among the first agentic voice AI tools deployed directly to customers by a carrier.
For boards running a telecom AI CIO search, the AT&T model shows what board-level accountability for agentic AI looks like in practice: public ROI commitments, named deployments, board-level reporting on AI outcomes, and a direct connection between AI investment and operating performance.
Verizon: Mano Mannoochahr, Chief Data, Analytics and AI Officer
Verizon appointed Mano Mannoochahr as Chief Data, Analytics and AI Officer in early 2025. His background spans GE, John Deere, and Travelers, where he led large-scale AI and digital transformation initiatives across industrial, agricultural, financial services, and enterprise technology environments.
Mannoochahr has described cross-functional alignment as beginning with governance structure: a senior AI council he chairs with monthly SVP representation across the business, and below that an operating council handling tactical decisions at the working level.
Verizon's AI strategy runs across three pillars: applied AI for employee productivity and customer experience, AI embedded into products and services, and infrastructure expansion to support the broader AI ecosystem through Verizon AI Connect, announced in January 2025.
Underpinning all three is the One Verizon data program, migrating one of the world's largest datasets to the cloud. Mannoochahr has described the resulting semantic layer as enabling the next decade of analytics and AI capability.
For boards earlier in their AI deployment cycle, the more useful Verizon lesson is governance architecture. The Verizon search followed a path worth noting for boards in a similar position: a leader brought in with broad AI and digital transformation experience across multiple industries, then given the governance authority to drive enterprise-wide transformation.
Deutsche Telekom: Agentic AI in Live Network Operations
Deutsche Telekom offers the most detailed public view of what agentic AI deployment inside live network infrastructure actually looks like in practice. The RAN Guardian Agent, developed in partnership with Google Cloud and launched in November 2025, operates as a multi-agent system that autonomously identifies upcoming public events, assesses network capacity impact, and executes optimization measures, including reallocating mobile resources and adjusting network configurations in real time.
In its first month of operation, RAN Guardian autonomously triggered over 100 remediation actions at Christmas market events across Germany. It has reduced event management time from hours to around one minute, a more than 95% improvement confirmed in Deutsche Telekom's own reporting. For 2026, the system has already identified 237,000 events across Germany, and is now scaling across Deutsche Telekom's European national companies, starting with the Czech Republic and Croatia.
The broader MINDR system, also developed with Google Cloud and announced in February 2026, extends this capability across the full network. MINDR correlates signals across RAN, transport, and core domains to proactively identify service-impacting issues and support autonomous remediation. First production releases are planned for later in 2026.
What the Deutsche Telekom model suggests to me is that agentic AI in telecom network operations has moved from pilot to production infrastructure for the carriers willing to commit to it. My read is that the technology leader who owns this mandate is no longer running experiments. They are operating systems that affect millions of customers in real time.
What Qualifications Boards Are Prioritizing and Why the Pool Is Smaller Than Expected
The telecommunications AI-native CIO search has a qualification profile that differs from the general AI-native CIO definition I outlined in the first article in this series, because operational AI deployment inside carrier infrastructure creates a very different accountability structure. For regional and mid-size carriers, this profile scales accordingly. Smaller operators typically sequence these capabilities across searches, starting with the one or two most critical ones.
Carrier-scale infrastructure experience is where boards cannot afford to compromise. A CIO who cannot engage credibly on network architecture and operational dependencies inside a large carrier environment will not retain the confidence of the engineering and operations organization.
Agentic AI deployment experience is where searches differentiate in 2026. The candidates worth serious consideration have run AI agents in production operational environments and can speak to results that boards recognize: downtime reduction, cost per interaction, fraud prevention rates, and automation ROI. The gap between executives who have managed AI pilots and those who have run production deployments is significant. Interview processes that do not probe this distinction often struggle to separate operational AI experience from pilot-stage exposure.
Data governance fluency has become a specific requirement in telecom. Carriers operate under regulatory frameworks across multiple jurisdictions and enterprise AI products that carry their own compliance obligations. A CIO who cannot build and defend a governance architecture that covers all of those layers is exposed in ways that become visible quickly.
Board communication on AI return on investment closes the evaluation. Carriers are now asking the same question every AI-forward board is asking: where does the AI investment show up in operating margins and customer retention? The telecom AI CIO who can answer that clearly, with specific numbers and a methodology for tracking them, is operating at the level the role now requires.
The market cannot reliably supply all four of those capabilities in one executive. Executives who built careers inside telecom often have the infrastructure knowledge. Most have not led AI deployment at the operational level that the role now requires. Leaders with production agentic AI experience often come from hyperscalers or enterprise software environments where carrier-specific regulatory and infrastructure constraints are absent.
That gap is moving in both directions. Executives who built their careers around infrastructure modernization are actively seeking operational AI deployment experience before these searches open, while AI leaders from hyperscalers and enterprise software companies are pursuing carrier-side roles specifically to close that credibility gap.
Boards that have moved quickly have generally followed one of two paths. Some promote from within telecom, pairing a strong infrastructure leader with a dedicated AI engineering organization reporting into the role. Others look outside the industry entirely, as Verizon did with Mannoochahr, prioritizing AI deployment track record and building carrier-specific knowledge around the new leader through a structured first year.
The searches that stall consistently share the same starting point: the mandate was defined too broadly, and the board discovers which capabilities matter most only after finalist conversations are already underway. Defining which of those capabilities is most critical for the first 18 months, and which can be built through the team, is the work that should happen before the first candidate conversation.
What the Interview Process Needs to Do Differently
The qualification profile above is only useful if the interview process is designed to test it. The most consistent failure I see is boards treating the pilot-versus-production distinction as self-evident. It is not. A candidate who has managed AI pilots presents almost identically to a candidate who has run production deployments. Both present well. The difference only surfaces when you press on specifics.
The question that separates them is not "Tell me about an AI initiative you led." It is: "Tell me about a specific agent deployment that went into production, what broke in the first 90 days, what you had to rebuild, and what the operating outcome looked like six months later." A candidate who has run production AI answers that question with operational detail, degraded data pipelines, retraining cycles, latency thresholds that had to be renegotiated, and escalation paths that did not exist at the pilot stage. Someone who has only run pilots answers it with methodology. They describe the framework and the stakeholder alignment process. The answer is technically accurate, but it tells you nothing about what happened when something went wrong.
Boards that do not probe this distinction consistently mistake sophistication for experience. The candidate who can describe the architecture of an agentic system in detail is not necessarily the candidate who has been accountable when one fails inside a live operational environment. Those are different things, and in a carrier environment, the difference becomes visible quickly.
How Telecom Carriers Are Building AI-Native CIO Succession Pipelines
The most visible change in telecom leadership succession over the past 12 to 18 months is how companies are evaluating pipeline candidates for the CIO role.
Traditional succession models prioritized enterprise systems leadership and operational continuity. Those capabilities still matter. What has changed is the additional layer boards are now looking for: evidence that a succession candidate has already led AI deployment inside operational environments, with measurable results. That includes:
- automation programs tied to measurable efficiency gains
- AI integration across infrastructure systems
- operational data platform development
- enterprise AI commercialization
- workforce restructuring driven by automation deployment
The carriers building the strongest internal pipelines are doing it before the search opens. They are identifying senior technology leaders with direct accountability for live AI deployments and giving them board visibility through quarterly performance reviews. The goal is to have a credible internal candidate ready before external pressure forces the decision.
The boundaries between CIO, CTO, Chief Data Officer, and AI leadership responsibilities are blurring inside some carriers. In several companies, the work has converged to the point where the title matters less than the mandate and who the role reports to. AT&T and Verizon have both resolved this by creating Chief Data and AI Officer roles that sit above the traditional CIO function.
What boards consistently underestimate is the organizational cost of that consolidation. When a Chief Data and AI Officer role is created above an existing CTO or CIO, the incumbent's mandate narrows in ways that are rarely communicated clearly at the time of the announcement. The new title gets the press release. The existing leader gets a revised reporting line and a scope that no longer matches what they were hired to do. In many cases, strong CTOs do not stay long in that position. The reorganization and the retention problem need to be planned in parallel. Boards that treat the new appointment as the only decision and the incumbent relationship as a secondary concern often find themselves running two searches where they expected to run one.
Boards also tend to underestimate how quickly an internal leader who demonstrates operational AI results attracts external interest. Executives who deliver visible AI results at carrier scale attract competing offers from infrastructure providers and other carriers within months of their results becoming public. The same pattern is visible in semiconductor leadership. Retention planning should begin before the appointment. In practice, that means equity structures tied to multi-year deployment milestones and an expanded mandate that gives the executive reasons to stay that a competing offer cannot easily match.
Telecom AI CIO Compensation in 2026
Telecom boards are running these searches with compensation benchmarks that are typically one to two years out of date. That gap does not become visible until a finalist is already deep in the process, which is the worst possible moment to discover it.
According to the Christian & Timbers 2026 Corporate AI Compensation Study, base salary for an AI-native CIO or Chief Data and AI Officer at a public company with 5,000 to 10,000 employees runs between $525,000 and $862,000, with annualized equity ranging from $525,000 to $5.75 million. At companies with 10,000 to 50,000 employees, base salary moves to $551,000 to $1.12 million with annualized equity from $551,000 to $7.475 million.
Large public carriers with more than 50,000 employees sit in the study's highest tier, where base salary for AI-native technology leadership roles commonly runs from $750,000 to $1.35 million with annualized equity from $1.5 million to $12 million.
The study draws on closed offer outcomes from Christian & Timbers searches conducted between Q3 2025 and Q1 2026, across more than 200 CEO, CTO, and board interviews. The figures reflect the 25th to 75th percentile of actual offers.
In telecom specifically, the compensation gap tends to surface at the finalist stage because the search opens with an IT leadership benchmark. By the time the board recognizes the difference, the cost of losing a candidate is measured in months of additional search time and the quarter spent restarting. Full salary ranges and equity benchmarks by company size are available in the 2026 Corporate AI Compensation Study.
The Search That Defines the Next Operating Cycle
Carriers that have already deployed agentic AI in network operations and customer automation are pulling further ahead every quarter. The CIO who owns that mandate is now one of the most consequential operational AI roles in the industry, and most boards underestimate how little time they have when they open the process.
Most searches that go slowly start with a mandate that was defined too broadly and a compensation benchmark that reflected the role as it existed two years ago. When the board expects one executive to carry deep telecom infrastructure credibility, production AI deployment experience, data governance authority, and enterprise transformation leadership simultaneously, the process runs longer than planned and often ends in a compromise hire.
The situation usually develops in one of two ways. The first is a strong infrastructure leader who cannot credibly own the AI deployment mandate. The engineering organization trusts them, but the board loses confidence within the first year when AI initiatives stall or remain in pilot indefinitely. The second is a strong AI leader who cannot retain the authority of the infrastructure organization. The strategy is credible, but execution breaks down because the operational teams do not extend trust to someone who cannot engage with what failure at carrier scale actually costs.
In both cases, the board typically runs a second search within 18 to 24 months, often following a visible reorganization or a leadership departure that makes the original hire's limits public. The cost is not the second search. It is the 18 months of lost ground that is hard to recover while the organization waits for clarity on who is actually accountable.
By the time both problems become visible, the candidates who could close the gap are already deep in other processes.
Boards that define the mandate before the first candidate conversation, and calibrate compensation before the first finalist conversation, move faster and make better hires. In telecommunications, that preparation is often the difference between a search that closes in six months and one that bleeds into the following year.
If your board is working through this decision, the AI Native C-Suite Search practice at Christian & Timbers is a good place to start. And if compensation is where the conversation needs grounding first, the 2026 Corporate AI Compensation Study gives you the current benchmarks before you open the search.
FAQ
- What is a telecom AI-native CIO?
A telecommunications AI-native CIO is a technology leader whose mandate explicitly includes operational AI deployment across network operations, customer automation, data governance, and enterprise AI products, in addition to traditional infrastructure and systems responsibilities. The role is measured through operating outcomes, including downtime reduction and automation ROI.
- What agent use cases are driving telecom CIO hiring in 2026?
Network optimization agents, customer support automation, field service coordination, fraud detection, and enterprise AI product development are the primary areas where carriers are deploying agentic AI in production today. These use cases are reshaping what boards expect from the CIO role and what candidates need to demonstrate.
- How can boards tell the difference between AI pilot experience and production deployment experience?
Executives who have managed AI pilots often describe frameworks and rollout methodology clearly. Leaders who have run production AI deployments speak differently. They can explain what failed after deployment, which operational metrics changed, what had to be rebuilt, and how the organization adjusted once the system moved into live production. In telecom environments, that distinction surfaces quickly when the interview moves from strategy to operational outcomes.
- What happens to the CTO role when carriers create a Chief Data and AI Officer position?
When a Chief Data and AI Officer role is layered above an existing CTO or CIO structure, the incumbent leader's mandate often narrows significantly even when that change is not communicated directly at the time of the announcement. Strong CTOs frequently leave when operational authority shifts away from their organization. Boards that separate AI leadership from infrastructure leadership without planning the retention implications often end up running additional executive searches sooner than expected.
- What does compensation look like for a telecom AI-native CIO?
At large public carriers with more than 50,000 employees, base salary for AI-native technology leadership roles commonly runs from $750,000 to $1.35 million with annualized equity from $1.5 million to $12 million. Full benchmarks by company size are available in the 2026 Corporate AI Compensation Study.