Does a broad confidentiality agreement prevent me from listing specific software frameworks on my resume?
Does a confidentiality agreement block your resume? Learn how to list software frameworks legally without violating NDAs. Use TermScore for analysis.
Does a broad confidentiality agreement prevent me from listing specific software frameworks on my resume?
Generally, no. Listing a software framework on your resume is a statement of your professional skill set, not a disclosure of proprietary trade secrets. Confidentiality agreements (NDAs) protect specific, non-public information, not your general knowledge or the tools you used to perform your job duties.
Key takeaway: You are entitled to market your skills. An NDA cannot legally prevent you from stating that you are proficient in a widely used framework like React, AWS, or Kubernetes, provided you do not disclose how your employer specifically configured or utilized those tools to gain a competitive advantage.
Understanding the Scope of Confidentiality
Confidentiality agreements are designed to protect "Trade Secrets" and "Proprietary Information." In the tech industry, this typically includes internal source code, proprietary algorithms, customer lists, and non-public product roadmaps. It does not include your general professional experience or the industry-standard tools you mastered during your tenure.
What You Can Safely List
- Industry-standard frameworks: React, Angular, Spring Boot, Django, etc.
- Programming languages: Python, Java, Rust, Go, etc.
- Cloud infrastructure: AWS, Azure, GCP (without revealing specific architecture).
- General methodologies: Agile, Scrum, CI/CD pipelines.
What You Must Keep Confidential
- Proprietary implementations: Custom internal libraries or "secret sauce" modifications to open-source frameworks.
- Specific project outcomes: Revenue figures, internal user metrics, or specific business logic that is not public knowledge.
- Architecture diagrams: Detailed descriptions of how your former employer connected various services to solve a unique business problem.
Risk Assessment: Skill vs. Secret
To determine if a resume bullet point crosses the line, apply the "Competitive Advantage Test." If the information you are sharing would allow a competitor to replicate a unique feature of your former employer's product, it is likely a trade secret. If the information simply demonstrates that you know how to use a standard tool, it is your personal professional experience.
| Category | Safe to List | Risk of Breach |
|---|---|---|
| Frameworks | "Proficient in React" | "Used React to build [Company Name]'s proprietary payment engine" |
| Cloud | "Managed AWS infrastructure" | "Configured AWS VPCs to support [Company Name]'s secret data pipeline" |
| Methodology | "Implemented CI/CD pipelines" | "Reduced [Company Name]'s build time by 40% using custom scripts" |
Action Item: Review your resume against your NDA. If a bullet point mentions a specific company project, rewrite it to focus on the technology and the general problem solved, rather than the specific implementation details.
How to Safely Describe Your Experience
When you need to highlight your achievements without violating your contract, use the "Problem-Action-Result" (PAR) method while stripping away proprietary identifiers.
- Identify the tool: State the framework or language clearly.
- Generalize the context: Instead of "Built the internal CRM for Company X," use "Developed a scalable customer management system."
- Focus on the outcome: Use percentages or timeframes that are public-facing or generalized (e.g., "Improved system latency by 20%" rather than "Reduced latency for the X-12 proprietary database").
Jurisdictional Nuances
In jurisdictions like California, non-compete and overly broad confidentiality clauses are heavily scrutinized under the Business and Professions Code Section 16600. Courts generally favor the employee's right to practice their profession. However, even in employee-friendly states, you are still bound by the Uniform Trade Secrets Act (UTSA), which protects actual trade secrets regardless of what your contract says.
Key takeaway: If you are unsure whether a specific project detail is protected, err on the side of caution. It is better to describe your skills broadly than to risk a cease-and-desist letter from a former employer.
Practical Steps for Resume Compliance
- Audit your resume: Remove all references to internal project codenames.
- Consult your NDA: Look for the "Definition of Confidential Information" section. If it is vague, assume it covers anything not found on your company's public website.
- Use TermScore: Our AI-powered platform can analyze your employment contracts to identify exactly which clauses are standard and which are overly restrictive, giving you the confidence to market your skills legally.
TermScore provides instant, AI-driven analysis of your employment agreements, helping you identify restrictive covenants and confidentiality obligations before you hit 'submit' on your next job application. By uploading your contract to TermScore, you can gain clarity on your legal boundaries and protect your career trajectory.
TermScore Research
Our legal AI analyzes thousands of contracts to surface market standards, common pitfalls, and actionable insights for anyone who signs agreements.
Get the contract red-flag checklist
Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.
Keep reading
Employment & NDA
Does an employment NDA prevent me from listing specific proprietary software tools on my resume?
Employment & NDA
Can an employment NDA legally prevent me from discussing specific technical challenges I solved during interviews?
Employment & NDA
How to evaluate if an employment NDA's definition of 'confidential information' is legally enforceable?
Employment & NDA
Can an employer use an NDA to restrict my ability to build open source projects on my own time?
Employment & NDA
Does an employment NDA cover personal side projects developed on my own hardware and outside of working hours?
Employment & NDA
How to tell if an employment NDA is being used as a pretext to restrict my access to professional networking on LinkedIn?