Employee Agreements and Intellectual Property
You'll learn how employment and consulting agreements define who owns the code you write and what restrictions may follow you after you leave.
What Are Employment IP Agreements?
When you join a company as an engineer, you typically sign agreements that determine who owns the intellectual property you create. These aren't just formalities—they're legally binding contracts that can significantly impact your career, side projects, and future opportunities.
Invention Assignment Agreements
An invention assignment agreement (also called an IP assignment) transfers ownership of your work creations to your employer. Most companies claim:
- Work-related inventions: Anything you create using company resources, time, or that relates to the company's business
- Scope during employment: Some agreements extend to all inventions during your employment period, even personal projects
- State-law limitations: In California and several other states, employers cannot claim inventions made entirely on your own time, with your own equipment, that don't relate to the employer's business
The trap: Vague language like "relates to the company's current or anticipated business" can be interpreted broadly. Always negotiate clarity.
Non-Compete Clauses
Non-compete agreements restrict where you can work after leaving. They might prevent you from:
- Joining direct competitors
- Starting a competing business
- Working in the same industry for 6–24 months
Geographic variation matters: Many states (like California) severely limit or ban non-competes, while others enforce them strictly. Always check local law.
Consulting and Contractor Agreements
As a consultant, IP ownership must be explicitly defined in your contract. Without an assignment clause, you may retain ownership—but clients usually require assignment. Negotiate rates accordingly, as you're selling both labor and IP rights.
Key Takeaway: Before signing any employment or consulting agreement, carefully review IP assignment scope, non-compete restrictions, and carve-outs for personal projects—these clauses determine who owns your code and where you can work next.