Products › Conversational Chat Interview
It reads like
a conversation.
Open-ended text rounds with adaptive follow-ups
No clock and no answer key — a real back-and-forth in writing. A thin answer draws a follow-up, a strong one gets pushed further, and how somebody writes under a prompt is the thing being assessed.
Blind assessed. AI-generated answers flagged as they arrive.
assets/conversational-interview-demo.mp4 — 16:9, 1920×1080, H.264. Autoplays muted on loop; keep it under roughly 8 MB and 30 seconds.An open round, a follow-up nobody scripted, and a flagged answer.
A follow-up is where
a rehearsed answer breaks.
Anybody can prepare a good answer to a predictable question. Very few can hold it up when the round asks what happened next, who disagreed, and what they would do differently. That second question is what this round is for.
- Follow-ups are drawn from your own set, selected when an answer is thin or unspecific. So the round goes deeper without inventing a question nobody signed off.
- Thinking time is a feature, not a loophole. A candidate who freezes on camera and writes clearly is somebody you would otherwise never have seen.
- Written communication as the actual skill. For support, documentation, legal, marketing and any remote-first role, this is the job rather than a proxy for it.
- Blind by construction. No name, no photograph, no accent, no appearance, no age cue — because none of them are on the review screen to begin with.
- This is where detection matters most. An open, untimed written question is the easiest thing in the world to hand to a model, so flagging runs live and shows its reasoning.
- The same rubric as MCQ and timed rounds, so a conversation score and a knowledge score sit on one axis.
Round in progress — support engineer
no names, no specifics, register shift from the answer aboveFlagged
Ask. Read. Ask again.
Five stages, and the third one is the reason this round exists. Identity is settled first so everything after it is about the answers.
What the Conversational round does
Follow-ups that were not scripted, but were not invented either+
Blind by construction, not by policy+
Detecting an answer a model wrote+
Identity and documents, collected first+
Scoring, with the excerpt attached+
Pipelines, leaderboards and evaluation+
A flag is not
a verdict
Detection is the most consequential thing on this page, so it is the one with the most restraint built around it.
A human makes the call
It ranks, evidences and flags. It does not reject anyone. A flagged answer is surfaced with its reason for a person to judge, never auto-removed from a pipeline.
One AI gateway, no loose ends
Every model call passes through a single choke point with schema validation, caching, per-tenant rate limits and spend caps. There is no second path to a provider.
Blind is the default state
Identifying detail is absent from the assessment screen rather than hidden behind a toggle somebody can switch off on a busy afternoon.
And plainly. No detector is perfect, and we publish no accuracy figure for this one — a percentage from somebody else’s dataset tells you nothing about your applicants. That is exactly why a flag carries its reasoning and never acts alone: the cost of a false positive is a person losing a job they were qualified for. Because this round has no time limit, a candidate can research, draft and revise — which is appropriate when you are assessing written work and wrong when you are assessing recall, and Timed Q&A is the instrument for the latter. A text round also cannot assess spoken fluency or presence; that is what the Voice and Video rounds are for.
Frequently asked questions
Does the AI make up its own follow-up questions for candidates?+
How are the written answers scored, and can I compare them with MCQ or timed test results?+
Can it detect answers a candidate wrote with an AI model?+
How accurate is the AI-written-answer detection?+
Does the reviewer see the candidate's name or photo when marking answers?+
When is a text-based interview the wrong format to use?+
Published 9 September 2026 · Updated 9 September 2026 · Written by the TalbotIQ team
