Knockout questions: the filter that actually rejects you

Almost every account of automatic rejection describes software reading a resume and judging it. That is not the mechanism.

The mechanism is a knockout question: a field on the application form that an employer has configured with a disqualifying answer. Are you legally authorised to work in this country. Do you hold a current licence for this practice. Do you have at least three years of experience in this role. Will you relocate. Can you work the listed shift pattern.

Answer one the wrong way and the application ends there, before anything reads your resume at all. It is not a model making a judgement. It is a rule a person set, working exactly as they intended.

Because of the timing. You submit, and within seconds or hours you have a rejection. That feels like a machine reading your resume and disliking it.

What actually happened is that a form field matched a disqualifying rule. The speed is the giveaway: nothing had time to evaluate your experience, because nothing tried.

When Enhancv put the question to 25 US recruiters in 2025, 23 said their systems do not auto-reject on formatting, content or design. Twenty-five people is a small sample and we will not pretend otherwise, but it points the same way as how these systems are actually configured. The rejection is coming from the form.

Some knockouts are not negotiable and should not be treated as though they were.

Work authorisation is the clearest. If a role requires authorisation you do not hold and the employer does not sponsor, that is a real constraint rather than a filter to get around.

Licensing is the same. A nursing role requiring an active licence in a particular state, a role requiring a security clearance, a driving role requiring a clean licence. These exist because the job cannot lawfully be done without them.

Answering these dishonestly does not help you. It moves the rejection to a later stage, after you have spent time on interviews, and it can end an offer that has already been made.

Others are softer than they look, and this is where most applications are lost unnecessarily.

Years of experience is the common one. Employers frequently set a threshold higher than the role needs, and the question usually asks about experience in a named area rather than in a job title. If you have done the work inside a different role, that counts, and it is on you to read the question as written rather than as you assume it.

Salary expectation is another. A number entered into a form can drop you below or above a band you never see. Where a range is invited, giving one is safer than giving a point.

Notice period, willingness to relocate and shift availability are similar. If the honest answer is conditional, say so where the form allows it, rather than picking the answer that closes the door.

Slow down on the questions and speed up on the upload. Most people do the reverse: they spend an hour on the resume and thirty seconds on the fields that decide whether it is read.

Read each question literally. Answer honestly. Where a free text box sits beside a hard yes or no, use it to explain a conditional answer.

And if you are rejected in minutes, look at the form rather than the resume. Rewriting your bullets will not change an answer that disqualified you.

None of this makes formatting irrelevant. It makes it a different kind of problem.

A resume the parser reads badly is harder to search and harder to shortlist. It costs you quietly, by keeping you out of the results when a recruiter searches their database, rather than by producing a rejection you can point at.

What that looks like in practice is covered in what an ATS actually does with your resume. And the claim that most resumes are auto-rejected outright is traced in where the 75% number came from.