An AI Note-Taker Is Sitting In on Your Interviews. Did Anyone Ask the Candidate?
Meeting bots now join calls and transcribe them by default, and interviews are no exception. The recording itself isn’t the risk — how, and whether, you get the candidate’s consent is. For a small team, getting that right is a cheap trust advantage most companies are fumbling.
You send the calendar invite, the candidate joins, you exchange the first bit of small talk — and a third participant slides into the call. “Someone’s Notetaker has joined.” Maybe it’s yours, quietly set to auto-join every meeting on your calendar. Maybe it’s theirs. Either way, a bot is now recording and transcribing a private conversation, and nobody in the room has actually talked about whether that’s okay.
This became normal so fast that most teams never stopped to think about it. The technology is the easy part. The part that trips people up — and quietly carries legal and trust risk — is consent. And small teams, who tend to adopt these tools first and worry about policy last, are the most exposed.
The Uninvited Guest in the Interview
AI note-takers went from novelty to default in about two years. They ride along on video calls, produce a speaker-attributed transcript, and hand you a summary afterward. In interviews the appeal is obvious: you get to actually listen instead of scribbling half-sentences, and you keep a record of what was really said rather than what you half-remember a week later. Increasingly, candidates bring their own note-takers too. The etiquette is being invented in real time.
So this isn’t an argument against recording interviews. A good transcript is one of the fairest things you can bring to hiring — it lets you go back to evidence instead of impressions, and it protects the candidate as much as it protects you. The problem isn’t that the bot is in the room. It’s that it usually got there without anyone deciding it should.
The Problem Isn’t the Recording
Recording a private conversation is governed by wiretapping and consent law, and the rules don’t care whether a human hit record or an AI joined automatically — the obligation attaches to the act of recording, not the tool. In the United States, federal law follows a “one-party consent” rule: as long as one person in the conversation knows and agrees, the recording is generally lawful. But roughly a dozen states require all-party consent — among them California, Illinois, Florida, Maryland, Massachusetts, Pennsylvania, and Washington — where every participant has to be notified and agree before recording begins.
For remote interviews, that’s a trap hiding in plain sight. When people on a call are in different states, the strictest rule tends to win: if even one participant sits in an all-party-consent state, you generally need everyone’s consent to be safe. You often don’t know where a candidate is physically sitting when they join, which means “just record it” is a gamble you can’t actually price. This isn’t hypothetical, either: in 2026 one of the most popular AI note-taking apps has been hit with a series of class-action lawsuits arguing that its auto-join and thin notifications don’t amount to valid consent under federal and state wiretapping laws.
In the EU and UK the framing differs but the direction is the same. Recording an interview means processing a candidate’s personal data, so under the GDPR you need a lawful basis, a clear notice about what you’re capturing and why, a defined retention period, and a way for the candidate to exercise their rights. “The bot was on by default” is not a lawful basis anywhere.
Why “Is This Okay?” Isn’t Really a Question
Here’s the part the legal checklist misses. Even where recording is perfectly lawful, the way most interviewers ask for consent makes it meaningless. Picture the candidate: they’ve joined the call, they want this job, and thirty seconds in the interviewer says, “We use an AI note-taker to help us stay fair — that okay?” What are they going to say? Objecting in that moment feels like flunking the first question. It reads as difficult, or as if you have something to hide. So they say yes, because the power sits entirely on your side of the table.
That’s consent in name only, and candidates know the difference. A candidate who felt cornered into being recorded trusts you a little less for the rest of the process — and on a small team, where your reputation travels by word of mouth and the whole pitch is “you’ll be treated like a person here,” that’s expensive. Compliance keeps you out of court. It doesn’t earn you trust. Those are two different jobs.
How to Record Interviews the Right Way
The fix is almost entirely about timing and framing. Real consent is asked for before the moment of pressure, and it comes with enough information to be a genuine choice. In practice, for a small team, that looks like this:
- Tell candidates before the call, not at the start of it. Put it in the scheduling email so they have time to read it, ask questions, and decide without an audience.
- Say the four things that matter: what you’re capturing, why, how long you keep it, and who can see it. Vague reassurance isn’t disclosure.
- Make opting out real. Offer a genuine alternative — you take notes by hand instead — so “no” carries no penalty. Consent you can’t refuse isn’t consent.
- Use the record for evaluation, not surveillance. The transcript exists to compare candidates fairly against the same criteria — not to catch people out.
None of this slows you down, and here’s the quiet upside: a candidate told up front, given a real choice, and shown exactly how the recording will be used walks in trusting you more, not less. The same transparency that keeps you compliant makes a small team feel like a good place to work. Handled well, the note-taker stops being a liability and becomes part of your pitch.
That’s the approach we built into Kynto. Its interview assistant joins the call to produce a speaker-attributed transcript, but it’s meant to be disclosed and agreed to up front rather than sprung on anyone — and the record it captures feeds a structured evaluation, where the candidate’s score is built primarily from your feedback and cross-checked against what was actually said. A fair, on-the-record interview, without the awkward ambush. You can see how it works at kyntoai.com.
Key Takeaways
- Recording interviews isn’t the problem — a good transcript is one of the fairest tools in hiring. Recording someone without valid consent is the problem, and default auto-join bots do it constantly.
- The law is real: US federal law allows one-party consent, but around a dozen states require all-party consent, and the strictest rule usually wins on a multi-state remote call. In the EU, recording an interview triggers GDPR duties no matter how small your team is.
- Asking “is this okay?” thirty seconds into the call isn’t real consent. Disclose before the interview, say what you capture and why, and make opting out genuinely free — that’s how transparency becomes a trust advantage instead of a compliance chore.
The bot in your interviews isn’t going away, and it shouldn’t — the record it creates makes hiring fairer. But a record taken without a real yes is a liability wearing the costume of a convenience. Ask first, ask early, and mean it.
Table of Contents
Record interviews the right way. Kynto captures a consented, speaker-attributed transcript and turns your feedback into a structured, comparable score — so a small team gets a fair, on-the-record hiring process without the awkward ambush.
See how Kynto works