Interview questions an AI can’t answer for them

An AI assistant thrives on questions with stable, general answers — definitions, stock behavioral prompts, classic coding puzzles. It has nothing to retrieve when the answer lives in the candidate’s own history two levels deeper than their résumé, or in the live thread of this conversation, or in a position they must now argue against. Every pattern below moves the answer into that territory. The questions aren’t trick questions — they’re better questions, and honest candidates tend to enjoy them.

Build each follow-up from a specific detail in their previous answer. A tool only knows what the candidate relays to it, and relaying your question plus their own earlier details takes audible time.

• “You said the migration slipped two weeks — walk me through the day you realized it would slip.”
• “Earlier you called the queue ‘the wrong tool’. What would have made it the right one?”
• “You mentioned a teammate owned the rollout — what did they do that you wouldn’t have done?”
• “Go back to that number you gave me. How was it measured, and what would make you distrust it?”

Put their real work on screen — code they wrote, a doc they shipped, a deal plan — and ask questions only its author can answer fast:

• “What would you change in this file today, and why didn’t you write it that way then?”
• “What breaks first here if usage grows ten times?”
• “Which part of this do you like least? Defend keeping it anyway.”

Don’t set a problem and sit back — evolve it. Scripted answers fracture when the ground moves:

• “Good. Now the API is rate-limited to ten requests a second — what changes?”
• “Make the strongest case against the design you just proposed.”
• “I’ll play the stakeholder who says no. Convince me — I’ll push back for real.”
• “We’re halfway through and the requirement just changed: it must work offline. Where do you restart?”

Ask for the sensory, social texture of their stories. It’s where generic answers go to die:

• “Who pushed back on that decision, and what did they actually say?”
• “What would your manager say you got wrong in that project?”
• “What did you change in the next project because of that failure?”
• “What’s something your team believed that turned out false — and how did you find out?”

Nothing makes an interview literally AI-proof — a determined candidate can relay anything. The goal is to raise the cost of faking until the seams show: the latency, the depth cliff two follow-ups in, the register change. Pair these patterns with the detection signals so you notice the seams, keep the role fundamentals from the role question sets so the interview still measures the job, and score follow-up depth on your scorecard, not first-answer polish. For the wider context, see AI cheating in interviews.

Every pattern on this page leans on remembering the candidate’s exact words while planning your next move. That’s the job incogno does: a live transcript of their answers beside your question kit, visible only to you, with no bot in the call — so “go two levels deeper on what they just said” stops being a memory test. See the AI assistant for interviewers.