The Salary Field Entry Standard, Graded Pass or Fail Before Submit

The form will not let you move on until you type a pay number, and the number you type does two things at once: it decides whether a screen filters you out before a human reads your name, and it sets the floor an offer gets anchored to later. This guide is for people applying at volume who need to grade that figure fast and consistently. It gives you a fixed pass-or-fail rubric so two people grading the same entry reach the same verdict, instead of choosing between the contradictory advice to "enter 000," "enter 99999," or "always give a range."

Why the usual salary-field advice contradicts itself

The advice you find is split by publication date, not by field type, and that is why it looks like noise. Older pages endorse placeholders; newer pages call the same entries a rejection risk. The mechanism is simple: applicant tracking system (ATS) validation, the automated check a form runs on what you type, got tighter over time.

iHire's career advisor recommends that if a numeric response is required, you use "000" or "999" and note in a comment box that salary is negotiable. Career Sherpa and Credit Karma give the same workaround. But Guidy now warns not to enter 0, because some systems "read it literally and sort you into the lowest band." Status.net agrees that "a placeholder like 0, 1, or 999999 can flag your application for manual review or get screened out." SkillHub reports that aggressively programmed systems reject "0" and "99999" and demand a realistic five-to-six-digit number. A real applicant on Bogleheads hit a form where "a range was not allowed, neither was 'negotiable' or 000."

So a rubric that repeats any single era's blog advice will fail on the next form. The only stable approach grades the figure against how the field behaves and what the label asks, not against a slogan.

Grade the number against how the field behaves, not against whatever a blog told you to type last year.

Who is actually on the other side of the field

The figure you type is first read by a recruiter applying a pay band that someone else designed, and there are far more of the former than the latter. That asymmetry is the single most useful fact for grading an entry.

In Refolk's index of professional profiles, 118,278 US recruiters and talent-acquisition professionals are the population screening these fields. The people who set the bands your figure is graded against - US compensation and total-rewards professionals - number just 2,857. That is roughly 41 recruiters per band-setter.

The practical consequence: most first-pass filtering is done by someone applying a band they did not build. A clean, in-band, correctly-typed number survives that pass. A nuance you could explain in conversation - "I said $140k because I am relocating" - dies at the form, because the person reading it is matching your figure against a range and moving on. That is why the rubric below rewards a defensible number over a clever one.

The grading unit is the floor, not the range

The number to grade hardest is the lowest one you enter, because employers treat it as your bottom line. A researched range with an unlivable floor still fails.

Career Intelligence states it plainly: "most employers will see the lower end of your salary range as your bottom line." So the floor is not a negotiating opener or a friendly starting bid. It is the number you might get. The checkable criterion is a single yes-or-no question: would you sign at your floor today, without hesitation? If the answer is no, the entry fails, and you raise the floor.

This reframes every "range vs number" argument. Whether you enter a range, a single figure, or a dropdown band, you are really committing to a floor. The high end signals ambition; the low end signals your reservation price. Grade the low end as if it is the offer, because it often becomes one.

Read the field label first: minimum, desired, expectations, bare salary

The field's wording encodes a screening function, so a single wrong word can cost you interviews. Read the label before you decide on a number, because the same figure passes in one field and fails in another.

• Minimum salary is a floor. It signals the lowest annual base pay you will accept, and it can be weaponized at offer time to set a hard floor. Enter the number you would sign at today, not your target.
• Desired salary drives screening and routing. Recruiters compare your request to their internal band for budget fit and to route candidates faster. You can pitch this at your target, slightly high.
• Salary expectations and compensation expectations overlap with "desired" but each phrasing carries a slightly different tone. Read the exact wording.
• Bare "salary" defaults to base pay unless the prompt says otherwise, and to a gross figure - pay before taxes and deductions.

The concrete screen risk: if you enter "$140,000" in a "minimum salary" field but your experience reads as a mid-level role, the screen may filter you out early. The same $140,000 in a "desired salary" field, where the recruiter reads it as an aspiration rather than a hard floor, may not. The label changes the grade.

Placeholder entries and what each one triggers

Placeholder numbers are the most common way a volume applicant gets auto-filed, and every one of them carries a documented failure. Grade any placeholder as a fail in a required numeric field unless you have already tested that the form accepts it.

Two of these deserve emphasis. First, "0" is dangerous precisely because the form accepts it, so it looks like success while it quietly bands you at the bottom. Second, text in a numeric field can silently fail: HireFlow documents a case where a field formatted as "$80k+" caused the ATS to fail to parse the number and auto-reject the application. "Negotiable" and "See resume" carry the same risk in fields that expect digits.

How jurisdiction changes the grade

Transparency law converts guessing into anchoring, and it changes the pass criteria by state. In states that require a posted range, you grade your figure against a public number; elsewhere you grade against your own research.

As of 1 July 2026, 18 of the 51 US jurisdictions have a statewide pay-transparency law, and 13 require the salary range in the job posting itself. Posting thresholds vary by employer size, ranging from 4 employees in New York to 30 employees in Minnesota. Salary-history bans are broader still, active in over 20 states; Delaware and Oregon have salary-history bans only. In Virginia, as of 1 July 2026, private employers are prohibited from asking applicants for their salary histories, and in Cleveland, Cincinnati, Columbus, and Toledo, employers with 15 or more employees cannot ask about wage or salary history.

Two practical branches follow:

1. A range is posted. Anchor to it. Grade your figure as pass only if it sits inside the published band, placed according to your requirement-fit (see the next section).
2. A "current salary" field appears in a salary-history-ban state. The ask may itself be non-compliant. You can answer with an expectation for the role rather than your prior pay.

Because these laws and thresholds change, re-check them per role rather than memorizing a list. A 50-state tracker with primary sources, or a law-firm pay-transparency tracker, will tell you the current state of the state you are applying in.

Setting the range spread so it reads researched

A range signals whether you did the work, and the tell is the spread. A tight spread reads as considered; a wide one reads as a guess. Grade the spread against roughly 10 to 15 percent of your floor.

The sources cluster around a tight band. Guidy is explicit: a spread of ten to fifteen percent reads as considered, and a spread of forty percent reads as a guess. ScoutLogic gives the concrete failure - a $30,000 to $70,000 range is too wide. Open Applier prescribes a mechanical version: minimum at 90 percent of your target, maximum at 115 percent. They do not all agree on the exact width, so the rubric grades against a range: keep the spread inside 10 to 15 percent of the floor, and never near 40 percent.

Placement inside the range is graded on requirement-match, and the penalty is asymmetric. If a posting shows $150,000 to $200,000 and you insist you are a $200,000 candidate while meeting only 60 percent of the requirements, that communicates a lack of market awareness. But automatically placing yourself at the floor is not wise either. The strongest candidates are ambitious and grounded: map your years and the posting's bullets to a placement, then defend it.

The procedure: from blank field to graded entry

Run these eight steps on each posting. The first six build the figure; step seven grades it; step eight keeps your later answers consistent. On a form you have seen before, the whole thing takes a couple of minutes.

Refolk can carry the first three steps for you across a batch. When Refolk writes your resume from your history and tailors it to each posting, it also scores how well you fit the role, which is the same requirement-match judgement that decides where in a posted range your number is defensible. That removes the per-posting research friction that makes step three the slowest part of the loop.

How this goes wrong: failure modes and false positives

Most bad entries feel like successes at the moment you submit them, which is why they are worth naming. Each failure mode below comes with the check that catches it before the figure leaves your hands.

• Entering 0 to stay open, then getting banded low. The false positive is that the form accepts it, so it looks like it worked. But some systems read it literally and sort you into the lowest band. Check: never submit 0 in a required numeric field; use your researched floor.
• A high number in a "minimum" field. "$140,000" in a minimum field, when your experience reads mid-level, can filter you out early. Check: minimum equals your livable floor, not your target.
• Floor set as a negotiating opener. The low end is not a starting bid; employers read it as your bottom line. Check: would you sign at the floor today? If no, raise it.
• Base versus total mismatch. Quoting total comp in a base field inflates you out of budget; quoting base where total is asked underprices you. Check: only include bonuses or equity if the prompt asks for total compensation.
• Non-numeric text in a numeric field. "Negotiable" or "See resume" can silently fail to parse. Check: confirm the field accepts text before you type words.
• Top-of-range claim without the match to back it. It feels confident, but claiming the ceiling at 60 percent requirement-fit reads as naive. Check: map your years and bullets to the posting before pitching high.
• Range too wide to read as researched. A 40 percent spread, or a $30k to $70k range, reads as a guess. Check: keep the spread inside 10 to 15 percent of the floor.

The through-line: a figure that clears the form's validation is not the same as a figure that survives the human reading it. Grade for both.

The submit-ready checklist

Run this before every submission. If any item fails, fix the figure and re-grade. All items must pass for the entry to be submit-ready.

Keep the standard current

The two things that move under this rubric are transparency law and ATS validation behavior, so re-check both rather than trusting a snapshot. Laws change by state and by employer-size threshold, and validation tightens over time, which is what turned "000" from advice into a risk.

To keep your grading calibrated to how real screeners and band-setters operate, it helps to see who is on the other side of the field. You can search Refolk's index directly for them.

When you re-check, confirm three things: the posting-requirement states and thresholds for the jurisdictions you apply in, whether the specific ATS a target company uses accepts ranges or text, and whether your researched floor still clears current market medians for the title. Update your paste-ready fallback whenever any of those move, and the rubric keeps grading the same way for you as it would for anyone else running it.