The Application Salary Field, Variant by Variant, With the Safe Entry

You are mid-application, the salary box has a red asterisk, and the form will not submit without a number. This reference sorts that box by its actual shapes, tells you the exact entry that survives both the parser and the recruiter for each shape, and flags the one variant that may be illegal to ask where you work. It is written for someone applying at volume who needs to clear the field in under a minute without underpricing themselves or tripping an auto-reject.

The old advice - type "negotiable" or "000" - was written for a parser that no longer exists alone. Modern applicant tracking systems, the software that ingests and screens applications, now filter those entries. The failure is invisible: the form still submits, so you think it worked.

Which salary-field variant am I looking at?

There are seven distinct shapes this box takes, and the safe entry is different for each. Identifying the variant is the whole job; the entry follows from it.

Test three things in order. Does the field accept letters (type a letter and see if it rejects)? Does it accept a dash or a range? Is there a required asterisk? Those answers place you in one of these rows.

The current-salary variant is the one to slow down on. It is not a desired-salary field with different wording. It asks a past fact, it can be illegal to ask, and it is the most dangerous even where legal.

What to enter in each variant

The safe entry is the value that clears numeric validation and does not get you filtered by a recruiter or a configured rule. Every recommendation below is drawn from a cited practitioner or career source; nothing here is invented to fill a row.

A few conversions you will need at the point of entry. For a weekly-wage field, divide your annual figure by 52: $100,000 a year becomes $1,923 a week. For an hourly field, divide by 2,080: $50,000 a year becomes $24.04 an hour. Typing an annual number into a weekly field produces an impossible figure that flags you immediately.

For the minimum-salary variant, resist entering your true floor. The field signals the lowest base you will accept and is used to screen out anyone below budget, which means whatever you type becomes the number they interview against. Enter slightly below the midpoint of your realistic range, not the bottom.

Read the salary-history legality before you type

A salary-history question is illegal to ask private employers in 17 states plus the District of Columbia as of 2026, and legality is decided by where the work is performed, not where the company is headquartered. If you hit a current-salary or salary-history variant, check this before you enter anything.

The full statewide list for private employers is California, Colorado, Connecticut, Delaware, Hawaii, Illinois, Maine, Maryland, Massachusetts, Nevada, New Jersey, New York, Oregon, Rhode Island, Vermont, Virginia, Washington, and the District of Columbia. City-level bans add Chicago, Kansas City, Louisville, New Orleans, New York City, Philadelphia, Pittsburgh, and San Francisco.

Two traps sit inside the list. North Carolina and Pennsylvania restrict the practice only for state-government employers through executive order, so a private company there can still ask. And Michigan and Wisconsin run the opposite way: they forbid their own municipalities from passing salary-history bans, so no local shield exists in those states.

For a remote role, the strictest applicable jurisdiction often governs. Do not assume the headquarters location controls. Apply the law of where you will actually perform the work.

What each field is really screening for

Every version of this box is a filter, and knowing what it filters tells you how to survive it. The desired-salary field is a budget-fit and routing tool: employers compare your request to their internal pay band to avoid interviewing candidates whose expectations comp cannot meet, and to route you to the right recruiter or approval workflow faster.

• Desired or expected salary compares your number to the internal band to screen and route.
• Minimum salary signals the lowest base you will accept, used to cut anyone below budget.
• Current salary correlates with seniority and title, so a low number can quietly down-level you.
• Salary history excludes people as "too expensive" or, if the number is low, as "poorly qualified."

The current-salary variant deserves the extra caution. Compensation expectations, including current salary, can correlate closely with seniority level and job title, which means one low past number can down-level the entire pipeline routing before a human weighs your actual experience.

A salary-history ban does not delete the filter. It moves it one field to the right.

There is a second reason to get the number right at entry: knockout logic. Auto-rejections are commonly triggered by configured "knockout questions," and some employers configure their ATS for blanket denial based on a salary threshold or a keyword. A number above their band, or a placeholder the system is set to catch, can end the application before anyone reads your resume.

The procedure: from box to submitted number

Work the field in one pass. The steps below move from identifying the variant to logging what you entered, so your numbers stay consistent across dozens of applications.

Sources disagree on step order. Some put "leave blank first" ahead of everything; others say research before you touch the field. I put identification and legality first because both are one-minute checks that change what a safe entry even is, and research is wasted if the field turns out to be skippable or illegal.

Deriving one defensible number

The three-source method exists because recruiters placing a role can differ from public salary data by ten to twenty percent. A single aggregator can miss the real band by that margin, so you triangulate: pull one aggregator range, one structured survey figure, and three real numbers from people you know.

Then convert the range into three figures. Take $80,000 to $88,000: that becomes an $86,000 target, a $93,000 opening ask, and a $78,000 walk-away point. When a field forces one value, use the low-but-defensible end - a number slightly below the midpoint that reduces the risk of pricing yourself out while still protecting leverage.

Role and level: ____________________
Aggregator range: $______ to $______
Structured survey figure (e.g. Robert Half 2026 Salary Guide): $______
Real number 1 (person you know): $______
Real number 2: $______
Real number 3: $______
Derived market range: $______ to $______
Target: $______   Opening ask: $______   Walk-away: $______
Safe single-field entry (slightly below midpoint): $______

Deferral phrasing for a notes box

When a comments or notes box sits beside the required field, anchor to scope and total compensation rather than a number. Enter your real figure in the required numeric field, then use the notes box to keep the door open.

Open to discussing salary based on the role's scope, level, and total compensation. My expectations align with market rates for this position and my experience.

Once you know the number you would defend and the recruiters who screen it, the friction is repetition: retyping the same figure across dozens of forms and keeping every stage consistent. Refolk writes your resume from your own history, tailors it to each posting, and scores how well you fit, so the number you log stays aligned with the story the application already tells.

How this goes wrong

The salary field fails quietly, which is what makes it dangerous. These are the documented failure modes and the check that catches each one.

• Placeholder trust. Entering 000, 999, or 99999 assumes recruiters read it as "open." Modern ATS may filter it, and the false positive is that the form submits, so you think it worked while you were silently screened. Check the specific ATS or company, not generic advice.
• Single-number anchoring. A forced number becomes your ceiling. You may get the interview, then the offer caps near your entry. Log your number and never enter below your walk-away.
• Legality assumption. Believing a ban covers you when only state agencies are covered (NC, PA) or when the state preempts local bans (MI, WI). Confirm private-employer coverage for your exact location.
• Range spread too wide. A $40,000 spread reads as unresearched, and the bottom becomes the offer. Keep the spread near $10,000 with a defensible floor.
• Current-salary conflation. Treating "current salary" like "desired salary" lets past pay down-level you. Enter your target or expected figure, and where legal, decline the history question.
• Weekly-wage misread. Typing an annual figure into a weekly field flags an impossible number. Divide annual by 52 before entering.
• Remote-law blind spot. Assuming the HQ location governs. Remote roles often fall under the strictest applicable jurisdiction, so apply the law of where the work is performed.

The recruiter-density gap explains why the US failure modes bite harder. In Refolk's index, about 91,800 profiles hold recruiter or talent-acquisition titles in the United States against roughly 6,595 in the United Kingdom, a derived 13.9x difference. More recruiters means more human-configured knockouts, so a US applicant hits more of the rules that turn a placeholder or an over-band number into a silent rejection.

Verify before you submit

Run this list on the field in front of you before you click submit. It is the difference between a number that clears and one that quietly screens you out.

Keeping this current

Two facts in this reference move, and both have a mechanism you can re-check rather than a value to memorize. Salary-history-ban coverage expands and occasionally reverses: Virginia's private-employer ban takes effect July 1, 2026, and states like Michigan and Wisconsin have preempted local bans. Before you rely on a shield, confirm private-employer coverage for the exact location on a running legal tracker.

The second is your own market range. Recruiter data drifts from public aggregators by ten to twenty percent, and bands reset over time, so re-run the three-source worksheet whenever you change target roles or metros. If you want to understand who configures the screens you are clearing, you can look at the recruiters themselves.

Do not treat the salary box as an afterthought at the end of a long form. It is a filter with a documented set of shapes, and the entry that survives one shape gets you screened out of another. Identify the variant, check the law, enter a researched number you would defend, and log it. That sequence takes under two minutes once the range is set, and it is the version of this task that does not cost you the interview.