Knockout Questions Are the Only Thing That Can Auto-Reject You

What Are Knockout Questions?

A knockout question is a screening field an employer attaches a rule to ahead of time, so that a specific answer alone ends the application, with no further reading involved. Greenhouse's documentation is precise about the mechanism: auto-reject rules can only be configured on Yes/No, Single-select or Multi-select questions, never on free-text fields or the resume itself ¹. That is a narrower target than most applicants imagine when they picture "the algorithm" reading them out.

The form itself usually tells you which questions are load-bearing, if you read it that way. A dropdown asking for a specific licence number, a required yes/no on authorization to work, a hard salary floor with no range option, these are structural signals that a rule is watching the answer. A free-text box asking you to describe a project is not wired the same way; nothing in Greenhouse's or Workday's own documentation describes a rule scoring open text at submission ¹².

That distinction matters more than it looks. It means the part of an application most applicants worry about, whether their writing sounds impressive enough, is almost never the part a rule reads at all. The part actually wired to a rule is a handful of structured fields, usually near the top or bottom of the form, that most applicants click through quickly without treating as consequential.

Name the Common Knockout Categories

Six categories cover most of what employers actually wire to a rule, and once you have the list, most application forms stop feeling arbitrary. They split into two kinds worth telling apart: facts about your status that a rule checks exactly as stated, and ranges where a specific answer matters less than being roughly honest.

• Work authorization. A factual yes/no. Answer it exactly as your status stands; there is no version of guessing here that helps you later.
• Minimum years of experience. Often a range question in disguise; answer with your actual tenure rather than rounding up.
• An active license or certification. Factual and checkable at the source; the issuing body can confirm or deny it.
• A salary floor. A range, not a commitment, though some systems treat the number as a hard cutoff.
• Location and shift availability. Factual, and worth answering precisely rather than optimistically.
• Willingness to relocate. A stated intention the employer may hold you to later in the process.

Workday's documentation describes exactly this kind of rule under "automatic stage routing," and its own worked example is declining a candidate ineligible to work in the country where the position is located, a factual eligibility check rather than a judgment about ability ². In a survey of 2,275 senior leaders across the US, UK and Germany, fielded in early 2020 by Harvard Business School and Accenture, more than 90 percent of employers using a recruitment management system said they use it to initially filter or rank candidates before a person looks ³.

Treat a Range Field as a Range, Not a Guess

Two categories above are commitments an employer can hold you to later, and the rest sit closer to ranges where a needlessly precise number can close a door for no real gain. Salary and years-of-experience fields are usually the second kind: state your actual number rather than inflating it, and use a range where the form allows one instead of a single figure that reads as a hard floor.

Work authorization and licensure are the first kind, and this is the one place the honest advice and the cautious advice are the same advice: never guess or round favorably on either. A wrong answer here is not a formatting mistake to fix later; it is the version of this that surfaces again at an offer stage, when it costs far more than a single rejected application, because verification at that point usually involves a background check or a licensing-board lookup rather than a self-reported field. If the form's requirements genuinely exceed what you hold, applying anyway when you do not meet every stated requirement is a different, defensible decision from misstating a fact a rule or a background check can verify.

Location and shift questions sit in between. They are factual in the moment you answer them, but a stated preference can shift between application and offer, and it is reasonable to say so honestly at the point it changes rather than let an early answer stand in for a decision you have not actually made yet.

Know Where the Legal Line Sits

US federal law already limits what a pre-offer question can ask, independent of how the form is built. Under the Americans with Disabilities Act, a covered employer may not ask whether an applicant has a disability, or run a medical examination, before making an offer, though it may ask about the ability to perform specific job functions ⁴.

A knockout question phrased around a genuine job requirement, can you lift 50 pounds unassisted, stays on the right side of that line; one that asks whether you have a disability, or about the nature or severity of one, does not.

If a fast, unexplained rejection follows a knockout question you believe you answered correctly, and you can rule out a simple mismatch on your end, it is fair to ask what happened. Employers are being told plainly what they owe a candidate an automated rule screened out: notice that a rule was involved, and a route to a person who can look again. You are allowed to ask the same question of any employer that rejected you this way, whether or not the jurisdiction you applied from actually requires an answer in return, and a polite written request costs you nothing to send.

Read the evidence >