Which AI Tools to Name on Your CV in 2026

Forbes reported this week that Claude has become the enterprise favourite, with Anthropic passing OpenAI in the corporate market. For job seekers, this is more than a tech-industry horse race. It is a signal that the AI tools worth naming on your CV are shifting, and the wrong choices can make your CV look dated.

Naming AI tools well is a surprisingly delicate skill. List the wrong ones and you look like you are chasing last year's hype. List them clumsily and you look like you are keyword-stuffing. Get it right and you signal that you are current, credible, and genuinely working with these tools.

In the 2025 Stack Overflow Developer Survey, ChatGPT led adoption at 82% and GitHub Copilot at 68%. But enterprise preferences move faster than survey cycles, which is exactly why naming tools on a CV needs care.

---

Why Tool Names Date So Fast

AI tools rise and fall on a quarterly cycle. The model that dominated enterprise last year may be an also-ran this year. A CV that leans too hard on a specific tool name risks looking out of date the moment the market shifts, which it does constantly.

The Claude-over-OpenAI enterprise shift is a perfect example. A candidate whose CV proudly named one specific assistant as their headline AI skill would suddenly look behind, through no change in their actual ability. The lesson is to name tools as evidence of capability, not as the capability itself.

The principle: capability first, tool as evidence

• Lead with what you can do, not which tool you used
• Name specific tools as proof, not as the headline
• Keep the named tools current, and refresh them regularly
• Show breadth of approach, not loyalty to one product

Key Takeaway: Name tools to prove a capability, never as the capability itself. Tools date. Capabilities do not.

---

Which AI Tools Are Worth Naming in 2026

If a tool genuinely reflects how you work, naming it helps with both ATS matching and human credibility. These are the categories currently worth referencing in UK white-collar roles, with the caveat that you should only name what you actually use.

Category	Why it signals currency
General assistants (Claude, ChatGPT, Gemini)	Name the one you use most, not all three
Coding (Copilot, Cursor)	For technical roles, still a strong signal
Research (Perplexity)	For analysis and knowledge work
Meetings and notes (Granola, Notion AI)	For knowledge and operations roles
Creative (Midjourney, Runway)	For design and marketing roles

Naming two or three that you genuinely use beats naming eight you have barely touched. A long list reads as performative. A short, specific one reads as real.

---

How to Phrase It

The phrasing is where most candidates go wrong. They either list tools with no context, or they bury the capability under the brand name.

Weak: "Skilled in ChatGPT, Claude, Gemini, Copilot, Perplexity, Midjourney, Notion AI."

Strong: "Built an AI-assisted research and drafting workflow using Claude and Perplexity, cutting report turnaround from three days to one while maintaining a manual fact-check step."

The strong version, illustrative as it is, names two specific tools as evidence of a real workflow with a real outcome. If the market shifts and you swap a tool, the capability and the result still stand.

Key Takeaway: A CV that names two tools inside a real workflow ages far better than one that lists eight tools with no context.

---

The Enterprise Context Matters

The Claude enterprise story carries a specific lesson for candidates targeting larger organisations. Enterprises increasingly care about which tools are approved, governed, and safe, not just which are powerful. Showing awareness of enterprise AI governance is itself a signal.

If you have worked within an organisation's approved AI tooling, named the governance you operated under, or helped shape an AI usage policy, that is worth surfacing for enterprise roles. It says you understand that in a big company, the question is not just "can this tool do it" but "are we allowed to use it, and how."

---

What to Avoid

1. Tool loyalty. Pinning your CV to one product makes you look dated when the market moves
2. The kitchen-sink list. Eight tools with no context reads as keyword-stuffing
3. Naming tools you do not use. It collapses in the first interview question
4. Leading with the brand. The capability should come first, the tool second

---

The Contrarian Insight

Most candidates treat naming AI tools as a way to look current. Done badly, it does the opposite. The market moves so fast that a tool-heavy CV is almost guaranteed to look dated within a year.

The candidates who stay current are the ones who lead with durable capabilities and treat tool names as interchangeable evidence. When Claude overtakes the field this year and something else overtakes it next year, their CV barely needs to change, because the capability was always the headline.

The tool you name will be outdated within a year. The capability you prove will not. Write the CV that leads with the second.

---

Your CV Refresh

1. Find every place your CV names an AI tool and check it still reflects how you work
2. Reframe each so the capability leads and the tool is evidence
3. Cut any tool you do not genuinely use
4. For enterprise roles, add a line on AI governance awareness if you have it
5. Run the result through CVPilot to confirm the AI phrasing matches current expectations

The Claude enterprise shift is a reminder that AI tool leadership changes constantly. Write your CV so it survives the next shift, and the one after that, by leading with what you can do rather than which product you happened to use.

Ready to future-proof how your CV names AI tools? Try CVPilot free and see your ATS score in under 60 seconds.