Can an employment NDA prevent me from using my own personal code?

An NDA typically protects trade secrets, not your personal code. However, 'Invention Assignment' clauses in your employment contract can claim ownership of anything you build. If the code was created on company time or equipment, the employer likely owns it, regardless of the NDA.

What is the difference between an NDA and an Invention Assignment Agreement?

An NDA restricts the disclosure of confidential information. An Invention Assignment Agreement (often part of an employment contract) legally transfers ownership of intellectual property created during your employment to the company.

How can I protect my personal projects while employed?

Maintain strict separation: use personal hardware, personal accounts, and work only on your own time. Document your development process and, if possible, get a written 'Prior Inventions' disclosure signed by your employer.

A TermScore is an AI-generated risk rating from 0 to 100 that evaluates the fairness and risk level of any legal document. A score of 86-100 means the contract is highly favorable, while 0-30 indicates dangerous terms you should walk away from.

What types of documents can TermScore analyze?

TermScore analyzes any legal document including freelance contracts, employment agreements, residential leases, NDAs, brand sponsorship deals, SaaS vendor agreements, and rental applications. Upload PDFs, Word documents, or images.

How much does TermScore cost?

TermScore offers a free plan with 3 scores per month. The Team plan is $15/month for 30 scores, and the Professional plan is $50/month for 500 scores with team collaboration features.

Is my document data secure?

Yes. Documents are processed in memory and analysis results are stored encrypted. TermScore never shares your document data with third parties and you can delete your data at any time from your dashboard.

Can an employment NDA stop me from using my own personal project code in future interviews?

An NDA alone rarely prevents you from using personal code, as NDAs protect confidential company information, not your own intellectual property. However, the Invention Assignment clause in your employment contract is the real threat. If your contract claims ownership of all 'work-related' creations, your personal projects may legally belong to your employer.

Understanding the Legal Distinction: NDA vs. Invention Assignment

Engineers often conflate NDAs with IP assignment agreements. Understanding the difference is critical for protecting your career assets.

NDA (Non-Disclosure Agreement): Focuses on secrecy. It prevents you from sharing the company's proprietary algorithms, customer lists, or internal roadmaps. It does not inherently claim ownership of your personal side projects.
Invention Assignment Agreement: This is a transfer of property rights. It states that any intellectual property you create—often including anything 'related to the company’s business'—is automatically owned by the employer from the moment of inception.

Key takeaway: An NDA stops you from talking about their code; an Invention Assignment clause stops you from owning your own code. Always check your contract for the latter.

Action Item: Search your employment contract for the words 'Invention,' 'Assignment,' or 'Intellectual Property' to see if your side projects fall under the company's scope.

The 'Scope of Employment' Trap

Most employment contracts use broad language to define what the company owns. You must determine if your personal project falls into these high-risk categories:

Category	Risk Level	Why?
Directly related to company business	Extreme	Courts often rule in favor of the employer if the project competes with them.
Created using company equipment	High	Using a company laptop or cloud account creates a clear nexus of ownership.
Created during work hours	High	Time-tracking logs can be used as evidence of company-funded development.
Created on personal time/gear	Low	Strongest defense, provided it is unrelated to company business.

Jurisdictional Protections

Some states offer statutory protection for employees. For example, California Labor Code Section 2870 prevents employers from claiming ownership of inventions developed entirely on your own time without using the employer's equipment or proprietary information, provided the invention does not relate to the employer's business.

Action Item: Research your state's labor laws regarding 'employee invention assignments' to see if you have statutory protections that override broad contract language.

How to Protect Your Personal Code

If you are currently employed or about to sign a new contract, follow these steps to insulate your personal projects from corporate claims:

Disclose Prior Inventions: Most contracts include a 'Prior Inventions' schedule. List every project you own before your start date.
Absolute Separation: Never push personal code to a company GitHub, use a company-issued laptop for personal development, or use company-licensed software (like IDEs or cloud credits) for your projects.
Document Everything: Keep a timestamped log of when you worked on your project to prove it occurred outside of your 9-to-5 hours.
Avoid Competitive Overlap: If your side project is a direct competitor to your employer's product, the risk of litigation increases by approximately 80%, regardless of whose equipment you used.

Key takeaway: If you are building something that could be a startup, consult an attorney before signing an employment agreement to negotiate an exclusion for your specific project.

Action Item: Create a 'clean room' environment for your personal projects using hardware and accounts that have zero connection to your employer.

Assessing Your Risk in Interviews

When presenting your personal code in interviews, you are not just showcasing your skills; you are potentially exposing yourself to liability. If you present code that your employer claims to own, you are effectively admitting to a breach of contract.

Check the 'Work-Related' Clause: If your contract says the company owns anything 'related to the company's business,' be extremely cautious about showing code in the same industry.
Use Open Source: If your project is open source, ensure you have the rights to the code. If you contributed to it while employed, your employer might technically own your contributions.

Action Item: Before an interview, perform a 'risk audit' of your portfolio. If a project was built while employed, verify that it is completely unrelated to your employer's business and was built entirely on personal time.

Navigating the fine print of employment contracts is complex, but you don't have to do it alone. TermScore uses advanced AI to scan your employment agreements, highlighting restrictive IP assignment clauses and potential conflicts of interest so you can understand exactly what you own before you sign or interview.