Assessment formats, tool policies and logistics

Why it matters

Candidates lose interviews for reasons unrelated to skill: practicing in one language and discovering the assessment expects another, preparing algorithms and meeting a pair-programming task in a large codebase, spending a weekend on a take-home meant to take a few hours, or using an AI assistant in a stage where it was not allowed. Each of these is preventable with a few questions and careful reading. Policies on outside tools vary widely: some companies publish stage-by-stage rules, some run programs that explicitly provide AI assistants, and others say nothing public. The only safe rule is to follow the written instructions for your specific process.

Core ideas

Formats and what they reward.

• Online assessments are timed and often auto-graded against hidden tests. Read the constraints first, match the input and output format exactly, handle edge cases, and submit a working partial solution early if partial credit exists.
• Take-home projects are judged on scope and quality together and are often followed by a discussion of your choices. Respect the time limit, include a README with assumptions, tradeoffs and how to run the tests, and keep the code reviewable.
• Live coding happens in a shared editor with or without execution, or in your own IDE over screen share. Without execution you must trace code by hand; with execution, run tests early and often.
• Pair programming means collaborating with an engineer on a realistic task, sometimes inside an existing codebase. Communication, reading code and steady progress matter more than a perfect final answer.
• System design uses a virtual whiteboard or a shared document. Practice drawing quickly in the tool you will use.
• Behavioral and project rounds have their own topics; ask whether they are separate rounds or folded into technical ones.

Tool and AI policies differ by company, program and stage. Anthropic's published candidate guidance, for example, encourages using AI to prepare and to refine application materials, but asks candidates to complete take-home assessments and live interviews without AI unless told otherwise. A CoderPad article describes a Meta pilot of AI-enabled coding interviews in which candidates have AI tools available; it describes one program, not a general policy. Treat the written instructions you receive for each stage as authoritative, and if they are unclear, ask in writing before the assessment starts.

What to confirm with the recruiter.

• Which rounds, in what order, how long each lasts, and whether they happen on one day.
• The level you are being assessed for, since it changes expectations in design and behavioral rounds.
• Which languages are allowed, and whether a specific language or framework is expected.
• The environment: which platform, whether code runs, whether autocomplete and documentation are available, whether you may use your own IDE.
• Tool permissions for each stage: AI assistants, web search, documentation, personal notes.
• Take-home rules: time limit, allowed libraries, AI policy, submission format, and whether a review discussion follows.
• Logistics: time zone, video platform, interviewer roles, breaks, travel for onsite rounds, and whom to contact if the connection fails.
• Accommodations: request them early through the channel the company names. Microsoft's technical interviewing page points candidates to an accessibility request, and Anthropic's guidance asks candidates to tell their recruiter early.

Environment rehearsal. Solve one practice problem on the exact platform or an equivalent setup, test camera, microphone and screen sharing, silence notifications, and keep a phone number for the interviewer in case video fails.

Common misconceptions

• "All companies treat AI the same way." Policies range from prohibited to explicitly provided, and can differ between stages of the same process.
• "If the instructions do not mention AI, it is allowed." Silence is ambiguous; ask in writing before you start.
• "A take-home should be polished like a product." Building far beyond the stated time can count against you; clear scope, tests and documented tradeoffs matter more.
• "Asking the recruiter questions looks unprepared." Recruiters expect logistics questions, and the answers shape your preparation.
• "Accommodations can be arranged at the last minute." Arrangements take time; ask at the start of the process.

How to approach it

When a process starts, send the recruiter a short list of the questions above and save the answers with your application notes. Read each company's official preparation and policy pages, rehearse once in the actual environment, and plan your preparation around the formats you will face. Re-read the tool policy before each stage, because a single process can have different rules for the take-home and the live rounds. If something goes wrong during an assessment, such as a crash, a broken link or an unclear instruction, tell the interviewer or recruiter immediately and in writing rather than working around it silently.