Job search
Stop Your Own AI Notetaker from Joining Job Interviews: Audit Defaults and Existing Events
Two completed fictional event and join-route audits distinguish disabled defaults, persistent exceptions, planned changes and actual readback evidence.
To keep your own AI notetaker out of a job interview, check more than its default. Existing event choices, recurring meetings, explicit invitations and provider-specific rules can still matter. Audit the actual interview event as well as the account preference.
Start before the interview day, while you have time to read the result and resolve uncertainty. Keep your own recording tools under control as you prepare for current roles on LandOffer. A notetaker you used for ordinary meetings should not become an unintended participant in a hiring conversation.

What this guide checks, and what it does not
This guide focuses on a candidate's own Otter or Fireflies setup. It does not establish what an employer records, decide whether a particular interview may be recorded, or promise that removing a bot deletes existing notes. Read the interview's instructions separately.
Current public provider guides were checked on October 21, 2026. Full rendered pages were reviewed; ordinary requests to two Otter pages returned access errors, which were retained rather than treated as successful fetches. No private account, calendar, event, invitation or meeting was inspected or changed. No bot was added, removed or admitted.
LandOffer publishes this guide and provides its own job-search product. The audits below use fictional people and invented event records to illustrate completed decisions. They do not report observed customer settings or changes to anyone's calendar.
A useful audit ends with specific evidence: you can identify the event, explain each way your own tool might join it, and see which routes have been addressed. “I turned something off last week” is too vague to support that conclusion.
Otter: inspect existing events after changing the default
Otter's stop-auto-join guide describes selecting Meetings I manually select, accessible through its homepage notetaker settings or Integrations, Meetings, Default auto-join settings. It also says previously modified events retain their choices. Review upcoming event entries after changing the default; do not assume that preference rewrites every earlier selection.
The distinction is important when an interview was added while automatic joining was enabled, or when you previously toggled a particular event on. An event-specific setting and a default for unmodified events are different pieces of evidence. Read both before considering your audit complete.
Otter's meeting-selection guide says enabling auto-join once for a recurring event enables the rest of the series. It also discusses making changes at least 30 minutes ahead to ensure joining. That is not a documented guarantee that a last-minute disable reaches every system within 30 minutes. Do the audit early rather than converting a joining instruction into a disable-propagation promise.
Manual addition through a meeting URL is another route described by the guide. Changing calendar defaults is therefore not equivalent to disabling every possible way the notetaker can be invoked.
Worked Otter audit: four events, four dispositions
Fictional candidate Sana wants her own notetaker absent from interviews. Her invented review record shows a manual-selection default, an interview event previously switched on, a recruiter follow-up belonging to an enabled series, and an unrelated study session she intentionally records.
Sana completes the following event-by-event diagnosis:
| Item in Sana's fictional record | Evidence available | Completed decision | Evidence she would need after acting |
|---|---|---|---|
| Account default | Manual selection is shown | Keep it as the default for unmodified meetings | Read back the same selected preference |
| Thursday technical interview | Event-specific auto-join is on | Turn off that interview's individual setting | Reopen that exact dated event and inspect its state |
| Recruiter follow-up series | One occurrence was enabled previously | Review the series and its upcoming interview occurrences | Confirm the intended future occurrences, not just the one currently visible |
| Saturday study meeting | Intentionally enabled, not an interview | Keep it separate from the interview decision | Avoid using it as proof of the interview's setting |
Sana's conclusion is not ready yet. Her default alone looks appropriate, but the technical event and recurring follow-up still need attention. The article does not claim those actions were carried out. The record is a finished diagnosis and action decision, with the required readback defined for each change.
She identifies events by date, time and meeting destination, not just a title containing “interview.” A recruiter might name a call “Conversation with engineering,” while an unrelated practice event might include the word “interview.” A title search is a way to locate candidates for review, not a reliable exclusion rule on its own.
Sana also avoids a destructive shortcut: deleting the interview from her calendar to stop the notetaker. That would discard useful scheduling information without proving the provider has no other join route. She keeps the appointment and handles the tool's own event controls instead.
The study meeting illustrates why a targeted audit is useful. Her goal is not to erase every legitimate recording preference. It is to make the upcoming interview's behavior explicit without confusing it with other events she deliberately handles differently.
Fireflies: check recording rules as well as auto-join
Fireflies' current stop-auto-join guide describes turning off Auto-record meetings under Recording & Privacy, or using the dashboard's meeting settings and manual-invitation option. The guide says the setting saves automatically. It also explicitly warns that configured meeting rules may still cause joining.
Do not read the short summary as a reason to skip that warning. An off toggle is useful evidence about that control, but it does not settle the state of another configured route.
The join-settings and recording-rules guide describes conditions involving keywords, addresses and domains. It also distinguishes a bot joining or attempting to join from actually capturing the meeting: admission and other recording conditions matter. A bot in a lobby is not proof of successful transcription, and failure to see a recording is not proof no invitation attempt occurred.
This guide does not recommend constructing a new keyword rule as a substitute for checking the actual interview. It does recommend reading the rules already present in your own setup. If a rule's interaction with the default is unclear, leave that route marked unresolved until you can establish its effect through the provider's current controls or support guidance.
Worked Fireflies preflight: trace each route to the same call
Fictional candidate Julian has a Friday 10:00 interview. His invented inventory says auto-record is off, but a domain-based meeting rule exists and fred@fireflies.ai is explicitly included on an older calendar entry for the same appointment. He also has access to an “Add to live meeting” control.
His completed preflight is a route audit, not a claim that one master switch solved the problem:
| Route in the invented inventory | Why “auto-record off” is insufficient evidence | Julian's completed disposition |
|---|---|---|
| General calendar automation | It describes only the default automation control | Retain the off state as one finding, then check the remaining routes |
| Existing domain rule | The provider warns that meeting rules may still cause joining | Review that rule's effect on the specific call; mark unresolved until confirmed |
| Explicit calendar invitation | Manual invitation is a separate entry route | Remove his own bot invitation where he has authority, or clarify the event ownership first |
| Add to live meeting | A person can invoke it separately | Do not invoke it for this interview; keep the join link out of that control |
| Botless recording tools | They are not represented by a participant-list bot | Check his own extension or recording app separately; do not activate it |
Julian's result is not cleared by the default alone. He has identified two concrete outstanding items: the domain rule and the explicit invitation. If he cannot edit the invitation because someone else owns it, he does not describe it as removed. The plan records the ownership limit instead of pretending that a calendar preference solved it.
His event-level record also checks that the old entry and the current appointment are actually the same call. If the interviewer issued a replacement link, reviewing only the canceled event would miss the live appointment. He compares the relevant date and destination rather than copying every private calendar detail into a troubleshooting message.
This distinction changes his preparation order. On the day before the interview, he resolves editable rules and event choices. Before joining, he reads back the exact appointment and his own recording-tool state. During the call, he checks whether an unexpected notetaker appears. These are separate observations, each useful for a different failure mode.

Know what removal and absence can actually establish
Fireflies' meeting FAQ lists calendar auto-join, an explicit calendar invitation and adding to a live meeting as distinct routes. It also documents botless recording through an extension or mobile app. That is why checking only the participant list cannot establish that every recording mechanism on your own devices is inactive.
The same FAQ says removing the bot ends transcription, but notes from the already recorded portion can still be received. Treat removal as stopping that bot's future participation, not as erasing the earlier portion. This article has not tested removal or deletion and does not establish anyone's data-retention outcome.
If your own bot unexpectedly appears, handle it openly through the meeting's available controls and permissions. If you cannot remove it, tell the host it is your notetaker and ask for it to be removed. Do not rename it to disguise its purpose or activate a botless recorder as a workaround.
That response is operationally different from changing next week's defaults. After the meeting, revisit the route that caused the attempted join so the same unresolved configuration does not carry into another appointment. If the bot returns, revisit the join routes instead of carrying the same assumptions into the next interview.
Keep a small, accurate record of your own preflight
A useful local record needs only the interview identifier you can recognize, the provider, the relevant controls and the time you checked them. Separate “read back off,” “planned change” and “unknown.” Do not attach a private invitation, attendee list or meeting URL to a public forum just to ask whether a bot will join.
For Julian, a truthful summary before the outstanding work is resolved would be: “Default off; domain rule and explicit invitation still need confirmation; no manual live addition planned.” That sentence is more useful than “Fireflies disabled” because it tells him what remains to do.
After an authorized change in his own account, the evidence would need to advance too. A saved plan or screenshot from last month cannot stand in for checking the current event. Likewise, a provider's generic help page explains a control; it does not show the state of his account.
Audit early, keep the interview appointment, and read back its event setting as well as the default. Keep your own notetaker out through the documented routes you control, while leaving employer-side recording questions to the interview instructions and organizer. Then return to preparing your experience and finding roles that fit your work.


