Is it a breach of an employment NDA to list specific software frameworks on a public resume?

Listing software frameworks on a resume is generally not a breach of an NDA, provided you avoid disclosing proprietary trade secrets. Use TermScore to verify.

November 2, 2026TermScore Legal Intelligence GroupStatutory & Corpus Verified607 words

Is it a breach of an employment NDA to list specific software frameworks on a public resume?

Listing standard software frameworks on a public resume is generally not a breach of an employment NDA. Employers cannot claim ownership over your general professional skills or the industry-standard tools you use. A breach only occurs if you disclose proprietary, non-public trade secrets or confidential internal architecture.

Key takeaway: Your NDA protects the employer's competitive advantage, not your ability to market your general professional proficiency in industry-standard technologies.

Understanding the Boundary Between Skills and Trade Secrets

The legal distinction between a "skill" and a "trade secret" is the primary factor in determining whether your resume content is protected or prohibited. Courts generally view general knowledge, skill, and experience as the property of the employee, not the employer.

What You Can Safely List

  • Industry-Standard Frameworks: Technologies like React, Django, Kubernetes, or TensorFlow are public knowledge.
  • Methodologies: Mentioning Agile, Scrum, or DevOps practices is standard and non-confidential.
  • General Achievements: Quantifiable results like "improved latency by 15%" are usually safe, provided they do not reveal proprietary code.

What Constitutes a Breach

  • Proprietary Algorithms: Disclosing the specific logic behind a company's unique recommendation engine.
  • Internal Infrastructure Maps: Detailing the specific, non-public way your company chains microservices or manages data pipelines.
  • Unreleased Project Data: Mentioning specific features or products that have not yet been announced to the public.

Action Item: Audit your resume to ensure you are describing the tools you used, not the proprietary implementation of those tools.

Risk Comparison: Public Resume vs. Internal Documentation

CategoryPublic ResumeInternal Documentation
Frameworks/LanguagesSafe to listConfidential if part of a secret stack
Project OutcomesSafe if generalizedHighly confidential
Proprietary AlgorithmsStrictly prohibitedStrictly prohibited
Internal API SchemasStrictly prohibitedStrictly prohibited

Jurisdictional Nuances and Legal Precedent

In jurisdictions like California, Business and Professions Code Section 16600 strongly protects an employee's right to practice their profession. Courts are highly skeptical of NDAs that attempt to prevent employees from listing their experience, as this effectively functions as a non-compete agreement. However, in states with stricter trade secret protections, the burden of proof remains on the employee to ensure that no "confidential information" is leaked.

The "Inevitable Disclosure" Doctrine

Some employers argue that by listing specific frameworks used in a highly specialized project, you are inevitably disclosing trade secrets. While this is rarely successful for general software roles, it is a risk if you were a lead architect on a unique, "black box" system. Always err on the side of caution by focusing on the function of the software rather than the architecture.

Action Item: If you worked on a highly specialized, proprietary system, use a "Project Description" that focuses on the business outcome (e.g., "Scaled platform to 1M+ users") rather than the technical "how" (e.g., "Re-engineered the proprietary database sharding logic").

Best Practices for Resume Compliance

  1. Generalize the Stack: Instead of "Used proprietary internal framework X to optimize Y," write "Utilized industry-standard frameworks to optimize system performance."
  2. Focus on Outcomes: Use metrics that demonstrate your impact without revealing the underlying technology stack.
  3. Review Your NDA: Check your contract for specific "Confidential Information" definitions. If it is overly broad, it may be unenforceable, but you should still avoid testing it.
  4. Sanitize Project Names: If a project is internal-only, refer to it by its function (e.g., "Internal Billing System") rather than its internal code name.

Key takeaway: If you are unsure whether a specific detail is protected, ask yourself: "Does this information provide a competitor with a shortcut to replicate our product?" If the answer is yes, remove it.

TermScore can automatically analyze your employment contracts and NDAs to identify restrictive clauses that might impact your ability to market your skills. By uploading your agreement, you can receive a clear, plain-English breakdown of what you are legally permitted to disclose, ensuring you can update your resume with total confidence.

Instant Clause Diagnostic

Check a suspicious clause

Paste a sentence or clause from your employment & nda to get an immediate statutory risk audit.

0/3000
§

TermScore Legal Intelligence Group

Audited for 2026 Standards

Researched and cross-referenced against statutory codes, judicial rulings, and TermScore's proprietary Corpus of 100,000+ analyzed contracts. Our intelligence unit continuously audits contract enforceability and predatory clause variance across all 50 US jurisdictions.

Methodology: Empirical Corpus + Statutory CodeEditorial Standards & Methodology →

Get the contract red-flag checklist

Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.

Keep reading

Don't guess. Get your TermScore.

Upload your lease, employment contract, or agreement and let our AI flag every risk in seconds.

Score my document free