If you are hiring in Germany or elsewhere in the EU, the short answer is: yes, you can generally record a job interview, but only with genuine, freely given, documented consent. Because consent in a hiring context is presumed not to be fully voluntary, you must offer a realistic no-recording alternative and delete the recording immediately if the candidate withdraws consent. This is a very different test from the US, and getting the frame right matters.
Why US "one-party" and "two-party consent" rules are the wrong frame
Search this question in English and most results answer with US law: whether you are in a one-party consent state or a two-party (all-party) consent state. That framework comes from US wiretapping and eavesdropping statutes, and it simply does not govern a job interview in Germany, the Netherlands, France, or anywhere else in the EU.
In Europe, recording a person's voice and words is processing of personal data. That puts it under the General Data Protection Regulation (GDPR) and national employment-data law, not under a state-by-state consent map. So the real question is never "how many parties consented" in the American sense. It is: do I have a valid lawful basis to record, and if that basis is consent, was the consent genuinely voluntary, informed, and documented?
This distinction is the single most common mistake English-language guidance makes for EU employers. If you apply US logic, you will both over-record and under-protect.
It also changes who is protected. US wiretapping law is mostly about the act of intercepting a conversation. GDPR is about the entire life of the data: how you collect it, how long you keep it, who you share it with, where it lives, and how you delete it. So even a perfectly consented recording can still become non-compliant later if you store it too long, move it outside the EU, or reuse it for a purpose the candidate never agreed to. Consent at the start is necessary, but it is not the whole obligation.
What lawful basis do you actually need under GDPR?
Under GDPR, every act of processing personal data needs a lawful basis under Article 6. For recording a job interview, the two candidates most people reach for are consent and legitimate interests.
In practice, legitimate interests is hard to rely on for recording an interview. Recording is intrusive, a candidate reasonably expects a normal conversation rather than a captured one, and the power imbalance between employer and applicant weighs heavily against the employer in the balancing test. That pushes most employers toward consent as the working lawful basis for interview recordings.
Germany adds a specific layer. Section 26 of the Bundesdatenschutzgesetz (BDSG) governs the processing of personal data for employment purposes, including the application stage. It allows processing that is necessary for decisions about entering an employment relationship, but "necessary" is a high bar, and recording a full interview is rarely strictly necessary to decide whether to hire someone. So again, you tend to land on consent, with all the fragility that consent brings.
Why consent is fragile in a hiring context
Here is the part that trips up employers. GDPR Article 7 sets conditions for valid consent: it must be freely given, specific, informed, and unambiguous, and it must be as easy to withdraw as it was to give.
Now layer in the employment relationship. Both GDPR and BDSG Section 26 recognise that in an employment or application context, consent is presumptively not freely given because of the power imbalance. A candidate who wants the job may feel they cannot say no without hurting their chances. If consent is not truly voluntary, it is not valid, and if the consent is invalid, your lawful basis collapses and the recording becomes unlawful processing.
This does not mean consent is impossible in hiring. It means you have to actively engineer voluntariness into your process, so that a "no" is genuinely costless for the candidate. That is what the checklist below is for.
There is also a timing trap. Asking for consent in the first thirty seconds of a live interview, with the candidate already nervous and eager to please, is weaker than giving advance notice in the invitation and confirming it at the start. Where you can, flag the recording ahead of the interview, so the candidate has time to think, decline, or ask questions before they are in the room. Consent given under time pressure, in front of the person deciding your future, is exactly the kind a regulator will look at sceptically.
What about health, ethnicity, and other sensitive topics?
Interviews wander. A candidate might mention a disability, a health condition, religious observance, pregnancy, ethnic origin, or trade union membership, sometimes to explain a gap or a scheduling need. The moment that happens, you are potentially processing special-category data under GDPR Article 9, which carries stricter conditions and a higher risk profile than ordinary personal data.
A recording captures all of it, verbatim, and stores it. That turns an offhand remark into a durable record of sensitive personal data. Two practical consequences follow:
- Train interviewers to steer away from questions that invite special-category disclosures. This is good hiring practice regardless of recording.
- If such data does surface, minimise what you keep. Consider deleting or editing that portion rather than storing a full transcript, and do not let it feed any downstream decision-making.
Special-category data is the strongest single argument for keeping interview recordings short-lived, tightly scoped, and easy to delete.
The employer's compliance checklist for recording interviews
If you want to record interviews in Germany or the EU defensibly, build these steps into your process. Treat them as a sequence, not a menu.
- Announce before recording. Tell the candidate clearly, before anything is captured, that you would like to record, why, what will be recorded (audio, transcript, summary), and who will see it. No silent or surprise recording.
- Capture explicit opt-in. Get an active, unambiguous yes, and log it: who consented, when, and to what. A pre-ticked box or assumed agreement is not valid consent.
- Offer a realistic no-recording alternative. Make clear that declining is completely fine and will not affect the candidate's chances, then be ready to run the interview live and unrecorded. This is what makes the consent freely given.
- State a retention period. Say how long you will keep the recording and derived notes, and tie it to the hiring decision. "Until the role is filled plus a short defined window" is far safer than "indefinitely."
- Honour withdrawal and delete. If a candidate withdraws consent at any point, stop using the recording and delete it, together with transcripts and summaries, without undue delay. Confirm the deletion.
- Keep data in-region. Process and store the recording on EU infrastructure, and check that any tool or subprocessor you use does the same. Data location is part of your accountability story, not an afterthought.
Document each step. If a regulator or the candidate ever asks, your defence is not "we felt it was fine," it is a short, clear record that consent was informed, voluntary, time-limited, and revocable.
Do you need the works council or other approvals?
In Germany, if you have a works council (Betriebsrat), systematically recording interviews or introducing tools that monitor and process personal data may trigger co-determination rights, so involve them early rather than after rollout. Larger or higher-risk processing can also call for a Data Protection Impact Assessment (DPIA). Neither is a reason to avoid recording, but both are reasons to plan it deliberately instead of switching a tool on quietly.
How do AI notetakers fit if configured correctly?
An AI notetaker does not change the legal test. It is simply an automated way to record, transcribe, and summarise a conversation, so every rule above applies unchanged: announce it, get explicit opt-in, offer a no-recording path, set retention, honour withdrawal, and keep data in-region.
What does change is the risk surface, in two directions. On the downside, a notetaker that ships audio to a US processor, retains transcripts indefinitely, or automatically scores and ranks candidates stacks additional legal exposure on top of the recording question, including automated-decision and special-category-data concerns. On the upside, a tool built for this can make compliance easier: clear pre-recording notice, EU-only processing, defined retention, and one-click deletion when consent is withdrawn.
This is the lane we built Numi for. It records, transcribes, and summarises interviews and pulls out action items and decisions, processed on European infrastructure, and it does not train on customer data. It deliberately does not score or rank candidates, because that is exactly the kind of automated judgement that turns a recording question into a much harder legal one. The tool captures and organises the conversation; the hiring decision stays with your people.
If you also record sales or customer calls, the same GDPR reasoning carries over. For that context, see our companion explainers on GDPR-compliant AI call recording for B2B and recording calls and meetings in Europe.
The bottom line
Recording job interviews in Germany and the EU is legal but conditional. Forget the US one-party and two-party consent map; it does not apply. Anchor on GDPR: have a lawful basis, use consent that is genuinely freely given, informed, documented, and revocable, watch for special-category data, keep recordings short-lived and in-region, and make a no-recording interview a normal, penalty-free option. Do that, and recording becomes a defensible convenience rather than a liability.
This article is general information, not legal advice. For your specific situation, consult a qualified data protection or employment lawyer.