Blog

AI fluency hiring: how to tell who steers AI from who just uses it

Everyone lists "proficient in AI tools". Almost nobody can show you what that means. Here's you can.

Victor EduohFounder, Laand9 min read
Claude Code running a candidate's submission and finding weak spots

Two engineers submit a solution to the same problem. Both used Claude. Both solutions pass the tests. The code is about the same length.

The first engineer's chat history is three messages long: the brief, pasted in; "make the tests pass"; "thanks".

The second's is twenty-two messages. She asks the agent to explain the existing retry logic before touching it. She rejects its first approach because it would hammer a rate-limited API. She catches that it invented a config option that doesn't exist. She asks it to write three extra tests for the edge case she's worried about. Then she rewrites the README herself, because the agent's version oversold what the code does.

Both of them would tick "proficient with AI tools" on an application. Only one of them is AI fluent.

What AI fluency actually means

AI fluency is the ability to produce better work, faster, by directing AI systems, while keeping responsibility for quality and judgment.

It is not:

  • Knowing tool names. Tools change every quarter.
  • Prompt tricks. Clever phrasing matters far less than context and checking.
  • Using AI a lot. Volume of use says nothing about quality of judgment.

It is a combination of four things:

  1. Delegation: knowing what to hand to an agent and what to keep.
  2. Direction: giving the agent the context, constraints and examples it needs.
  3. Verification: checking the output, catching errors and hallucinations, testing assumptions.
  4. Ownership: taking responsibility for the result, including what the agent got wrong.

The four levels of AI fluency

LevelNameWhat it looks likeHire for it?
1AvoiderDoesn't use AI, or only for trivial tasksRarely, on an AI-native team
2UserPastes tasks in, ships the outputRisky: fast, but errors ship too
3CollaboratorIterates with AI, checks major outputsGood for most roles
4SteererDesigns the work around AI, verifies rigorously, catches subtle errors, owns the outcomeThe people who move milestones

Level 2 is the dangerous one. It looks productive, and in a demo it can look like level 4. The difference only shows when something's subtly wrong.

Why AI fluency is now the core hiring question

On an AI-native team, agents do the first draft of almost everything. That changes the shape of every role. The scarce skill isn't producing output; it's judgment over output.

You can see the market shifting. In October 2026, the Laand Hiring Index found AI & ML Engineering roles growing 28% month on month, second only to Product Marketing.

Laand Hiring Index, October 2026: growing fastest: Product Marketing +40%, AI & ML Engineering +28%, Sales Development +22%, Legal +11%; cooling: Product Management −31%, Customer Success −25%, Solutions & Sales Engineering −19%, Finance −16%. New roles, like-for-like boards.
Laand Hiring Index, October 2026: growing fastest: Product Marketing +40%, AI & ML Engineering +28%, Sales Development +22%, Legal +11%; cooling: Product Management −31%, Customer Success −25%, Solutions & Sales Engineering −19%, Finance −16%. New roles, like-for-like boards.

But AI fluency matters far beyond AI roles. A growth marketer who can't tell good AI copy from generic AI copy will flood your channels with sameness. An operations lead who trusts an agent's spreadsheet without checking will make decisions on invented numbers.

How to test for AI fluency

Don't: ban AI in your assessment

A no-AI test measures a level-1 skill. Unless you specifically need to see an unassisted skill, banning AI tests a job nobody on your team does.

Don't: ask "which AI tools do you use?"

The answer tells you their tool list, not their judgment.

Do: let them use AI on real work, and ask for the chats

Give a short, paid piece of your real work. Ask candidates to share the public links to the AI chats they used, or to say they didn't use AI. Then read the chats.

What to look for:

SignalLevel 2 (User)Level 4 (Steerer)
First messageBrief pasted inContext, constraints, what good looks like
When the agent is wrongDoesn't noticeCatches it, says why, redirects
VerificationNoneAsks for tests, checks sources, sanity-checks numbers
EditsShips first outputRewrites the parts that matter
Ownership"The AI did this""I chose this, and here's why"

Do: plant a mistake

Put one wrong number or broken assumption in the brief. A level-2 user feeds it to the agent and ships it. A level-4 steerer catches it, often before the agent sees it.

Do: ask about the chats in the interview

"At message eight, you rejected the agent's approach. Why? What would have happened if you'd accepted it?" Fluent people light up. Others get vague.

AI fluency interview questions

  1. Walk me through a time an AI tool gave you something that looked right and wasn't. How did you catch it?
  2. What do you never delegate to an agent? Why?
  3. How do you decide when AI output is good enough?
  4. Show me a chat where you changed the agent's mind. What was the turning point?
  5. "Here's an AI-generated analysis of our churn. What would you check first?"
  6. Which parts of this role would you hand to agents in week one?

How Laand tests AI fluency

Laand treats AI fluency as a first-class signal in every Talent Hunt.

AI is allowed, per project, and visible. In each paid micro-project, candidates share the public links to the chats they used, or state they didn't use AI. You can switch AI off for a specific project when you need to see a skill unassisted.

An AI agent listing a hunt's micro-projects, turning AI off on one, and adding the team's own from a sentence
An AI agent listing a hunt's micro-projects, turning AI off on one, and adding the team's own from a sentence

Every brief has a planted mistake. It's the cleanest test of verification there is.

Laand scores how they worked with AI, not just the work. Each review includes an AI-collaboration score alongside the work score, so you can tell a steerer from a user even when the outputs look similar.

What Laand shows instead of a cover letter: the submitted work, a score, the remaining gaps, and interview questions about it
What Laand shows instead of a cover letter: the submitted work, a score, the remaining gaps, and interview questions about it

Your own agents can dig in. Ask Claude Code or Codex to run a finalist's submission and find its weak spots, or ask Claude which candidates' work is strongest.

Claude Code running a candidate's submission and finding weak spots
Claude Code running a candidate's submission and finding weak spots

And the whole hire runs through your own AI. Start the hunt in Claude or Slack, review in your agent, decide in a Slack channel, unlock at $750 per talent unlocked. Publishing is free.

Before you hire for AI fluency, check your own

The best way to evaluate AI fluency is to have it. If your team doesn't use agents seriously, you'll struggle to tell level 2 from level 4.

Laand starts every hunt with hire or agent?: which parts of the role agents can already do, and which a person must own. If you find most of the role is agent work, the fluency you need might be a level-4 steerer to run those agents, not three level-2 users.

An AI agent starting a Talent Hunt: Laand's answer to hire or agent, what a person must own and what agents can already do, and what's still needed
An AI agent starting a Talent Hunt: Laand's answer to hire or agent, what a person must own and what agents can already do, and what's still needed

A founder who works this way

Sokari Gillis-Harry, founder of Roofteller, runs his company through AI:

Sokari Gillis-Harry, CEO & Co-founder of Roofteller: “Jumping into another tool to do hiring was more like giving me more work, and I wanted to just focus on building.” Watch his 2-minute story.
Sokari Gillis-Harry, CEO & Co-founder of Roofteller: “Jumping into another tool to do hiring was more like giving me more work, and I wanted to just focus on building.” Watch his 2-minute story.

AI fluency by role

AI fluency looks different in each function. Here's what level 4 (the steerer) looks like across the roles startups hire most.

RoleLevel 2: UserLevel 4: Steerer
Software engineerAccepts the agent's code if the tests passReads the diff, rejects invented APIs, adds tests for edge cases the agent missed
Forward-deployed engineerUses AI to write integration codeUses AI to map the customer's system, then decides what to build and what to push back on
Growth marketerShips AI copy with light editsUses AI for variants and research, throws away the generic ones, writes the line only your company could say
Product marketerGenerates positioning docsUses AI to synthesise call notes, then makes the positioning call and defends it
Operations leadTrusts the agent's spreadsheetSanity-checks totals, traces odd numbers to source, sets up agents to monitor and escalate
DesignerGenerates mockupsUses AI to explore widely, then cuts to one direction with clear reasons
Founder's associateSummarises everything with AIDecides what's worth summarising, and spots what the summary left out

The pattern is the same everywhere: the steerer uses AI to go wider and faster, then applies judgment to go narrower and better.

A worked example: scoring two submissions

Picture a growth marketer micro-project: diagnose the biggest drop-off in the trial funnel and draft three emails to fix it. The brief claims most trials come from paid search. The data says most come from a partner integration.

Candidate A pastes the brief and the CSV into an AI chat, asks for an analysis and three emails, asks for the emails to be "punchier", and submits. The emails are well written and aimed at paid-search trials. The planted mistake ships.

Candidate B asks the AI to summarise trial sources before anything else, notices the mismatch, and writes in her submission: "The brief says paid search; the data says 61% of trials come from the integration. I've built the sequence for integration-led trials." Her chat shows her rejecting two of the AI's email drafts as "could be any SaaS company" and rewriting the subject lines herself.

CriterionCandidate ACandidate B
Solves the problem24
Judgment and trade-offs24
Caught the planted mistake14
AI collaboration24

Both "used AI". Only one is AI fluent. You'd never have seen the difference on their CVs.

Common mistakes when hiring for AI fluency

  1. Asking about tools instead of judgment. Tool lists go stale; judgment doesn't.
  2. Rewarding speed alone. The fastest submission is often the least checked.
  3. Ignoring the chat links. The process is the evidence.
  4. Testing fluency only for technical roles. Your marketers and operators use AI as much as your engineers.
  5. Hiring fluency your team can't recognise. If nobody on your team works this way, start by using agents seriously yourself.

Key takeaways

  • AI fluency is judgment through AI: delegation, direction, verification and ownership.
  • Level 2 users and level 4 steerers can produce similar output; only their process differs.
  • Allow AI in assessments, ask for the chat links and plant a mistake.
  • AI fluency matters in every function, not just engineering.
  • Laand scores how candidates worked with AI alongside the work itself.

Frequently asked questions

What is AI fluency?

The judgment to get excellent results through AI: deciding what to delegate, giving agents the right context, checking and correcting their output, and owning the outcome.

How do you assess AI fluency in candidates?

Let them use AI on a short, paid piece of real work, ask for the public links to their AI chats, plant a mistake in the brief, and score how they directed and checked the AI, not just the final output.

Should AI be allowed in job assessments?

For most roles on an AI-native team, yes. Allowing it, and making it visible, is the only way to see AI fluency. Turn it off only for a specific skill you need to see unassisted.

What's the difference between using AI and being AI fluent?

Using AI is producing output with it. AI fluency is the judgment around it: knowing what to ask for, catching what's wrong and taking responsibility for the result.

Is AI fluency only important for technical roles?

No. Marketers, operators, salespeople and analysts all work through AI now. Fluency decides whether their output is distinctive or generic.

Keep reading

Or start a Talent Hunt and see how candidates steer AI before you meet them.

AI fluencyAI skillshiring for AI skillsAI-native hiringassessment

Stop applying blind.

Laand scores your fit for any role, then builds the application kit that proves you can do the job.

Join Laand

See how candidates steer AI

Laand's paid micro-projects let candidates use AI and share their chats, then score how they worked with it. Free to publish; $750 per talent you unlock.

Start a Talent Hunt