4 ms·
This paperwork is standard. The company wants to protect itself against a scenario in which you, after being steeped in its business, come up with some way to d
by pvg 11y ago
This paperwork is standard. The company wants to protect itself against a scenario in which you, after being steeped in its business, come up with some way to do it better/more efficiently/cheaper but claim the idea came to you while you were at home in the shower and thus they have no rights to it. Your out is the form that lists the 'inventions' you might have that you want excluded from this clause. You can always add to it later, too, should you come up with something that is unrelated to your employer's business that you want to work on yourself as long as you and the employer can agree it doesn't interfere with your full-time duties as an employee. Usually, all of this is a formality - just keep the paperwork up to date when needed. I don't think your new employer is trying to screw you.
- Silhouette 11y agoThis paperwork is standard. I strongly disagree. It's not unusual for a new employer to try to pull a fast one here, but IME the actual standard among reasonable employers and employees involves wording like "in the course of your employment" or the local equivalent. In short, what you do on company time, with company resources, or in connection with your work at the company is theirs, but anything else is yours by default. This sort of arrangement protects their interests just fine without granting them unnecessary and unreasonable control over their employees' lives outside work, at which point whether the employer is trying to screw the employee on this or not is academic because they have no contractual ability to do so.
- pvg 11y agoWell, I guess I strongly disagree that it's 'not unusual' for employers to try to 'pull a fast one'. This sort of agreement is standard precisely because it gives both parties a way to protect themselves and delineate what belongs to whom. Bad things happen when you don't have such an agreement. Perhaps things are different in the UK, but I'll echo what 'borksi said downthread - just about every software job in the US will come with such an 'Assignment of Inventions' bit of paper.
- Silhouette 11y agoThis sort of agreement is standard precisely because it gives both parties a way to protect themselves and delineate what belongs to whom. But it doesn't. What it does is make the employer win by default, even for things that have nothing to do with the job. Given the dramatic power imbalance that almost certainly exists between employer and employee anyway, this is the wrong way around. In fact, it's such a bad idea that there is now statute law on the books in various jurisdictions -- including, as I understand it, some states in the USA -- explicitly to nullify such terms in employment contracts.
- pvg 11y agoThis is such a bad idea [...] I'm afraid this matches neither my experience and, I'm willing to bet, the experience of just about everyone who's worked in the field in the US in the last couple of decades. Again, I know nothing about how things work in the UK. In the US, this stuff is a formality akin to all the other formalities of an employment contract, say, your tax, 401k and health insurance forms.
- crdoconnor 11y ago"Just a formality" or "standard" is how 100% of abusive contractual terms are described. The fact it is common (and, sadly, it is) does not mean it is right.
- pvg 11y agoI'm not entirely sure of your statistics but I'd urge you to consider that 'standard' and 'just a formality' is also how very nearly 100% of things that are actually standard and a formality are also described.
- crdoconnor 11y ago"Just a formality" = "it's meaningless" Well, if it's meaningless you can take it out. So suggest that. You'll quickly find out when you suggest that, that "just a formality" usually translates as "ok, maybe it's not such a formality after all, but just sign the damn thing already please". Red flag, in other words. Similarly, "standard" is another ridiculous term to use in contracts. There are no "standard" contractual clauses, there are only common contractual clauses, and "common" does not necessarily mean "reasonable". There are plenty of very common and highly unreasonable clauses like the one the OP complained about. Both terms are examples of weasel words when used in the context of contracts: https://en.wikipedia.org/wiki/Weasel_word https://en.wikipedia.org/wiki/Weasel_word
- ChuckMcM 11y agoI agree with this, mostly its about avoiding in interesting litigation hassle where you 'submarine' your invention into a company and then sue the company for stealing it. That said, it is always a good idea to keep really good records of what you're doing on your time, and the things you have "baking" when you join a company. That will help you in two ways, one it makes this paperwork trivial to fill out [1] I know of one case where it started a discussion with some IP people at the hiring company who then offered a lump sum to purchase the disclosed IP. It is pretty standard language these days. Given the hiring challenges you have the option of working with a lawyer to create an agreement that is more agreeable to you, however failing to come to terms on that agreement is a perfectly reasonable reason for someone not to hire you, even if they had previously said they would. Last tip, if its something that keeps you up at night you're probably not going to be happy, long term, working for anyone but yourself. [1] One tip, you don't have to have list details here just a reference identifier, so for example if you're working on "Studmuffin: The Game" just mention "all rights related to the game: Studmuffin: The Game" on your disclosure form, and later if the question comes up (like they try to say you some how worked on it on their time) you can refer back to your dated notes from before your employment and your records that you kept on time spent that wasn't company time or company equipment.
- pvg 11y agoI had the pleasure of reading some comment of yours a few months back about your work on NIS+ at Sun. These are all perfectly sane ideas but surely when you were at Sun, you signed an AoI agreement _at least_ as restrictive as what the OP is talking about. Or was that not the case and/or did you involve lawyers?
- ChuckMcM 11y agoCoincidentially I've been on a kick for a while now of scanning stuff and was looking recently at some of the employment agreements I've signed over the years. My non-lawyer impression is that they all "say" about the same things but get progressively more detailed about it. The most recent one I signed was as part of the Blekko acquisition by IBM. Blekko's was pretty strictly boiler plate, IBM's has clearly been litigated a few times and the terms stated more clearly. The exact contents are of course confidential (which I find sad because as far as I can tell there isn't anything particularly valuable in say Google's terms versus Sun's terms and comparing them is interesting.) And when I went to Sun my 'disclosures of previous inventions' was empty, when acquired by IBM it was about a page and a half. Of course if they are going to be somewhat detailed, so am I. So for example I now always mention my web site (which is much neglected of late but has a few ads which make a small amount a money each month), between my Google and Blekko engagements I had a pitched a storage idea to a couple of people, no one has actually built it yet so I keep it on the list, Etc. The sorts of the things you tend to collect over the years. Nobody has ever had any issue with me putting these things on the pre-disclosure list. Generally I've found the much more onerous terms are the requirements for using your personal device to access work resources, they have gotten quite extreme (which I understand, given the security challenges). When the agreements start to reach out to computers or what not that I own and that do not have any connection with my employer I start to get a bit twitchy :-). Bottom line, I think Sun's AoI had the same Intention as the ones the OP is talking about but it wasn't as verbose about it, and over the years I've noticed more and more verbiage to make it really clear that when you work for company X they really own the things you develop on their time, even if you think you're contributing to an open source project as part of your job. That latter wasn't even a 'thing' when I joined Sun.
- learnstats2 11y agoDisagree. We haven't seen the paperwork, but a deliberate change in employment contract is not something that's done just for fun or on a standard basis. It doesn't seem to benefit the original poster to sign the contract as it stands. Contracts are supposed to be an equitable agreement between two parties - there is no "standard". Standards which benefit only the employer can and should be questioned. OP should speak to an employment lawyer about the contract as a whole and any clause they are concerned about.
- pvg 11y agoI'm not sure what you disagree with. And I suppose I'd have to ask you and all the other 'speak to a lawyer' people. Have you ever signed an employment contract in the US? Have you ever hired a lawyer to review it? If so, what did they tell you about the AoI?
- learnstats2 11y agoI'm disagreeing mainly that any clause can be described as "standard" - if it is described as "standard", it usually means "unfairly in the company's interest". There is no standard employment contract, by any definition of the word standard that I understand. I've signed employment contracts, not in the US. I've hired lawyers to review employment contracts on several occasions. One reason that advice here on HN is insufficient is because we don't know how or whether any clause affects or will affect the OP. A lawyer will be able to discuss the full consequences of the contract with reference to the OP's personal situation. In my personal case, lawyers have consistently advised me that an Intellectual Property transfer clause is strongly against my interest to sign. When I have taken this back to employers, this has led to quick and easy resolution - in both directions. In one case, that clause was stricken happily and with no problem. In another case, it quickly became obvious that the employer was acting in bad faith and I was happy to leave.
- pvg 11y agoI've signed employment contracts, not in the US. You'll forgive me, but surely, in this case at least, this makes further conversation pointless. It's a question about a US employment contract and whether its clauses are onerous, unusual and how to handle them. A topic in which, as far as I can tell, by your own admission, you have neither experience nor expertise. Correct me if I've misrepresented your position in some way.
- jacquesm 11y agoIt's not a matter of whether or not the paperwork is standard, the problem is that an acquisition does not normally require existing employees to sign new contracts and 'harmonizing' the relationships the company has with its employees is something they would only do if they feel their own contracts give them a more solid position on something they care about. So this is a non-negotiable reduction in the legal position of the employees at best.
- pvg 11y agoan acquisition does not normally require existing employees to sign new contracts I'm not sure why you think that is true. So this is a non-negotiable reduction in the legal position of the employees at best. This is an extraordinary statement that requires the requisite evidence. I don't think it matches US law or precedent, it simply seeks to formalize it, while giving the other party a full and fair negotiating position. Every single case I can think of where employer and employee/buyer got into such a spat are the ones where such agreements were not in place. Can you think of a counterexample?
- cactusface 11y agoEvery single time a man has abducted a child he was not in jail. Can you think of a counterexample?
- mynameisvlad 11y agoPlenty, would you prefer those of a man who has not abducted a child and not in jail, those where a man has abducted a child and gone to jail, or those where a man has not abducted a child and gone to jail? Because all three have very many examples available.
- cactusface 11y agoIt probably would have worked better if I phrased it in the present tense. Every single time a man abducts a child he is not in jail.
- nemmonszz 11y agoI'm very uninformed on these matters, but just out of curiosity, what about the cases where you come up with some way to do it better but your employer isn't interested? Is getting them to sign a waiver saying that you can develop something on your own time on your own equipment the only way to legally create something that falls into the same category as what your employer is doing? So if they refuse to do that, you're effectively barred from writing a certain category of software unless you quit the company and wait X years?
- pvg 11y agoI think it's reasonable to say that you can't compete with your employer, without drawing their legal ire, while you work for them. The flip side of it, at least in California, that it's very difficult for an employer to keep you from working on whatever you want for whoever you want (as long as you're not actually infringing on their IP or running off with their trade secrets), once you are no longer employed by them. The examples of this are legion - HP didn't sue Wozniak after he left to invent personal computers. Same for everyone who leaves Google or Facebook or Apple to pursue some idea of their own. "Former employer sues budding entrepreneur" is a story you almost never hear.
- mikeash 11y agoI really hate this idea that there is anything you can put your signature to which is "standard" or "a formality." I can absolutely 100% guarantee you that if there ends up being a legal dispute here, anything and everything signed by the employee will be used against them to the extent possible. Nothing is going to be "a formality" in that case, which is the only case where it really matters. "Standard" is just another way of saying, "we hope you don't try to negotiate anything, because that would be inconvenient." Both are ways of trying to make an already lopsided transaction even more unfair. My response to "standard" would be, it may be standard for you but it's not standard for me, so I'm going to check it out, and if I want changes I'll suggest them. If you're inflexible on making changes, then I guess we won't sign. My response to "formality" would be, if it's important then it matters, and if it's not important let's just take it out. It's really funny how these things suddenly change if you challenge them. Stuff that's "just a formality" suddenly becomes super important if you try to remove it. Stuff that's "standard and cannot be changed" is suddenly completely negotiable if you tell them you'll walk if it's not changed.
- pvg 11y agoWell, I hate to be the 'do you even lift, bro?" guy but do you work in the US? Has an AoI never crossed your desk? These aren't some oppressive tools of the man trying to keep you down. They're an attempt to head off the terrible problems that arise when IP issues are not explicit. And yes, they're standard. Was your response to 'standard' the same last time you signed an agreement for apartment rental or car insurance? How did that work out?
- mikeash 11y agoYes I work in the US, and no I've never signed anything like that. I've never had anybody who rented me an apartment or sold me car insurance try to tell me that their agreement was "standard." I mean, I'm sure the insurance stuff at least is literally standard, in the sense that they have a single document they give to everybody. But I've never had anyone use the word "standard" in any context except a stupid contract that they wanted to scare me away from negotiating. I have no illusions about being able to negotiate a contract I get from Geico. But I also won't sign it unless I actually agree with the whole thing. Call it "standard," fine. But don't say it's "standard" therefore it's OK if there are parts you don't like. And I don't care how common it is, a contract that says the company by default owns everything you've ever done except for things you've explicitly listed is oppressive. What if you just forgot about something important when you make the list? A clause that says things you make on company time are owned by the company is somewhat sensible (although my understanding is that it's unnecessary, as that's already the law). Say you have to tell them everything you've ever made, and they by default claim anything you didn't explicitly list, is nuts.