Prep for the in-person interview that proves you can think without AI

You may pass an AI-assisted remote interview and still fail the in-person whiteboard round because the proof changes. The in-person round is where you show you can reason without help.

A recent Gartner survey found that 72.4% of recruiting leaders said they were conducting interviews in person to reduce candidate fraud. During the past year, Google, Cisco, and McKinsey & Co. brought back in-person interviews for some candidates. Some job candidates use off-camera AI tools to receive interview answers and, in some cases, use deepfake technology to impersonate applicants.

Fabric, an AI interview platform, ran 19,368 AI-powered interviews between July 2025 and January 2026. Its analysis identified cheating behavior in 38.5% of candidates in its AI interview dataset. For software engineering candidates, Fabric's data showed a 48% cheating rate. CodeSignal's proctored assessments showed cheating and fraud attempts increasing from 16% in 2024 to 35% in 2025.

The round type changes the answer

Before you practice, identify whether the round is remote and AI-allowed, or in-person and unassisted. The same question can require different proof: a remote round may show tool use, while an in-person round must show unassisted reasoning.

Ask the recruiter which tools are allowed, whether code completion is on, and whether you will explain reasoning out loud. If unclear, plan for the stricter version. The safer default is to narrate every step. You are ready when you know the tools and what the interviewer will listen for.

Remote rounds reward fluent tool use

For AI-allowed remote rounds, your job is to direct a tool, not hide behind it. Use the same sequence: prompt with constraints, verify the draft, and explain the reasoning out loud.

Do not let the tool answer the behavioral question. If the prompt produces a polished story, own the decision, tradeoff, and result. Keep a short list of prompts for your role. For data work, request a query structure and check assumptions. In consulting, stress-test the framework before recommending it. In engineering, verify edge cases after asking for a scaffold.

In-person rounds reward narrated reasoning

Whiteboard prep should feel slower and messier than a polished remote answer. The interviewer is listening for how you think, not just whether you reach the right answer. Practice saying the parts you would normally skip: your choice of data structure, the rare edge case you ignored, and the clarification you would ask for before coding.

The round is a conversation, not a performance of speed. You want the interviewer to follow your path through pauses, rough edges, and the choices you would ignore first.

Run the two-mode checklist this week

• Remote AI-allowed: prompt with constraints. State role, audience, data limits, and output format before asking for a solution. Done looks like a defensible draft, not a generic essay.
• Remote AI-allowed: verify the draft against the problem. Check edge cases, missing assumptions, and claims that need a source. You are done when you can point to what you would test before sending it to a stakeholder.
• Remote AI-allowed: explain the reasoning out loud. Summarize what you asked, what you changed, and why the final answer fits the business question. The result is a brief explanation a non-technical interviewer can follow.
• In-person unassisted: narrate the problem before solving it. Say what you know, what you assume, and what you would ask if you could. Done looks like the interviewer can follow your path even when you pause.
• In-person unassisted: constrain the solution. Pick the smallest useful version, name tradeoffs, and say what you would ignore first. You are done when scope is clear and ignored options are named.
• In-person unassisted: defend the choice with autocomplete off. Turn off code completion or note-taking apps, then walk through the logic step by step. The result is a clear explanation of a flaw, given without prompting.

Set a short block this week and run each mode back to back. Start with a remote-style question using notes and a tool, then switch to an unassisted question with nothing open except a blank page. Use a question from your last application, a common role-based problem, or a past interview that felt hard.

Record the unassisted round if you can. Listen for the moments you stop explaining, jump to code, or assume the interviewer knows your next move. Fix the habit that hurts most before your next interview.