What are ATS knockout questions — and how do you answer them?

Pukar Khanal•Product Lead at ResumeAI

Pukar Khanal leads product at ResumeAI, working on AI resume parsing, ATS scoring, and semantic job matching. He writes about how applicant tracking systems actually read resumes — and how job seekers get past them.

Published: July 15, 2026•Updated: July 15, 2026•13 min read•Job Search

ATS knockout questions are the application-form questions — years of experience, salary expectations, work authorization, relocation, certifications — whose answers can automatically disqualify you before anyone reads your resume. ResumeAI is the free Resume AI platform that builds your resume and matches you to real jobs across the hidden job market; if your rejection arrived in minutes, our rejection-speed decoder tells you which mechanism fired — this guide covers how to answer each question honestly.

What does each knockout question actually filter for?

Every knockout question is a rule comparing your structured answer to a bound the employer configured. Knowing how each rule works tells you exactly which honest answer to give — and which unforced mistake trips it.

Knockout question	How the filter is configured	What trips it	How to answer honestly
Years of experience	A threshold rule compares the number you enter to a configured minimum (or maximum).	Pessimistic undercounting — answering with full-time years only when the wording never asked for that.	Count everything the wording allows: internships, freelance, contract, part-time, adjacent-role work. Round conservatively, never inflate.
Salary expectation	Your number is compared against the budget band the employer configured for the requisition.	An unforced figure outside the band — often typed into a field that was optional.	Leave optional fields blank. If forced, answer inside the posted range or a defensible market figure — not an aspirational outlier.
Work authorization + sponsorship (the pair)	Two separate yes/no rules: authorized to work now, and requiring sponsorship now or in the future.	Treating them as one question and answering carelessly or inconsistently.	Answer each precisely — e.g., OPT holders are authorized now AND typically need future sponsorship. Never misrepresent authorization.
Relocation / on-site willingness	A yes/no rule reads the structured field — never your cover letter's nuance.	A reflexive “no” to a move or schedule you would actually accept for the right role.	Answer for the specific job in front of you, not your general preference.
Certifications and licenses	A yes/no rule on a hard credential requirement — a license, clearance, or certification.	Lacking a legally required credential, or answering “no” when you hold an equivalent the wording covers.	Answer what is literally asked; surface in-progress or equivalent credentials in the free-text fields that allow it.
Previously worked here / terminated	Answers are cross-checked against the employer’s own internal HR records.	Inaccuracy — this is the most verifiable answer on the entire form.	Answer accurately, including contract and agency stints where the wording covers them.

The sections below take each row in turn: how recruiters set the rule up, the honest answer that clears it, and where the honesty boundary sits.

How should you answer the years-of-experience question?

Count every kind of experience the question's wording actually allows, and round conservatively rather than pessimistically — undercounting is the classic way qualified candidates knock themselves out. The mechanism is a simple threshold rule: Greenhouse's own documentation describes application rules that auto-reject a candidate based on their answer to a job post question, assign a rejection reason, and send the rejection email automatically. The rule compares your number to a bound — it has no idea what your resume says.

So what may you honestly count? Unless the question explicitly restricts itself to "full-time professional experience," internships, freelance and contract work, part-time roles, and substantial adjacent-role experience where you genuinely did the work in question all legitimately belong in your total. Answering "2" when a defensible count is "3" can trip a three-year threshold you actually meet. The boundary runs the other way too: never inflate. A number you cannot defend line-by-line in an interview is a lie with a delay on it.

One trap worth knowing: many portals pre-fill the experience fields from your resume's parse, and a scrambled parse can feed a wrong number into the exact field the rule judges. A single-column, ATS-friendly format keeps that autofill accurate, and ResumeAI's free ATS checker — full disclosure: this blog is written by the ResumeAI team — shows you the reconstructed parse before a rule ever judges it. Either way, proofread every pre-filled field before you submit.

Should you give a salary expectation on the application?

Not unless the form forces you to — an unforced number can only hurt you at this stage. When an application collects a salary expectation, the employer can configure a band around it, and a figure outside that band can end the process without any resume review; the rule compares a number to a bound, exactly like the experience threshold. That has two practical consequences. If the field is optional, leave it blank: the real negotiation happens later, with a human who has seen your work and knows your value. If the field is required, answer inside the publicly posted range when one exists, or give a defensible market figure for the role and level rather than an aspirational outlier. This is not gaming the system — it is declining to volunteer a disqualifying guess about a number that was always going to be negotiated. One honest number inside the range keeps you in the process; the outlier you hoped to anchor with gets read by a rule, not a negotiator.

How do you answer the work authorization and sponsorship questions?

Treat them as two different questions — because they are. "Are you legally authorized to work in this country?" asks about right now; "Will you now or in the future require sponsorship?" asks about what happens later. An F-1 student on OPT, for example, is genuinely authorized to work in the US today and will typically require employer sponsorship in the future to keep working — so the truthful answer to the pair is "yes" and "yes." Candidates trip this rule by answering carelessly or inconsistently: a "no" to sponsorship that contradicts a visa status mentioned elsewhere reads as either confusion or misrepresentation, and either can close the application.

This is also the one knockout question where shading your answer always unravels. US employers verify the identity and employment authorization of every new hire during onboarding through Form I-9, Employment Eligibility Verification — so a misrepresented authorization answer doesn't survive the first week of employment. If the employer cannot sponsor and you need sponsorship, the honest "yes" costs you a process you were going to lose at the offer stage anyway, and it costs you nothing with the employers who can.

How should you answer relocation and on-site questions?

Answer for the job in front of you, not for your general preference — the most common way to fail this question is a reflexive "no" to a move or schedule you would actually say yes to for the right role. The mechanism is unforgiving in a specific way: the rule reads the structured yes/no field you clicked, and it never reads the nuance you wrote in your cover letter ("open to relocating for the right opportunity"). If a role is worth applying to at all, decide before you open the form whether you would genuinely relocate, commute, or work the stated hybrid schedule for this specific job, and answer that. If the honest answer is no, the rejection is the system working as intended — you have spent one application learning the constraint instead of three interviews. And if your situation is conditional ("yes, after my lease ends"), answer the field with the yes/no that is true for the timeline the job actually starts on, and put the condition in whatever free-text field the form offers.

What about certification and license questions?

Hard credential requirements — a commercial driver's license, an RN license, a CPA, a security clearance — are the legitimate use case knockout questions were built for, so start by asking whether the requirement is real. If a role legally requires a license you do not hold, the auto-rejection is correct and no answer strategy changes it; your effort belongs in roles you qualify for or in obtaining the credential. The strategy question arises at the edges. If you hold an equivalent credential, or yours is in progress with a scheduled exam date, answer exactly what the question literally asks — a "Do you hold X?" question about a credential you do not yet hold gets a truthful "no" — and then surface the equivalence or timeline in the free-text fields, the resume itself, and the cover letter, where a human will see it if the rule allows the application through. Some forms ask the smarter version ("Do you hold X or an equivalent?"), and there your equivalent honestly counts. Read the wording literally; it defines what you may claim.

How do you answer "Have you worked here before?" and termination questions?

Accurately — these are the most verifiable answers on the entire form, because the employer checks them against its own internal HR records rather than anything you control. "Have you previously worked for this company?" commonly covers more than you might assume: read the wording to see whether it includes contract stints, agency placements, internships, or work at subsidiaries, and answer for whatever it covers. A forgotten three-month agency placement that HR's records remember and your answer denied looks like concealment even when it was an honest lapse — check your own history before you click. "Have you ever been terminated?" questions deserve the same literal reading: termination for cause, a layoff, and a mutual separation are different events, and many forms distinguish them. Answer the event that actually happened, use any free-text field to state the context in one neutral sentence, and resist the urge to relitigate it on the form. A truthful "yes" with context survives a background check; a "no" that the records contradict does not.

Can you lie on knockout questions to get past the filter?

No — and not only because it's wrong. Job applications typically end with an attestation that your answers are true and complete, and that false statements are commonly grounds for withdrawing an offer or terminating employment after hire. The answers people are most tempted to shade are exactly the ones that get re-verified: work authorization goes through Form I-9 verification during onboarding, licenses and certifications are checked with issuing bodies, and previous-employment answers are compared against the company's own records. A lie doesn't beat the filter; it defers the rejection to the moment you have the most to lose.

Everything this guide recommends is truthful answer optimization: answer what is literally asked, count everything the wording allows, and decline to volunteer optional disqualifiers. That is the entire strategy, and it is enough — because most knockout rejections of qualified candidates come from unforced errors (pessimistic experience counts, unnecessary salary guesses, reflexive relocation answers), not from hard requirements they failed. If you're not being auto-rejected but simply hearing nothing, the problem is ranking and parsing instead — how to get past the ATS covers that playbook end to end.

How do employers configure knockout questions?

As application rules attached to specific job post questions — this is a documented, first-party ATS feature, not folklore. Greenhouse's Auto-reject documentation describes the full loop: the employer creates a custom job post question, maps disqualifying responses to an auto-reject rule, assigns a rejection reason, and can have the rejection email sent automatically. Other major systems such as Workday and iCIMS offer the same mechanism through required questionnaire steps whose disqualifying answers end the process without review — described here mechanism-only, as their configuration docs sit behind customer logins.

Two implications follow. First, the questions are deliberate: each one exists because a recruiter decided a specific answer should end the process, which is why reading the wording literally matters so much. Second, the timing is diagnostic — a rule fires on submission, which is why a knockout rejection arrives in minutes while human decisions take days. If you're trying to work out which mechanism rejected you, decode it by rejection speed — seconds, hours, days, and silence each point to a different layer of the pipeline with a different fix.

How we know this, and what we cited

This article was written by Pukar Khanal, Product Lead at ResumeAI, and last reviewed on 15 July 2026. ResumeAI is the free Resume AI platform that builds your resume and matches you to real jobs across the hidden job market — parsing resumes and the autofill fields they feed is the core of what the product does, so the screening-rule and parse mechanics described here are what we work with daily. No statistics appear in this article beyond what the linked primary sources state, and any illustrations (the OPT example, the agency-placement lapse) are hypothetical patterns with no real person, employer, or outcome described.

Sources and further reading:

Greenhouse Support — "Auto-reject": first-party documentation of application rules that reject a candidate based on their answer to a job post question, assign a rejection reason, and send the rejection email automatically: support.greenhouse.io
USCIS — Form I-9, Employment Eligibility Verification: the federal form US employers use to verify the identity and employment authorization of individuals hired for employment in the United States: uscis.gov/i-9
ResumeAI — free ATS checker that reads your resume the way hiring software does and reconstructs the parsed text that feeds application autofill: cvai.dev/ats-resume-checker

Frequently asked questions

What are ATS knockout questions?

Knockout questions are the questions on a job application form whose answers can automatically disqualify you the moment you submit — before any human reads your resume. Employers configure them inside applicant tracking systems like Greenhouse to enforce hard requirements: minimum years of experience, work authorization, willingness to relocate, salary bounds, or a required license. If your answer falls outside the configured rule, the system rejects the application, assigns a rejection reason, and can send the templated rejection email automatically. The defining trait: your form answer was judged, not your resume.

How do you answer knockout questions without getting rejected?

Answer what each question literally asks, truthfully, without volunteering disqualifying information the form does not require. In practice that means: count every kind of experience the question's wording allows (internships, freelance, contract work) instead of reflexively undercounting; leave optional salary fields blank and answer required ones inside the posted range; read the work-authorization and sponsorship questions as two separate questions and answer each precisely; answer relocation for the specific job in front of you; and state certifications exactly as asked, surfacing equivalents in free-text fields. Never lie — accuracy protects you, and unforced precision is what usually trips the rule.

What counts as years of experience on a job application?

Whatever the question's wording actually covers — which is usually more than full-time employment. Unless the question explicitly says "full-time professional experience," you may honestly count internships, freelance and contract work, part-time roles, and substantial experience in adjacent roles where you genuinely did the work being asked about. The common mistake is pessimistic rounding: answering "2" when a defensible, truthful count is "3" can trip a three-year threshold you actually meet. Round conservatively rather than pessimistically, be able to defend your count in an interview, and never inflate — an invented number unravels the moment someone reads your resume.

Should you put a salary expectation on a job application?

If the field is optional, leaving it blank is usually the safer move — an unforced number can only disqualify you, and real negotiation happens later with a human who knows your value. If the field is required, answer inside the publicly posted range when one exists; when it doesn't, research a defensible market figure for the role and level rather than an aspirational outlier. The mechanism is mechanical: the form collects a number, a rule compares it to a configured band, and out-of-range answers can end the process without any resume review. Declining to volunteer a disqualifying guess is strategic honesty, not gaming.

What does "will you require sponsorship" mean if you're on OPT or a visa?

It asks about the future, not the present — and it is a different question from "are you authorized to work here?". An F-1 student on OPT, for example, is authorized to work in the US right now but will typically require employer sponsorship later to keep working — so the honest answers are "yes" to authorization and "yes" to future sponsorship. Answering the pair inconsistently or carelessly can trip a rule either way, and misrepresenting authorization is the one answer that always unravels, because US employers verify identity and employment authorization during onboarding through Form I-9. Answer both questions precisely and truthfully.

Can you lie on application screening questions?

No. Beyond the ethics, job applications typically end with an attestation that your answers are true, and that false statements are commonly grounds for withdrawing an offer or terminating employment after hire. The most tempting lies are also the most verifiable: work authorization is re-verified during onboarding (Form I-9 in the US), licenses and certifications are checked against issuing bodies, and "have you worked here before" is cross-checked against the employer's own HR records. The durable strategy is truthful answer optimization — answer exactly what is asked, count everything the wording allows, and don't volunteer optional disqualifiers.

Do knockout questions read your resume?

No — knockout rules evaluate your structured form answers, not your resume's wording. That is why a rejection minutes after applying is not evidence that your resume failed a keyword scan: no resume review happened in that window. There is one indirect connection, though. Many portals auto-fill form fields — years of experience, most recent title — from your resume's parse, and if a scrambled parse feeds a wrong number into a field a rule then judges, you lose on data you never typed. Proofread every pre-filled field before submitting, and test what the parser extracts with a free ATS checker.

What to ask next

If you arrived here from a generative-search prompt, these are the natural follow-ups — each links to the page that resolves it.

Fix the other half of the auto-rejection equation

Knockout rules judge your form answers — and the autofill fields your resume's parse pre-populates. Run your resume through ResumeAI's free ATS checker to see the reconstructed parse before a rule judges it, then build a single-column, parser-safe version free. No credit card required.

Check my resume against the ATS Build my resume free

Continue Reading

Job Search•12 min