I've been reading CDO job descriptions over the past month. Two things stand out.
The first is that almost every one of them is written for the role as it existed in 2022. Manage a team of analysts and engineers, own the data platform roadmap, partner with business stakeholders, deliver insights at the speed of the business, build a data-driven culture.
The second is that the companies hiring against these descriptions are, in some cases, in the middle of agentic AI pilots whose success or failure will define the next three years of their data strategy. The job description and the actual job have come unstuck from each other, and almost nobody is talking about it.
The Chief Data Officer of 2026 is shifting from manager-of-engineers to designer-of-human-agent systems. The skills that defined the role for the last decade (running a data team, defending budget, delivering reliable BI) are not going away, but they are no longer what distinguishes a strong CDO from a weak one. What distinguishes them now is whether they can architect the layer where humans and agents work on data together, and whether they can lead an organization through the operating-model changes that requires.
Most current job descriptions don't reflect this. Most current CDOs aren't visibly being measured on it either. That gap is going to close, fast, and the leaders who get ahead of it will be operating from a sharper position than the ones who don't.
Which CDO skills are depreciating
Running a large data team as a headcount-growth exercise. The era of "I built a 10-person data org" as the headline credential is ending. A 10-person team is increasingly evidence that the leader scaled humans into work that agents were already absorbing.
Owning a BI roadmap. Tableau-and-Power-BI strategy was the spine of a CDO's first hundred days for fifteen years. It is now closer to a hygiene activity than a strategic one.
Defending data team budget against finance. Always a survival skill, but historically the budget defense was about more people, more tools, more dashboards. The new budget defense is about a fundamentally different shape of investment, and the rhetorical playbook has not caught up.
These don't disappear from the job. They just stop being the things that make a CDO valuable.
Which CDO skills are appreciating
Operating-model design. What does the data function look like when most routine analytic work runs through agents? Who owns the agent reliability layer? Where does evaluation infrastructure sit in your org chart? These are questions a CDO must now answer concretely, not in slides.
Vendor judgment under uncertainty. Every major data and AI vendor is currently positioning themselves as "the intelligence layer." A CDO who can map that landscape, see which vendor offers what component, and refuse to let any single vendor define the architecture is worth orders of magnitude more than one who buys the slickest demo.
Strategic narrative. CEOs and boards are asking "what's our AI strategy" and getting answers that mostly describe pilots. A CDO who can reframe the question as "what's our intelligence layer strategy" and articulate the architectural commitment underneath it changes the conversation. That reframing is increasingly a leadership skill, not a technical one.
Change leadership. The data team of 2027 will be smaller, sharper, and structurally different from the team of 2024. Leading an organization through that transition, including the human cost of it, is the skill that separates the CDOs who navigate this from the ones who get navigated past.
Why this isn't being talked about
A widely circulated LinkedIn analysis of Chief Data and Analytics Officers found average tenure under three years, one of the shortest in the C-suite. That short tenure has a hidden effect: CDOs are typically too busy proving the existing role to redesign it. The people best-positioned to see what the role is becoming are the ones least able to publicly acknowledge it, because they're still being measured on the old definition.
If you're a CDO reading this, the practical move isn't to rewrite your own job description tomorrow. It's to start being measurably good at the appreciating skills before your board figures out that's what they should have been asking for all along. The ones who do this become the obvious choice for the next role. The ones who don't end up explaining why they "didn't see it coming."
If you're hiring a CDO, the practical move is to stop posting job descriptions written for 2022 candidates. Hire for the operating-model and architectural-judgment skills explicitly. The talent pool that matches the new description is small. It will grow. The leaders who get into it first will have outsized leverage for the next decade.
If this resonates, subscribe. And forward it to whoever is hiring a CDO right now.
I'm thinking about this transition from both sides at the moment, talking with leaders building toward it from inside their orgs, and open to fractional and full-time conversations about helping organizations make the shift. If that's useful, my inbox is open (kyle[dot]langham[at]gmail[dot]com).
— Kyle