Can you record a job interview with an AI note-taker?

Can you record a job interview with an AI note-taker?

Yes, you can record a job interview with an AI note-taker — provided you ask the interviewer first and they agree. That single step keeps you on the right side of consent law in every jurisdiction and, just as importantly, keeps you on the right side of the hiring manager. The technology stopped being the hard part a while ago. On 8 October 2026 Google released AI Edge Foresight, an experimental Mac app for Apple Silicon that transcribes conversations, drafts notes and answers questions about them using models running entirely on the machine. No cloud subscription, no upload.

Foresight is worth understanding because it shows where this category is heading. It pairs EmbeddingGemma 2, a 740-million-parameter embedding model released under the Apache 2.0 licence, with the Gemma 4 language model, and it captures both microphone input and system audio — so it works with any video platform rather than joining your call as a visible bot. The interface splits in two: your shorthand bullets on one side, the AI's expanded notes on the other. You can also upload PDFs, Office files, Markdown and bookmarks into a local knowledge base the assistant draws on while you talk.

Google itself calls it experimental, and it sits mainly as a showcase for its offline Gemma models alongside Granola and a crowded field of meeting note-takers. For a job seeker, though, the architecture is the headline. A job interview is one of the most sensitive conversations you'll have all year: your current salary, your reason for leaving, your manager's name, sometimes details about your employer that shouldn't travel. An on-device tool keeps that audio on your laptop. A cloud note-taker sends it to a vendor's servers, where it sits under someone else's retention policy and someone else's breach risk.

Is it legal to record an interview without telling the interviewer?

Often it's legal, but it's rarely wise — and in a sizeable minority of places it's a crime. Federal law in the United States sets a one-party consent baseline, meaning one participant in the conversation needs to know it's being recorded, and that person can be you. Most states follow that default. A well-known cluster of jurisdictions does not: California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania and Washington are commonly listed as all-party consent states, and published lists disagree at the edges because several of them apply split rules.

Those split rules are exactly where secret recording goes wrong. Oregon treats electronic recordings as one-party but in-person conversations as all-party. Connecticut's phone-recording statute creates civil exposure for recording a call without everyone's agreement even where criminal law is looser. California and Florida have both applied their stricter standards to out-of-state callers recording someone inside the state, which matters enormously for remote interviews: you might sit in a one-party state while the interviewer sits in an all-party one. Nobody wants to resolve that question after the fact, and Florida treats a violation as a third-degree felony.

So treat consent as a universal habit rather than a jurisdictional calculation. The practical risk isn't only legal, either. Recruiters talk. If a hiring manager discovers mid-call that they're being taped without having agreed, you've lost the role and probably the agency relationship behind it. One more thing worth saying plainly: company policy often forbids recording regardless of what the law allows, and an interviewer who says no is usually relaying a rule, not a personal preference. None of this is legal advice — if a lot rides on it, check your own state's statute.

How do you ask to record an interview without sounding odd?

Ask in one short sentence, in the first thirty seconds, and frame it around accuracy rather than evidence. Something like: "Before we start — would you mind if I record this just for my own notes? It helps me follow up properly, and I'll delete it afterwards." That phrasing works because it tells the interviewer three things they care about: the purpose, the audience of one, and the deletion. Wait for an explicit yes. A pause and a shrug isn't consent, and on a video call you want the agreement captured in the recording itself or confirmed in writing afterwards.

If the answer is no, accept it immediately and without visible disappointment — then say you'll be taking written notes instead, and actually do. Interviewers rarely object to typing. For a technical screen or a panel round, email the question ahead of time so nobody has to decide on the spot; recruiters appreciate the warning and will tell you if policy forbids it. Avoid tools that join the meeting as a named bot participant for a conversation like this. A visible "AI Notetaker has joined" banner reads as a surprise rather than a request, and it hands the decision to the platform instead of to you.

Two situations deserve extra care. First, anything covered by a non-disclosure agreement: if the interviewer starts describing unreleased product work, stop the recording and say so. Second, interviews conducted through an agency, where the recruiter may have agreed but the end client hasn't. Ask who else will hear the conversation and keep the file off anything synced — no shared drives, no team folders, no default cloud backup. The point of recording an interview is to remember it accurately for a week, not to build an archive you'll still be carrying around in two years.

Why is an offline AI note taker safer than a cloud tool?

An offline note-taker is safer because the audio never leaves your device, so there's no vendor retention policy, no training-data question and no third party to breach. That's the whole argument, and it's a strong one for interviews specifically. When you record a hiring conversation you're capturing your current salary, your notice period, your reasons for leaving, the interviewer's candid take on the team, and occasionally details about your employer you'd never post publicly. Cloud transcription services handle that competently, but they handle it on infrastructure you don't control and under terms you probably didn't read.

On-device processing is what makes Foresight interesting beyond the novelty: Google says all transcript and audio processing happens locally, which is precisely the concern that keeps corporate users away from cloud note-takers. The trade-offs are real, though. Local models are smaller than the frontier models running in data centres, so expect weaker speaker separation, more trouble with heavy accents and crosstalk, and slower output on an older machine. Battery drain during a long panel round is noticeable. And an experimental developer showcase is not a product with a support line — treat it as a tool you test before you depend on it.

The same split shows up across AI-assisted job hunting generally. There's a genuine privacy win in keeping salary figures, home addresses and employer names on hardware you own, and a genuine capability ceiling on what a small local model can do with them — a gap worth reading about in this breakdown of what on-device AI can and can't do for your CV. My own rule is blunt: run the recording locally, then do the thinking with a stronger model on a cleaned-up transcript with the salary numbers and names stripped out. You get the privacy where it counts and the quality where it counts.

How do you turn interview notes into a follow-up email and a better CV?

Mine the transcript for three things: the exact words the interviewer used for the problem they're hiring to solve, the questions where you hesitated, and any commitment about next steps and timing. Those three feed everything that comes next. A follow-up email built from notes beats a generic thank-you because it's specific — you can quote the phrase the hiring manager used about their migration backlog, add the number you couldn't recall on the call, and attach the one example you wish you'd led with. Send it within twenty-four hours, keep it under 150 words, and don't mention the recording.

The gaps matter more than the wins. If the interviewer pushed twice on whether you've owned a budget, or asked how large the data sets were, that's not small talk — that's the doubt that will come up when the panel debriefs without you. Write those questions down verbatim and treat them as a to-do list for round two. Then fix the document that created the doubt. A CV that forced someone to ask "so what was the team size?" has an impact problem, not a formatting one, and the same gap will show up in the next application too.

That's where an automated read on your CV earns its place. A free CV analysis scores the file out of 100 across experience, tech stack, impact and ownership, clarity and structure, and ATS compatibility — and if you paste in the job description for the role you just interviewed for, it lists the skills the posting asks for that your CV doesn't mention. More often than not, those missing skills are the same ones the interviewer probed. Fix them before the next round, rather than discovering the gap again in another debrief you don't get to attend.

Frequently asked questions