It turns on one thing, and it is not your diagnosis: whether the employer has stated a rule. Where none is stated, as in most unproctored live conversations, captions, notes and a glanceable on-screen prompt sit inside what candidates have always been allowed to bring. Where the instructions say no outside assistance, as on a proctored assessment or inside a lockdown browser, a disability does not turn a prohibited tool into a permitted one, it turns it into an accommodation you request in advance. The table below makes that call across five contexts and gives you the sentence to send in each.
This is disclosure wording, not legal advice. In the United States the ADA covers the application process, not only the job, and in the UK the Equality Act 2010 uses the language of reasonable adjustments. Both are built around the barrier and the change that removes it. Neither gives anyone a unilateral right to ignore a stated assessment rule, which is exactly why the request has to be made before the assessment rather than explained afterwards.
There are three rule states, not two
Most of the anxiety in this question comes from collapsing three situations into one. They behave completely differently.
- Explicitly permitted. Common on take-homes now, usually phrased as "use whatever tools you normally use, and expect to explain every line". The only thing that matters here is whether you can defend and modify the output live. Disclosure is a courtesy line, not a confession.
- Silent. Most behavioural and conversational rounds. Silence is not blanket permission, but it is not a prohibition either, and reading it as one is why people over-disclose things nobody asked about. Notes, a printed prompt card and live captions have never needed announcing. A tool that composes the substance of your answer is a different category and deserves a separate decision.
- Explicitly forbidden. Proctored assessments, secure browser exams, many timed platform tests. The route is the accommodation request. No version of this page tells you to route around a stated rule quietly, because the outcome of that is an offer that can be withdrawn later.
The five contexts, decided
Column two is the default before you find any written rule. If you find one, it wins. Column four is what to actually say or send, and in three of the five rows the answer is that you say nothing to the interviewer and everything to the coordinator, days earlier.
| Context | Is assistance appropriate | What actually constrains you | What to say up front |
|---|---|---|---|
| Unproctored live interview Zoom, Teams or Meet, human interviewer, no stated tool rule |
Yes for captions, notes and a short prompt. Treat anything that writes the substance of an answer as a separate call you make deliberately, not by drift. | Not software. A person listening. A four second silence followed by a fluent, evenly paced paragraph sounds like reading, and eyes tracking a second region of the screen are visible on webcam. | Nothing for notes. For captions, one line at minute zero: "I use live captions, so I may pause a beat before I start answering." If you are asked directly whether you are using AI, say what you use and why in one sentence. A denial that is later contradicted costs far more than the disclosure would have. |
| Take-home assignment Coding exercise, case study or written task with a deadline |
Usually yes, and often stated outright in the brief. Read the README and the invite email before assuming in either direction. | The follow-up call, not the submission. You will be asked to explain a decision and change the code while someone watches, so anything you cannot defend is a liability you shipped yourself. | Three lines at the bottom of the README: which parts were AI assisted, what you changed by hand, what you would do differently with more time. Your accommodation ask here is rarely about tools, it is the calendar: "Could I return this by Friday rather than Wednesday, with the same scope?" |
| Recorded one-way video Fixed think time, capped retakes, no human present |
For preparation, yes. Live, no, in practice. The format is built to catch reading, and the camera is pointed at your eyes for the whole answer. | Think time, retake limits and eye movement. Some setups also record the screen or require the camera on, and that varies with how the employer configured the job rather than with the platform name, so check your own invite. | Nothing to the machine. Email the coordinator before the invite link is issued: longer think time, more retakes, the questions supplied in writing, or a live call in place of the recording. The swap to a live call is granted more often than people expect, because it costs the employer half an hour. |
| Proctored assessment Webcam and screen recording, focus and tab-switch logging |
No. The instructions say no outside assistance, and that settles it regardless of what the monitoring can or cannot detect. | The rules first. Then webcam monitoring, screen recording, focus logging and sometimes a second-device camera, none of which are touched by a tool hiding itself from screen capture. | Nothing during. Before: ask the recruiting coordinator for extended time, a rest break that pauses the clock, or screen reader compatibility, and ask for it to be applied to your invite. Name the platform in the email, because that setting usually lives on the invite and cannot be granted once the timer is running. |
| Lockdown or secure browser Kiosk mode exam, often with a room scan first |
No, and mostly not even possible. The software takes over the machine and blocks other applications by design. | The environment and the rules at the same time. A room scan, a locked desktop, and a supported-software list that was decided before you arrived. | Ask the testing or accommodations contact, not the interviewer, and ask a list question: "Which assistive software is supported inside your secure browser?" Screen readers and magnifiers are frequently supported explicitly. General purpose assistants are not. Allow several days, since approval often routes through the proctoring vendor rather than the employer. |
Ask in this order, and before the invite is generated
Find the rule text before you ask anything
The invite email, the platform instructions page, the take-home README, the "before you begin" screen. Screenshot it. Plenty of these requests ask permission for something the brief already granted, and asking makes it look contested when it was not.
Name the barrier, not the tool
"I need to use software X" invites a security review. "I take in questions more accurately when I can read them as well as hear them" invites a solution. Sort your barrier into one of four buckets: input, processing time, output, or recall. The ask follows from the bucket.
Send it at scheduling, to the coordinator
Extended time, accommodated sessions and captioning are settings applied when your invite is created. Once the link exists someone has to reissue it, which is a second approval and another day.
Ask a list question, not a yes or no
"Is assistive software allowed?" gets a cautious no from someone protecting a process. "Which assistive software is supported during the proctored portion?" gets a list, and the list is the only thing you can rely on in the room.
Get it in writing, then re-confirm at 24 hours
The common failure is not refusal. It is a granted adjustment that never reaches the panel or the platform settings. One short reply the day before catches most of them.
Subject: Interview adjustment request, [Role], [assessment date]
Hi [Name],
Thanks for setting this up. Before the assessment invite goes out, I would like to request an adjustment. Is there an accommodations contact I should copy, or are you the right person?
I process written questions considerably more accurately than spoken ones, and I need longer to type than most candidates. For the [platform] assessment, could extended time be applied to my invite? I understand this normally has to be set before the link is generated, which is why I am raising it now. Second, which assistive software is supported during the proctored portion? I would rather work inside your supported list than guess at it.
Happy to provide whatever documentation your process requires.
Best regards,
[Your name]
Notice what that email does not do. It never names a product and it never argues about detection. It puts the supported-software question in writing, so the answer becomes something you can point at later. If the reply is a flat no with no alternative offered, you still hold a record of a specific request and a specific refusal.
What screen capture exclusion does not do
This needs saying plainly, because the marketing in this category is routinely dishonest about it. The OfferPilot AI overlay is excluded from screen capture at the operating system level, so it does not appear in Zoom, Teams, Meet, OBS or a screenshot, while staying visible on your own monitor. That is a privacy property. It is not an anti-detection property, and the gap between the two decides three of the five rows above.
- It does nothing about a webcam. Eye movement, head angle and the pause before a suspiciously fluent answer are visible to a human reviewer and to camera-based monitoring.
- It does nothing inside a lockdown browser. A secure browser is not trying to photograph your screen. It is trying to stop other software running at all, and it controls the machine while it does so.
- It does nothing about a proctor watching you in person, eye tracking, or a phone propped up as a second camera.
- It does not change what the rules said. Whether a tool shows up in a recording has no bearing on whether you were permitted to use it, and permission is the question an employer asks afterwards.
Where this is the wrong tool
We sell a live assistant, so here is the boundary drawn honestly. A copilot helps with retrieval and comprehension speed, the moments where the answer exists but will not assemble quickly enough. It is a poor substitute for four other things.
- It is not a substitute for a granted adjustment. If your barrier is that spoken questions arrive too fast, the fix is the questions in writing. Reaching for software instead means walking into every future round with the same unsolved problem and no record that you ever raised it.
- It is not a screen reader. If you need a screen reader, a magnifier or a switch input, use the assistive technology built for that job. It is also the category most likely to appear on a supported-software list, which matters in exactly the contexts where a general purpose assistant is refused.
- A second stream of text competes for attention. For some people a written prompt steadies them, for others it becomes a third participant in the conversation. Find out on a mock, not on a final round. Holding
Pghosts the overlay andCtrl+Alt+Hhides it. - Windows 10 and 11 only. No macOS, no Linux, no mobile, no browser extension. If your interview machine is a MacBook this is not an option at all, and no amount of accommodation wording changes that.
Where it does earn a place is the unproctored live round, and the preparation that precedes every other kind. Interview Copilot transcribes the interviewer on device with Whisper and drafts a speakable answer grounded in your own resume in roughly a second, which is the difference between a usable prompt and a pause everybody hears. The company Q&A generator turns "prepare for the interview" into a finite list you can drill in an evening, and the meter counts listening time only, so rehearsing in silence costs nothing.
Related guides
- ADHD Interview Accommodations: 9 Asks and the Exact Wording
- Interview Accommodation Request Emails: 6 Copy-Paste Templates
- Job Interview With a Stutter: Disclosure and Accommodations
- Deaf Interview Accommodations: CART vs Captions vs Interpreter
- Dyslexia Coding Interviews: Cutting the Reading Bottleneck