AI fluency in an interview is a hiring signal about how a candidate talks about using AI — their toolkit, learning agility, and how they would redesign work with agents — usually judged in conversation (sometimes after an AI “candidate coach” helped them prep). Proof they can do the job is a role-specific task whose output a hiring manager can open, read, and defend in a debrief (a work sample or job simulation). Fluency answers “can they discuss working with AI?” It does not prove “this person can do this job on day one.”
That split sharpened on 4 Oct 2026. Financial Express reported Salesforce EVP of Global Talent Acquisition Suzana DelliSanti describing an AI-powered candidate coach that prep candidates for interviews, plus a hiring bar that looks at AI fluency across levels — including how candidates use AI to redesign their roles. Engineering candidates increasingly show what they have built (including open-source), and Salesforce tracks internal AI adoption and fluency on a dashboard; executives are expected to build agents as part of learning. That is a serious enterprise posture on AI-native work habits. It is still not the same as opening a JD-native work sample for the role you are hiring. Schmidt and Hunter’s classic meta-analysis (Psychological Bulletin, 1998) estimated work-sample tests at about .54 predictive validity for job performance, while years of job experience sat near .18 and years of education near .10. An interview answer about prompting habits sits closer to talk about tools than to that openable sample.
This guide is for TA and hiring managers who hear “they showed strong AI fluency” or “the candidate coach prepped them well” and wonder whether they still need a job task before panel time. It separates prep chatbots, fluency bars, and conversational screens from hire-time proof, and shows where Dotof AI Role-Simulation Assessments fit: after you hear how they use AI, prove day-one work before you spend scarce interviews. Related (not rewrites): AI lookalike application floods vs work sample, AI sourcing agent vs work sample, AI authenticity checks vs work sample, and AI interviewer vs job simulation.
What does an AI fluency interview actually deliver?
It delivers a conversation signal — how the candidate describes their AI toolkit, where they would apply agents, what they have learned from using them, and (for technical seats) projects or open-source work they can point to. Inputs are interview questions, sometimes a prep coach that answers process questions candidates will not ask a recruiter, and a human or AI rater listening for fluency language. The output is an advance/hold judgment about whether this person sounds ready to work alongside AI. That is valuable when every role is being redesigned with agents. It is not a triage note they wrote on this req, a customer reply they drafted, a ranked backlog they built, or an incident write-up a manager can open in a hire debrief.
Treat fluency as a competency conversation, not a capability sample. Celebrate candidates who can redesign work with AI. Do not import a polished fluency monologue — or a coach-prepped interview transcript — into a new-hire debrief as proof that Candidate A can ship this job’s day-one work.
Why isn’t “they sound AI-fluent” enough at hire time?
Because the hiring manager’s job in a debrief is to open evidence of work on this req — not proof that the candidate can narrate AI usage. Fluency answers “how do they talk about tools and redesign?” A work sample answers “what would this person produce next week?” Managers defend shortlists to peers with the second answer. A candidate can ace the fluency bar after a candidate coach and still leave the interview packet empty of role output. When the only artifacts are a prep-chatbot transcript and a fluent walkthrough of Agentforce-style habits, the panel rediscovers capability live — which is the expensive screen fluency hiring was never meant to replace.
The shelf also mixes different products under one “AI already handled them” story. Lookalike floods are the inbound volume problem. Sourcing agents find and engage. Authenticity or ID checks ask who is in the seat. Conversational AI interviewers book calendar-free talk. Fluency bars ask how candidates use AI. All can be useful. None answer “can they do the work?” until someone opens a role-specific sample. Salesforce’s own engineering tilt toward showing what candidates have built is the useful half of the story — openable artifacts, not only fluency talk.
When should HR use a work sample instead of (or after) an AI fluency interview?
- Use fluency screens when every role is expected to work with agents, learning agility is a stated bar, or you need a consistent way to ask “how do you use AI?” Keep a human owner on who advances and a clear appeal path when the model over-weights polished tool talk.
- Add proof before panel time once candidates are in-funnel and the role has observable day-one deliverables, a wrong hire is costly, or managers refuse to interview without something they can open. Generate the task from the live JD — see from job description to role simulation.
- Prefer the sample over the fluency monologue as the hire gate for professional roles where “can they do the work?” is the question you cannot afford to get wrong. Use fluency to decide who enters the sample; use the sample to decide who advances to offer.
Do not ask the simulation to answer pure fluency questions (“how would you redesign this role with agents?”) — keep that conversation in the interview layer. Pair integrity controls so the sample itself is trustworthy; see how to prevent AI cheating in hiring assessments. Keep a written human override: no coach transcript or fluency score should be the only hire vote. The practical gates are in the responsible AI hiring checklist.
Which should we buy for skills-based hiring in 2026 — an AI fluency interview or a work sample?
Buy both for different jobs — or at least do not let fluency talk replace the sample. An AI fluency interview (with or without a candidate coach) is a selection conversation: learn how candidates use AI and whether they can redesign work. A work sample is a selection purchase of a different kind: openable evidence before panel hours. If your buyer question is “what should TA use instead of ranking AI-fluent interview answers?”, start with the artifact managers will open in a debrief — then layer fluency questions so you know who will thrive with agents. That is the answer to “AI fluency interview vs job simulation”: hear how they use AI, then prove the work. See also AI interviewer vs job simulation (talk ≠ sample) and the anatomy of a useful AI assessment report for hiring managers.
How does Dotof fit this decision?
Dotof AI Role-Simulation Assessments start from the job description, generate a realistic task, run it in a supervised browser, and return structured evidence hiring managers can compare. Use fluency interviews and candidate coaches if you need to learn how people work with AI — or as a soft prior on who enters the sample. Use the simulation when the decision you cannot afford to get wrong is whether this candidate can do the job. AI fluency and job-task proof can coexist — they should not be confused.