The No-Salary Job Posting, Scored to Apply, Ask First, or Skip

This is a scoring framework for one repeated decision: a posting in your queue shows no pay, and you have to decide whether it deserves an application. It's written for job seekers applying to many companies at once. It covers five dimensions scored 0 to 2, gates and decision rules that end in Apply, Ask First, or Skip, and a record format that lets a second reader reach the same call from the same inputs.

The usual advice is to apply anyway and ask about pay on the first call. That skips a step. You can often price a range-less posting before you apply, and some laws let you request the range. This framework adds that step to every posting, so you stop paying for long interview loops that end below your floor.

Is it worth applying to jobs with no salary listed?

Often it is, but you should look for the pay before you commit. A range-less posting can frequently be priced or asked about in a few minutes, and the missing number is weak evidence of low pay, especially for senior roles.

Three findings set the baseline.

• Opacity sits at the top of the pay scale. Research on Colorado's law found "the highest paying occupations still tend to be the ones with the lowest transparency, suggesting that employers prefer to bargain over the salaries" of these roles. A separate study of 141M job posts found that "among the wages that are posted, high wage firms are more opaque, with more and wider ranges."
• Range-less postings are still common. On Indeed, the share of postings with at least some employer-provided salary information rose from 18.4% to 60% across five years. A stricter "explicit pay" measure from the same tracker reads lower, around 50.4%. The two measures differ, so don't compare them directly. Either way, a large part of your queue will show no pay.
• Some sectors are much worse. In one tracker snapshot, pharmacy postings carried pay only 26.3% of the time, and physicians and surgeons 32.3%. If you work in a low-transparency sector, Skipping every range-less posting would empty your queue.

The survey numbers people quote don't settle the question. Monster reports that 60% of workers say they won't apply to a job without a salary range. Patriot Software reports 44% say they are unlikely to. The two surveys disagree, and both measure what people say they'll do, not what they actually do. They describe a mood, and a mood can't tell you whether this particular posting is worth your time.

Colorado's law gives a partial answer on cost. Researchers found wages rose 1.3% to 3.6% across three datasets after the reform. New-hire wages rose 3% at firms that hadn't shown salaries before, relative to firms that always had. One reading is that opacity cost new hires something at those firms. That supports pricing the role before you accept an offer. It doesn't prove that any single range-less posting pays less.

A missing range on a senior role is a bargaining signal, not a low-pay signal.

The five dimensions and how to score each

Score each posting on five dimensions from 0 to 2: Recoverability (R), Legal lever (L), Application cost (C), Fit (F), and Volume need (V). Higher numbers favour applying. L doesn't go into the total; it decides whether Ask First is available.

R: Recoverability

What it proves: whether you can price the role before applying, and how much to trust the number. A 2 means the employer's own listing shows a range for this location. A 1 means you have a proxy: a sibling posting from another location, or an LCA base-wage filing. An LCA filing is a Labor Condition Application, the public record a US employer files with the Department of Labor before hiring on certain work visas.

How it lies: a proxy can look like a real range. A Seattle range used for a lower-paid location, or a Level I filing used for a senior role, both read as R=1 and both mislead. Write the source location and wage level next to every proxy.

L: Legal lever

What it proves: whether a law entitles you to the range, and at what point in the process. A 2 means you can request it now (California, Rhode Island). A 1 means the range arrives later or through a correction process: Nevada after the first interview, Washington through written notice, or New York and Illinois, where the range belongs in the posting and the original listing probably has it. A 0 means no law covers the role.

How it lies: an employer below the size threshold scores 0 even in a covered state. So does a role whose remote reach you haven't confirmed.

C: Application cost

What it proves: how much effort you lose if the pay turns out wrong. A mandatory assignment or test scores 0. That cost is real: mandatory assignments or tests would put off 34% of job seekers from applying at all.

How it lies: it's easy to rate a cover letter as free when you're tired of writing them. Score the effort as it actually is. Refolk tailors the resume and drafts the cover letter from your own history for each posting, which moves many postings from C=1 toward C=2. That cheapens the application, but it doesn't make an eight-round loop worth sitting through.

F: Fit

What it proves: whether you'd get through screening if the pay were right. Count the posting's must-haves and how many you meet at the level the posting asks for.

How it lies: a matching title inflates fit. Two "Senior Analyst" titles can describe different jobs. Score against the requirements, not the title. Refolk scores fit against the posting itself, which gives you a consistent F that a second reader can check.

V: Volume need

What it proves: how much interview volume you can afford to lose. If you have few live interviews, losing a possible one costs a lot, so V is high. If your calendar is full, V is 0 and you can afford to be strict.

How it lies: V drifts with your mood. Score it from a count of live interviews in your tracker, not from how the week feels.

Which pay transparency laws give you a right to the salary range

A few US states give an applicant a lever on a range-less posting. California and Rhode Island let you request the range. Nevada gives it automatically after an interview. Washington lets anyone flag a non-compliant posting for correction. New York and Illinois require the range in the posting itself, so a missing range there usually means you're looking at a copy, not the original.

Coverage is wider than the table shows. One tracker counts 18 of the 51 US jurisdictions with a statewide pay-transparency law, 15 of which require the range in the posting itself. It lists California, Colorado, Connecticut, Hawaii, Illinois, Maine, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, Virginia, Washington, and DC. Sources disagree on that count, so treat it as a starting point. Employer-size thresholds run from four employees in New York to fifty in Hawaii, and four jurisdictions have no threshold at all.

What triggers each right

• Request: Rhode Island must disclose the wage range if an applicant asks, and must give it before discussing pay even if nobody asks. California must provide the pay scale "upon reasonable request."
• Interview: Nevada must provide the range automatically after an initial interview.
• Posting: in the posting states, the range belongs in the listing itself. Since 1 January 2026, California's pay scale must be "a good faith estimate of what the employer reasonably expects to pay."

None of the sources I found give a fixed number of days for answering a request.

Remote reach

California covers any position that "may ever be filled in California, either in-person or remotely." New York covers work "physically performed, at least in part, in the state." Illinois covers remote employees reporting to Illinois. Connecticut's newer law reaches roles performed outside the state that report to a Connecticut supervisor or worksite. I haven't verified remote reach for Colorado, Washington, Nevada, or Rhode Island. If a role is remote, read that state's agency guidance before you score L.

What a complaint actually gets you

• Washington: any person may give written notice of non-compliance. The employer then has five business days to correct the posting before penalties can apply, and a timely correction means no damages or penalties. Damages otherwise run $100 to $5,000 per violation, plus civil penalties up to $500 for a first violation and $1,000 for a repeat. Well over 200 class actions had been filed before the amendment. Sources expect the cure requirement to effectively stop new ones, because every class member would have to prove they asked for a cure.
• California: an applicant may file the DLSE 001 Pay Transparency Complaint with the Labor Commissioner within one year of learning of the violation. If you have the posting, the complaint goes by PDF to paytransparency@dir.ca.gov. The penalty is $100 to $10,000 per violation, paid by the employer.
• Nevada: penalties run up to $5,000 for non-compliance.

My read of these sources: in Washington, the realistic result for you is a corrected posting. In California, it's a penalty against the employer, and none of the sources describe a payment to the person who complained. Neither gets you the job.

How to find the salary when the job posting doesn't list it

Work down a ladder of sources and stop at the first usable number: the employer's own listing, then a sibling posting in a state that requires ranges, then public LCA wage filings. Each step down gives you a weaker number, so record where it came from.

Rung 1: the original listing

Open the employer's careers page or its applicant tracking system (ATS, the software that hosts its listings) and find the same requisition. Nobody has published how often job boards drop a range that the employer's own page shows, so you can't know without looking. Washington law makes the point directly: a posting does not include a "solicitation for recruiting job applicants that is digitally replicated and published without an employer's consent." A scraped copy isn't the legal posting, and a missing range on it proves nothing.

Rung 2: a sibling posting

Search the same employer and title in a state that requires ranges in postings. Multi-state employers sometimes post the same role in several places. Nobody has measured how reliably they publish per-state ranges for one requisition, so treat a sibling as something to look for, not something you can count on. One finding makes a sibling range usable: after Colorado's law, "employers are not posting wider salary ranges in their vacancies." That means the sibling range probably isn't padded. It's still a range for a different place.

Rung 3: LCA filings

The Department of Labor's Office of Foreign Labor Certification publishes LCA disclosure files. They include:

• employer name and FEIN (federal employer ID number)
• SOC code (the federal occupation classification) and job title
• wage level from I to IV, and the prevailing wage source
• offered wage
• full-time or part-time status, and worksite geography

The limits matter as much as the fields. An LCA wage is what the employer agreed to pay when it filed, and it may not include bonuses, equity, or later raises. A filing doesn't confirm that anyone was hired at that wage. How far the filed figure usually sits from the eventual offer isn't established publicly. So use it as a base-wage floor tied to a date and a level, not as an offer forecast.

Market research

Monster advises seekers to research typical ranges so they can "decide whether to pursue the position or ask about the pay range early in the process." That's why research comes before the ask in the procedure below. A typical range for the occupation doesn't score R, because it isn't this employer's number. It does tell you whether your floor is realistic before you write to a recruiter.

The five-minute scoring procedure

Run these steps in order and stop recovering as soon as a step gives you a number. The time estimates are my own framework estimates, not measurements. Postings that resolve at rung 1 come in under five minutes, and a full ladder runs closer to seven.

The sources disagree on order. Monster's advice puts research before the ask, which is why steps 3 and 4 come before step 7. Nevada's law puts the interview before disclosure, so for Nevada postings step 7 simply becomes "apply, and expect the range after the first interview."

Reading the score: Apply, Ask First, or Skip

Run the rules in order and stop at the first one that applies. Two gates come first, because they can end the decision regardless of the total. After that, the legal lever decides whether Ask First is available, and the total of R, C, F, and V settles the rest.

1. Gate: below-floor range at source. If R=2 and the top of that range is below your floor, Skip.
2. Gate: no fit. If F=0, Skip. Knowing the pay can't fix a weak fit.
3. Range found and it reaches your floor. If R=2 and the range reaches your floor, Apply. C only sets how much effort you put in.
4. Right to ask now. If L=2 and R is under 2, Ask First. In those states, asking costs one email.
5. Everything else: total R+C+F+V.
   • 6 to 8: Apply.
   • 4 to 5: Ask First. Without a legal right, this is a courtesy request. In Nevada, it means apply and treat the first interview as the price of learning the range.
   • 0 to 3: Skip.

Two adjustments keep the rules honest:

• Proxy below floor. If your only number is a proxy (R=1) and it sits below your floor, cap the call at Ask First. The proxy is for another place or only covers base pay, so it can't justify Skip on its own. It also can't justify Apply.
• Senior override. If you're senior and the only thing pulling the total under 4 is R=0, land on Ask First instead of Skip. For senior roles, opacity tracks higher pay, not lower.

The record below is what makes the call reproducible. Someone given only this record should reach the same call.

Posting: [employer] / [title] / [requisition ID] / [worksite or remote reporting location]
Date scored: [date]
My floor: [base pay figure]

Jurisdiction tag: [posting-state | on-request | none] - checked against: [agency page or tracker]
R Recoverability: [0/1/2] - source: [original listing | sibling in (location) | LCA level (I to IV), filed (date)] - figure: [range or wage]
L Legal lever: [0/1/2] - trigger: [request | interview | posting | none] - employer size checked: [yes/no]
C Application cost: [0/1/2] - required: [resume | letter | questions | test or assignment]
F Fit: [0/1/2] - must-haves met: [x of y]
V Volume need: [0/1/2] - live interviews right now: [n]

Gates hit: [below-floor range at source | F=0 | none]
Adjustments: [proxy below floor | senior override | none]
Total (R+C+F+V): [n]
Call: [Apply | Ask First | Skip]
Reason: [one sentence naming the rule that decided it]
Ask sent: [date, or n/a]   Re-check by: [date]

How to ask for the salary range before applying

Ask in writing, name the requisition and location, and cite the right only where one exists. Expect a recruiter to answer, not the person who sets the pay band. No exact recruiter-endorsed wording has been published that I could find, so the message below is built only to be clear and to leave a dated record.

Recruiters vastly outnumber the people who set pay bands:

In a sample of 25 profiles from each group, the most common US title was Technical Recruiter (8 of 25) and the most common UK title was Talent Acquisition Partner (14 of 25). The US compensation group includes people at employers such as Meta, Okta, and Lightmatter.

That ratio shapes the message. The recruiter may not know the band offhand, so give them everything they need to look it up: the requisition ID, the location, and the level. Keep it short and make it easy to forward.

Subject: Pay range for [job title], requisition [ID], [location]

Hi [name],

I'm interested in the [job title] role (requisition [ID]) based in [location, or remote reporting to location].

Before I submit a full application, could you share the pay range for this position at this location?

[California or Rhode Island only: I understand applicants can request the pay range for a position, and I'm making that request here.]

For context, I'm targeting roles at the [level] level, and I'd like to make sure we're aligned before either of us invests interview time.

Thanks,
[your name]
[phone or email]

Three notes on sending it:

• Date it and log it. The dated request is what step 7 asks for, and it's what you'll point to if you follow up.
• Choose your own wait. No source gives a deadline for answering. Pick a follow-up date, write it in the record, and keep to it.
• Silence means different things in different states. Where no law requires an answer, silence is information, not a violation. Where one does, silence gives you a reason to follow up and cite the rule.

How the score goes wrong

The score fails in predictable ways. Most failures come from treating a stand-in as the real thing: a scraped copy treated as the posting, another location's range treated as this one's, a base wage treated as the full offer, or a matching title treated as fit. Check this section before you trust any score that pushes toward Skip.

Recoverability that lies

A sibling posting's range belongs to its own location. The false positive is a high-cost-city range applied to a lower-paid location, which makes a posting look like it clears your floor when it may not. Check whether the employer's careers page shows ranges per location, and always write down where the proxy came from.

LCA data fails the other way. The figure is a base wage at filing time, not the total offer. A Level I filing for a role you'd be hired into at a higher level can make a good job look underpaid. Check the wage level and the filing date before the number touches your score.

A missing range that proves nothing

In Washington, a range missing from a replicated board copy says nothing about the employer, because that copy isn't the legal posting. The same reasoning is worth applying everywhere: until you've seen the original listing, "no range" describes the board, not the job.

Legal levers that aren't there

Seekers often assume they can ask Nevada employers for the range before applying. Nevada's disclosure is triggered by the initial interview, so an ask sent before applying has no legal backing. Size thresholds catch people too: a 10-person employer in a state with a 15-employee threshold scores L=0.

Washington's cure step also has an expiry. The provision expressly expires on 27 July 2027, and a notice sent after that date follows different rules. Check the current statute before you rely on the five-business-day process.

Skip scores that run too high for senior candidates

High-wage firms are more opaque. If you're senior, a range-less posting from a well-paying employer may pay above your floor, and an R=0 drags the total down for the wrong reason. The senior override exists for this case. Use it.

Survey rates used as a rule

The 60% and 44% figures describe what people say about range-less postings. They don't describe what those people did, and they aren't a reason to Skip. If "most people wouldn't apply" is your entire reason for a Skip, rescore the posting.

Ranges that turn out to be soft

Even a posted range doesn't guarantee the offer. In the Patriot survey, 17% of respondents had received a job offer below a publicly posted pay range. R=2 tells you what the employer published, not what it will offer you. Bring the number into the first conversation and confirm it there.

Keeping the score current

The framework stays the same, but the legal inputs change, so re-check them on a schedule. Re-check them whenever you score a posting in a state you haven't checked in a while. Treat any count of covered states as provisional, because trackers disagree with each other.

Watch these moving parts:

• New laws and effective dates. Delaware's law goes into effect on 26 September 2027. When a state's law takes effect, its postings move from L=0 to posting-state, and missing ranges there start to mean "check the original."
• Cure windows and amendments. Washington's five-business-day cure expires on 27 July 2027. Before sending a notice, check the Washington statute or a current employment-law analysis.
• Remote reach. Four rows in the table above are unverified for remote work. If you apply remotely often, check each state's labor agency guidance once and record the answer in your tracker.
• The pay-transparency baseline. Indeed Hiring Lab publishes its pay-transparency tracker as open data under a CC-BY license. Check it to see whether your sector's share of postings with pay has moved, because that changes how unusual a missing range is.
• LCA freshness. Newer disclosure files replace older ones. An LCA floor from an old filing gets weaker as the date ages, so note the filing date in every record.

Once the score is consistent, the time it saves goes into the postings that earned an application. Score the queue in one sitting, send the Ask First messages together, and put real effort only into postings scored Apply.