What a knockout question is, and how to spot one

Short answer: a knockout question is a question on the application form that has an automatic reject rule attached to it, so one wrong answer closes the application without a person ever opening it. Greenhouse calls the feature auto-reject; Workday builds the same thing out of condition rules. Either way, it fires at submission.

That timing is the part worth holding on to. The rejection you get four minutes after applying is almost never a recruiter reading fast. It is a rule that matched a single field.

What a knockout question actually is

Greenhouse's own documentation is unambiguous about what the feature does: with auto-reject, an organization "can set up application rules so that, based on an applicant's answer to a question, they will automatically be rejected as a potential candidate." The example on the page is a Class A Commercial Driver's License - reject anyone without one, because the role involves driving a tractor trailer.

So the mechanism is a rule, not a judgment, and the rule is attached to a specific question with a specific answer marked as the trigger. Here is what the common ones are checking.

Not every question on the form is one of these. Most are stored and read later by a person, or stored and never read at all.

One detail from the same page changes how you should read any given form: auto-reject is a paid feature. Greenhouse restricts it to the Plus and Pro subscription tiers, and configuring a rule needs Site Admin or Job Admin permissions. Nor are the three application rules sold together - auto-tag runs on Core too, so a company on the entry tier can still be sorting your answers into buckets. It just cannot have the system reject you on one. The identical Yes/No question, on an identical job post, at that company, is a field that gets stored and looked at by whoever opens the application. You cannot tell which one you are looking at from outside, and neither can anyone else - which is a reason to treat every closed-answer question as though a rule sits behind it, and no reason at all to assume one does.

Why employers filter before a person reads

Because of arithmetic. BLS counted 7.3 million job openings and 5.1 million hires in July 2026 - a gap that lands on the desks of the people posting those reqs, and the cheapest way to make an inbox smaller is a rule that runs before anyone opens it.

The volume the filters are built for, July 2026

7.3MJob openings, July 2026

5.1MHires, July 2026

4.4%Job openings rate

How to spot one before you answer it

The tell is the answer format, and it is more reliable than the wording. Greenhouse's auto-reject page states the limit flatly: "Auto-reject application rules can only be configured for questions of the following type: Yes / No, Single-select, Multi-select." Auto-advance runs on the same three. A box you type sentences into cannot trigger either. That single fact tells you where the danger is on any form you open: the radio buttons and the dropdowns, not the essays.

Reading a form for its knockouts

Two minutes before you start typing. The closed-answer questions are the ones with rules behind them.

1. 1
   Scroll the whole form first

   Do not answer anything yet. You are looking for shape, not content - which questions have radio buttons, dropdowns or checkboxes, and which have a text area.

2. 2
   Mark every closed-answer question

   Yes/No, single-select and multi-select are the only types Greenhouse's rules run on. Everything else on the form is stored for a human.

3. 3
   Check which of those are required

   A required closed-answer question is the highest-probability knockout on the page. An optional one rarely carries a reject rule, because the employer cannot rely on getting an answer.

4. 4
   Match each one against the posting

   If the posting says "CDL required" and the form asks about a CDL as a Yes/No, that is the rule, stated twice. The requirements list is the draft of the rule set.

5. 5
   Decide before you invest the time

   If a hard, checkable requirement is one you do not meet, the ten minutes of form-filling buys nothing. Spend it on the next posting.

If a knockout question tests a hard, checkable requirement you do not meet, do not submit the application. This is not the usual advice, which says apply anyway because postings are wish lists. That advice is right about the wish-list part - years of experience, degree preferences, the ninth bullet under "nice to have" - and wrong about this specific class of question. Greenhouse states that auto-rejected applicants do not trigger notifications to hiring team members. There is nobody at the other end to be impressed by your initiative, because the rule ran before anyone was told you existed. An unqualified application to a role with a soft requirement is a lottery ticket; the same application to a role with a knockout rule is a form you filled in for a database.

What Greenhouse and Workday actually do with the answer

The two systems reach the same outcome by different routes, and the difference matters when you are trying to work out what happened to you.

The same knockout in two systems

Greenhouse exposes it as a named rule on the job post. Workday builds it into the business process, which is why it is harder to reason about from outside.

	Greenhouse	Workday
What it is called	Auto-reject, one of three application rules	Condition rules on the Job Application business process
Where the question lives	A custom job post question	A questionnaire attached to the requisition
Question types it runs on	Yes/No, single-select, multi-select	Mapped eligibility fields and calculated report fields
Combining questions	AND across up to 5 questions, or OR across responses	Rules evaluated in the order they are displayed
When several rules match	Only one advance or reject rule applies; reject wins	First matching rule runs; the rest are ignored
What you are told	A rejection reason internally; an email only if configured	A disposition on your candidate record

Workday's side is worth a sentence more, because its shape explains the forms you have been filling in. A requisition can carry a primary and a secondary questionnaire, each holding no more than 50 questions excluding branching, and a single-select question can branch six levels deep - which is how a form that looked like four questions turns into fourteen. Workday also ships 12 Class Report Fields for the questions employers ask over and over - Legal_Eligibility, Require_sponsorship, Willing_To_Relocate, Felony_Conviction, Notice Period and seven more - which an administrator maps to their own wording on the Map Job Application Questions task. Those mapped fields are what disqualification rules are built on.

What none of this documentation says is how many employers switch any of it on. Neither vendor publishes adoption figures, or the share of applications that end this way, and any number you see quoted for that is somebody's guess. The mechanism is documented; its prevalence is not.

What the rejection looks like from your side

Three things happen when a Greenhouse auto-reject rule matches, and only one of them is ever visible to you.

The application is rejected and assigned a rejection reason from a dropdown the employer chose in advance - that reason is internal, and it is what shows on their reporting rather than in your inbox. The applicant can be tagged with a candidate tag, again internally. And a rejection email goes out only if the employer ticked the box and picked a template; sending one is optional, and the configuration screen treats it as an extra step rather than a default.

That is the source of a pattern most people applying have noticed without being able to explain. Two applications submitted the same evening, both rejected by a rule within minutes, and one produces a polite templated email while the other produces silence that lasts forever. Same feature. Different checkbox.

Workday's version ends the same way and looks different in the account. Its condition rules end the Job Application business process and apply a disposition the administrator created on the Maintain Recruiting Dispositions task, which is why a Workday candidate home sometimes flips a role to a closed status with no message attached. If you have an account at that employer, the status change is the notification.

If the honest answer is the disqualifying one

Answer it anyway, and be precise rather than defensive. Two cases, both from the roles that ask these questions most.

A Warehouse Associate posting asks: Can you lift up to 50 pounds on a repeated basis throughout an 8-hour shift? If you can, with or without an accommodation, the answer is:

Yes.

That is the whole answer. The question is about a job function, which an employer is entitled to ask about before an offer, and the accommodation conversation is a separate one you are not required to open in a radio button. This is not a small population of jobs: BLS counts 6,917,800 hand laborers and material movers in 2025, on a median wage of $38,220 a year - $18.38 an hour - in May 2025, and it is the field where lift-and-shift questions are near-universal.

A Software Engineer posting asks: How many years of professional experience do you have building production software? with the options 0–2, 3–5, 5–8, 8+. Pick the band your dates support, not the one the posting asks for. Greenhouse's auto-advance example advances applicants in the 3-5 and 5-8 bands straight to Hiring Manager Review - so an inflated band is as likely to route you into a screen you will fail as past a filter you would have cleared. For context on who is answering these: BLS puts the median wage for software developers at $135,980 in May 2025, inside an occupation group - developers, quality assurance analysts and testers counted as one - that held 1,905,400 jobs in 2025 and has a group median of $134,040.

If the question is one the employer should not be asking

Some knockout questions are not lawful to ask before an offer. The EEOC's line on disability is specific: an employer "may not ask any questions about the nature or severity of the disability pre-offer." What it may do is ask "if the applicant will need an accommodation to perform a specific job duty, and if the answer is yes, the employer may then ask what the accommodation would be."

Read the warehouse question above against that. "Can you lift 50 pounds?" is a question about performing a job duty and is fine. "Do you have a back injury?" is a question about a medical condition and is not. If you meet the second kind on a form, you are looking at a compliance problem in someone's job post, not a test you have to pass - and you can answer the job-function version of the question in the free-text box next to it.

If the form has no "prefer not to say"

Then the question is required, and a blank answer is an answer, and it is the wrong one. A required closed-answer field will not let you submit, so the choice is between answering and abandoning the application - which is a real choice, not a failure, and one worth making deliberately for a salary-expectations dropdown at a company you are lukewarm on.

Where the field is optional and you skip it, understand what you have done. Greenhouse rules can be built with AND conditions across up to five questions, and an unanswered question simply does not match - which normally means no rule fires, and you land in the pile with everyone else. It also means you have opted out of the rules that would have helped you, since auto-advance runs on the same question types and would have moved you forward on the same answer. Skipping is safe and inert. It is not free.

The demographic block at the end of the form is a different animal, and the software treats it that way. Greenhouse's documentation on custom demographic questions states that "marking a custom demographic question as required will automatically add an answer choice for I don't wish to answer" - the decline option is generated by the system, not by the employer's goodwill. If a demographic question has no way out on the form in front of you, that is worth noticing, because in Greenhouse a required one always does.

The one thing to get right

Before you type anything into a form, find the closed-answer questions and read them against the posting's requirements. That is the whole exercise: those questions, and only those, are the ones with rules behind them, and the answer you give in a dropdown is worth more to your application than the four paragraphs you write underneath it.

If you are answering the same authorization, location and experience questions on every form this week, HeroApply answers the screening questions from your resume so the answers stay consistent from one application to the next.