Pay transparency is rapidly reshaping hiring practices worldwide, and independent recruiters can no longer afford to overlook its implications. As more jurisdictions adopt strict disclosure requirements, understanding pay transparency is essential for maintaining compliance and protecting both your firm and your clients.
A Q&A guide for Recruitment Firms
Q: Why should recruiters outside the United States care about US pay transparency laws?
Because if you recruit into the US, or post remote roles open to US-based candidates, you and your clients may fall under state pay transparency requirements. Many laws apply based on where the candidate is located, not where the recruiter or employer is located. For example, Massachusetts’ 2025 law requires employers with 25+ employees to disclose pay ranges in job postings as of October 29, 2025. Likewise, states such as New Jersey (effective June 1, 2025) and Illinois (effective January 1, 2025) mandate salary ranges and benefits information in job postings. If your job ad can be viewed by candidates in these states, compliance is expected.
Q: Which states currently require pay ranges in job ads—and is the list growing?
Yes, the list is expanding. Several US states and cities now require employers to include salary ranges in external postings. This includes California, Colorado, Washington, New York State, Massachusetts, Illinois, Minnesota, New Jersey, and Vermont, each with differing thresholds and definitions of job postings. Delaware also passed pay transparency legislation in 2025, with enforcement beginning in 2027, showing continued momentum toward nationwide adoption.
Q: What exactly must be disclosed in job postings?
Most state laws require disclosure of:
- A good-faith salary or hourly wage range
- A general description of benefits and compensation programs (in some states)
For instance, New Jersey mandates the salary range plus a description of benefits in every posting, while Massachusetts requires a range for all job ads, including internal promotions.
Q: What happens if a recruiter or client fails to comply?
Penalties vary by state and can escalate quickly. Washington can fine employers between $100 and $5,000 per violation, while New Jersey’s fines start at $300 and increase for subsequent offenses. Even if a recruiting agency posts the role on behalf of the employer, both parties can be held liable for non-compliance.
Q: Does pay transparency apply to remote jobs?
Yes—this is one of the biggest compliance traps for global recruiters. If a remote job could reasonably be performed by a candidate in a regulated state, that job posting must comply with that state’s rules. For example, a global remote posting that reaches candidates in Colorado or New York must meet those states’ disclosure requirements, regardless of where the employer or recruiter operates.
Q: What should global independent recruiters do to stay compliant?
- Build a salary range verification step. Require clients to supply a range before any posting goes live. Delaware and Illinois laws explicitly require employers to maintain accurate pay data for compliance—making documented ranges a best practice globally.
- Maintain a state-by-state compliance matrix. Because laws differ, recruiters should keep an updated reference that outlines requirements for each US jurisdiction.
- Train teams on compliant job-ad language. Many states require good faith ranges; vague phrasing like “competitive salary” may be noncompliant.
- Update service agreements. Add language clarifying that postings will follow pay transparency laws and that clients must provide truthful ranges.
- Advise clients early. With new and upcoming laws in states like Delaware and Massachusetts, proactive guidance builds trust and reduces risk for everyone involved.
Q: Is pay transparency just a US issue?
Not anymore. While the US patchwork is the most complex, pay transparency is part of a global trend toward pay equity. Recruiters working across borders should expect more jurisdictions—both inside and outside the US—to adopt similar requirements.
