The Job You're Hiring For Today Won't Exist in Six Months

AI is changing how some roles are performed. Hiring teams should evaluate the work candidates can demonstrate with AI tools and review whether existing job descriptions still reflect the role.

Three Things That Happened This Week

I have been in recruitment for a while now, and recruiter years feel similar to dog years. Every one feels like seven. I have never seen a landscape shift this fast.

This week alone:

AI tools increasingly support work inside collaboration and development environments. Assess specific capabilities and access requirements against the provider's current documentation rather than assuming every announcement is generally available.

Z.ai dropped GLM-5.2. A Chinese lab most people haven't heard of released an open-source model with agentic capabilities matching Anthropic's top tier. Stanford's AI Index says the quality gap between Chinese and US models has nearly disappeared. A year ago that sentence would have been laughable.

The "tokenmaxxing" debate hit a wall. Uber burned through its entire 2026 AI budget in four months. An Nvidia VP admitted compute now costs more than the employees using it. Jensen Huang suggested giving engineers AI token allowances worth half their base salary. JPMorgan published a note saying AI token costs are eating internet profits alive.

What This Means for Hiring

Every role description you read today will look different in six months. Not because the titles change. Because the expectations of what one person can do with the right tools will be unrecognisable.

Think about three roles most Australian recruitment agencies fill regularly:

The Implementation Consultant who can configure a platform AND prompt an AI agent to handle the data migration validation in parallel. That person is worth twice the one who can only do it manually. The hiring manager who writes a job spec asking for "3-5 years of implementation experience" without mentioning AI fluency is screening out the best candidates before they apply.

The Sales Engineer who can demo the product AND build a custom proof of concept using Claude Code on the call. That person closes deals the old version of the role never could. They are not just technically competent — they are showing the buyer what their own team could do with the same tools. That is a different calibre of SE entirely.

The CSM who runs a 200-account book because they have automated the health scoring, the renewal alerts, and half the QBR prep. They are not replacing their team. They are doing what three people used to do. And the companies that recognise this are restructuring their CS orgs around fewer, better-equipped people rather than adding headcount.

The AI-fluent Operator

This is the bit that most hiring managers have not caught up with yet.

Some candidates use AI tools daily in production. Ask for examples of what they delivered, how they checked the output and where human judgement remained necessary.

The mismatch creates a real problem for recruiters. You are presenting candidates whose capabilities exceed what the job spec describes. The hiring manager sees a CV that matches the written requirements. They do not see that this person has spent the last six months building AI-augmented workflows that make them materially more productive than anyone else they are interviewing.

AI-fluent candidates may value teams that understand their tools and working methods. Discuss expectations directly instead of assuming a universal productivity multiplier or salary premium.

Two Gaps That Are Opening

The gap between companies that hire for AI-native talent and companies that hire for headcount is going to be massive by the end of this year.

Companies in the first camp are rewriting job specs to include AI fluency as a core competency, not a "nice to have." They are asking candidates about their AI workflows in interviews. They are providing token budgets and tool access as part of the compensation package. They are measuring output, not hours.

Companies in the second camp are still writing job descriptions that ask for "proficiency in Microsoft Office." They are hiring for headcount because that is how they have always scaled. They will hire three people to do what one AI-fluent person could do, and they will wonder why their competitor's team of five is outperforming their team of fifteen.

The second gap is between candidates. The ones building their AI fluency now — learning to prompt, learning to build agents, learning to integrate AI into their daily work — are compounding their advantage every week. The ones waiting to be trained by their employer are falling further behind with every month that passes.

That second gap is already here. It is visible in every placement process where one candidate talks about their AI workflow and another asks "do you use AI here?"

What This Means for Recruiters

If you recruit commercial and delivery roles in tech, SaaS, or any AI-adjacent sector, here is what to think about:

Rewrite how you qualify candidates. "Tell me about your AI workflow" should be a standard interview question. Not "are you open to AI?" — that is a 2024 question. Ask what tools they use, how they use them, and what they can do now that they could not do a year ago. The answer tells you more about their trajectory than five years of employment history.

Educate your clients. Most hiring managers have not connected the dots between AI capability and role output. When you present a candidate who runs a 200-account book solo, explain WHY they can do that. Frame it as a competitive advantage, not an anomaly. The hiring manager who understands this will pay for it. The one who does not will lose the candidate to someone who does.

Rethink your own operations. The same dynamic applies to your desk. The recruiter who uses AI to research companies, generate call prep, draft outreach, and automate pipeline management is covering more market than the recruiter who does everything manually. This is not theoretical. It is happening right now in agencies across Australia.

Watch the compensation bands. Compare current roles, scope, location and demonstrated skills. This article does not establish a measured salary premium for AI-fluent talent.

The Role Will Still Exist

Implementation Consultants, Sales Engineers, Customer Success Managers — these roles are not disappearing. The demand for them is as strong as it has ever been. What is changing is the definition of "good" in each of them.

Good used to mean experienced, reliable, and technically competent. Good now means all of that plus the ability to leverage AI to multiply your output. The baseline has shifted, and it shifted faster than anyone expected.

The job you are hiring for today will not exist in six months. The role will. The job won't. The question is whether you are hiring the person who can do the job as it exists today, or the person who can do the job as it will exist in six months.

The best candidates have already made that choice for you. They are the ones who will not accept a role that does not match where they are going.

Frequently Asked Questions