Can an employment NDA legally restrict me from mentioning company-specific software stacks on my public resume?

Can an employment NDA legally restrict me from mentioning company-specific software stacks on my public resume?

No, an employment NDA cannot legally prevent you from listing standard software stacks on your resume. Courts generally view your professional skills and experience as your own property. You are legally entitled to describe your work history, provided you do not disclose actual trade secrets, proprietary code, or confidential internal business strategies.

Understanding the Legal Distinction: Skills vs. Trade Secrets

The core of this issue lies in the legal distinction between general knowledge and proprietary information. Employers have a legitimate interest in protecting trade secrets, but they cannot claim ownership over your professional development or the tools you mastered while in their employ.

What You Can Safely List

• Industry-standard tools: Languages (Python, Java), frameworks (React, Django), and cloud infrastructure (AWS, Azure, GCP).
• Methodologies: Agile, Scrum, DevOps, or CI/CD pipelines.
• General achievements: "Improved system latency by 15%" is acceptable; "Used our proprietary algorithm X to optimize database Y" is likely a violation.

What You Must Keep Confidential

• Proprietary Codebases: Never copy or describe specific snippets of internal source code.
• Internal Architecture: Specific configurations, API keys, or unique network topologies that are not public knowledge.
• Business Logic: Proprietary formulas, pricing models, or non-public strategic roadmaps.

Key takeaway: If a tool is commercially available and widely used in the industry, it is almost certainly safe to list. If the tool was built in-house and is the company's "secret sauce," omit it.

Risk Assessment: When Does an NDA Become Overly Broad?

Some companies draft "overly broad" NDAs that attempt to restrict your ability to work in the same industry or discuss your experience. In many jurisdictions, such as California (under Business and Professions Code Section 16600), these clauses are unenforceable. However, you should still exercise caution.

How to Audit Your Resume for Compliance

1. Review your NDA: Look for definitions of "Confidential Information." If it includes "skills acquired during employment," it is likely unenforceable but still a red flag.
2. Sanitize descriptions: Replace specific project names with functional descriptions (e.g., "Internal CRM" instead of "Project Phoenix").
3. Focus on outcomes: Emphasize the metrics of your success rather than the specific internal tools used to achieve them.

Practical Steps to Protect Your Career

If you are concerned about a specific clause in your contract, do not guess. Follow these steps to ensure your resume is both impressive and legally compliant:

• Check for "Non-Solicitation" and "Non-Compete" overlap: Sometimes the restriction isn't about the software, but about the industry. Ensure your resume doesn't inadvertently reveal you are working for a direct competitor in a way that violates a non-compete.
• Maintain a "Public vs. Private" list: Keep a document of the technologies you used that are public (e.g., AWS) versus those that were custom-built.
• Consult your contract: If the contract explicitly lists specific software as "Proprietary Trade Secrets," treat that list as off-limits.

Key takeaway: Your resume is a marketing document, not a technical manual. Focus on your expertise, not the company's internal infrastructure.

How TermScore Can Help

Navigating the fine print of employment contracts can be daunting, especially when your career mobility is at stake. TermScore uses advanced AI to instantly analyze your employment agreements, highlighting restrictive clauses that may unfairly limit your ability to showcase your professional experience. By identifying these issues before you sign—or before you update your resume—TermScore gives you the clarity you need to protect your professional future.