The AI-Only Interview Invite, Scored to Complete, Request a Human, or Decline

An employer has invited you to an interview a bot runs and grades with no human present, and you have to decide: do it as-is, push for a human or an alternative format, or walk. This guide is for a candidate holding one such invite right now. It gives you a scoring model that weighs your pipeline against the rights you can actually invoke, so you choose on evidence, then hands you the written request to send.

Most of what is published on this sits on the employer's side of the table (how to fix pipeline drop-off) or reports that candidates are quitting. Neither scores the invite in front of you. This does.

What you are actually deciding

You are choosing among three verdicts for one invite: complete it as presented, request a human interviewer or an accommodation, or decline. The right choice turns on two things that pull against each other - how much the pipeline is worth to you, and which rights the role's location lets you invoke.

The decision is not "do I like AI interviews." Only 19% of candidates say they want less AI overall, yet 38% of US candidates withdrew from a process because it included an AI interview. That gap is the whole problem. People are not walking from the technology; they are walking from non-disclosure, from no human recourse, and from the sense that an undisclosed model is grading them against criteria they cannot see. Score those specifics, not the mood.

This is now the default gate, not an edge case. So the skill you need is not avoidance. It is a fast, repeatable read that tells you when to comply, when to push, and when the push is free.

The leverage that sets your floor

Your leverage is the single variable that decides how much a refusal costs you, and it correlates almost perfectly with whether you face the one-way gate at all. Score it first, because it sets the floor under every other dimension.

The pattern in the data is blunt. In Enhancv's survey, earners over $200k abandon AI interviews at 17.5%, about half the rate of every other band. They walk cheaply because they rarely face the bot in the first place - scarce talent gets routed to concierge pipelines and human screens. Abundant talent gets the machine. The junior and sub-$100k cohorts face the gate most and absorb the cost when they refuse: 36% of 18-24s and 35% of 25-34s have given up at least one AI screening, against 21% of those 55 and over.

Refolk's index puts a number on why the junior band has so little room. In Refolk's index of professional profiles, there are 365,273 US software, backend, and full-stack engineer profiles at the entry-level band, with Google, Figma, and Microsoft among the top current employers. That is a vast, interchangeable supply pool. When the queue behind you is that deep, a refusal reads as self-selection out, not as a stand.

Leverage is the real decision variable, not preference. Scarcity routes you to humans; abundance routes you to the bot.

An honest limit: I could not produce a clean seniority or cross-country comparison from the index on this pass. The senior-band US and senior-band Germany variants of the same title set returned no populated records, so treat the entry-level figure as a floor marker, not a full distribution. Where you sit against it, you can judge from your own offer history and inbound.

The scoring model, dimension by dimension

Score the invite across six weighted dimensions, total the points, and read the band below. Each dimension is phrased so that a worse situation for you scores higher, and a higher total pushes you from complete toward decline. What each dimension proves - and what it looks like when it lies - matters as much as the number.

Weight each dimension 0 to 3 of its cap, then sum. The bands:

• 0 to 6: complete. Disclosure is present, a human can override, and your leverage is low. Pushing buys little and risks the pipeline. Do it as-is and move on.
• 7 to 11: request a human or accommodation. At least one real gap exists and you have a right or an ADA route to invoke. This is the modal verdict. Send the written request in step 5 before you record.
• 12 to 15: decline, or request then decline. Multiple gaps stack and either your leverage is high enough to walk cheaply or the role involves undisclosed monitoring with no recourse. If a statute applies, send the request first so your walk is documented.

The matrix is the shortcut when you do not have twenty minutes. Place the invite in a quadrant from two reads - your leverage and your rights - and the action follows. The full score is for when the quadrant is a tie.

The rights you can actually invoke, by jurisdiction

Which rights attach depends entirely on the role's posted location, not yours, and on whether the stage is "solely automated." Fix the jurisdiction before you draft anything, because the wrong statute names the wrong right and the employer will ignore it.

A few operating notes the table cannot hold. Illinois AIVIA applies when AI analyzes recorded video: it requires notice, an explanation of the AI, and written consent before analysis, and on request the employer must delete all copies within 30 days and instruct recipients to delete theirs, reaching cloud storage, the vendor's copies, and downstream backups including AI vendor training data. NYC LL 144's notice must tell you that you can request an alternative selection process or an accommodation, and it turns on job location, so a fully remote role tied to a NYC office is in scope even if the employer has no other city presence. The EU AI Act bans workplace emotion recognition from 2 February 2025, with high-risk employment obligations from 2 August 2026, and GDPR Article 22 runs in parallel, giving the right to human intervention, to express your point of view, and to contest a solely automated decision.

This classification is the hinge. Employers add nominal reviewers precisely to escape Article 22. The ICO and EDPB counter that human involvement must be substantive and capable of influencing the outcome; the sequencing of human and AI factors is crucial. Under NYC LL 144, a tool that scores or ranks you is more likely in scope than a filter that only checks a credential. So your test is specific: ask who can override the score and whether they see your full interview or just the number.

Run the procedure

Work the invite through seven steps in order. The first four produce a verdict; the last three execute it. Budget roughly an hour for a contested invite, less once the model is familiar.

The order is load-bearing. Classification (step 3) has to precede scoring (step 4), because the automation call changes which jurisdictional rights are even available. And the deletion clock (step 6) only runs once something was actually recorded and analyzed, so it follows the interview or the documented refusal, never precedes it.

The written request, ready to send

The request that works names one right, asks one question that forces a classification, and sets a response window. Vague "can I speak to someone" emails get deflected; a request that cites the statute and asks who can override the score gets escalated. Adapt the template to your jurisdiction.

Subject: [Role] interview - format question and request

Hi [name],

Thanks for the invitation to interview for [role]. Before I complete the assessment, two things.

First, could you confirm whether a member of your team reviews the full interview and has authority to reach a different conclusion than the automated score, or whether the score itself advances or rejects candidates? I want to understand how the stage is evaluated.

Second, [choose one]:
- I'd like to request an alternative selection process for this stage, as provided for in the notice. [NYC LL 144]
- I'd like to request an accommodation: a live interview with a human reviewer in place of the automated format. [ADA]
- Please confirm what the tool assesses and that I have consented before any recorded analysis. [Illinois AIVIA]
- Please confirm the human oversight applied to this decision and my right to contest it. [EU / GDPR Article 22]

Happy to find a time that works. Could you let me know by [date, 3-5 business days out]?

Best,
[name]

Two things make this land. The opening question forces the employer to state whether the stage is solely automated, which is the fact your whole score hinged on. And the ADA route, where it applies, is often the lowest-friction path to a human: the request can be oral, needs no words like "disability" or "accommodation," and the employer must provide an alternative testing format or more accurate assessment unless doing so is an undue hardship - a bar the EEOC calls very high. If a third party runs the tool, the employer is expected to have that vendor forward accommodation requests promptly.

How this goes wrong

The scoring model fails in predictable ways, and each failure flips a verdict. Treat this section as the part to re-read before you hit send, because a false read here is more expensive than a slow one.

• Fake human-in-the-loop. The invite says "reviewed by our team," but the reviewer sees only a pass/fail score. If you score that as "assists," you skip the Article 22 rights you actually hold. Check: ask who can override the score and whether they see your full interview. Rubber-stamp review does not count, per the EDPB and ICO.
• Jurisdiction misread by your own location. You assume your home state governs. NYC LL 144 and others key off job location. Check: confirm the role's posted location, not where you sit.
• Consent treated as already given. A buried terms-of-service checkbox is relied on as consent. Illinois requires consent before analysis, and buried-checkbox consent in a ToS flow does not satisfy it. Check: was a plain explanation given before you recorded.
• Deletion assumed complete. You request deletion but the vendor keeps training data. Check: ask for written confirmation covering vendor and backup copies within the 30 days.
• Accommodation request too narrow. You ask only for extra time when you need a human reviewer. The ADA menu includes routing to a human and an alternative format, not just timing. Check: ask for the remedy you actually need.
• Overestimating leverage. Junior candidates assume walking is costless. The data shows the sub-$100k and under-35 cohorts face the gate most and still absorb the cost. Check your segment against the walk-away table before you decline.
• Treating no outcome as a decision. Silence is the modal result, not a signal. Among candidates who completed an AI interview, only 28% moved to the next round and 13% got a formal rejection. Do not re-apply on the assumption of a glitch.

That last point reframes the walk-or-stay call. If you were counting on a regulator to make the employer blink, recalibrate. The credible threat is the public review, the referral you withhold, and the candidate pool that routes around the AI-only gate on word of mouth.

Keep a human path open, and keep the read current

The best defense against the one-way gate is a parallel path to a human that does not run through the bot. Build it before you need it, so that declining one invite never means losing your only live opportunity.

Two-thirds of recruiters plan to increase AI pre-screening, and 51% of US companies already use AI in hiring, so the gate is spreading, not receding. The counter-move is a referral into a human screen. The example queries in Refolk's own research point straight at this: find senior people at companies known to run live human screens, and ask for an intro that lands you in front of a person instead of a model.

Where a tailored application is what gets you the human screen in the first place, Refolk writes your resume from your own history, tailors it to each posting, and scores how well you actually fit, so the referral has something to point at.

Before you call any single invite done, run the checklist.

Re-check the rights table on a cadence, because the dates move. Colorado's human-review right is effective January 1, 2027, the EU AI Act's high-risk employment obligations from 2 August 2026 (with one source noting stand-alone deployer obligations pushed to 2 December 2027), and new state regimes keep arriving. When an invite lands, confirm the current statute for that location rather than trusting a figure you memorized. The model stays the same; only the rows in the table change.