Accommodations, Accessibility, AI, and Tool Policies

Process controls

Policy-sensitive mechanics should be explicit before the interview starts.

This chapter covers four related areas: accommodations, accessibility needs, AI-assisted tools, and general tool permissions. The shared principle is simple: do not guess. Ask the recruiter, coordinator, or HR contact for written instructions that apply to your interview process. Keep those instructions available during the loop.

The process controls:

• accommodation requests and instructions;
• accessibility needs for remote and onsite interviews;
• permitted and prohibited tools;
• AI assistant, autocomplete, search, documentation, note, and recording policies;
• written confirmation of special instructions;
• day-of escalation path when the setup does not match the written plan.

The senior behavior is neither hiding needs nor improvising around ambiguous rules. It is clarifying the operating constraints early and following them.

Inputs, outputs, and constraints

Inputs

Gather the facts that affect access and policy compliance:

• interview format, round types, durations, and tools;
• whether rounds are remote, onsite, or mixed;
• coordinator, recruiter, HR, or accommodations contact;
• written tool policy, if provided;
• written accommodation instructions, if applicable;
• platform requirements such as browser IDE, shared document, video call, whiteboard, or company laptop;
• restrictions on AI assistants, autocomplete, documentation, search, notes, recording, screenshots, and communication with third parties;
• accessibility needs related to audio, video, captions, screen readers, keyboard use, lighting, breaks, mobility, timing, environment, or assistive technology.

Outputs

Before the interview, you should have:

• written confirmation of any approved accommodations or process adjustments;
• written instructions for AI and tool usage;
• a setup that follows those instructions;
• a short script for clarifying uncertain policies;
• a contact path if the day-of environment does not match the agreed setup.

Written does not need to be elaborate. A recruiter email that confirms the rule is usually far better than a memory of a phone call.

Constraints

Do not make company-specific assumptions. Different employers, teams, jurisdictions, vendors, and interview formats may use different rules. A policy from a previous interview does not carry over to the next process.

Do not assume that a common tool is allowed because it is installed, convenient, or widely used in daily engineering work. Do not assume that a tool is forbidden because another company forbade it. Ask for the rule that applies to this process.

Do not disclose private medical or personal details beyond what the official process requires. Ask the recruiter or HR contact how to submit accommodation information and what documentation or instructions they need.

Workflow and cadence

When scheduling begins

Ask for the operational rules early, especially for coding, practical engineering, and remote rounds.

Example:

“Could you send the interview tool policy in writing? I want to confirm what is allowed for editor choice, autocomplete, documentation, search, notes, AI assistants, and recording.”

If you need an accommodation or accessibility adjustment, ask for the correct process rather than negotiating details informally with an interviewer.

Example:

“Could you direct me to the right recruiter, HR, or accommodations contact for interview accessibility arrangements? I would like to make sure any instructions are confirmed in writing before the loop.”

After receiving instructions

Translate the instructions into setup decisions:

• turn off tools that are not allowed;
• use the specified editor or platform;
• prepare allowed notes only;
• verify captions, audio, keyboard, screen reader, magnification, timing, break, or room needs;
• save the written instructions somewhere reachable;
• ask follow-up questions for ambiguous wording.

If the policy says “no AI tools,” disable AI assistants, chat panels, agent extensions, and AI autocomplete in the interview environment. If the policy permits limited tool use, clarify the boundary before relying on it.

One day before

Run a compliance and accessibility check:

• open the exact browser profile, editor, IDE, or machine you will use;
• confirm disallowed extensions are disabled;
• confirm allowed assistive technology works with the platform;
• verify captions or audio settings if needed;
• prepare approved notes or materials;
• place written instructions and contact details where you can access them without searching.

During the interview

If the environment matches the instructions, proceed normally. If it does not, name the mismatch factually and ask for the agreed path.

Example:

“My recruiter confirmed in writing that I would have captions for the remote rounds. I do not see them enabled in this meeting. Could we enable them before starting, or should I contact the coordinator?”

For tool ambiguity:

“Before I use browser documentation, I want to confirm whether that is allowed in this round. The policy I received allowed language documentation but not AI assistants.”

Do not surprise the interviewer with undisclosed tools. Do not ask the interviewer to improvise an accommodation process if the company gave you a recruiter or HR path. Use the written path.

Decision points and trade-offs

Asking early versus waiting

Ask early when the answer affects setup, access, timing, or tool configuration. Waiting until the round starts can force the interviewer to resolve process questions while the interview clock is running.

Disclosing needs versus oversharing

You may need to describe the adjustment required for the interview process. You usually do not need to provide a full personal history to an interviewer. Use the official recruiter, HR, or accommodations channel and follow their instructions.

Useful phrasing:

“For interview access, I need captions enabled and written prompts available in the shared document. Please let me know the required process for confirming that.”

Convenience tools versus clean compliance

Many tools that help in daily engineering can create ambiguity in interviews. AI autocomplete, coding agents, chat assistants, grammar assistants, search, personal snippets, private notes, and pair-programming tools may be treated differently by different processes.

When unclear, choose the lower-risk path:

• ask for written clarification;
• disable the ambiguous tool until clarified;
• state what you are using when relevant;
• keep the environment auditable and simple.

Interviewer permission versus official policy

An interviewer may casually say a tool is fine, but the recruiter policy may say otherwise. If there is a conflict, pause and clarify through the official contact path. Do not put yourself or the interviewer in a position where the process can be challenged later.

AI use versus authentic signal

If AI use is allowed in some form, treat it as a tool you must operate transparently within the rule. The interview is still about your judgment, problem framing, validation, and communication. Do not let a tool produce work you cannot explain, test, or defend.

Worked scenario

You are scheduled for a remote practical coding round. The invite says “use your preferred editor,” but says nothing about AI autocomplete or documentation.

Five days before, you email the recruiter:

“For the practical coding round, could you confirm the written tool policy? Specifically: local editor, autocomplete, AI coding assistants, browser documentation, search, personal notes, and whether recording or screenshots are prohibited.”

The recruiter replies:

“You may use your local editor, standard language/library documentation, and your own brief notes. Please disable AI coding assistants and do not record, screenshot, or use third-party help during the interview.”

You save the email. The day before, you create a clean editor profile with AI extensions disabled. You keep only brief notes visible. During the round, the interviewer asks why autocomplete is not suggesting as usual. You answer:

“The policy I received allows standard editor use but asks me to disable AI coding assistants. I am keeping the environment simple and will use language documentation only if needed.”

You have avoided ambiguity without making the tool policy the center of the round.

Failure modes

Common failures:

• assuming AI tools are allowed because they are part of the normal editor;
• assuming documentation or search is allowed without checking;
• relying on a verbal policy that was never confirmed in writing;
• waiting until the round starts to request a needed accessibility adjustment;
• sending sensitive accommodation information to the wrong person instead of asking for the official process;
• over-disclosing personal information to interviewers who do not need it;
• forgetting to disable prohibited extensions, agents, or background tools;
• using private notes that look like prepared answers to the live prompt;
• recording, screenshotting, or sharing interview content without explicit permission;
• treating one company’s policy as a general industry rule.

Red flags an interviewer or process owner may notice:

• “The candidate used tools that were not approved.”
• “The candidate surprised the interviewer with a process issue that should have been handled before the round.”
• “The candidate’s environment made it hard to tell what work was theirs.”
• “The candidate did not follow the written instructions.”

Readiness checklist and rubric

Practice actions

Field reference

Related reading

• Chapter 19: The Six-Phase Response Loop
• Chapter 20: Asking High-Value Clarifying Questions
• Chapter 23: Handling Hints, Corrections, and Disagreement
• Chapter 25: Communicating Trade-Offs Like a Senior Engineer