copyright intellectual-property software employment patents
Could signing an intellectual property agreement for an algorithm coding job prevent me from working in a similar industry later?
<p>I am a computer coder / algorithm developer and am just getting started in industry where I know I'll have to deal with IP agreements. In particular, the question I'm asking here came about because I was set to go ahead with a company funded masters project writing code and developing algorithms.</p>
<p>The IP agreement for this project felt so restrictive to me that I (sadly) ended up declining the project. It essentially said that all copyright, patents, know-how, etc. would belong to the company.</p>
<p>The main reason I declined was because I thought it could give me problems later on if I were to work for a different company applying similar algorithms, potentially for a similar purpose.</p>
<p>For argument sake, let's say there were no patents; would I be able in the future to write code for another company that used similar algorithms, expressed in slightly different terms (noting that there only so many ways you can actually code up these algorithms)?</p>
<p>As an aside, I'd love if you could give me, someone just starting in industry, some advice on how to navigate this topic of IP, especially noting that these contracts can feel rather vague/ambiguous as to what you're actually allowed to do after completing the project. I understand I'll probably eventually just have to bite the bullet and be ok with signing this sort of thing if I want to get a job.</p>

<blockquote>
<p>would I be able in the future to write code for another company that used similar algorithms, expressed in slightly different terms (noting that there only so many ways you can actually code up these algorithms)?</p>
</blockquote>
<p>Yes. The clauses you describe (&quot;<em>all copyright, patents, know-how, etc. would belong to the company</em>&quot;) are about intellectual property, not to be confused with non-compete agreements.</p>
<p>Copyright matters are convoluted and jurisdictionally inconsistent, but elementary tasks or commands are not copyrightable insofar as they lack the originality/innovation on which copyright is premised. Likewise, a similarity of algorithms does not necessarily imply <em>misappropriation of [employer's] trade secrets</em>. The lower the originality of an algorithm or implementation, the unlikelier a company will have a valid claim of copyright or of misappropriation of trade secrets.</p>
<blockquote>
<p>I'd love if you could give me, someone just starting in industry, some advice on how to navigate this topic of IP, especially noting that these contracts can feel rather vague/ambiguous</p>
</blockquote>
<p>IP particulars aside, you made the right decision by reading/understanding <em>and</em> declining a contract that you consider unacceptable. People, and especially those who are starting their career, tend to do the opposite: First they sign a contract that is unintelligible or unacceptable to them, and by the time they regret signing that contract they cannot evade the ensuing ramifications.</p>
<p>It is typical for employment agreements to have clauses of the sort you describe. However, that does not mean that you <em>have</em> to agree to those clauses. A person's <em>freedom of contract</em> is neither determined nor necessarily constrained by the common practices. From your freedom of contract it follows that you can always propose changes to the contract a counterparty (such as an employer) wants you to sign. Once the parties have signed a contract, such modifications are harder to attain because the favored party has no incentive to give up its beneficial position.</p>
<p>When it comes to contract ambiguities, it is important to bear in mind the <a href="https://en.wikipedia.org/wiki/Contra_proferentem" rel="nofollow noreferrer">doctrine of <em>contra proferentem</em></a> and that its application is subject to reasonability and consistency [of the adopted interpretation] with the contract altogether.</p>
