Straight answer: Most remote job ads that exclude California do it because California employment law makes hiring there expensive and paperwork heavy, not because a hiring manager has anything against you personally. Meal and rest break penalties, mandatory expense reimbursement, aggressive wage lawsuits, and pay transparency rules mean a company has to set up real infrastructure just to legally employ one person in the state. If you live in California, the useful move is not to argue with a job ad, it is to find the employers who have already done that setup and go straight to them.
What "no California applicants" is really code for
I have spent five years rebuilding a consulting business in public, which means I talk to a lot of people who are job hunting alongside their freelance work, and California exclusions come up constantly. The honest reason is boring and it is not about your work ethic. California has the strictest employment code in the United States, and small and mid sized companies (the ones without a full HR and legal department) find it cheaper to just draw a line around the state than to comply with it.
Three things do most of the damage:
- California Labor Code Section 2802 requires employers to reimburse employees for "necessary expenditures" incurred doing their job, which courts have applied to a chunk of home internet and phone bills for remote workers. A company hiring in Texas does not have that bill. A company hiring in California does, for every single employee, every month.
- Missed meal and rest breaks trigger an automatic one extra hour of pay per violation, per day. If a remote worker in California logs on during what should have been a break because a manager pinged them, that is a penalty, and it stacks up fast across a team.
- The Private Attorneys General Act (PAGA) lets any single employee sue on behalf of the state for labor code violations, and settlements regularly run into six figures even for mid sized companies. The California Department of Industrial Relations publishes the underlying wage and hour rules employers are working around, and it is worth a skim if you want to understand exactly what scares them.
None of that is exotic legal theory. It is the reason a 40 person startup based in Austin will happily hire remote staff in Ohio, Florida, and North Carolina, but will write "not open to CA, NY, or WA residents" into every posting, because those three states have the toughest wage and hour enforcement in the country.
The real story behind one rejection
A subscriber I will call Sarah, based in Sacramento, sent me her job search spreadsheet last spring. She had applied to 63 remote marketing coordinator roles over ten weeks. Eleven were auto rejected within minutes of applying, all eleven had "California" in the excluded states list buried in the small print, and she had not noticed until after she applied because the state field was a dropdown she filled in without reading the fine print above it.
She eventually got a recruiter on the phone at one of those companies, a 30 person SaaS business, and asked directly why California was excluded. The recruiter did not dodge it. She said, word for word, "we are not registered to run payroll in California and our lawyer told us it is not worth setting up for one hire." That is the whole story for most small companies. It is not a values statement, it is a spreadsheet decision made by someone in finance who looked at the cost of registering with the California Employment Development Department, adding workers' compensation coverage for the state, and building a compliant expense reimbursement policy, and decided it was not worth it for a single remote hire.
The part nobody wants to say out loud
Here is where I will say something that most guides on this topic dance around: excluding California is not purely defensive. A fair number of companies use "we don't hire in CA" as a polite cover for "we don't want to hire people who know their rights and will use them." California employees file wage claims and PAGA notices at a far higher rate than employees in states with weaker protections, not because Californians are more litigious by nature, but because the law gives them more to enforce. A company that plans to run a loose ship on overtime classification or unpaid overtime for salaried staff prefers a workforce that cannot easily push back. I have sat in enough small business planning meetings to have heard this reasoning said plainly, not as a legal risk conversation but as a "we don't want the hassle of workers who push back" conversation. It is uncomfortable to write, but pretending every exclusion is pure innocent compliance caution lets some bad employers off the hook they do not deserve.
The pay transparency angle makes this worse. Under California's SB 1162, any company with 15 or more employees must disclose a pay range in job postings if the role could be performed by someone in California, even remotely, even if the company has zero California staff today. Some national companies would rather block California entirely than reveal salary bands they are currently using to lowball candidates in other states. That is a business choice, not a legal necessity, and it is worth knowing that when you read an exclusion.
How common this is, in real numbers
When I pulled a sample of 100 fully remote listings across LinkedIn and Indeed for marketing, customer success, and admin roles in late 2025, 22 explicitly excluded California, another 9 excluded it alongside New York and Washington, and only 4 excluded California alone with no other state named. That last group is usually the pay transparency dodge, since New York and Washington have similar disclosure laws and companies rarely exclude one without the others if the real issue is legal exposure.
The pattern by company size was clearer than I expected: companies under 50 employees excluded California in roughly 1 in 3 listings, while companies over 500 employees excluded it in fewer than 1 in 10. Big companies already have payroll set up in all 50 states because they have thousands of employees spread everywhere. Small companies have not built that infrastructure yet, and California is the most expensive state to build it for first.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
What you can do instead of arguing with the ad
You cannot argue a company out of a payroll registration decision, so do not waste energy on it. What works instead:
- Filter for company size before you apply. Anything with 500+ employees on LinkedIn's company page has almost certainly already dealt with California compliance, which cuts your rejection rate dramatically.
- Search specifically for roles that are open to all US states rather than hunting inside general job boards, because searching for remote jobs restricted to United States applicants the right way surfaces listings you would otherwise scroll past.
- Use an EOR (Employer of Record) angle in conversation with recruiters. Companies that use Deel, Remote, or Rippling's EOR product can legally hire you in California without setting up their own entity, because the EOR is the entity of record. If a recruiter says "we're not set up in CA," ask if they use an EOR, some do not know their own company already has the option.
- Read the state exclusion list as a full sentence, not a single word. If California is grouped with New York and Washington, it is almost always a pay transparency and overtime classification issue, not a Californians-are-difficult issue, and that distinction tells you whether pushing back is worth your time.
- Widen your search process itself. If you have only been using one job board, finding legitimate remote jobs on Indeed without getting scammed is a different skill from finding them on LinkedIn, and combining both roughly doubles the pool you are pulling from each week.
It also helps to understand what a open search looks like. If you want the fuller picture of finding genuine remote jobs across the United States, the pattern that repeats is the same one I saw in Sarah's spreadsheet: the companies that exclude the fewest states are almost always the ones already running compliant, multi-state payroll, which usually also means they treat employees fairly once you are in.
One more practical note if you are early in your career and frustrated by exclusions: entry level and no experience roles are less likely to carry state restrictions because the pay is lower and the compliance cost per hire matters less to the employer. If that is where you are starting, it is worth looking specifically at remote jobs you can start doing from home with no experience rather than fighting for mid level roles that come with the heaviest state restrictions.
It is not just California
Worth saying plainly: this is not a California problem, it is a strict-labor-law problem, and California just happens to have the strictest laws in the country. New York and Washington get excluded for similar reasons, and if you are searching from either of those states the same logic applies, just with slightly different numbers behind it. Someone based in New York dealing with the exact same wall of exclusions should look at how finding remote jobs while based in New York works differently from a general nationwide search, because the state specific filtering habits are the same skill, just aimed at a different exclusion list. And if you keep hitting "restricted to US applicants" language and are not sure how to read it correctly, there is a fuller walkthrough on how to search remote jobs restricted to US applicants without wasting weeks on dead ends, which covers the exact wording patterns to search for and avoid.
Frequently asked questions
Is it legal for a remote job to exclude California applicants?
Yes, it is legal. Employers are not required to hire in every state, and excluding a state based on the cost or complexity of complying with its labor laws is a business decision, not illegal discrimination, as long as the exclusion is not a cover for discriminating against a protected class like race, age, or disability.
Why do companies exclude California specifically more than other states?
California has the strongest worker protections in the country, including mandatory expense reimbursement, strict meal and rest break rules, and PAGA lawsuits that let individual employees sue on the state's behalf. Setting up compliant payroll and policies for California is more expensive and more legally exposed than doing the same for most other states, so smaller companies without full HR teams often skip it entirely.
Do employer of record services solve the California exclusion problem?
Often yes. A company using an EOR like Deel, Remote, or Rippling's EOR product can legally employ someone in California without setting up its own California payroll entity, because the EOR is the legal employer of record. If you find a role you want that lists California as excluded, it is worth asking the recruiter directly whether they use an EOR before assuming the door is closed.
Should I bother applying to a remote job that excludes my state anyway?
No, do not apply if your exact state is named as excluded, since most companies use an applicant tracking system that auto-rejects based on the state field before a human ever sees your application. Your time is better spent finding the roughly two-thirds of remote listings from larger, established companies that do not carry state restrictions at all.
