Can You Record Your Own Job Interview?

Federal law permits a participant to record their own conversation, but that is the least important rule governing your interview. Roughly eleven states require every party to consent, your meeting client probably will not let you press record without the host's permission, and if the interview is an automated assessment, the binding constraint is not wiretap law at all — it is the platform's terms, which in at least one case prohibit recording the test outright.

This article covers recording you initiate, as the candidate. That is the mirror image of the more familiar question: what the employer's AI notetaker captures, whether you are told, and how to decline, which we covered in what an AI notetaker captures in a live interview. Here the recording device is yours, which moves you from the subject of the statute to its target. Sources are current as of 17 October 2026. This is a reading of statutes and vendor terms, not legal advice.

Three interviews, three different rule sets

Candidates ask one question and mean three situations. They are not governed by the same body of law.

A live call with a human. You and one or more interviewers on Zoom, Teams, or Meet. This is a two-party oral communication, so wiretap and eavesdropping statutes are the governing rules, and the meeting client's own recording permissions sit on top of them.

A one-way or AI-led interview. You answer prompts from a platform or an agent, and there is no second human in the room. There may be no other party whose consent a wiretap statute protects, which sounds permissive — and then the vendor's terms of service do the work instead.

A proctored assessment. A timed coding test under integrity monitoring. The audio question barely arises; the question is screen capture, and the platform is often watching for exactly that.

Work out which one you are in before you decide anything, because the answer changes completely between the first and the third.

Federal law allows it. About eleven states do not.

The federal wiretap statute carves out participants. Under 18 U.S.C. § 2511(2)(d), "It shall not be unlawful under this chapter for a person not acting under color of law to intercept a wire, oral, or electronic communication where such person is a party to the communication or where one of the parties to the communication has given prior consent to such interception," unless the recording is made "for the purpose of committing any criminal or tortious act" (18 U.S.C. § 2511).

State law is where candidates get caught. The Reporters Committee for Freedom of the Press summarizes the landscape as "About 11 states primarily have all-party consent requirements for recording," listing California, Delaware, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, New Hampshire, Pennsylvania, and Washington, with Connecticut, Missouri, Nevada, and Oregon requiring all-party consent for only one type of conversation (Reporters Committee).

Two of those statutes are worth reading closely, because they fail in different ways.

California turns on whether the conversation was private

California Penal Code § 632(a) punishes a person who, "intentionally and without the consent of all parties to a confidential communication, uses an electronic amplifying or recording device to eavesdrop upon or record the confidential communication," with a fine up to $2,500 per violation, up to a year in county jail, or both. The hinge is the definition in subsection (c): a confidential communication is one "carried on in circumstances as may reasonably indicate that any party to the communication desires it to be confined to the parties thereto," excluding circumstances "in which the parties to the communication may reasonably expect that the communication may be overheard or recorded" (Cal. Penal Code § 632).

A closed-door interview about your salary history and your current employer looks like a conversation the parties wanted confined to themselves. An interview the recruiter already told you is being transcribed by the company's notetaker looks less like one. That asymmetry is real, but it is an argument you would be making after the fact, not a permission slip.

Massachusetts turns on secrecy alone

Massachusetts is stricter and simpler. Chapter 272, Section 99 defines interception as "to secretly hear, secretly record, or aid another to secretly hear or secretly record the contents" of a wire or oral communication, excluding anyone with prior authority from "all parties to such communication." The penalty reaches a fine of "not more than ten thousand dollars" or state prison for up to five years (Mass. Gen. Laws ch. 272, § 99).

There is no expectation-of-privacy test to argue about. The operative word is secretly. A Massachusetts candidate who announces the recording and gets agreement is in a materially different position from one who does not, and that distinction is the practical takeaway from the whole statutory tangle: disclosure is what moves you out of the prohibited category in most of these states.

Which state's law applies is genuinely unsettled

Remote hiring makes this routine rather than exotic. You are in one state, the hiring manager is in another, and a second interviewer joins from a third. The Reporters Committee notes that courts disagree over whether the governing law is that of the state where the recording device sits or the state where the recorded person sits, and advises that one should "err on the side of caution and assume that the stricter state law will apply."

For a candidate, the operational version is short: if anyone on the call might be in an all-party state, treat the call as an all-party call.

Your meeting client probably will not let you anyway

Before the legal question becomes concrete, a product constraint usually settles it. Neither major meeting client lets an invited guest start a recording unilaterally.

Zoom's documentation on starting a computer recording states that "The host must record the meeting or grant the ability to record to a participant," granted from the Participants menu via More and Allow Record, after which the participant is notified of the privilege; while recording is active, participants see an indicator and dial-in participants "will hear a message informing them that the meeting is now being recorded" (Zoom Support).

Google is equally direct: "Participants can only record a meeting if the host has permission to record," recording must first be enabled by a Workspace administrator, and "Participants get a notification when the recording starts or stops" (Google Meet Help).

That has a consequence candidates rarely trace through. Because the in-client path is gated and announced, "recording the interview" in practice means running a separate capture tool outside the meeting — a screen recorder, a notetaker bot, a phone on the desk. Doing it that way strips out precisely the notice that Zoom and Meet would otherwise have given the other side, which is the posture that all-party consent statutes exist to address. The convenient method is the one that forfeits the strongest defense you had.

In an automated interview, the terms bind before the statute does

A one-way video interview or an agent-run screen often has no second human participant at all, so the eavesdropping analysis gets thin. The contract does not.

TestGorilla's candidate terms are the clearest example in the category. Section 4.3 states that "You are expressly prohibited from recording, disclosing, publishing, sharing or making available assessment tests, individual questions or assignments, either to other individuals or by the general public, online or otherwise," and Section 7.3 grants candidates no ownership in "test content, test questions, and test answers" (TestGorilla candidate terms). That is a direct prohibition on the act, not an inference from an IP clause.

Most platforms get to a similar place less explicitly. CodeSignal's terms provide that "Use, reproduction, modification, distribution or storage of any Content for any purpose other than using the Services" is "expressly prohibited without prior written permission from us," and separately bar conduct that "copies or stores any significant portion of the Content" (CodeSignal terms). HackerRank's terms do not mention screen capture, but reserve that "HackerRank or its licensors exclusively own and reserve all rights in and to the Services and all works and materials thereof," prohibit copying or publicly displaying the Services, and prohibit circumventing "any security, access controls, or use limits of the Service" (HackerRank terms of service).

Note the split this produces. Recording yourself answering a behavioral prompt is a weaker target for these clauses than recording the questions, which is the platform's product. A candidate who wants a record of their own answers for self-review is in a defensible position; a capture of the question set is the thing every one of these documents is built to prevent. And the remedy is not usually a lawsuit — CodeSignal states that a violation "is grounds for termination of your right to use or access the Services," which in hiring terms means a withdrawn assessment.

Under lockdown, the attempt is itself an event

In a proctored coding assessment, capture is not merely prohibited — it is monitored. HackerRank's terms describe customers applying "behavioral and proctoring analysis (including analysis of video, audio, keystroke patterns, and session activity)" and "detection of integrity, facial image matching or anomaly detection or potential non-compliance with rules." What various platforms can and cannot observe about capture attempts varies by whether the test runs in a browser or a desktop app, which we worked through in what interview websites can detect about screenshots.

The asymmetry matters more than the technical detail. A legitimate motive — wanting to review a question you found unfair — produces the same telemetry as an illegitimate one, and you will not be present for the conversation in which someone interprets it.

Asking is the underrated option

Candidates skip the direct request because it feels confrontational. The published evidence runs the other way. Some employers maintain candidate-facing policies stating that opting out of their recording carries no effect on evaluation — two such policies are quoted in the companion piece linked above — which establishes that recording is treated as a negotiable term of the conversation rather than a fixed condition of it. The same norm is what makes asking to record your own side a reasonable request instead of a red flag.

Phrase it as a logistics question when you schedule, in writing:

"Would you be comfortable with me recording my side of the conversation for my own notes? Happy not to if it's a problem."

Three outcomes, all useful. Yes, and you have consent from every party, which resolves the all-party problem in every state listed above. No, and you take notes instead, having lost nothing. No answer, which tells you to assume the answer is no.

What to ask for instead

The usual reason a candidate wants their own recording is that the employer has one and they do not — especially after an AI-scored interview where the transcript is the whole basis of the decision. There is a route to that artifact that does not involve a recording device.

1. Ask what is being captured, before the interview. Which tool, what it records, how long it is retained. A recruiter who cannot answer has told you something.
2. Request the employer's copy afterward. The recording, the transcript, and the scorecard are held by the employer as controller, not by the vendor, which determines where the request has to go and which deadline you can cite — the mechanics are in how to request an interview recording be deleted or disclosed.
3. Know what disclosure you were owed. Several jurisdictions require notice, and in some cases consent, before an AI system evaluates you; what AI hiring rules entitle candidates to know in 2026 covers the current obligations.
4. Write your own account immediately. Contemporaneous notes made within the hour are weaker evidence than audio and stronger than memory, and no statute restricts them.

What this does not settle

Recording law varies by state and by where each participant is physically sitting, courts disagree about which state governs an interstate call, and none of the statutes quoted here were written with hiring in mind. Vendor terms change, and the version that binds you is the one you accepted on the day. If something turns on the answer — a rescinded offer, a discrimination claim, a dispute about what was said — that is a question for a lawyer in the relevant jurisdiction, not for a checklist.

What is settled is the ranking. In a live interview, consent is the whole game, and asking for it is cheap. In an automated assessment, the terms of service bind you before any statute does, and capturing the platform's questions is the specific act those terms target.

The practical answer

If you are in a live interview with a human and everyone consents, recording is likely lawful in every US state, and the simplest path is to ask. If you have not asked, or you cannot establish that every participant is outside an all-party state, do not record. If you are in a one-way, agent-run, or proctored assessment, the realistic answer is no, and the reason is contractual rather than criminal.

The same questions apply to any tool you bring to your own side of an interview: what it captures, whether that stays on your machine, and what the platform's terms say about it. Control is a desktop AI interview assistant for Windows and macOS; as of October 2026 its site lists a day pass at $12, a 72-hour sprint pass at $19, and $39 per month, with a free allowance of five messages and two minutes of voice transcription for new users — enough to check what it does with audio and screen content before an interview depends on it. Ask a vendor the same things you would ask a recruiter, including ours.