Short answer: Yes. Virginia now requires a wage or salary range in job postings, including remote roles tied to a Virginia employer or vacancy, starting July 1, 2026.
Yes. Virginia now requires a wage or salary range in job postings, including remote roles tied to a Virginia employer or vacancy, starting July 1, 2026. The rule covers public and internal postings, so the common mistake is assuming remote work is exempt.
The part people get wrong is location. A remote job is not automatically outside the law just because the work is not done in a Virginia office. If the posting is for a Virginia position, or the employer is posting it in Virginia, the range disclosure rule applies.
The official Virginia Code update says employers must disclose the wage or salary range in each public and internal posting for each job, promotion, transfer, or other employment opportunity. The Virginia Department of Labor and Industry’s update says the new pay transparency rule begins on July 1, 2026, which is the date that matters for current postings.
What gets missed is that this is a posting rule, not a hiring conversation rule. If a recruiter only mentions pay in interviews but leaves the posting blank, that does not satisfy the law. The range has to appear in the job ad itself, not only after someone applies.
For remote jobs, the practical question is where the job is being offered, not where the applicant sits on day one. A company can still have remote staff in many states, but if it is advertising the role as a Virginia opening, the posting needs a range. That is the part employers often overlook when they copy a generic national template.
The range also has to be a real range, set in good faith. Virginia’s guidance points employers to a wage or salary range based on an applicable pay scale, an existing range for the role, the pay of comparable employees, or the budgeted amount for the position. A placeholder like “competitive salary” is not a range.
Salary history questions are separate, and Virginia bans those too. The law says employers may not seek wage or salary history from a prospective employee as part of the hiring process. That means the posting should not try to work around the range requirement by asking applicants to name their current pay.
The inconvenient part is timing. If a company had an old remote posting up before July 1, 2026, it still needed to review whether the posting stayed live after the effective date and whether the content matched the new rule. A stale listing can turn into a compliance problem fast if nobody revisits it.
Employers should also check where the listing is published. If the same role is posted on a Virginia jobs page, a corporate careers page, and a recruiter’s board post, each version should carry the range. The legal duty follows the posting, not the platform, so a missing range on one version can still matter.
For candidates, the simplest test is this: if the role is a Virginia posting, look for a posted pay range before you apply. If you do not see one, that is a red flag worth raising with the employer. In practice, the safest reading is to expect the range on any Virginia remote opening, not to assume the remote label removes it.
If you are building a hiring workflow for a product, internal tool, or jobs board, the clean rule is simple: show the range at posting time for Virginia roles, including remote ones tied to Virginia. If your team also posts on devconnectplatform.com, keep the same range visible there so the posting stays consistent across channels.
The exception people ask about most is whether every remote job anywhere in the country needs a Virginia range just because the company has a Virginia employee. That is not the rule stated in Virginia’s posting law. The rule is about Virginia job postings, and the safe operational habit is to tag the role by location and state law before it goes live.
If the role is fully remote and not connected to a Virginia posting, another state’s law may control instead. That is why the part that actually matters is the posting jurisdiction, the employer’s setup, and where the job is being advertised. For a Virginia posting, the answer is yes, show the pay range.
FAQ
Does Virginia require pay range disclosure for internal postings too
Yes. The Virginia Code update says the disclosure applies to public and internal postings.
Can an employer use “DOE” or “competitive salary” instead of a range
No. Virginia’s rule calls for a wage or salary range, not a vague label.
Does the law also ban salary history questions
Yes. Virginia bars employers from seeking wage or salary history from prospective employees in the hiring process.
What date should I use for compliance checks
Use July 1, 2026, which is the effective date cited by Virginia’s labor and human resources updates.
What should a company do before publishing a remote Virginia role
Add a good-faith wage or salary range, remove salary history prompts, and check every posting channel for the same language.
Frequently asked
Does Virginia require pay range disclosure for internal postings too
Yes. The Virginia Code update says the disclosure applies to public and internal postings.
Can an employer use “DOE” or “competitive salary” instead of a range
No. Virginia’s rule calls for a wage or salary range, not a vague label.
Does the law also ban salary history questions
Yes. Virginia bars employers from seeking wage or salary history from prospective employees in the hiring process.
What date should I use for compliance checks
Use July 1, 2026, which is the effective date cited by Virginia’s labor and human resources updates.
What should a company do before publishing a remote Virginia role
Add a good-faith wage or salary range, remove salary history prompts, and check every posting channel for the same language.
Sources
- Virginia Department of Labor and Industry, Employment Law Updates
- Code of Virginia, § 40.1-28.7:12
- Virginia Department of Human Resource Management, HR Highlights May 2026
- UVA HR, Pay Transparency
- Virginia Code full text, Title 40.1
- Virginia Department of Human Resource Management, Hiring Policy
Originally published at devconnectplatform.com, where it is kept up to date.
Top comments (0)