The Pay Field, Carried Entry by Entry Across One Application Batch

You have a dozen applications open. One asks for a single required number, one gives you two boxes for a range, one wants a weekly rate, and one has a current-salary box in a state where asking is illegal. This guide is for a job seeker running a real batch who has already set a pay position and now needs to type the right value into each form variant without lowballing or getting screened out. I carry one worked batch through every fork, show the exact value typed into each variant, and mark the entries that backfired.

The position-setting work is a separate job, covered in Refolk's guide on setting a search-wide pay position once and holding it. Here I assume you already have your number. The problem this guide solves is the last mile: the field in front of you does not match the answer in your head, and you have eleven more to fill.

Why the pay field breaks a set position

The pay field breaks even a well-set position because the form dictates the format, not you. You decided on one annual figure; the form wants an hourly rate, or two boxes, or a required single number with a digit-only mask, and each one turns your one decision into a different typing choice.

There are, in practice, five field variants, and each accepts something different. A free-text box takes words like "negotiable." A required single number rejects blanks and often rejects non-numerals. An optional field can be left blank. A two-box min/max range wants two figures. And a rate field wants an hourly, weekly, or monthly number instead of an annual one. Which specific validation each applicant tracking system enforces - character limits, digit-only masks - is not established publicly at the vendor level, so you cannot look it up in advance. You classify the field when you see it.

The hiring side understands this unevenly too. In Refolk's index of professional profiles, only about 6.9% of the 131,376 US recruiters listed as recruiters or talent-acquisition specialists list ATS as a skill. That thin fluency is part of why field behavior is inconsistent: the people configuring these forms often do not deeply understand the software's screening rules either.

The batch I am carrying through this guide

The worked example is a job seeker with an annual anchor of $52,000 and a defensible band of $48,000 to $56,000, applying across a dozen postings. I follow the forks that actually appear in a batch: a required single number, a two-box range, a weekly rate field, and a current-salary box in a ban state. For each, I show the value typed and the outcome, including the two entries that backfired.

The anchor of $52,000 is deliberate because it converts cleanly and shows the arithmetic without rounding noise. Substitute your own number; the mechanics are identical. The point of carrying one batch is that a generic "what to put for desired salary" answer does not survive contact with the specific form on your screen. You need to know which fork you are at.

Convert the anchor to every format before you start

Convert your annual anchor into hourly, weekly, and monthly rates once, before you open a single form, so you never do arithmetic inside a live application. The standard formula assumes a 40-hour workweek across 52 weeks, which equals 2,080 total work hours a year, so hourly rate is annual salary divided by 2,080.

Weekly is annual divided by 52, and monthly is annual divided by 12. If the role runs a 37.5-hour week, use 1,950 as the divisor instead of 2,080, because 37.5 times 52 is 1,950. Getting the divisor wrong is a real failure mode: using 2,080 for a 37.5-hour role overstates or understates your hourly figure enough to matter on a rate-field form.

Here is the anchor and three nearby figures converted to every field format, so you can see the shape of the math.

Write your own row as a single cheat line you can paste from. For the $52,000 batch it reads: annual $52,000 / hourly $25.00 / weekly $1,000.00 / monthly $4,333.33.

Annual: $52,000  |  Hourly (/2,080): $25.00  |  Weekly (/52): $1,000.00  |  Monthly (/12): $4,333.33
Band: $48,000 to $56,000  |  Hourly band: $23.08 to $26.92

Which entries advance and which trigger a knockout

An above-budget single number is the documented knockout; a below-market number almost always advances but sets a low ceiling for the rest of the process. These two errors are not symmetric, and understanding the asymmetry is the whole game.

The knockout is a ceiling test, not a floor test. The salary desired field acts as a brutal, efficient filter: if a company has a strict maximum budget of $80,000 and you type $110,000, the system automatically moves your file out, assuming you will reject any offer. Nothing tells you this happened. The below-market error is the opposite - it advances you but anchors the offer low, and the cost is realized at offer stage, not application stage. That is exactly why batch logging matters: you cannot feel a lowball, you can only see it later against your callbacks.

If your expectation is way under the range, it can signal you are too junior; way above, that you are over-qualified. The top edge of any range you enter is what gets tested against budget, so keep it defensible and inside what you believe the band is.

Placeholders are their own trap. Entering "99999" or "00000" appears unprofessional and may cause automated systems or recruiters to flag your application. Zeros are genuinely contested: one view holds that a human recruiter reads a string of zeros in the desired-salary box as leaving the conversation open, which is a recognized signal; a staffing-firm view holds the same string is a flag. The mechanism split is simple - humans interpret, parsers reject. If the field is numerals-only and machine-screened, a real range beats zeros every time.

You cannot feel a lowball. You can only see it later, against your own callback log. </pull> Note on the frequently cited Glassdoor figure - that 59% of workers who accepted a first offer without negotiating left $5,000 to $10,000 a year on the table - I flag it as cited secondhand and needing primary confirmation. Treat it as a directional reminder that the below-market error compounds, not as a hard number. ## Geography decides whether the field is even legal Before you triage field variants, triage by geography, because in some jurisdictions the current-salary box should not exist at all. As of mid-2026, 18 states plus Washington, D.C. have a statewide law restricting employers from asking about pay history or relying on it. Those states are California, Colorado, Connecticut, Delaware, Hawaii, Illinois, Maine, Maryland, Massachusetts, Nevada, New Jersey, New York, Oregon, Rhode Island, Vermont, Virginia, and Washington, plus D.C. Virginia's law takes effect July 1, 2026. Two more states, North Carolina and Pennsylvania, restrict the practice only for state government employers through executive order, not for private businesses statewide. Local bans exist independently in Chicago, Kansas City, Louisville, New Orleans, New York City, Philadelphia, Pittsburgh, and San Francisco. Counts of local ordinances vary by source and date, so re-check the specific city rather than trusting a running tally. | Jurisdiction type | Employer may ask current salary? | Example | |---|---|---| | Statewide ban (18 states + DC) | No | California, New York | | State executive-order only | Private employers: yes | North Carolina, Pennsylvania | | Local ordinance, no state ban | Depends on employer size and location | Cincinnati (15+ employees) | | No ban | Yes | Arkansas | Two subtleties trip people up. First, a ban covers past and current pay, not your desired pay - refusing to state expectations is not protected, only the past-salary box is illegal. Second, a state ban does not automatically cover a small employer under a city ordinance; Cincinnati and Toledo apply only at 15 or more employees. Check the exact work location and headcount. When a current-salary box appears in a ban state, it usually means a stale template copied across jobs, the same mechanism that leaves the wrong pre-screening questions attached to a posting.

callout kind: warning title: Do not disclose past pay where it is illegal to ask If a current-salary box appears in one of the 18 ban states or D.C., treat it as improperly present. Enter your desired figure or contact recruiting. Never type a past-pay number into a field the employer is barred from asking.

To sanity-check a band before you type in a ban jurisdiction, it helps to reach a real gatekeeper who configures these fields.

The procedure, entry by entry

Here is the full procedure, matching the steps you will follow on your own batch. It runs from setting one anchor to logging what advanced.

Walking the forks with the real values

Now the batch itself, fork by fork, with the value typed and the outcome.

Optional field, blank allowed. Posting one left the desired-salary field optional. Entry: left blank. Ideally you either leave the field blank or put "negotiable," and blank is cleanest when the form permits it. Outcome: advanced.

Free-text box. Posting two accepted words. Entry: "negotiable." Outcome: advanced. Sources disagree on ordering here - some say try blank first, then "negotiable," then a number - but in a true free-text box, "negotiable" is safe.

Required single number, numerals only. Posting three forced a figure and rejected letters. First entry: "negotiable," which triggered a validation error and forced a number anyway. That was the first backfire. Corrected entry: $54,000, the top of the band but inside the employer's posted range. Outcome: advanced. The lesson is to always have a real number ready as fallback for a numerals-only box.

Two-box min/max range. Posting four gave two boxes. Entry: $48,000 min, $56,000 max. Outcome: advanced. The range field is the friendliest variant because it lets your position breathe; keep the max defensible.

Weekly rate field. Posting five wanted a weekly figure. Entry: $1,000.00, straight from the cheat line. Outcome: advanced. Had I done the math live and used the wrong divisor, the number would have been off.

Required single number, above budget. Posting six was the second backfire. Reading the posting fast, I typed $62,000 into a role whose band topped out near $55,000. Outcome: no callback, no error message, silent knockout. This is the ceiling test in action - the file moved out with no notice.

Current-salary box in a ban state. Posting seven, worked in California, showed a current-salary box that should not have been there. Entry: I skipped the past-pay disclosure and put my desired figure of $54,000, then noted it as a stale template. Outcome: advanced.

How this goes wrong

The most valuable part of this job is knowing the failure modes, because most of them are silent. Here are the ways the pay field defeats a good position, what each looks like, and how to check.

• Above-budget single number. Goes wrong silently: your file is auto-moved out with no notice. Check by comparing your entry to the posted range or asking the recruiter their band before typing.
• Zeros as a "signal." False positive: you think a human read it as "negotiable," but an automated parser reads 0 as out-of-band or garbage and flags it. Check by preferring a real range if the field accepts numerals only.
• Blank in a required field. Looks submitted but silently blocks completion. Check that the form actually advanced to the next page.
• "negotiable" in a numerals-only box. Triggers a validation error and forces a number anyway. Check by having a real number ready as fallback.
• Treating salary-history and salary-expectation as the same field. A ban covers past pay, not desired pay; refusing to state expectations is not protected. Check that only current or past-salary boxes are the illegal ones.
• Assuming a state ban covers a small employer under a city ordinance. Cincinnati and Toledo apply only at 15 or more employees. Check employer headcount and exact work location.
• Wrong divisor on rate fields. Using 2,080 for a 37.5-hour role overstates or understates hourly pay. Check the standard workweek before converting.
• Lowball that advances but caps you. No knockout, so it feels like success, but it sets the ceiling. Check callbacks against entered value to see the tradeoff.

The matrix below sorts the four typing errors by how loud they are and how much they cost, so you know which ones to hunt for.

Wage optimism concentrates among the lowest earners, who tend to anchor to their pre-unemployment wage and display overly optimistic expectations. That means the people most at risk of the above-budget knockout are often those least able to gauge the band, which is one more reason to anchor to researched market data rather than to what you used to make.

Keep the batch honest with a log

The single habit that makes this repeatable is logging every entry against its outcome, because the two most expensive errors leave no trace at submission time. Record the posting, the variant, the exact value you typed, and the callback result, then review the table for what advanced versus what got knocked out.

Posting | Location | Field variant | Value typed | Legal to ask? | Outcome
Role A | Remote (CA) | Optional-blank | (blank) | n/a | Advanced
Role B | Austin TX | Free-text | negotiable | Yes | Advanced
Role C | Remote | Required-single | $54,000 | n/a | Advanced
Role D | Chicago | Two-box range | $48,000 / $56,000 | No | Advanced
Role E | Dallas TX | Weekly rate | $1,000.00 | Yes | Advanced
Role F | Remote | Required-single | $62,000 | n/a | Silent knockout
Role G | Los Angeles | Current-salary box | desired only, $54,000 | No (ban state) | Advanced

Reviewing the log is where the asymmetry becomes visible. Role F got no callback and no message - the silent knockout of an above-budget number. The advanced rows are not automatically wins either; any of them entered below market advanced while quietly setting a ceiling. The log turns invisible costs into something you can see and adjust.

Keeping this current

The arithmetic is stable - 2,080 hours for a full-time year does not change - but the ban geography does, so re-check the map rather than trusting a number you memorized. Virginia's statewide law, for example, takes effect July 1, 2026, and local ordinance counts vary by source and date.

When you start a new batch, re-verify two things: the statewide list against a running legal tracker, and any specific city where your target employers sit, because local bans move independently of state law. Refolk tailors each application to the posting and scores how well you fit, which surfaces the pay-field variant and the work location for each role so you are not classifying blind. The mechanics in this guide stay the same; only the map of where the current-salary box is illegal shifts under you.