The Application Form, Field by Field, and What Each One Screens

You are mid-application, staring at a field for desired salary, work authorization, or a screening dropdown, and you do not want a wrong answer to end the application before a human reads it. This is the reference for that moment. It covers every recurring field in the order the form asks them, says which fields auto-reject you, which are structured data recruiters filter on, and which are legally voluntary and safe to skip - so you can jump to one field, get the answer, and finish the form.

The library already has a guide for the resume parser and one for the recruiter screen. This one is about the form itself: the boxes between your resume and a human being.

Which fields can end your application, and which cannot

Application-form fields fall into three classes, and the class decides how carefully you answer. Auto-reject knockouts have a single correct answer and route a wrong answer straight to rejection. Stored filters are compared against a budget or threshold. Voluntary self-ID is firewalled from the people deciding on you.

The single most useful thing to internalize: the knockout, not the resume parser, is what kills applications. In a recruiter survey, 84% of recruiters rely on knockout questions to screen for work authorization, certifications, or location. The keyword optimization most job seekers obsess over matters far less than one dropdown answer.

Here is the whole form, classified. Read the mechanism column, because it tells you what a wrong answer actually does.

Sources for each row are cited practitioner and regulator materials named throughout this guide. The important reading: only one class can silently end your application, and it sits early in the form.

The form in the order it asks: a field-by-field walkthrough

An online application asks its fields in a predictable order, and the stakes fall as you go. The highest-risk fields sit at the top; the safest sit at the bottom. Knowing the shape lets you slow down where it counts and move fast where it does not.

Identity, contact, and the authorization pair

The identity block looks harmless, but it holds the two most dangerous questions on the form. Work authorization and sponsorship are the classic knockout pair, and they are usually phrased as:

• "Are you legally authorized to work in the United States?"
• "Will you now or in the future require sponsorship for employment visa status?"

If a company does not sponsor visas, answering "Yes" to the second is an immediate automatic rejection. The word that traps people is future. A citizen or permanent resident who reads "future" too quickly can answer Yes and knock themselves out. Answer only what your documents confirm.

Resume parse and years of experience

The ATS may parse your resume and pre-fill an experience field. Correct any number it got wrong, and count only professional-level years. This field is verified later against your resume, so an inflated figure becomes a mismatch that surfaces in the screen. Inflated years of experience belong to the category of self-reported claims that break down where they cannot be verified.

Desired salary

Salary is a stored filter, not usually a hard gate, and it is the one filter field that can hurt in both directions. Budgets are predetermined; recruiters check whether you fit, and if your asking price is too high they may remove you early. Too low signals low skill. The section below covers exactly what to type.

Availability, relocation, travel, notice period

These are structured picklists or yes/no items, treated as knockouts or filters depending on how the employer sets them. Answer them consistently with what an offer or document will confirm. The willing-to-relocate question is not a loyalty test; it is a yes/no that has to match reality at offer.

Free-text prompts

"Why do you want to work here" and "how did you hear about us" have no publicly established correct answer beyond researching the company. Their real screening function is consistency: keep them from contradicting the structured fields above.

What to put for desired salary

Put a real market range if you have one, or the word "negotiable" if the field allows text. If the field is mandatory and numeric, enter "000" and add a note that salary is negotiable. Never enter "99999" or "00000" as a placeholder.

The reason is specific. Placeholder salaries like "99999" or "00000" can flag your application as unprofessional to automated systems or recruiters. Meanwhile, leaving a mandatory field blank does not read as neutral; it stops submission entirely. So the field forces a choice, and the safe choices are narrow.

Free-text field:  Negotiable, targeting $X to $Y based on the role and market.
Range field:      Enter a researched market range for the level and metro.
Mandatory numeric only:  000
                  (then, in any comments box:) Salary is negotiable and open to discussion.
Never enter:      99999 / 00000 / any obvious placeholder as a real figure

Because salary is two-sided, anchor your range on public market data for the level and metro rather than guessing. Refolk can triangulate a target range from public market data as part of tailoring your application, which removes the guesswork this field otherwise demands. If you do not have a range ready, use "negotiable" and keep moving; you can raise a real number in the recruiter screen.

Salary is the one filter field that can hurt you in both directions, so anchor it on data, not nerves.

Knockout and screening questions, and how to clear them

Knockout questions are mandatory binary items with a single correct answer, and they route a disqualifying answer straight to a rejected status without a human ever seeing your resume. They appear as checkboxes, radio buttons, or dropdowns, and they sit early in the form on purpose.

The mechanism is explicit in the ATS. Candidates who answer incorrectly are flagged as auto-rejected and dispositioned into a "Not Hired" status. A disqualifying answer can trigger that rejection within minutes of submitting. So if you submit and get a rejection almost immediately, that is not a resume judgment; it is a knockout misfire.

The good news is that the mechanism is reversible. A failed candidate is not erased; they sit in an "unqualified" status, and a recruiter can un-reject them in one click. That changes your recovery play entirely.

The productive move after an instant rejection is to reach a human, not to reapply. Find a recruiter or hiring manager and message them about the specific field that likely misfired, for example clarifying that you do not in fact require sponsorship. Reapplying just re-runs the same gate.

This is where a targeted people search does real work: you need the specific recruiter behind that posting, not a generic inbox.

The screening workforce you are trying to reach is heavily US-concentrated. In Refolk's index, the recruiter pool differs sharply by market.

Counts come from Refolk's index; the share is derived. The practical read for a global applicant: the density of humans you can reach behind a posting varies by roughly 14x between these two markets, so a "reach a human" recovery is easier in some places than others.

Voluntary self-identification: should you answer it

Yes, or decline - it does not matter for your outcome. The EEO, veteran, and disability self-ID boxes are voluntary and structurally firewalled from the people deciding on you, so answering and selecting "decline to answer" are equivalent in screening terms. The anxiety about these boxes is misplaced.

The legal guarantees are concrete:

• Veteran (VEVRAA): the invitation to self-identify is voluntary, and a contractor must not use your refusal to self-identify to subject you to any adverse treatment.
• Disability (Form CC-305): completing the form is voluntary, the answer is confidential, and no one who makes hiring decisions will see it.
• Race and gender (EEO-1): the survey is voluntary, but if you do not self-identify, the employer is still required to report the data and can use existing records or visual observation to complete it.

That last point is worth sitting with: declining the EEO-1 box does not remove you from the count. The employer fills it in anyway. So declining protects nothing and reveals nothing.

Sources are the Department of Labor, directemployers.org, and Justworks. Two dates are worth tracking because these forms turn over: federal contractors had to adopt the updated CC-305 by July 25, 2023, and the current CC-305 is set to expire April 30, 2026. If you see an older form, that is a compliance lag, not a trap - but it is the kind of detail worth re-checking against the current DOL form rather than trusting a copy embedded in an ATS.

There is a related legal tell to watch for. Before a conditional offer, the ADA prohibits all disability-related inquiries and medical examinations, even if job-related. The voluntary CC-305 is the one permitted exception, precisely because it is voluntary, confidential, and screened off. So if you see a disability or medical question that is not framed as voluntary and confidential, that is a red flag worth noting - not a box to fill in reflexively. After a conditional offer, an employer may make such inquiries, but only if it does so for all entering employees in the same job category. Drug tests are a separate case: they are not "medical examinations" under the ADA, so those restrictions do not apply to them.

The procedure: filling the form without knocking yourself out

Work the form top to bottom, treating each stage by its class. The order below matches the order the form asks, and each step tells you what "done" looks like.

How this goes wrong: the seven field-level failures

Most self-inflicted rejections come from a small set of predictable mistakes, and each has a check you can run before or after you submit. This is the section to re-read when something feels off.

1. Misreading the sponsorship question

Answering "Yes" to "Will you now or in the future require sponsorship?" when the employer does not sponsor is an instant auto-reject. The false positive is a citizen who misreads "future." Check: a rejection within minutes confirms a knockout fired.

2. Placeholder salary

Entering "99999" or "00000" can flag your application as unprofessional. The false positive is assuming any numeral is neutral. Check: use "000" with a negotiable note, or a real market range.

3. Assuming self-ID is a trap

Declining EEO, veteran, or disability self-ID is legally safe and hidden from deciders. The failure is believing it helps or hurts screening. Check: the CC-305 language stating deciders never see it.

4. Believing a knockout deletes you

The misconception is that your record is erased. In fact you sit in an "unqualified" status and can be un-rejected in one click. Check: ask a recruiter to reinstate you rather than reapplying.

5. Inflating years of experience

Self-reported experience is verified later against your resume and documents; overstating creates a mismatch. Check: count only professional-level years.

6. Leaving a required field blank

If the form mandates salary, blank stops submission entirely - it is not neutrality. Check: does the form validate on submit.

7. A pre-offer medical question that should not exist

A pre-offer disability inquiry is generally prohibited; the false positive is confusing it with the voluntary CC-305. Check: is it framed as voluntary and confidential.

Before you hit submit

Run this pass before submitting any application. It catches the failures above while they are still fixable.

Keeping the form work current

Two things drift over time, so re-check them rather than trusting a memorized value. First, the self-ID forms turn over on a schedule: the current CC-305 is set to expire April 30, 2026, and a fresh version will replace it. When you see a self-ID box, confirm it is framed as voluntary and confidential; the exact form revision matters less than that framing.

Second, whether a specific employer sponsors visas, and who the recruiter behind a posting is, changes constantly. When a fast rejection tells you a knockout misfired, the recovery is to find the human, and that lookup is worth doing fresh each time. Refolk tailors your application to each posting and scores how well you actually fit before you submit, which is the cheapest place to catch a field that would otherwise knock you out silently. The form is a gate, not a judge - answer it as one, and keep a human in reach for when it misfires.