The short version
- A knockout question is a screening question wired to reject you automatically. No recruiter reads the application first.
- Greenhouse documents this precisely: auto-reject fires only on Yes/No, single-select and multi-select questions. A free-text box cannot auto-reject you.
- The same page carries the detail nobody mentions: the hiring team is not notified. Anyone set to receive alerts about new applications does not hear about auto-rejected ones.
- Where a rule could both advance and reject you, Greenhouse applies the rejection.
- Workday supports the same idea: employer-written condition rules can decline you at the point of application based on your questionnaire answers.
- This is not the keyword score people worry about. It runs earlier, it is binary, and no amount of resume tailoring reaches it.
Most advice about getting past an ATS is about the resume: the wording, the layout, the keyword overlap with the job description. That advice addresses a real mechanism, but it addresses the second one. Before any of it applies, a much blunter filter has already run, and it does not look at your resume at all.
It looks at the dropdowns. The questions underneath the upload field, the ones that take ten seconds and feel like paperwork, are the ones that can end the application outright. They are called knockout questions, and unlike most of what gets written about applicant tracking systems, the vendors document exactly how they work.
What a knockout question actually is
A knockout question is an application question with a rule attached. The employer picks an answer, and any candidate who gives that answer is moved to rejected without a human step. Work authorisation, a required licence, a minimum years-of-experience threshold, willingness to relocate, notice period. The question looks identical to every other field on the form. The rule behind it is invisible from the candidate side.
The distinction that matters is automation, not subject matter. A screening question collects information for a recruiter to weigh later. A knockout question moves you through the pipeline by itself. Both sit on the same form and look the same to you.
What Greenhouse documents
Greenhouse calls the feature auto-reject and describes application rules as automatic actions applied to job post questions. An admin picks a custom question, picks the disqualifying response, and checks a box. Conditions can be combined, up to five questions joined with AND logic.
Two constraints in that documentation are worth knowing, because they bound what the feature can do to you. The first: auto-reject works only with Yes/No, single-select and multi-select questions. A free-text field cannot trigger it. Whatever you type into a text box is read by a person or not at all, never by a rejection rule.
The second: where both an auto-advance and an auto-reject rule match the same candidate, Greenhouse applies the reject. Meeting every other bar does not offset one disqualifying answer.
Why you never hear anything back
The line in the Greenhouse documentation that explains the candidate experience better than any article about ghosting is this one: anyone set up to receive notifications about new candidate applications will not be notified of auto-rejected applicants.
“It is not that nobody replied to your application. It is that, on the employer side, no notification of it was ever generated.”
The rejection email itself is optional, and it is a separate checkbox from the rule. An employer can configure the disqualification and skip the notification. That combination produces the outcome candidates describe constantly: an application that returns nothing at all, indefinitely, and a role that stays open.
Worth noting that the feature is gated to the Plus and Pro tiers. Not every Greenhouse job has auto-reject configured, and plenty of silence has more ordinary causes. But when it is on, this is what it looks like from the outside.
How Workday does the same thing
Workday builds it out of questionnaires attached to the job requisition, with separate questionnaires available for internal and external career sites. Disqualification is assembled through calculated custom report fields evaluated inside the Job Application business process, and Workday ships twelve delivered report fields for eligibility-type questions intended for exactly this use.
The decline itself runs through what Workday calls automatic stage routing. An employer writes condition rules using data from the job application, the job profile, the requisition and the questionnaires completed when a candidate first applies. Workday's own example is declining candidates who are ineligible to work in the country where the position is located. Rules are checked in the order the employer set, and the first one a candidate meets decides the outcome while the rest are ignored. That differs from Greenhouse, where a matching reject rule always wins over an advance rule.
One Workday behaviour has no Greenhouse equivalent: a questionnaire can be changed or removed on a requisition after candidates have already applied. The screening logic attached to a posting is not necessarily the logic that was there the day you submitted.
This sits upstream of the grade Workday's HiredScore assigns to the applications that survive. The two get discussed as one thing and are not: the questionnaire decides whether you remain a candidate, the grade decides where you land in the recruiter's list.
Check what a parser extracts from your resume
Optimize your application materials in under 2 minutes.
Worth being clear that no resume tool, this one included, can see or influence a knockout rule. Extraction quality decides how you rank once you are past the form. The form itself is answered by hand, and answered carefully.
How to answer them
Answer them accurately, and slow down while you do. The realistic failure here is not dishonesty, it is carelessness: a dropdown left on its default, a years-of-experience band misread, a sponsorship question answered backwards because it was phrased as a negative. Those are unforced, they are irreversible, and they happen at the end of an application when attention has already run out.
- Read sponsorship and authorisation questions twice. They are frequently worded as negatives, and the two questions are not the same question.
- Never leave a default selected. An untouched dropdown is a submitted answer, not a blank.
- Take experience bands literally. If the threshold is five years and you have four, selecting five is a false statement that is checkable at offer stage.
- Answer the licence question about the licence you hold now, not the one in progress. In-progress belongs in a text field, which cannot auto-reject you.
- Use free-text boxes for nuance. They are the one field type a rejection rule cannot read, so context and caveats belong there rather than in a dropdown.
Where a question is genuinely ambiguous and the honest answer sits on a boundary, answer it truthfully and put the explanation in whatever open field the form provides. That is the only route that both keeps you in the pipeline and survives contact with a recruiter.
What this does not mean
It does not mean the resume stopped mattering. Knockout questions are a gate, not a ranking. Clearing the gate puts you into the pool where parsing quality and evidence determine whether a recruiter opens your file, and that is still where most applications are actually lost. That later stage is where tailoring your resume to the posting is worth the effort.
It also does not mean most rejections are automated. Auto-reject requires configuration, a paid tier in the Greenhouse case, and a question with an unambiguous disqualifying answer. Most roles do not set one up. The point is narrower: when it is configured, no resume work of any kind reaches it, so the ten seconds spent on the dropdowns are worth more than the tenth revision of a bullet point.