Do I Have to Post Salary Ranges for My Remote Job Listings in Every State?

You posted one remote job listing. You did not think about which states it touched.

Turns out, it touches more than your headquarters. If the role could be performed from a state with a pay transparency law, that law may apply, whether or not your company has ever had an office there.

Get this wrong across enough job posts and you are not looking at one mistake. You could be looking at separate violations for each noncompliant posting.

As of 2026, 18 states plus Washington, D.C. require salary range disclosure in job postings, with California, Colorado, Illinois, New York, and Washington among them.

California also tightened its rules through SB 642, signed in October 2025 and effective January 1, 2026. The law redefined “pay scale” as the good faith estimate an employer reasonably expects to pay, making it harder to use an extremely broad range that provides little useful information.

Virginia joined the list on July 1, 2026, while also banning employers from asking applicants about their salary history.

Which State’s Law Applies to a Remote Job?

Your headquarters does not necessarily determine which pay transparency laws apply.

For a remote position, you generally need to look at every state where the employee could actually perform the job.

So if your company is based in Texas but advertises a fully remote position that can be performed from California, New York, Colorado, or another covered state, those states’ requirements may affect the posting.

This is why a single national job template can create problems.

One posting may reach employees across several jurisdictions, each with different requirements.

What Does “Good Faith” Salary Range Mean?

Posting a salary range does not mean you can choose any numbers you want.

California’s SB 642 requires the range to reflect what the employer genuinely expects to pay for the position. An intentionally enormous range that covers every possible outcome may not satisfy the requirement.

For example, posting “$50,000 to $250,000” for a position when the company realistically expects to pay around $90,000 to $110,000 could create questions about whether the posted range is a genuine estimate.

Your compensation team should therefore have a reasonable basis for the range appearing in the job advertisement.

Which States Require Salary Disclosure?

As of 2026, 18 states plus Washington, D.C. require salary range disclosure in job postings.

The listed states include:

• California
• Colorado
• Illinois
• New York
• Washington
• Virginia, effective July 1, 2026
• 12 additional states plus Washington, D.C.

The list is not static.

New requirements can take effect throughout the year, which means your hiring process needs a way to track changes rather than relying on one template forever.

Why Multiple Violations Can Add Up

One incorrect job posting may not seem like a major issue.

But imagine your company has 30 open remote positions using the same outdated template.

If each posting represents a separate violation, your exposure can multiply across every active listing.

Penalties can range from $100 to $250,000 per violation, depending on the jurisdiction.

That makes template management more than an HR task.

It becomes a compliance control.

Your ATS Can Become Part of the Problem

Your job posting template may be correct while your applicant tracking system (ATS) continues generating outdated listings.

For example, HR may update the standard template but fail to update the ATS fields that automatically populate salary information.

Or your recruiting team may copy an old job description instead of using the new approved version.

Outdated HR language, outdated ATS fields, and the absence of an owner for tracking legal changes are recurring problems.

Your compliance process therefore needs to cover the entire publishing workflow.

Common Founder Mistakes

• Assuming headquarters location controls: Founders may believe that if the company is based in a state without a pay transparency requirement, the company does not need to disclose salary information. For remote jobs, that assumption can be wrong. What matters is where the position can actually be performed. A single remote listing may therefore need to satisfy requirements in several states at the same time.
• Posting an intentionally wide range “just to be safe”: A company may use an extremely broad range because it wants flexibility during negotiations. But a range that does not represent what the company genuinely expects to pay can create its own compliance problem. California’s SB 642 specifically tightens this issue by requiring a good faith estimate of the expected pay range.
• Never updating job templates as laws change: Founders may approve one hiring template and use it for months or years. That creates a problem as new state requirements take effect. HR may continue using outdated wording, ATS fields may not match the current requirements, and nobody may be responsible for tracking legislative changes. A template needs periodic review rather than being treated as permanent.
• Failing to review every state covered by a remote role: A company may check California because it has heard about California’s rules and forget other jurisdictions where remote employees can work. Different states can impose different requirements. Before publishing a remote position, identify every state where the role is actually open and confirm which requirements apply in those locations.

10-Minute Pay Transparency Self-Check

Before publishing your next remote job listing, ask:

• Do I know every state where the role could actually be performed?
• Does the job posting include a salary range wherever required?
• Is the range a genuine good faith estimate?
• Have I checked whether Virginia’s July 1, 2026 rules apply?
• Has someone reviewed our job posting template since new state laws took effect?
• Are our ATS fields updated?
• Do we know the potential per violation penalties in the states where we are hiring?
• Has someone been assigned responsibility for tracking new pay transparency laws?

If you cannot answer yes to all of these, your next job posting could already create compliance risk.

Bottom Line

Pay transparency compliance is not simply about where your company is headquartered.

For remote positions, it can depend on where the job can actually be performed.

As of 2026, 18 states plus Washington, D.C. require salary range disclosure, and Virginia added its requirements on July 1, 2026. California’s SB 642 also tightened the meaning of a good faith pay range beginning January 1, 2026.

For a scaling company, the safest approach is to maintain a current multistate hiring checklist, update your ATS, and assign someone to track changes.

Do not assume one job template works everywhere.

Is Your Remote Hiring Process Compliant With Multistate Pay Laws?

Schedule a free 30-minute call with our team to discuss your needs and concerns.

Book here: Initial Consultation with Primum Law Group