Can You Stop Candidates From Recording Interviews for AI?

Can you stop a candidate from recording the interview?

You can make it a term of the interview and you can end a call when someone refuses. What you can't do is verify it. Federal wiretap law, 18 U.S.C. § 2511, lets any party to a conversation record it without telling the others, unless the recording is made to commit a criminal or tortious act ¹. Under that floor, a candidate with a phone face-down beside the laptop is doing something federal law permits.

Some states go further, and California is the strict version. Penal Code § 632 makes it an offense to use a recording device on a confidential communication "without the consent of all parties," carrying a fine of up to $2,500 a violation on a first offense, and it defines a confidential communication as one carried on in circumstances indicating that a party wants it "confined to the parties thereto" ². A scheduled interview on a video call is a fair candidate for that description, and which state's rule reaches the call turns on where each party is sitting, which on a remote round is rarely one state.

Read the two statutes side by side and the useful thing is what neither one says. Neither cares which side of the table the recorder sits on. The all-party rule that makes a candidate's silent recording unlawful in California makes your notetaker unlawful in California when nobody asked the candidate first ². If your position is that recording an interview without telling everyone is wrong, you have already ruled on the bot sitting in your own calendar invite.

Three things are actually in your control: you can require disclosure, you can decline to interview someone who won't agree, and you can say what happens to anything recorded. You cannot confirm compliance, and a rule whose enforcement depends on a candidate volunteering that they broke it is a rule about honest people. Proctoring software runs into the same wall: the control lands hardest on the candidates who were never the problem.

Should it bother you that they run it through a model afterward?

Less than the recording itself. A transcript handed to a model the night after a screen produces preparation: likely follow-ups, the vocabulary your team uses, a tidier version of the answer they fumbled at minute twelve. That is coaching at a scale that used to require a friend inside the industry. It changes who can afford preparation. It does not change what a good question is able to measure.

The part that should bother you is narrower, and worth naming exactly: your question bank leaks faster. It always leaked, through review sites, group chats, and the candidate who tells three friends over dinner. A recording plus a model turns a paraphrase of question four into the exact wording, the follow-up you always ask second, and the sentence that made you nod. So run the bank as though it is already published, and give one person the authority to retire a row once it stops separating people: who owns the question bank, and when a row retires is that job written down.

If a question stops working once it's written down, it was measuring recall. Whether a structured interview still separates candidates who have all been AI-coached is the same problem one level up, and the answer transfers: structure survives being known, novelty doesn't.

Every unscripted aside about the last person who held the role, every hint about the band, every remark someone would not have put in writing now has a transcript attached to it. Your interviewers are on that recording as much as your questions are. A round you'd be comfortable having replayed is a materially different round from one you wouldn't, and the difference has nothing to do with the candidate's tooling.

Write one recording rule that binds both sides of the call

One rule, in the scheduling email and again in the first minute of the call, covering both directions at once. Name what your side captures and why, ask whether the candidate is capturing anything, set the scope, say who reads it, and give a retention date. A rule that materializes only when a candidate's notetaker joins is a rule invented on the spot, and everyone on the call can hear that.

Five lines, in the order they belong:

• What this side records. The call, a transcript, an AI-written summary, or nothing. Say which.
• What that side records. Ask directly, ask every candidate, and take yes for an answer.
• Scope. The scheduled interview. Not the small talk before it, not the debrief after it.
• Who reads it. The interviewers and the hiring manager, or whoever it actually is.
• How long it lives. A date. Not "as long as needed."

Two conditions turn that from a paragraph into something defensible. It applies to every candidate for the role rather than to the one whose notetaker happened to announce itself, and it applies to every interviewer, including the one keeping a private transcript because it helps them write feedback. EEOC guidance is that employers should administer tests and other selection procedures "without regard to race, color, national origin, sex, religion, age (40 or older), or disability" ³, and a standard enforced only where recording became visible is a standard about visibility.

One thing is worth refusing outright: a bot admitted to the call as a participant when nobody asked. Not because its recording is worse than a phone on a desk, but because an unannounced participant in a room where someone is about to discuss a third employee is a problem that predates AI. What belongs in an AI hiring policy and who signs off on it is where this paragraph lives; recording is one section of that document, not a memo of its own.

Who has to keep the interview recording, and for how long?

Your side does, on a clock you don't fully control. EEOC regulations require employers to keep all personnel or employment records for one year, and once a charge of discrimination is filed, records relevant to that charge must be preserved "until the final disposition of the charge or any lawsuit based on the charge" ⁴. A recording made about a hiring decision is that kind of record.

So "sure, record it" carries a cost worth pricing before you say it. An interview you captured is an interview someone can read back, including the aside and the interviewer who cut a candidate off at minute six. Most of the time that helps: a contemporaneous record of a structured round is the best available evidence that the round was structured. Occasionally it will be the worst document in the file.

Your own AI is regulated in places where the candidate's is not. Illinois's Artificial Intelligence Video Interview Act, effective January 1, 2020, requires an employer using AI to analyze video interviews to notify each applicant before the interview, provide information "explaining how the artificial intelligence works and what general types of characteristics it uses to evaluate applicants," and obtain consent to be evaluated by it, and delete the interviews within 30 days of an applicant's request ⁵. Notice which party that binds.

The candidate's copy is theirs. No retention schedule of yours reaches it, no deletion right, no say in who sees it. Sit with that asymmetry rather than writing a rule that pretends otherwise. What you do control is what your own summary says about a person: a notetaker's line about a candidate seeming nervous is the part of this that actually reaches a decision, and it has no business in the file.

Which interview questions survive being replayed?

The ones asking a candidate to do something rather than describe something. An answer that is a story can be rehearsed off a transcript in an evening. A question that hands over a real artifact (a brief with a hole in it, a figure that doesn't reconcile, a model's confident wrong paragraph) and asks what's wrong with it cannot be pre-answered by a recording of last week's call.

What that swap looks like in the round you're actually running:

• Product management. Instead of "walk me through scoping an ambiguous request," hand over two paragraphs from a real stakeholder and ask which sentence they'd refuse to build against until someone answers it.
• Data and analytics. A chart plus an assistant's fluent explanation of it, where the explanation is wrong about what the axis measures. Ask what they'd run before repeating it to anyone.
• Supply chain. Three quotes written on three different sets of terms, and a landed-cost figure only one of them supports.
• Journalism. A press release, and one claim inside it that settles only when someone opens the filing underneath.
• Accounting and audit. A schedule that reads as settled until it's re-added.

None of those get easier because a candidate holds last month's transcript. They get easier if the candidate has done the work, which is the only advantage worth protecting.

Candidates started recording for a reason, and a policy written without it will be the wrong policy. In a multi-market candidate survey Greenhouse published in May 2026, covering 2,950 job seekers across the US, UK, Germany, Australia and Ireland, 63% of the 1,200 US respondents said they had been interviewed by an AI, and 38% of them said they had walked away from a hiring process because it included one ⁶. A recorder on the desk isn't the opening move in that exchange; it's the reply. The round least likely to provoke it is the round whose record you'd hand over willingly, and what showing candidates their own report does to legal exposure is that argument with the numbers attached.

Run the interview you would be comfortable having replayed, and say so in the first minute. That sentence settles more of this than any rule you can enforce.

Read the evidence >