Looking for your first CS job? Be sure to own your ideas(devver.net)
devver.net
Looking for your first CS job? Be sure to own your ideas
http://devver.net/blog/2008/08/looking-for-your-first-cs-job-be-sure-to-own-your-ideas/
6 comments
I once signed on as a contract engineer (mechanical, not software) for a Fortune 100 company. My contract was actually with a contract agency that this company normally uses. I had negotiated the details of the job with my manager and then met with the onsite manager of the contract agency to deal with the paperwork. The lady got bent when I actually took about 45min to read every single line of the contract. She got even more huffy when I signed it but crossed out and initialed about 3 lines of the contract and handed it back. She claimed that I could not do that. I told her to talk to my manager and run it by legal (I knew they really needed my skill set) and get them to initial the crossouts and mail me a copy. The lines that I crossed out legally claimed anything I might invent, create or produce at work or off-hours for the terms of my employment. So if I invented the proverbial better mouse trap on my own time this Fortune 100 company would have moved up a few notches and I would get my salary. Legal signed off on my edits and I went to work. So the moral of the story is don't be intimidated into signing something you don't understand and don't be afraid to seek changes to the contract if it is not acceptible.
I think most employers will have a blanket "we own your IP" policy. But most of them will also make exceptions (and in writing) on a case-by-case basis once you prove you're a valuable employee. Because obviously you're not going to actually do anything on your own time if it's going to be your employer's property, whereas if you convince them that there's a potential for good PR with no real cost, they'll go for it. Once you've demonstrated that you're good at your job, and your side activities won't conflict with that.
"But most of them will also make exceptions (and in writing) on a case-by-case basis once you prove you're a valuable employee."
The way you've phrased that implies that policy is reasonable. It isn't. Why should anybody have to prove that he is a valuable employee before he gets freedom to do what he wants (on a case-by-base basis) in his free time?
The way you've phrased that implies that policy is reasonable. It isn't. Why should anybody have to prove that he is a valuable employee before he gets freedom to do what he wants (on a case-by-base basis) in his free time?
I think companies don't want employees who stop thinking when they walk out the door, and if they just happen to have a key idea while in the shower, they don't want to be blackmailed later on.
Everything's negotiable, and IP is definitely something you should negotiate, but often there's a process for this that legal has approved and changing it is a dealbreaker.
A typical process is that you "disclaim" up front all the IP you take into the company, and they own everything after that.
A typical exception to that process that might be accepted is that they own everything related to their business that you come up with after you join the company.
An exception that can be pretty hard to get is that you own everything you come up with off-hours. This is reasonable, (though obviously you can disagree and turn the job down): if the company is providing you access to knowledge and domain exposure, you shouldn't be exploiting it to start your own business on the side. Also, it can be hard for them to pinpoint exactly when you came up with something, which creates legal headaches down the road.
A typical process is that you "disclaim" up front all the IP you take into the company, and they own everything after that.
A typical exception to that process that might be accepted is that they own everything related to their business that you come up with after you join the company.
An exception that can be pretty hard to get is that you own everything you come up with off-hours. This is reasonable, (though obviously you can disagree and turn the job down): if the company is providing you access to knowledge and domain exposure, you shouldn't be exploiting it to start your own business on the side. Also, it can be hard for them to pinpoint exactly when you came up with something, which creates legal headaches down the road.
if the company is providing you access to knowledge and
domain exposure, you shouldn't be exploiting it to start
your own business on the side
This is the line of reasoning that breeds contempt down the road - company says "you can't have your own ideas", employee says "Fine, then I'm working here 9-to-5". Everybody loses.
It might be if you are creating a breeding ground for competitors. There's nothing immoral about asking to own all your personal time IP, but I can see both sides to the argument.
So you MIGHT be breeding competitors, therefore you have to ask for any and all IP? A bit over-reaching it seems. There is really no need for it in most cases, the only reason they always ask for it is because nobody ever questions the practice.
You can call it overreaching; I don't mind. But you just disqualified yourself from a big chunk of otherwise interesting jobs. It's not like I'm making up the fact that software startups have non-negotiable IP clauses.
You want a really fun non-negotiable clause? Come up with something "patentable", then quit. You can be forced to work on the patent application, a year later, at a rate set by your ex-employer. Happened to me.
You want a really fun non-negotiable clause? Come up with something "patentable", then quit. You can be forced to work on the patent application, a year later, at a rate set by your ex-employer. Happened to me.
Well, so yo should have kept it to yourself to preserve your own best interest. That's exactly the problem with that situation, it stimulates you to work 9-5 and keep quiet about everything and anything. I think that situation is broken.
And it's strange how you, an apparent victim of the system, come to its defense. Doesn't compute.
And it's strange how you, an apparent victim of the system, come to its defense. Doesn't compute.
I should do crappy work because otherwise I might get burned? Yeah, sorry, I'm busy living an actual life.
I'm not making moral judgements here; I'm just offering some data points on how some places in the industry actually work.
I'm not making moral judgements here; I'm just offering some data points on how some places in the industry actually work.
Many states have limits on what bits of IP agreements can be enforced.
Regardless of the IP agreement, the important thing is to be at least a little careful. If you have a new, world changing piece of software you're writing, do it on your own time with your own resources. Avoid doing anything at all with it on company time, and don't use your company owned laptop to do development.
Regardless of the IP agreement, the important thing is to be at least a little careful. If you have a new, world changing piece of software you're writing, do it on your own time with your own resources. Avoid doing anything at all with it on company time, and don't use your company owned laptop to do development.
The flipside is that if you're a founder, you'll have to deal with investors wanting the startup to own its IP.