- Stage one: the job ad. AI helps a lot, used carefully
- Stage two: sourcing. AI helps if you watch the data sources
- Stage three: screening. The stage where AI most often makes things worse
- Stage four: interviewing. AI helps with prep, not assessment
- Stage five: offer and onboarding. AI helps a lot, with a guardrail
- What HR should walk away with
Thereâs a counterintuitive finding shaping HRâs relationship with AI in 2026, and most hiring teams havenât fully reckoned with it yet. SHRMâs 2025 Talent Trends reports that AI adoption in HR jumped from 26% to 43% year over year, with 64% of AI-using HR teams using it for recruiting, interviewing, or hiring. Across that same period, both cost-per-hire and time-to-hire have increased.
Two things are happening simultaneously. Candidates are using AI to mass-apply. Recruiters are using AI to screen. The funnel volume is up, the per-hire cost is up, and the hiring quality (where it can be measured) is roughly flat. The teams pulling ahead arenât applying AI to every stage, theyâre being deliberate about which stages it helps and which stages it actively makes worse.
Hereâs the five-stage hiring funnel and what AI should and shouldnât do at each.
Stage one: the job ad. AI helps a lot, used carefully
This is the stage with the biggest payoff and the lowest risk. A well-written job ad attracts the right candidates and repels the wrong ones, which makes everything downstream easier. AI is genuinely good at job-ad rewriting because the work is largely linguistic.
âYou are an experienced talent partner reviewing the attached job ad for the [JOB TITLE] role at [COMPANY] in [LOCATION]. Rewrite the ad with these constraints: (1) Keep the responsibilities and requirements unchanged unless theyâre vague (e.g. âstrong communication skillsâ), in which case reword them as observable behaviours, (2) flag any ârequirementsâ that are likely preferences in disguise (specific years of experience, specific tool names) and suggest broader phrasings, (3) check the language for terms shown to deter qualified women or older candidates from applying (ârockstarâ, âaggressiveâ, âdigital nativeâ, etc.) and replace them, (4) write the first 80 words to focus on what the candidate will get to do in the role, not what the company is, (5) add one sentence near the end explicitly inviting career changers and returners with relevant adjacent experience. Output the rewritten ad and a short bullet list of the changes you made and why.â
Run this through ChatGPT or Claude. The before-and-after comparison is the single highest-yield AI exercise an HR team can run, and the change to inbound applicant quality is usually visible within a week.
Stage two: sourcing. AI helps if you watch the data sources
Sourcing is where AI tooling has matured fastest. hireEZ, LinkedIn Recruiterâs AI features, and the AI inside Greenhouse and Lever all surface candidates from public profile data with a citation back to the source. Used well, these cut sourcing time meaningfully.
The risk is in the criteria you give the tool. Vague criteria (âsenior engineers in fintechâ) produce noisy, biased lists. Specific criteria tied to public profile evidence (âworked on payment systems handling [VOLUME] in the last 24 monthsâ) produce sharper lists. The work isnât in finding a smarter sourcing AI, itâs in writing better source criteria, the same problem you had with Boolean searches a decade ago, dressed differently.
Stage three: screening. The stage where AI most often makes things worse
This is the one to be careful with. Screening is the stage where youâre filtering thousands of applicants down to dozens, and the cost of a bad filter is invisible (you never see who you wrongly rejected) but real.
The mistake to avoid: pasting in 200 resumes and asking for âthe best fit.â That produces a confident ranking with no transparency about what was scored, no auditable trail, and no defence if a candidate (or a regulator) asks how decisions were made.
The defensible version is structured rubric scoring. Build a four-criterion rubric for the role first. Then run this prompt:
âYou are screening resumes against the attached rubric for [JOB TITLE]. For each candidate below, output a row with: candidate identifier, score (1-5) on each rubric criterion, the specific resume text that justifies each score (quoted), an overall recommendation (advance / borderline / decline), and any criteria you cannot assess from resume alone (mark âunknownâ, do not infer). Do NOT use any criteria not in the rubric. Do NOT factor in name, gender or age cues, university prestige, or location unless explicitly required. If a candidateâs resume gives insufficient evidence for a criterion, score it âunknownâ.â
Save the output. Thatâs your audit trail. In jurisdictions where AI-assisted hiring decisions are subject to disclosure (NYC Local Law 144, Illinois AIVID Act, the EU AI Actâs high-risk classification of recruitment tools), this trail is the difference between a defensible process and a regulatory headache.
Stage four: interviewing. AI helps with prep, not assessment
This is where the line gets sharp. AI is genuinely useful for interview preparation: drafting question sets aligned with the rubric, simulating answers to test if the question is well-formed, structuring an interviewerâs notes after the fact. AI is genuinely risky for interview assessment: scoring a candidateâs answer against a âgood answerâ pattern is the kind of task that quietly encodes bias and produces false confidence.
The prompt that earns its keep here is the question-design prompt:
âFor the [JOB TITLE] role with this rubric [PASTE], draft a 45 minute structured interview with: (1) one role-specific behavioural question per rubric criterion, written in âtell me about a time whenâ format, (2) a follow-up probe for each that pushes past a rehearsed surface answer, (3) a âwhat makes a strong answer / what makes a weak answerâ note for the interviewer (not for the candidate), (4) one open-ended question at the end designed to surface what the candidate cares about, not test what they know. Tone: respectful of candidate time, no trick questions, no brain-teasers. After the interview script, list two questions that this rubric tempts us to ask but that donât actually predict role success.â
The âtempts us to ask but doesnât predict successâ list is often more useful than the script itself. Itâs the kind of insight a senior talent partner would offer in a calibration meeting, and itâs now available to a junior recruiter at the start of every search.
Stage five: offer and onboarding. AI helps a lot, with a guardrail
Offer letters, employment paperwork, and onboarding sequences are routine writing tasks AI handles well. BambooHR, Workable, and Rippling all integrate AI features here that produce defensible, on-brand documents in seconds.
The guardrail is simple: never let AI write the parts of an offer that have legal weight (compensation specifics, equity terms, restrictive covenants) without an attorneyâs review. Use AI for the cover note, the welcome message, the day-one schedule, the manager intro, and the first-week reading list. Donât use it for the parts where a hallucinated detail could become a contract dispute.
What HR should walk away with
The 26 to 43% jump in AI adoption is real, but the simultaneous increase in cost-per-hire is the part that matters. AI doesnât fix hiring on its own. It accelerates whatever process you point it at, including the bad parts. The teams that beat the trend are doing four things consistently: writing tighter rubrics before any AI involvement, scoring transparently with an auditable trail, using AI for preparation and writing rather than for assessment, and editing every AI output before it reaches a candidate.
Thatâs not a moonshot. Itâs a 30 day team upgrade. And itâs the difference between a hiring funnel that genuinely got faster and one that just got busier.