[0] https://leginfo.legislature.ca.gov/faces/codes_displaySectio...
[1] https://www.revisor.mn.gov/statutes/cite/181.78
[2] https://www.hdp.com/blog/2016/11/22/employers-dont-own-your-...
At least in NC I was informed by lawyers I hired that my employer wouldn't let me moonlight in a 500 mile radius, as while they wouldn't own the output. any software was considered "in competition".
But I'm not a lawyer and I'm sure the lawyer you hired knows better than me.
(FWIW I think this is fair. You shouldn't be allowed to compete with your employer while still employed by them, as this creates a massive conflict of interest. Though if your employer is claiming that any and all software you write "competes" with them then that is obviously BS...)
I worked on enterprise data storage operating systems, and I wanted to work on a personal phone application in my off hours.
And what even is the significance of 500 miles when it comes to software?
Re significance of 500 miles, state courts generally ruled that was a reasonable distance for non compete at the time, and so your company's lawyers would put together the most conservative contract that was borderline.
I'm very glad to have left that employment market, it was clear why startups never seemed to start in RTP unless they came out of Universities, specifically because of these huge liabilities for any investor. It's a shame, because the area now just waits for the next globo corp to open a remote office, rather than anything starting locally.
I've dealt with this:
1. When accepting a new job, I make a list of all the side projects I had and got a signature from the company that they were my projects.
2. When starting a new side project while employed, the first thing I'd did was write up a description and get a signed buyoff from the company that it was my project.
Never had a problem. The trick is to do this stuff up front and in advance, not after-the-fact.
I have, for example, rejected claims on my work outside of the office done with my own time/equipment and not in my employer's industry. You don't need the government to say it for you. You can say it yourself as part of the contract.
So far, the lawyers have always approved my edits with no further discussion and without contacting me. They just tell HR they're fine with it, and that's that. It's fun when this surprises HR, but again, sometimes it is no surprise to them at all.
It hasn't happened to me yet, but I'm sure there will be cases where HR will get very upset, so you'll have to be gracious about it and reassure them that you fully intend to satisfy their lawyers. But you'd think that the lawyers would be the ones who got upset, but they don't. Lawyers do this with each other all the time: A writes up a contract, hands it to B, and tells him to sign it. "This is our agreement." B edits it, signs it, and says, "this is our actual agreement", followed by more back and forth. So if you propose a minor change to a contract that you had no part in writing, that's just ordinary business for a lawyer, and it's what they would be doing as a matter of course when hiring a senior executive.
> except for those inventions that either:
> (1) Relate at the time of conception or reduction to practice of the invention to the employer’s business ...
https://leginfo.legislature.ca.gov/faces/codes_displaySectio...
EDIT: Odd voting on this one. It's literally in my employment agreement. You might want to check yours!
EDIT: OK, let's look at CA labor code, specifically 2870 (a) (1): https://leginfo.legislature.ca.gov/faces/codes_displaySectio...
Without making any argument about what is legal in California, I will note that it is not particularly valid to argue for “it is California law” on the basis of “its what my employer claims in the employment agreement”. Employers are notorious for claiming things beyond what the law allows, knowing that the resulting effect on employee behavior is nearly as good as if the claim was actually enforceable.
Twice I've asked an employer for an amendment to the assignment contract to say that only works developed on my own time "with the primary purpose of benefiting the company" were assignable. Though, the second time I was told to f' off; to take it or leave it.
Now, California's legal hostility toward non-compete agreements is clear. It's not just because of the statutory law, but also because of precedent. Other jurisdictions could and have interpreted similar language differently (including other states interpreting California statutes, IIRC). That hostility is usually what people refer to, or would mean to refer to it they understood the nuances.
A lot of the time you'll hear "oh this is a standard contract, everyone signs it & we don't make exceptions". If they want you bad enough they will make an exception.
Most people don't have the luxury of walking away from an employer that won't make an exception with the confidence that they can find an employer who will.
This is definitely true on the east coast. :(
In most of the country, your employer can claim 100% of your intellectual output, no matter if your work was 'on your time'. If you come up with something clever on the weekend on your own computer, your employer still owns it.
(Aside, I think this is one issue that could be a motivation for unionizing tech folks.... or at least collectively bargaining.)