Mercor AI Interview: 3 Retakes, and Only the Last One Counts

The Mercor AI interview gives you three attempts and evaluates only the most recent one. That rule sits in Mercor's own application documentation, and most candidates find it after they have already burned a retake on a bad connection.

The second thing worth knowing before you click start: Mercor's interviewer decides you have finished speaking after roughly nine-tenths of a second of silence. Pause to think mid-answer and it starts talking over you. That number is not a rumour. It is published in Mercor's own engineering write-up on the system.

Most guides for this interview hand you a list of invented sample questions. Mercor publishes none, and the real questions are generated live from your resume, so those lists are fiction. What Mercor does publish is the machine: how the interviewer decides your turn is over, how many attempts you get, which one is scored, what you are allowed to use, and what a passing score is actually worth afterwards.

This guide covers all of that, plus the Mercor assessment that runs alongside the interview, the automated gate that can block your application before you ever reach the interview, and the one paid work trial you get in your lifetime on the platform.

What the Mercor AI interview actually is

Mercor's AI interviewer is called Monty. Mercor's engineering team describes around 10,000 conversations a day, one starting every nine seconds, across hundreds of job categories. Its docs put a typical interview at approximately 20 minutes; the engineering write-up describes fifteen. Take the wider range as your planning window.

Three formats cover 90% of Mercor's interview volume:

• Domain Expert. Over 70% of all sessions. Medicine, economics, history, law, software architecture, and essentially any other knowledge domain. If you are applying to AI training work, this is almost certainly the one you get.
• Code. A live coding conversation. The problem is generated fresh from your profile and the conversation as it happens, so a Go engineer and a Python engineer get different starter code, and a senior candidate gets a more open-ended problem than a new graduate.
• Language. Fluency and comprehension work for language and localisation roles.

Before the call starts, Mercor processes your resume, and in its own words that context shapes what gets asked, how deeply to probe, and what to skip. You are not being read a script. You are being interrogated about the document you uploaded.

Your video, audio and an AI-generated transcript are retained and attached to your profile. Mercor states it does not sell interview data and does not use it to train third-party language models.

The 900ms rule: why the AI keeps cutting you off

The single most useful number in this article. Mercor's interviewer runs a turn-detection model that decides when you have stopped talking. The production threshold is 900 milliseconds of silence, with a 120ms floor so mid-sentence breaths do not trigger it and a 1.6 second hard ceiling. Mercor says those values came out of A/B testing against session completion rates.

Once it decides your turn is over, it takes about 700 milliseconds to start speaking: roughly 150ms to detect the turn, 350ms to the first token from the language model, 200ms to the first audio.

Add those together and the practical rule is brutal. Somewhere between 0.9 and 1.6 seconds of thinking silence, and the interview moves on without you.

This is why Mercor's own candidate tips say extended pauses cause the AI to interrupt. It is not a bug and it is not impatience. It is a tuned parameter.

What to do with that:

• Narrate your thinking instead of doing it silently. "Let me think about the trade-off between the two" buys you the pause. Silence does not.
• Never pause before the substance. The dead second most people take between hearing a question and starting an answer is exactly the gap the model reads as a completed turn.
• Finish clean. Because silence ends your turn, trailing off mid-thought gets treated as a finished answer, and the follow-up will be built from an incomplete one.
• Use a headset. Mercor recommends headphones and an external microphone. Laptop speakers feeding back into a laptop microphone corrupt the same silence detection you are trying to work with.

If you have never spoken to a real-time voice AI under scoring conditions, this timing is the thing that will surprise you, not the questions.

Three attempts, and only the last one counts

Mercor lets you retake an official AI interview up to three times. Two details make that less generous than it sounds.

The cap is shared, not per job. Completed steps sync across every application that requires the same interview. That is convenient when you pass and expensive when you do not, because attempts are counted across all applications combined rather than resetting for each new listing.

Only your most recent attempt is evaluated. This is stated plainly in Mercor's application docs and it is the trap in the whole process. Retaking is not "best of three". A strong first attempt followed by a rushed second one leaves you holding the rushed one. If you already have an interview you were happy with, do not retake it to chase a marginal improvement.

If you burned attempts on a genuine technical failure, Mercor's docs say support can grant one additional attempt. Email support@mercor.com with your operating system, browser version, the interview name and screenshots.

There is one clean way to practise without spending an attempt, and it is the most underused feature on the platform.

The free practice interview nobody uses

Mercor offers a practice interview that is not tied to any application. You can take it as many times as you want. Mercor's docs confirm practice interviews are never shared with companies and do not affect future opportunities.

That makes it a free rehearsal against the exact system that will score you. Use it to check three things: whether your microphone and camera survive the session, how the 900ms turn-taking feels when you are the one talking, and whether your answers hold up when the follow-up comes from something you said thirty seconds ago rather than from a script.

Do the practice run on a different day from the real one. The point is to be bored by the format before it counts.

Where the Mercor AI interview sits in the funnel

The interview is one step of five, and two of the other four have rules that cost people money.

1. Application Fit Guidance. An automated compatibility check runs the moment you apply to a listing. Three outcomes: allowed, a warning you can ignore, or blocked. Blocked means you cannot submit at all, and Mercor states the feature does not permit manual overrides. A block affects only that listing, not your account. If you are hitting blocks, the fix is your profile and resume detail, not persistence.
2. The AI interview. Three attempts, latest scored, result synced everywhere and never expiring.
3. Assessments. Forms or recorded interviews, usually one submission only.
4. Work trial. A paid, one-time assessment on a project-like task before any contract, typically four to six hours. You are paid whether or not you are selected, within 7 to 14 days of review. The catch: Mercor pays for one work trial per person, ever, and accepting one invalidates every other trial offer you are holding. If two arrive, that is a decision, not a formality.
5. Contract. Hourly, remote, time tracked by software, with a rate published upfront.

Running alongside all of it: Instant Work Offers. When your verified interview scores, assessments, skills and availability match a listing, Mercor surfaces your profile to the hiring team as prequalified, and offers arrive for roles you never applied to. Your interview score is the asset that makes that happen, which is the real argument for treating one 20-minute call as seriously as you would a final round.

Mercor interview questions: what it actually asks

Mercor publishes no question bank, and any site claiming to list the real questions is guessing. What is knowable is the shape, because the shape follows from how the system is built.

Questions come from your resume. Every technology, method, client type and responsibility on the document is a candidate for a probe. Anything you cannot discuss for two minutes is a liability, not a credential.

Follow-ups come from your last answer. The model listens, picks the most probeable thing you said, and pushes there. Name a framework casually and you will be asked to defend it. This is the same mechanic behind micro1's Zara interview, covered in the micro1 AI interview guide.

Domain Expert interviews test judgment, not recall. The work Mercor is hiring for is grading and correcting model output in your field, so the interview probes whether you can tell a good answer from a plausible one and explain the difference. Expect to be asked how you would evaluate something, not just whether you know it.

Code interviews are generated live. A fresh problem built from your stack and seniority, discussed aloud while you write. Talking through your approach is not optional here, because silence ends your turn.

The reliable preparation is four or five stories from your own practice where you made a real call with real trade-offs, each one you can open in fifteen seconds and sustain for two minutes.

How to answer

The failure mode is narrating your resume. The interviewer already has your resume. Reading it back adds nothing and gives the model nothing new to probe.

A structure that survives the timing:

1. Answer in one sentence first. State the decision, position or conclusion before any context. If you are interrupted, the substance is already recorded.
2. Then the reasoning. What you considered, what you ruled out, and why. This is the part that separates practitioners from people who have read about the field.
3. Then one concrete detail. A number, a constraint, an outcome. Specifics are the difference between a transcript that reads as real practice and one that reads as generic.
4. Stop cleanly. Hand back the turn deliberately rather than trailing into silence.

Two more things. Mercor's docs tell you to have pen, paper and a calculator to hand, which is a hint about the interviews that involve reasoning through numbers. And captions are on by default, so you can read the question back if the audio is unclear rather than losing a second to confusion.

What you are allowed to use

Mercor's LLM usage policy is specific and worth reading before you rationalise anything.

Allowed: using an AI tool to check grammar and wording, as long as the ideas and structure remain yours.

Not allowed: using an LLM to compose your responses, to rate model responses, to generate rationales or explanations, or to predict code behaviour or runtime results. Mercor's stated position is that submissions evidently produced by AI are identified and flagged, and that it is generally apparent what a human wrote.

The consequences are in Mercor's account security and conduct policy: reductions or reversals of payment on affected work, removal from projects on repeat violations, and suspension in serious cases. Sign-ins through VPNs, proxies and anonymising services are reviewed. One account, in your own name, and the person hired is the person expected to do the work.

You are also asked to keep specific questions and screenshots confidential, which is the other reason the question lists you find elsewhere should be treated with suspicion.

Technical setup, in one pass

• Chrome, latest version, on a desktop. Edge and Safari are supported. Firefox and mobile browsers are not.
• Camera and microphone tested before you start, with your full face visible.
• Headphones and an external microphone. Recommended by Mercor, and they protect the turn-taking.
• A quiet room. Background speech is competing input to a system listening for the end of your turn.
• Full-screen sharing only where an interview requires it. Sharing a single window is not supported.
• Pen, paper and a calculator within reach.

The Mercor assessment, and how it differs

The secondary half of most applications is an assessment: a written form or a recorded interview that evaluates your skills, judgment and ability to follow instructions on tasks resembling real project work.

Two rules invert what you learned about the interview:

• Most assessments permit only a single submission. No retake, and once submitted the form usually reopens read-only.
• Where retakes do exist, the highest score is retained, not the most recent. The opposite of the interview rule.

Most assessments have no strict time limit, so finish in one sitting rather than racing. AI tools, copying external content and collaborating with others are all prohibited, and copy and paste is disabled on some. Mercor staff cannot review drafts or coach you. Passed assessments, like interviews, are reused for compatible roles.

What your score is worth afterwards

Mercor's docs say you should hear about advancement within two to four weeks, and that detailed feedback on rejections is not provided because of application volume. Applications also age off your dashboard within a few weeks once processing concludes.

The honest caveat is the one covered in full in the Mercor review: a good interview score is necessary and nowhere near sufficient. Mercor's 2026 security update referred to nearly five million experts on the platform while its homepage advertises a network of 30,000-plus. Matching is driven by client demand for your specific profession, and no interview performance creates demand that is not there. Prepare properly because the score is permanent and reused, not because it guarantees work.

That review also covers the November 2025 Meta project pay cut and the March 2026 supply-chain breach, both of which you should read before uploading identity documents.

The same interview, elsewhere

The format is spreading, and preparing for one prepares you for most. All five gates in this market are compared in how AI training platforms screen you.

• micro1 runs Zara, a conversational AI interviewer, followed by a proctored coding assessment with gaze and tab-switch detection. Its published research also shows your resume predicts far less there than your live performance does. See the micro1 AI interview guide and the micro1 review.
• HireVue is the enterprise version most large employers use, and its scoring model differs in ways worth knowing. See the HireVue interview questions guide.
• Alignerr, Outlier and DataAnnotation screen differently, with the entry bars and pay bands compared in the best AI training jobs roundup and in the Alignerr review, Outlier AI review and DataAnnotation review.

Live Mercor listings with published rates sit on the Mercor jobs page, and the wider AI training jobs board collects openings from Mercor, micro1, Alignerr, Outlier, DataAnnotation and Terac into one feed.

Rehearse the format, not the answers

Mercor's practice interview tells you whether your setup works. It does not tell you whether your answers are any good, because it does not score you and Mercor gives no feedback on the real one either.

That is the gap worth closing before you spend attempt one of three. Running a scored mock interview with a live AI interviewer costs an evening and puts you in the same conditions: a voice asking follow-ups built from what you just said, a clock, and no second chance to phrase it better. If your last interview was a human being across a table, or your recent experience is task queues rather than conversations, one rehearsal changes what your permanent Mercor score is worth.

Verdict

The Mercor AI interview is not a hard interview. It is an unfamiliar one, and almost everything that goes wrong is mechanical rather than intellectual.

Take the free practice run first. Do your thinking out loud, because a second of silence ends your turn. Answer with real decisions from your own work rather than the contents of your resume. And treat the retake cap as what it is: three attempts, most recent scored, one shared pool across every job you will ever apply to on the platform.

Get it right once and the score follows you to every listing on Mercor without you sitting another interview.