Are AI interviews a red flag? Not by themselves. A specific kind of AI interview is: one the candidate was not told about, scored from a recorded video with no person involved. Candidates are objecting to how AI interviews are run, not to the format.
The numbers are blunt. In a 2026 survey of 2,950 job seekers, 38% of US candidates had already withdrawn from a hiring process because it included an AI interview. Only 19% wanted less AI in hiring overall. The rest want the same or more, with clearer rules and a visible human.
So the job is not to defend AI interviews. It is to answer the seven questions candidates are actually asking, and to have a setup that lets you answer them truthfully. This post gives you both: what each objection really means, what to check on your side before you reply, and a script you can paste into an email or say on a call.
If you are still deciding where an AI round belongs, start with how AI interviews work. This post assumes the round exists and candidates are pushing back.
What candidates mean when they say "red flag"
Every objection in your inbox maps to one of three underlying questions: Who decides? What are you measuring? What happens to me after? The four setups candidates abandon most often (a pre-recorded video scored with no human present, AI use nobody disclosed, monitoring during the session, and an AI round with no alternative) are each a failure to answer one of those three.
Notice that none of the right-hand answers are about the technology. They are about your process. If you cannot say one of them truthfully today, fix the setup before you fix the script.
Check your setup before you reply
A reply script is a promise. Make sure your tool and your process can keep it. Four things to confirm:
On Equip, these are defaults rather than configuration: the AI scores the transcript against the criteria you set, each topic score comes with a written reason, the report includes the full timestamped transcript, and a recruiter can change any score before deciding. Candidates see the format and the active proctoring measures before they start. If you use a different tool, ask the vendor these four questions in writing before you promise anything to a candidate. The post on AI interview scorecards and rubrics covers what a defensible scoring setup looks like.
The seven objections, with reply scripts
Each script is written to be sent as-is by a recruiter. Adjust the specifics (minutes, dates, names) and leave the structure. The pattern is the same every time: acknowledge, answer the real question, name the human, give the next step.
1. "Is this a red flag? Does this mean you don't value candidates?"
This is the headline objection and the one with the most search volume behind it. The candidate is testing whether the company has thought about the experience at all. A defensive answer ("everyone uses AI now") confirms the red flag, so explain what the round replaces and what it buys them.
2. "Is a robot deciding whether I get the job?"
Candidates want confirmation that a person reviews the AI's output before any decision. Give it to them by name and by role, not as a policy statement. "A human is in the loop" is vague enough to be disbelieved. "Priya, our recruiter for this role, reads every report" is not.
3. "Is it judging my face, my voice, or my accent?"
This is the objection that matters most legally and ethically. Facial-expression and voice-tone analysis is what gave AI interviews their reputation, and it is what candidates mean when they talk about being "monitored." If your tool scores anything other than the content of the answers, you have a product problem, not a messaging problem.
If scoring is transcript-only, say so in plain terms, and say what the camera is for if it is on.
If you hire in Illinois, the state's Artificial Intelligence Video Interview Act requires you to tell candidates that AI may analyse their video, explain how it works and which characteristics it evaluates, and obtain consent before the interview. New York City's Local Law 144 requires notice and a bias audit for automated employment decision tools. Treat those as the floor for your disclosure everywhere, not as region-specific extras.
4. "Where does my recording go, and who sees it?"
Be specific about the three things that matter: who has access, how long it is retained, and how to request deletion. Illinois law requires deletion within 30 days of a candidate's request, which is a sensible default for everyone.
5. "Can I refuse the AI interview and ask for a human instead?"
Yes, and you should say yes before you are asked. Roughly half of candidates want the option to request a human interview instead; most never use it. Offering it is what signals that the process was designed around people, and it costs you a handful of phone screens a quarter.
Be clear about what changes if they opt out, because something usually does. A human screen takes longer to schedule, and the candidate should know that. Do not penalise the choice, and do not pretend it has no cost.
For senior roles, candidates with accessibility needs, and roles where you have fewer than ten applicants, consider skipping the AI round entirely. The format earns its place at volume. It does not earn it when you could have called everyone by Thursday.
6. "Will I even hear back?"
This is the objection that comes after the interview, and it is the one most companies lose on. Half of candidates who complete an AI interview never get an outcome. An automated round makes silence feel worse, because the candidate suspects nobody ever looked.
Set a date before the interview. Then hit it, including for rejections. The reliable way to hit it is to take the follow-up out of a recruiter's to-do list: on Equip, an automation rule can email the candidate the moment their stage changes, so the "you will hear from us by" promise is kept by the pipeline rather than by memory.
If your tool produces a strengths-and-gaps summary per candidate, you can send a one-line reason with each rejection without writing it from scratch. Candidates who get a reason tend to reapply; candidates who get silence tend to post about it.
7. "Isn't this biased?"
Do not promise that it is not. Candidates perceive bias from AI and human interviewers at similar rates, and they know a blanket denial is marketing. The honest claim is narrower and more convincing: this process removes specific inputs that drive bias, and every score can be inspected.
That last sentence is the one that lands. It is also only safe to say if you have an audit trail. Equip's page on how it prevents AI bias in hiring describes one way to structure that; whichever tool you use, make sure you could answer the question within a day.
Say it before they ask
Most of these objections never get sent if the invite answers them first. Here is a disclosure block you can drop into the job post and the interview invite. It takes 90 seconds to read and covers every question above.
When to concede the point
Some objections are correct. If your tool scores video or voice, the candidate's concern about being judged on their face is accurate, and the fix is a different tool. If nobody on your team reads the reports before rejections go out, "a human decides" is a lie, and candidates will find out from Glassdoor. If you cannot say how long you keep recordings, you do not have a retention policy, and you should before you run the next drive.
Candidates have been remarkably clear about what they want: tell them upfront, score what they said, keep a person on the decision, and close the loop. Those are process requirements, and they are the same ones that make an AI interview defensible when a regulator asks. Handle those, and the objections mostly stop arriving. For the other side of the integrity question, see how to spot and stop AI-assisted cheating in AI interviews.