Skip to content
← Back to blog
Regulation·November 20, 2026·8 min read

California's pay scale law for startup engineering job posts: remote roles, recruiters, and what a good-faith range looks like

California requires a pay range in every job post from employers with 15+ staff, remote roles included. How a funded startup sets one it can defend.

A funded startup with 15 or more employees has to put a salary range in every job posting it publishes, and California's Labor Commissioner reads that as covering a remote role that could ever be filled from California. Most engineering leaders know the rule exists. Fewer know the range has to be a good-faith estimate of what they expect to pay on hire, that a link to the range does not count, and that the recruiter posting on their behalf is bound too.

This post reads the Labor Commissioner's own guidance (its FAQ page, dated 24 August 2026) and turns it into decisions a VP of Engineering makes when opening a senior req. It is a builder's reading, not legal advice. Employment counsel decides how the law applies to your company.

What California's pay transparency law requires in a job posting

The rule is Labor Code section 432.3(c)(3). The California Labor Commissioner's Office states it in one line: "An employer with 15 or more employees must include the pay scale for a position in any job posting."

"Pay scale" has a definition, in section 432.3(m)(1): a good faith estimate of the salary or hourly wage range that an employer reasonably expects to pay for a position upon hire. Three practical consequences follow from the Labor Commissioner's FAQ:

  • The range goes in the posting itself. The FAQ answers the question directly: an employer cannot link to the pay scale from an electronic posting or use a QR code on a paper one.
  • Equity and bonus are optional. "Any compensation or tangible benefits for a position in addition to a salary or hourly wage are not required to be posted." For an equity-heavy startup offer, the legal minimum is the base salary range.
  • Commission and piece rates are not optional. If the wage is built on them, the expected range of those rates has to be posted.

The penalty is set out in section 432.3(d)(4): civil penalties between $100 and $10,000 per violation. An aggrieved person can file with the Labor Commissioner within one year of learning of the violation, or go to court for injunctive relief.

Does it apply to a remote role, or a startup under 15 people?

Two questions decide whether a seed or Series A company is in scope, and the Labor Commissioner's FAQ answers both.

Headcount. The statute does not say how to count. The Labor Commissioner says it counts the way it counted for the 2022 COVID-19 supplemental paid sick leave and for minimum wage rates, and that "at least one of the employees must be currently located in California." A 40-person company with one engineer in Oakland is counted. A company that crosses 15 mid-round is in scope from that point, which means the req template your first recruiter set up at 11 people is now out of date.

Remote roles. The FAQ says the Labor Commissioner's Office interprets the rule "to mean that the pay scale must be included in the job posting if the position may ever be filled in California, either in-person or remotely." A posting that says "Remote, US" is a posting that may be filled in California. So is one that says "Remote, Americas time zones." If you would hire a strong candidate in Sacramento, the range goes in.

The recruiter, the job board and the referral post

Section 432.3(c)(5) covers postings made through someone else. If a covered employer engages a third party to "announce, post, publish, or otherwise make known a job posting," the employer must give the third party the pay scale, and the third party must include it.

That reaches the contingency recruiter running your search and any agency syndicating the req. The practical gap is the one nobody owns: a recruiter's LinkedIn post about "an exciting Series A AI company" that names no company and no range. Put the range in the brief you send every recruiter, in writing, and ask them to confirm their postings carry it. It is a one-line clause in the search agreement.

What a good-faith range looks like for a senior engineer

The law does not set a maximum width. It asks for the range you "reasonably expect to pay for a position upon hire." Our view, the one we would defend on a call: a range so wide that it describes three different levels is not an estimate of what you expect to pay for one position, and candidates read it as a sign the company has not decided what the role is.

Picture a 24-person Series A company in San Francisco opening one req for a senior ML engineer, remote within the US. Three ways it could post the range:

Posted rangeWhat it tells a candidateRisk
$120,000 to $320,000"We have not levelled this role"Hard to call a good-faith estimate for one position on hire; senior candidates assume the real offer is near the bottom
$185,000 to $215,000"We will pay around the market mean"Defensible, but may sit below what senior AI candidates are being offered
$210,000 to $250,000"We levelled this as senior and priced it"Defensible and specific; the top end becomes visible to every engineer you already employ

For an anchor, the US Bureau of Labor Statistics' Occupational Employment and Wage Statistics put the mean annual wage for software developers in the San Jose-Sunnyvale-Santa Clara metro area at $221,710 in May 2025 (released 9 July 2026), across 87,350 jobs. That is a mean across every level, not a senior band, which is why the third row starts near it rather than ending there. We read the BLS figures in more depth in what a Bay Area software developer actually earns.

The range is a decision you have to stand behind, so write down how you set it: the level, the internal comparators, the market source. Section 432.3(c)(4) already requires employers to keep each employee's job title and wage rate history for the duration of employment plus three years, and the Labor Commissioner can inspect those records.

What the posted range does to the people you already employ

A posted range is public, and section 432.3(c)(2) gives each current employee the right to ask for the pay scale for their own position. Your existing senior engineers will read the new posting. If their salary sits below its floor, expect that conversation soon after the posting goes live.

That is the real cost of the third row in the table above, and it is a reason to set bands before posting rather than after. Two more rules shape the offer itself. Section 432.3(b) bars asking an applicant for salary history, and 432.3(a) bars relying on it to set an offer. Section 432.3(j) still lets you ask a candidate what salary they expect. And the California Equal Pay Act, section 1197.5, applies to every employer regardless of size, so a posted range does not excuse a pay gap between people doing substantially similar work.

If you are also screening candidates with software, California's other AI hiring rule applies to that step, independently of the pay scale law.

When a req at the posted range will not fill

Here is where the law meets the hiring market. Once the range is public, stretching an offer well past its top for one candidate undercuts the claim that the range was your good-faith estimate, and every engineer who read the posting can see the gap. A senior req that sits open at its posted range forces a choice: raise the band (and re-price the team under it), lower the bar, or keep waiting. We worked through what waiting costs in the empty seat.

There is a fourth option for the work itself, as distinct from the hire. If the req exists because a roadmap item is slipping, a senior engineer engaged through a delivery partner can carry that work while you fix the band and keep searching. That is what our build-your-team service is for: one or two engineers embedded in your team, scoped and quoted for the work.

It is the wrong answer for some roles. A founding ML lead, a head of platform, anyone who will set technical direction for years and should hold meaningful equity: hire that person, post the honest range, and wait for them. Borrowed capacity is for the roadmap, not for the people who own it.

If you have a req that has been open longer than your board expected and want a second opinion on whether it is a hiring problem or a delivery problem, tell us about it.

Sources

Written by Zain Ali

Frequently asked questions.

Yes, if the role could be filled from California. The California Labor Commissioner's Office, in its pay transparency FAQ dated 24 August 2026, says it interprets Labor Code section 432.3(c)(3) to require the pay scale in a job posting if the position may ever be filled in California, in person or remotely. A posting marked "Remote, US" falls within that reading.

Fifteen. Labor Code section 432.3(c)(3) applies to employers with 15 or more employees. The Labor Commissioner's Office FAQ (dated 24 August 2026) says it counts employees the same way it did for 2022 COVID-19 supplemental paid sick leave and minimum wage rates, and that at least one employee must currently be located in California.

No. The California Labor Commissioner's Office FAQ (dated 24 August 2026) says compensation or tangible benefits in addition to a salary or hourly wage are not required to be posted. The required pay scale is a good faith estimate of the salary or hourly wage range the employer reasonably expects to pay on hire, under Labor Code section 432.3(m)(1). Commission or piece-rate pay is the exception and must be included.

Yes. Under Labor Code section 432.3(c)(5), a covered employer that engages a third party to post or announce a job must give it the pay scale, and the third party must include it in the posting. The California Labor Commissioner's Office restates this in its pay transparency FAQ dated 24 August 2026.

No. The California Labor Commissioner's Office FAQ (dated 24 August 2026) says the pay scale must be included in the job posting itself, and an employer cannot satisfy the rule with a link in an electronic posting or a QR code on a paper one.