The Per-Posting Pay Screen, Scored to Apply, Probe, or Skip

You are working down a list of postings and you need one repeatable judgement, run the same way every time: is this role's pay worth spending an application on before you invest the hours? This guide is for a volume applicant, not someone deciding on a single dream job. It gives you a scored screen with defined pay-signal inputs and a three-way route - apply now, apply-and-probe-pay-early, or skip - that you can run in under two minutes per posting.

The reason to score instead of read is simple. Most advice on this answers one narrow question ("should you apply to a low-range job? yes, probably") as a pep talk. That does not help when you have forty postings open. A pep talk gets read once; a screen gets run forty times. What follows is the screen.

Why pay is the first filter, not effort

Screen on pay first because the application itself is cheap and the interview cycle is not. An audit of Fortune 500 apply flows found applications took, on average, only about 5 minutes to complete, even though the forms buried that in an exorbitant number of steps. The expensive thing is what happens after you apply: a hiring process that now runs about 44 days, against roughly 250 applications per corporate opening with only 4 to 6 people invited to interview and one hired.

So the real cost of a bad application is not the form. It is the loop you burn on a role that was never going to pay you. That reframes the whole exercise. When effort was the scarce resource, "just apply to everything" made sense. It no longer does, because effort is no longer scarce - your attention across a 44-day funnel is.

There is a second reason to lead with pay. A missing range now functions as a filter that other candidates respond to. A Gartner survey of about 3,500 candidates found 44 percent did not apply to a role because no range was listed. That means the pools for opaque postings are smaller and, on average, more desperate. If you can estimate the pay on a no-range role and it clears your floor, your relative leverage is higher, not lower.

The scarce resource is not the application form, it is the interview loop you waste applying blind.

What the pay signal actually tells you

Every posting gives you exactly one of three pay signals, and each one means something different. Classify first, because the route depends on the category, not on how you feel about the company.

The three categories:

• Explicit range. A stated minimum and maximum, usually because law or policy compels it. This is the only category where you can score against a real number, and even here the number is a good-faith estimate, not a promise.
• Vague band. A very wide spread, or language like "competitive," "DOE," or "commensurate with experience." This looks like information and is not. Treat it as no usable number.
• No number. Silence. This is the highest-uncertainty category, but not automatically the lowest-paying one.

The market context matters when you decide how much weight to give silence. Roughly half of US postings now carry pay, up from an average of about 15 percent before 2018 to around 53 percent since the start of 2024. Disclosure varies sharply by country, which matters if you apply across borders.

Shares from Indeed and Indeed Hiring Lab tracking. Sources conflict on the exact US level; "roughly half, rising" is the defensible reading.

In a market like Germany, where only about 12 percent of postings disclose, silence is the norm and tells you almost nothing. In the UK or US, where more than half disclose, silence is more of a choice and worth reading harder.

Reading band width: what a real range looks like

Band width is a proxy for how much the number can lie to you. A tight band is a genuine estimate; a very wide band is either legal box-ticking or a signal of wide discretion to lowball. Use the NYC compliance data as your reference for "normal."

In NYC's salary-transparency data, more than 80 percent of posted ranges had a maximum no greater than 1.5 times the minimum, and in all but 3 percent of ranges the maximum was less than double the minimum. That gives you a hard working threshold: a band wider than about 1.5x its minimum is an outlier.

The trap here is treating a wide band as a real range. A spread of 20,000 to 200,000 satisfies nobody, and California has flagged such bands as non-compliant. If you score that "pass" on the minimum, you have been fooled by a number that was never meant to inform you. When the maximum runs past 1.5 to 2 times the minimum, treat it as "no usable number" and route to probe.

The other reason a range lies: employers commonly open new hires 10 to 15 percent below the midpoint, justifying it as room to grow. So the number that predicts your offer is closer to the minimum than the middle. Score against the minimum plus a small margin, never the midpoint.

Jurisdiction: when silence is a violation, not a choice

Check the work location because in a mandate state a missing or absurd range may be non-compliance rather than a neutral omission. The list of jurisdictions requiring disclosure varies by counting method - one tracker cites 27 US jurisdictions with enacted laws, others cite 18 states plus DC - but the mechanism matters more than the count.

Selected US posting-range mandates. Requirements and effective dates change; verify against the specific state law rather than this snapshot.

Two things to hold in mind while reading a mandate state. First, compliance is partial: the NY Fed found roughly a quarter of listings covered by these laws still fail to include salary information. So "it is a mandate state" does not guarantee the number is present or trustworthy. Second, most laws exempt small employers, so a missing range from a five-person startup in a mandate state is probably legal, not evasive. Confirm company size before you infer intent.

The states also differ in what they compel. Colorado, Maryland, and Illinois-style laws require range plus benefits and other compensation, while others require only a wage range. When a Colorado posting shows a bare number and no benefits, that is itself a mild signal of a thin listing.

The screen, step by step

Run these seven steps in order on each posting. The first six take about 90 seconds combined; the seventh only fires for the probe route.

Here is how the scores combine into a route. This is the part you memorise so the whole thing runs in under two minutes.

The logic is deliberately asymmetric. The floor score is a gate: fail it and nothing else matters, because a number that is already too low rarely climbs at offer. Trust and effort only sort the survivors into apply versus probe. A tight, floor-clearing range on a quick-apply form is the cleanest apply-now you will see. A no-number role where the market rate plausibly clears your floor is the classic probe.

Tailoring each surviving application to the posting is where volume applicants lose hours, and it is the point where a tool pays for itself. Refolk writes your resume from your own history, tailors it to each posting, drafts the cover letter, and scores how well you actually fit, so the screen decides which roles are worth applying to and Refolk handles the applying.

How this screen goes wrong

The screen fails in predictable ways, and every failure is a false positive or a false negative you can catch with one check. This is the part to reread before you trust your own routing.

• Treating a wide band as a real range. A 20,000 to 200,000 spread scores "pass" on its minimum and fools you. Check: if the maximum runs past 1.5 to 2 times the minimum, treat it as no usable number and route to probe.
• Reading silence as employer choice everywhere. In a mandate state, a missing range may be non-compliance, not a small exempt firm, and you skip a good role assuming they hide low pay. Check: confirm company size, since small employers are exempt in most states.
• Anchoring on the midpoint. Offers commonly land 10 to 15 percent below the midpoint, so scoring your floor against the middle overstates likely pay. Check: score against the minimum plus a small margin.
• Combining the 5-minute and 44-minute figures. One is observed click-time, the other self-reported total effort; blending them warps your effort score. Check: use the observed time for quick-apply and the self-reported time for tailored applications.
• Assuming the posted range binds the offer. No statute found guarantees an in-range offer; the standard is good faith. Check: probe pay early rather than trusting the band to hold.
• Trusting national compliance stats for your state. The roughly 25 percent non-compliance figure is an average, and your jurisdiction may differ. Check: verify against the specific state law, not the aggregate.
• Over-indexing on "17 percent got below-range offers." That is one survey of 1,000 people, not a rigorous panel. Check: treat it as directional, not a base rate for your role.

Where the evidence is thin, I say so. There is no rigorous published correlation between specific posting features and eventual below-midpoint offers, so band width and vague titles are practitioner-documented signals, not proven predictors. Use them to route toward probing, which costs you a question, not toward skipping, which costs you a role.

Reading supply: why your floor moves by market

Talent-pool depth predicts your negotiating floor, and it is a signal the posting will never show you. When a title has deep supply in your market, employers feel less pressure to move off the low end of a band, so you should widen your skepticism of the posted minimum. In Refolk's index of professional profiles, the US Software Engineer pool is roughly eight times the size of the UK's.

Counts and regions from Refolk's index; the ratio is derived from the two counts.

The practical read: in a high-supply market for your title, weight the posted minimum more heavily as your likely offer, because the employer has many alternatives. In a thinner market, the top of the band is more reachable. This does not change the screen's mechanics; it changes how conservative you set your floor before you run it.

You can check the supply picture for your own title and market before you decide how skeptical to be. That is the kind of question Refolk's index answers directly.

Scripting the probe

For every role you route to probe, the goal is to confirm the band before you invest interview time. You can ask even in non-mandate states; the worst case is a non-answer, which is itself information. Timing is a judgement call, because sources disagree on where in the funnel pay surfaces - some say the first call, some say the offer stage. Ask early and accept that you may get deflected once.

Hi [name], thanks for reaching out about the [role] position - it looks like a strong fit for my background.

Before we schedule the next round, could you share the budgeted range for the role? I want to make sure we are aligned on compensation before we both invest time in the process. My target is in the [figure] range based on the market for this work.

Happy to walk through my experience on a call once we know we are in the same ballpark.

Two rules for the probe. First, name a target anchored to the market and your floor, not to the posted midpoint. Second, if the answer is a non-answer or a number under your floor, that converts the probe into a skip immediately - you have spent one message, not one loop.

Keeping the screen current

Run this checklist before you trust a session's worth of routing decisions. It catches the failures above and keeps the screen honest as laws and your own floor change.

The screen is evergreen in shape but not in inputs. Disclosure laws are still spreading, with Virginia and Maine effective in mid-2026 and Delaware signed for 2027, and the share of postings with pay keeps rising. Re-check three things quarterly: the mandate states relevant to where you apply, the current disclosure share for your market so you know how to weight silence, and the supply depth for your title so you know how conservative to set your floor. The method stays the same; the numbers you feed it move.