4 ms·
A lot of engineers don't work on their side projects because they can't. Every company I've interviewed with requires IP assignment agreement. From my experienc
by throwaway189262 6y ago
A lot of engineers don't work on their side projects because they can't. Every company I've interviewed with requires IP assignment agreement. From my experience, it's standard outside of California where they're banned.
If you asked me to work on something, it would be a toy project. Because I can't contribute to open source and if I build anything substantial it will be taken from me.
You shouldn't punish people in this situation. It's extremely common, maybe even the majority of coders outside California.
- gkoberger 6y agoI already answered this elsewhere: https://news.ycombinator.com/item?id=24457320 https://news.ycombinator.com/item?id=24457320 That being said, I've interviewed hundreds of candidates over the past 5 years, and not a single one has cited IP assignment as a hesitation.
- logicallee 6y ago>Every company I've interviewed with requires IP assignment agreement. of course they do, you're a knowledge worker for them. they need to own what you create. a standard phrasing includes "related to the employer's business". see for yourself: https://www.lawinsider.com/clause/intellectual-property-assignment https://www.lawinsider.com/clause/intellectual-property-assi... "during the period of his employment relating to the business of the Company". If your contract doesn't have the words "relating to the business of the Company" then add those words in yourself, signing and dating the change and telling the company of your change. you're not their slave you know. they don't get stuff you make in your free time. however, not replicating the company's business is a fair requirement, since they might share enough information with you to do just that. I think it's fair for them to get everything related to their business.