I got one first, read through the contract, saw the standard clause about owning your whole life. I told them it was a deal-breaker if we couldn't get it changed. I got the standard response "oh we never act on that, lots of people here have side-projects", etc. I told them if that was the policy, it needed to be in writing. They escalated internally, talked with legal, etc, but the decision-makers ultimately wouldn't budge. I walked away, and told them in very plain terms that their legal department was responsible for how things turned out.
Shortly afterward I started the process with the second company. Got to the end, saw the clause, told them it was a deal-breaker. Discussed it on multiple calls with different people, eventually the CTO himself who was still reluctant to change it but was sympathetic. Eventually they were able to come back with a contract where that entire section was cut out. I took the offer and it's been a great job so far.
I guess what I'm saying is: hold out. Make a stink about these draconian contracts, and you'll eventually get through and find someone willing to be reasonable. Who knows, if enough people draw a line in the sand maybe it'll become a big enough roadblock that they'll stop putting it in the "standard" contracts.
This is startups, though. YMMV with big companies. Still, no way I'd accept them owning my considerable volume of (FOSS) side-projects.
Cue an exciting month or two when I technically had no contract, as the previous workplace no longer existed as a legal entity, but the new workplace had failed to come up with one having equivalent terms and conditions.
ETA: By "all IP", I literally mean "all IP", as it was worded, the company laid claim to even fiction. May have been challengable in court for over-reaching, but I felt much better renegotiating it to terms taht were more liveable-with.
A few years ago, my co. was acquired, and they wanted to change our contracts.
New contract had a clause: You cannot do any work - paid or unpaid - without the companies' express permission.
So, like, I can't fire the starting gun at the village 3-legged race without your say-so ?
Cue the usual "oh it's standard we never enforce it" BS. Entire team refused to sign. Eventually it got struck.
They similarly wanted to wheedle in 24/7 support rota into my contract. I simply crossed it out (annotated with a witness signature in the margin) and returned. Never heard about it again.
P.S. I really enjoyed your website. I'm a type 1 and 3 mix myself :)
The origins of these clauses appeared to be entirely from third party lawyers, probably derived from some boilerplate contract. I presume their priority is to maximise legal "protection" for the company at all cost... even if it drives employees away, so it's not necessarily something the company explicitly asked for. Whether or not you are able to push back against them probably has more to do with the company culture and whether the leaders or hiring managers are sympathetic to developers and how the FOSS world really works.
I think this is probably true for most small companies, that it's incidental and intended for protection... but obviously in this case Bumble seem to actively be exploiting these clauses for gain rather than protection.
They may not have explicitly asked for any particular clause but when someone in the GC’s office of a company large enough to have a GC reaches out to outside counsel to have one of these agreements drafted the general tone and parameters are very much discussed. If the resulting contract is very one sided and anti-employee it’s because that’s what the company that paid for it to be drafted wanted. Don’t be fooled into thinking otherwise.
You shouldn't need to back and forth and have leverage to get a reasonable contract, the "standard contract" should be balanced. If they argue that it's the lawyers doing it and that oh no of course they would never use total ownership is a good starting point -- regardless of whether there's competition with their business or whether it's done on the clock -- they are going to keep using lawyers as an excuse to screw you over.
Yeah, companies need protection from some things but employees do too. It shouldn't take a state law to get employment contracts to be appropriate instead of simply "arguably legal".
Sure, you can be a bit conspiratorial and say that this works out in the employers favor, helps suppress side projects that might become profitable, etc. etc. but I prefer the simple-stupid reading that the weaker part has trouble pushing back on inertia and the stronger party alike.
Of course, it's far more common to develop the attitude that if it was "standard" when they were junior and they turned out alright then surely it's fine. And for 99% of them it will have turned out fine.
I've repeatedly heard from older engineers that you shouldn't worry too much about what the contract says because [you're going to get it perfect so it won't come up, the customer in question would never, it's just standard language so you can ignore it, if you try to push back you just won't get the work] and while I understand the desire to ignore the problem and instead do the fun engineering this just seems ridiculous to me.
What I takeaway from this is that engineers, like any reasonable human, aren't interested in legal documents and have been trained over decades by companies to not care how abusive their contracts are, because they personally haven't been bitten.
"Sure, you hear about it from time to time but it'd never happen to me," is an unfortunate attitude for the only people senior enough to do anything about it. I wish I saw a better way out but it's hard not to empathize with someone who has been doing engineering for 40 years and has had to sign scores of employment agreements and just wants to build some stuff before they retire.
This example is rightly absurd because if someone told me "don't worry about that code that will segfault, it's never actually called", I would naturally say "WTF this is unacceptable complacency". And yet the argument in both situations is damn near identical!
I think this no good at all, and when the humanities people bring up STEM credulousness, I am quite sympathetic.
replying to myself because this is incorrect, as others have pointed out it seems to be in the grey area of previously open sourced work that derived from the company's IP... Which is not uncommon, i'm sure plenty of people here have open sourced small projects from their work with their employers permission... and there's the question, did this person have permission, if they did then Bumble is trying to "unopensource" a previous decision, if they didn't approve it then I guess the employee has broken their contract.
with that clause ownership mattered less because i knew that i would be able to reuse any of my code under the GPL which was good enough for me.
>You will give the Company full written details of all Inventions and of all works embodying Intellectual Property Rights made wholly or partially by You at any time during the course of Your Employment (whether or not during working hours or using Company premises or resources) which relate to, or are reasonably capable of being used in, the business of the Company or any Group Company. You acknowledge that all Intellectual Property Rights subsisting (or which may in the future subsist) in all such Inventions and works will automatically, on creation, vest in the Company absolutely. To the extent that they do not vest automatically, You hold them on trust for the Company. You agree to execute promptly all documents and to do all acts as may, in the opinion of the Company, be necessary to give effect to this clause 20.1.
Was this intended as an example of a desirable version or an undesirable version of such a clause? I thought the poster you're replying to asked for a suggestion for something you might actually want to put in your contract, but your example seems to give the company exclusive rights to everything (unless it's not "capable of being used" by the company, but surely they could find some use for any piece of software if they want to).
This part was missing from my old contracts.
As far as I understand it, this clause does not force you to even disclose projects you have that are completely unrelated to the company's business. Key word "business" here, not "company".
Example: your personal blog is not related to the fact that your employer develops and sells databases. So whatever code you write to develop/manage your blog won't be a "invention" the company needs to know about and own. This is in contrast to a contract that states "whether during our normal hours of business or otherwise, or at the premises or using our facilities or otherwise, for the whole term" like I used to have. Here the word business does not even refer to the company activity, but to the 9-6 schedule.
> Example: your personal blog is not related to the fact that your employer develops and sells databases.
Couldn't this be interpreted very broadly though? Like if you write your own web server, programming language, optimisation tool, build tool, CMS, CRM etc. they could likely find a use for these within their business.
After reading through all the tweets and replies, especially this one https://twitter.com/_strlght/status/1467460142279143428 where @arkivanov replies they have the same clause in their contract, this one being 19.4, my belief is that there are other clauses besides this one (19.4.1.. or 19.5 onwards) that place even more restrictions.
I think we need to see the entire section 19 to be able to judge.
Or does it only apply to the "business" at that time, not for future business?
"which relate to, or are reasonably capable of being used in, the business of the Company or any Group Company" sounds like a good phrasing to me, especially the "business" part of it as I interpret it to be the company simply wanting you to not build a competing product while employed there (a fair thing to have in a contract).
For reference, this is what my last contract had: https://news.ycombinator.com/item?id=24220800 (notably 13.4 (c))
How I see it, "whether or not during working hours or using Company premises or resources" is not problematic here as "or otherwise" was in my block of text since this only refers to the employer's "business" related IP, and not "everything" you create (if your personal work is a stock trading library and your employer sells a booking for dog haircuts SAAS, these won't collide).
Personally, at the same time as signing the employment contract, I would create a list of projects I develop/contribute to outside of work with a description and links, and have them sign an acknowledgement these don't interfere with their "business" (and if they refuse to sign simply resign on the spot the same second), whether or not they use them already for business purposes or not, and an obligation for them to notify me if they ever start using one of my projects internally in the future.
Also, for open source projects I contribute too that the company uses I'd have a separate paper stating my role in them, and both of our expectation for contributions that are made during/outside of hours, again signed by both parties.
For FOSS projects that I own that the company wants to use, I'll have them clearly define my scope in them during employment, have them assign copyright ownership to me for any contribution they want upstreamed, and have every commit with their hashes reviewed and approved by a lead/manager.
But as far as I'm concerned, there is no point in doing any of this if the employment contract states they own all my IP, since the documents would contradict one another. That's why cleaning up the mess in the employment contract is such a big deal for me.
What matters is how a judge will interpret it, if it should become an issue.
The judge comes in when there is a disagreement on the interpretations, which means I have to state what makes my position stand and bring arguments. With a clause that states "the company owns all", I have no arguments I can come up with, but with the one in the post above, I can at least come up with the reson that "it falls outside that clause written here in the contract".
It might be, or not be enough, but at least I have one thing I can use to my advantage and not make a fool of myself in court.
This is a naive view imo. Legal counsel advises leadership and protects them when they eff up or otherwise go to far. Legal doesn’t run the business. I actually heard a particularly coarse, unsympathetic CEO say this in a townhall once. It is true though.
Civilization and its ways.. they come and go, I hear
I once did a consulting gig for a C-suite of a very, very large company, personally. Uncharacteristically I was a tiny bit awed by this guy. I asked him about dealing with his company's attorneys .. it was nothing specific, but I got the sense that the executive in front of me, could in fact change the results, even with those kind of lawyers and that business environment.
I was told once long ago that it is a leadership job to set the culture of the company, the way contracts are written and enforced is part of that. There is a very wide margin of behavior overall in the business world. Let's not rush to the worst of it here.
I was not hired as a developer, more like devops. But I ended up creating a lot of code. And through sheer principle I did it all open source. Created public repos of everything and then private branches for our internal Git.
Fast forward 7-8 years and we're using our parent orgs system to manage salary, vacation and stuff like that.
My manager wants me to approve something in this new system so I login and I'm greeted with a new employee contract.
The system says I have to sign this to proceed, and in this country we have digital identities so signing it would be as simple as taking out my mobile phone, starting an eID app, challenge, response, code, voilá signed.
Luckily I became very suspicious, downloaded the PDF version instead of signing it. Read it carefully, showed friends who are in the business.
Turns out it was the exact same clause, everything I create, on or off hours, belongs to parent org.
I simply refused to sign it and since I was already hired from a previous contract they removed the requirement from the system so I could proceed.
Now I believe this was a simple case of Hanlon's razor, but damn it would have caught a lot of less vigilant people.
And to be fair, I have nothing against keeping certain code private. If my employer tells me that a project cannot be open source then I will comply. But by default anything I write is open source unless anyone requests otherwise, or I consider it a bad idea due to some reason that is usually about security.
And most of the stuff I write has a use outside of work, even if it's just for myself to learn something. So that's why in 90% of cases I start with making something open source and just use it at work.
So it's no different than me using someone elses open source code, it's just written by me, both on and off duty.
Ehhhh? We spend our free time drinking and sleeping to forget the horror…
THE HORROR.
;)
However, in CA at least, these clauses are limited by law and, as long as your employer doesn’t work on everything, employees have fairly broad protections for side projects that don’t compete with their employer.
Mind you, if many people have the same attitude as you, the hiring people may actually make the change happen forcing the people in charge to approve a variant of the contract without that clause and offer it to the ones who complain but are otherwise excellent candidates. But this is not a quick and easy process.
I sincerely hope enough people refuse to sign those that it becomes a problem for companies.
When I go into an employment, I'm agreeing to rent a certain number of hours of my skills to the company's benefit. I'm not agreeing to give the company any kind of control of what I do or don't do outside of those hours. Mind you, I'm not saying I would _never_ sign such a clause, but that would be a lot more expensive. I would probably agree to it if I could work 3-5 years and retire comfortably.
The clause ought to be that your off-hours, personal work must not have a direct conflict of interest with your job.
https://law.justia.com/codes/california/2011/lab/division-3/...
I agree with the rest of your post, and I think this is the most important part: if enough people do it, than it's likely that a change will happen. If no one ever bothers to complain, nothing will ever change.
I've also had many contracts amended on request/insistence, but I have a lot of leverage. I shouldn't need a bunch of leverage to get obviously abusive clauses removed, a brand new graduate deserves to be subjected to it no more than I do.
I have gotten through changes 2 times at the places I joined. I have simply told them I cant accept the agreement because of X.
Making some amendment to a employment contract is probably cheaper than skipping a hire the last second after several interviews.
I said hell to the no. I was prepared to walk out rather than sign that.
Thankfully they drew up another contract om the spot with that bit removed. Not so thankfully, they dropped me before I could actually prove myself (about 3 weeks) so I might've pissed someone off.
They went back to the lawyers and came back to me saying that this is not the first time this has been brought up, that the contract was standard across the org and was originally written for managerial types and C-suites, and that the company had never even considered taking over an employee's off-hours work, open source or otherwise.
I said good, then it should not be a problem to remove the clause. They said they would have another discussion and would really like it for me to join. I said great, then once you issue me a contract with that clause I'll be happy to join, assuming I hadn't found something else.
They never came back to me. For years I wondered if anything had actually changed. Reading this tweet I'm glad I declined.