The Salary Box Entry Run, One Target Range to Every Pay Field You Submit

This is the procedure for anyone sending dozens of applications a week who hits a different salary box at every portal. It turns one researched target range into a fixed entry rule for each pay field type, adds a one-minute check against the posted range and the job location's salary-history law, and keeps a log so the number you give on the first recruiter screen matches the number you typed.

What the salary box entry run produces

The run produces three things: a range card with your floor, target, ceiling and precomputed variants, an entry rule for each of eight pay field types, and an entry log with one row per application. Once these exist, each portal's pay fields take about three minutes: read the posting, classify the field, enter the value, check it, log it.

The pages that rank for "what to put for desired salary on application" answer one box at a time, and they disagree. One says lean toward the top. Another says enter a researched range or a number near the low end of a range you would genuinely accept. An older one recommends placeholders like 0 or 999999999. Each answer might work on a single application. None of them deals with the problem a volume applicant actually has, which is keeping fifty entries consistent with each other and with what you say later.

That consistency matters because recruiters notice when it breaks. One hiring-side write-up describes the pattern exactly: a desired salary on page one, a current salary on page three, and an expected base in a follow-up email that do not line up. Recruiters flag that inconsistency as a risk even when the skills fit. The run is built to make that impossible.

The eight field types this guide covers:

• Single numeric: one box, numbers only.
• Range: one box that takes a range string.
• Two-box range: separate minimum and maximum boxes.
• Free text: a text area where you can write anything.
• Dropdown band: a select list of pay bands.
• Hourly: a rate field, labeled per hour.
• Minimum acceptable: the lowest pay you would take.
• Current or prior salary: what you earn or earned.

Which pay fields can auto-reject you?

Field type sets the risk more than the number does. On Greenhouse, only yes/no, single-select and multi-select questions can trigger auto-reject, so a dropdown pay band can drop you silently, while a typed number in a free-text box always reaches a person.

Auto-reject means a rule in the applicant tracking system (ATS) that rejects an application at submission, based on its answers, before anyone reads it. Here is what the evidence supports, vendor by vendor:

Some Greenhouse details make the dropdown risk worse than it looks:

• If an Auto-Advance rule and an Auto-Reject rule both fire, Greenhouse applies the Auto-Reject rule.
• One rule can combine up to five custom questions with AND conditions, so a pay band can be one gate among several.
• The rejection email is optional, and auto-rejected applicants do not trigger the hiring team's new-application notifications. You may never hear anything, and nobody on the team may ever see your name.

On Ashby, a secondary source says rules evaluate structured fields (yes/no, single-select, multi-select, number, date) at the moment of submission. Its operators include "empty", "equals", "contains", "starts with", "ends with" and a fuzzy "similar to" match. If that is accurate, a blank number field and a placeholder number can both be caught. Ashby also announced that Enterprise customers can set up application questions that appear across all jobs, with auto-reject rules attached, so one company-wide pay question can screen every requisition at once.

What is not established from vendor documentation: whether any ATS rejects a 0 or non-numeric input, how hourly fields are handled, and whether "minimum acceptable" exists as a distinct field type at all. If one portal matters a lot to you, read that vendor's help center rather than trusting a blog's claim, mine included.

How to build one target range and its variants

Build one range per role family: a floor you would accept, a target you will ask for, and a ceiling you can defend, spread tightly enough to show you know the market. Then precompute the hourly and single-number versions, so no portal makes you do arithmetic mid-form.

Allow 10 to 30 minutes per role family. Use two inputs:

• Occupational wage percentiles from the BLS Occupational Employment and Wage Statistics (OEWS) program, the federal survey of pay by occupation and area.
• Posted ranges from the postings you are actually applying to.

Keep the spread tight. Robert Half's example: "$85,000 to $95,000 tells the employer you know the market; $70,000 to $110,000 tells them you're guessing." A wide range also undermines you in a quieter way. Whatever low end you type is the number a recruiter remembers.

Converting between annual and hourly

BLS annualizes hourly wages on "a year-round, full-time figure of 2,080 hours (52 weeks × 40 hours) per year," and warns that these figures "may not represent annual pay should the workers work more or fewer than 2,080 hours per year."

The 2,080 basis is where most hourly entries go wrong. If you take an annual target, divide it by 2,080, and enter that rate on a 30-hour posting, you under-ask by 25%, because 30 hours a week is 1,560 hours a year, not 2,080. Always divide by the posting's stated hours. For some occupations that do not work 2,080 hours a year, OEWS publishes hourly wages only, such as teachers, pilots and flight attendants. For those, start from hourly data rather than converting.

One limit: I found no published guidance on folding shift differentials or overtime into an application entry. My default is to enter base rate only, so the figure stays comparable across postings, and to raise differentials on the call. Treat that as my practice, not a standard.

ROLE FAMILY: [e.g. Senior analyst, full-time]
Floor (lowest base I accept): $85,000
Target (what I ask for): $90,000
Ceiling (top I can defend): $95,000

Range string (free text, range fields): $85,000 to $95,000 base, depending on scope
Single number (one numeric box): $90,000
Two-box: min $85,000 / max $95,000
Minimum acceptable: $85,000
Hourly at 2,080 hrs: floor $40.87 / target $43.27 / ceiling $45.67
Hourly at posting's hours: annual figure / (weekly hours x 52)
Current salary policy: blank in ban jurisdictions; otherwise decline or state, never contradict desired

What is the entry rule for each pay field type?

Type a real number from your range card into every field that accepts one, choose the band that overlaps both your range and the posted range, and treat minimum-acceptable and current-salary boxes as separate questions with separate answers. Placeholders are out.

The sources disagree on desired salary, and I have taken a side. The top-of-range advice and the low-end advice both assume one application read closely. Placeholder advice assumes the form takes text and a person reads it. At volume, on forms that may filter numbers and blanks, the only entry that stays safe and consistent is a real figure taken from one card.

When the posted range sits below your target

There are three cases:

1. Posted top is at or above your target. Enter your target.
2. Posted top falls between your floor and your target. Enter the posted top. You stay inside the range, and negotiating up from the top of a range is a normal conversation.
3. Posted top is below your floor. Decide whether to apply at all. If you do, enter your floor, and expect a structured field to reject you.

The only published reference I found for how far above a range a recruiter will go is an illustration from a recruiter-side guide: a range that tops out at $120,000, with a hiring manager who agrees to go up to 10% higher, gives a threshold of $132,000. That is one example, not a reported norm. Do not plan around 10%.

Minimum acceptable is not desired salary

A minimum-acceptable box asks for your floor directly. Type your floor. A figure below your real floor will come back at offer stage, and anything above it misstates what you would take. Search pages for "minimum acceptable salary field job application" mostly fold this into desired-salary advice. It is a different question, so log it separately.

Be honest about how thin the evidence is here. One article claims that most employers use the salary answer to screen before a first conversation, but it gives no figure or link, so treat it as unverified. Secondary sources agree on the direction: too high can end an application, and too low can be read as underqualified.

Which salary-history rule applies to this posting?

The rule that governs a current-salary box is the job location's, not yours. There is no federal salary history ban in the US, so the answer depends on the state and sometimes the city where the role is based.

One published list covers California, Colorado, Connecticut, Delaware, Hawaii, Illinois, Maine, Maryland, Massachusetts, Minnesota, Nevada, New Jersey, New York, Oregon, Rhode Island, Vermont, Virginia and Washington, plus the District of Columbia. I have verified citations for these:

Points that change what you type:

• California still allows the salary expectation question. Section 432.3(j) permits asking about "the applicant's salary expectation for the position being applied for." The desired-salary box is lawful. The current-salary box is the restricted one. Penalties run from $100 to $10,000 per violation.
• Volunteering is what costs you the protection, not being asked. California says nothing prevents an employer "from considering or relying on that voluntarily disclosed salary history information." Whether typing into an optional current-salary box counts as volunteering is arguable. I found no ruling on it.
• NYC makes multistate disclaimers unlawful. An application "may not include a request for information about applicants' salary history, even if the employer makes clear that a response is voluntary." The same form can be lawful for a Texas requisition and unlawful for a NYC one.
• New York State goes further than NYC and covers seeking any compensation information, including counteroffers.
• Virginia applies to all private employers with no size threshold, and also requires posting a wage range. Check the statute's current status, since its effective date is fixed in the text.

Lists disagree at the edges. One includes Alabama, whose law covers only retaliation against candidates who decline to answer. Another includes Michigan, even though Michigan and Wisconsin prohibit local jurisdictions from enacting salary history bans. The first ban passed in Massachusetts in August 2016, and states keep adding them, so recheck against a maintained source such as HR Dive's running salary-history list before you rely on any list, this one included.

For the question "should I enter current salary on job application" outside a ban jurisdiction: you can still decline. If you answer, the figure must reconcile with your desired entry on the same form.

Who reads the number you type?

After the ATS, your salary entry is almost always read first by a recruiter, not a compensation specialist. In Refolk's index of professional profiles, US recruiters outnumber compensation and total rewards professionals by roughly 25 to 1.

The inference, which I flag as unverified, is that first-pass reading of salary answers falls mostly to people applying a range someone else set. A recruiter holding a posted range does a quick comparison: inside, above, or below. That is why the entry rules above aim for clean in-range figures and a short range string rather than nuanced prose. The nuance belongs on the call.

Title mix matters if you apply across countries, because it tells you who is likely holding the range:

The US sample includes some off-target titles, so read the title shares as indicative only.

The pay field procedure, step by step

The procedure is eight steps. The first two happen once per role family, and the rest take about three minutes per posting. Run them in order on every application, including the ones that feel obvious, because skipped steps are where the inconsistency creeps in.

Steps 3 and 4 fit into the reading you already do for each posting. If you use Refolk to tailor the resume and score your fit for each posting, do the pay classification in the same pass. You are already reading the posted range and location to judge fit, so capturing them for the log costs nothing extra. The fit score is also a reasonable input to the single-number choice. A strong fit supports entering your target. A weak fit is a reason to ask whether you should apply at all, not a reason to drop below your floor.

Step 7 is the one people skip, and it is the one that pays off. Employers are told to document in writing when a candidate volunteers salary history. You should keep the same discipline about everything you enter. The log is a plain spreadsheet:

Date | Company | Role | Job location | ATS | Posted range | Field type | Exact entry | Second pay field (type: entry) | History rule | Screen date | Said on screen
2024-xx-xx | Example Co | Senior Analyst | Austin, TX | Greenhouse | $80,000 to $100,000 | Free text | $85,000 to $95,000 base, depending on scope | Current (optional): left blank | No state ban found | |

Fill the last column after each call. If what you said differs from what you typed, note why. That one cell is how you catch drift across fifty applications before a recruiter does.

Refolk also drafts the cover letter for each posting. If a posting asks you to state salary expectations in the letter, paste the same range string from your card, so the letter and the form say exactly the same thing.

How the salary box entry run goes wrong

Most failures are not bad numbers. They are the right number typed into the wrong kind of field, the wrong unit, or the wrong jurisdiction, and each one has a check that takes seconds.

1. Placeholder 0 or 999999. On forms with "number" or "empty" rules, the placeholder itself can trip a condition, and recruiters mostly advise against all of them. Check: does the field accept text? If it does not, type a real number from your card.
2. A band choice on a dropdown that misses the posted range. On Greenhouse, select fields are the only type that can auto-reject, so picking a band above the posted range is the highest-risk click on the form. Check: confirm the band you pick overlaps the posted range.
3. Current and desired that clash on the same form. A current figure sitting below desired on the same form can look like a typo or misclick to recruiters, and any pair you cannot explain in one sentence reads as risk. Check: look at both fields side by side before you submit, and have the explanation ready for the call.
4. Answering current salary in a ban jurisdiction. In California and NYC, an unprompted disclosure can be relied on, which means it can be used against you. Check: confirm the job location, not your own.
5. Hourly entered as annual, or the reverse. "52" against "52000" is a different application. Check: find the unit label, then recompute using the posting's hours, not 2,080 by default.
6. Volunteered history on a NYC requisition using a multistate form. A "voluntary" checkbox does not make the question lawful, but your answer still exists once you type it. Check: leave it blank or write "N/A per NYC law".
7. The spoken number drifts from the logged number. Three weeks and forty applications later, you will not remember what you typed for this one. Check: read the log row before every screen call.

Two false positives give people false confidence:

• "The form accepted it, so it's fine." Acceptance at submission says nothing about whether a rule then rejected you. Greenhouse auto-rejections can go out with no email and no notification to the team. Silence after a structured pay answer may be a filter, not a slow recruiter.
• "The 10% example means I can go 10% over." The $120,000 to $132,000 figure is one recruiter-side illustration. It shows the mechanism, a manager-approved stretch above the top, not a norm you can count on.

The number is rarely the mistake; the field type, the unit, or the jurisdiction usually is.

Before you submit, and keeping the run current

Run the checklist on every application before you press submit, then refresh the inputs on a schedule rather than when something breaks. The range card, the jurisdiction list and the vendor behavior all change, and none of them will tell you when they do.

Keep the run current:

• Range card: rebuild when you change role family, and whenever three or more postings in a row show ranges that sit wholly above or below your card. A card that disagrees with the market will fail the in-range test on every form.
• Jurisdictions: recheck the salary-history list each time you add a new state or city to your search, against the statute text or a maintained running list. Statutes with future effective dates, like Virginia's, change status on that date.
• ATS behavior: if a portal you rely on runs on one vendor, read that vendor's own help pages on application rules once. Vendor tiers and question types determine what can filter you, and secondary write-ups lag behind.
• Log hygiene: fill in the "said on screen" column the same day as each call. The log only protects you if it records both what you typed and what you said.