Posting a Job With a Pay Range Now Required? What That Forces You to Settle First

For most of the last two decades, a job posting was a lure. It described the upside, left the compensation to a later conversation, and treated the awkward parts of the role as something to raise once a candidate was already invested. That model has been dismantled by statute in a growing number of states. Colorado moved first, then California, Washington and New York, with Illinois and Minnesota among the more recent additions. If you post a role that could be performed in one of those states, or you post remotely without geographic limits, you are probably obligated to publish a good-faith pay range.

The practical effect is larger than the compliance question. A pay range on the page forces an employer to settle internally, before publication, what the job is worth. That single change has quietly separated the ads that work from the ads that generate volume and nothing else.

The range is the filter, and a vague one filters nothing

A range of $48,000 to $92,000 technically satisfies a disclosure requirement and tells a candidate nothing. It reads as two different jobs stapled together, and experienced applicants treat it that way: the strong ones assume the top of the band belongs to someone already on staff, and the underqualified ones apply anyway because the bottom looks reachable. You have widened the funnel at exactly the point where you wanted it narrow.

A good-faith range is narrow because the employer has actually decided. That decision is uncomfortable. It means agreeing internally whether you are hiring at the journeyman level or the lead level, and whether you would genuinely pay the top number to a candidate who walks in matching every requirement. Employers who do this work write ranges that span a few thousand dollars at the low end of the market and maybe fifteen percent at the senior end. Employers who skip it publish a band so wide it converts the disclosure requirement into noise.

Some states also require disclosure of benefits and other compensation in the posting, or on request. Worth checking your own state rather than assuming the base range covers it. Bonus structure, commission, shift differential and the employer share of health premiums all change what the number means, and a candidate who discovers the difference at offer stage is a candidate who negotiates or walks.

Write the parts people quit over

The pay range is only the most visible thing that moved to the front. Once compensation is public, the remaining reasons a hire fails in the first ninety days are the ones the posting still hides. Honest filtering means naming them.

The specifics that actually decide whether someone stays:

• Schedule, in plain terms. Not "occasional flexibility required." Say that the role covers one Saturday in four, or that month-end means two twelve-hour days.
• On-site days, counted. "Hybrid" is now meaningless. Three days in the office, Tuesday through Thursday, is a fact a candidate can plan around.
• Physical demands. Lifting, ladders, cold storage, standing for a full shift. The Occupational Safety and Health Administration oversees workplace safety standards for the conditions you are describing, and candidates who cannot meet them should learn that from the ad, not the first week.
• On-call and travel. How often the phone rings after hours, and how many nights away per month.
• Who they report to, and how many people do this job. A team of one is a different job than a team of nine.

Every one of those lines will reduce your applicant count. That is the point. The count is not the metric. The number of candidates you would actually hire is the metric, and adding a hard fact usually raises it.

Stop listing requirements you do not enforce

The requirements block is where most postings lose credibility. A role that pays at the midpoint of the market and asks for a bachelor's degree, seven years of experience, three named software platforms and a professional certification is describing a candidate who has better offers. Strong applicants read the mismatch instantly and skip it. Weaker ones apply regardless, because they have learned that requirements lists are aspirational.

The repair is to split the list. Two or three genuine non-negotiables, the things that would cause you to reject on sight. Then a short "helpful, not required" section. If you cannot name which items would actually disqualify someone, the list has not been thought through, and it is doing the opposite of filtering.

The same applies to the credential line. Several states and a growing number of large employers have removed degree requirements from roles where the degree was never used on the job. If your last three successful hires in the role did not have one, the requirement is costing you candidates and buying you nothing.

Move one screening question into the ad

Phone screens exist largely to ask questions the posting refused to answer. Pull one or two of them forward. A single line such as "this role requires a valid driver's license and a clean record, since you will be driving a company vehicle daily" removes an entire category of applicant before anyone spends time on a call. So does naming the start date if it is inflexible, or the shift if it is fixed.

Employers who make this shift usually report the same pattern: fewer applications, a much higher share worth interviewing, and a shorter time to fill. The ad did the first round of screening while everyone slept.

The disclosure laws did not create the need for an honest posting. They removed the option of writing a dishonest one and calling it strategy. The employers who adjusted early are now hiring from a smaller pile of better candidates, and the decisions they were forced to make before publishing turn out to be the decisions that make the job easier to fill.