Is listing proprietary software frameworks on a resume a breach of an employment NDA?

Is Listing Proprietary Software Frameworks on a Resume a Breach of an Employment NDA?

Listing proprietary software frameworks on a resume constitutes a breach of an employment NDA if the framework is non-public, proprietary, or classified as a trade secret. Merely naming an internal tool can violate confidentiality clauses, exposing you to litigation, injunctive relief, and the forfeiture of severance or equity.

Understanding the Scope of Your NDA

Most employment NDAs are drafted broadly to protect the company's "intellectual property" and "confidential information." In the context of software engineering, this often extends beyond source code to include internal frameworks, architecture patterns, and proprietary methodologies that provide the company with a competitive advantage.

What Constitutes Confidential Information?

• Internal Tooling: Custom-built frameworks, libraries, or APIs not available to the public.
• Architecture Patterns: Unique ways your team structured microservices or data pipelines.
• Project Codenames: Internal names for products that have not yet launched.
• Performance Metrics: Specific data points regarding system throughput or latency that reveal internal capabilities.

Key takeaway: If you cannot find the framework name on the company’s public GitHub or a technical blog post, assume it is confidential and off-limits for your resume.

Action Item: Review your original employment agreement for a section titled "Confidential Information" or "Definitions." If the definition includes "proprietary software" or "internal systems," you are legally restricted from disclosing those names.

The Risk of "Resume-Driven Development"

Engineers often feel pressured to list specific technologies to pass automated resume screening tools (ATS). However, the legal risk of disclosing a trade secret far outweighs the benefit of a keyword match. Courts in jurisdictions like California (under the Uniform Trade Secrets Act) take the misappropriation of trade secrets very seriously, even if the disclosure was unintentional.

Risk Comparison: Public vs. Proprietary

Action Item: Audit your resume for any tool names that are not industry-standard (e.g., React, Kubernetes, AWS). If you see a name that sounds like an internal project, remove it immediately.

How to Showcase Skills Without Violating NDAs

You can demonstrate your expertise without naming the proprietary framework. The goal is to describe the complexity and impact of your work rather than the specific tools used.

1. Focus on the Problem: Instead of saying "Built the X-Framework for data ingestion," say "Architected a high-throughput data ingestion pipeline handling 5TB of daily traffic."
2. Use Industry Standards: Describe the underlying principles. If you used a proprietary ORM, describe your experience with "advanced database abstraction layers and query optimization."
3. Quantify Results: Focus on the outcome. "Reduced system latency by 40%" is more impressive to a recruiter than the name of the tool you used to achieve it.

Key takeaway: Recruiters care about your ability to solve problems at scale. Focus on the 'what' and 'how' of the engineering challenge, not the 'what' of the internal tool name.

Action Item: Rewrite your bullet points to follow the "Action + Context + Result" formula. This highlights your skills while keeping your resume compliant with your legal obligations.

When in Doubt, Seek Clarification

If you are unsure whether a specific framework is proprietary, check your company’s public-facing engineering blog. If the company has written about the framework publicly, it is generally safe to list. If there is no public record, do not list it. If you are leaving the company, you can ask your manager or HR department for a "letter of reference" that explicitly states what you are permitted to discuss regarding your technical contributions.

TermScore can automatically analyze your employment contracts and NDAs to identify specific clauses that restrict how you describe your work experience, ensuring you stay compliant while effectively marketing your skills to future employers.