Does an employment NDA prevent me from listing my software stack on a public resume?

Does an employment NDA prevent me from listing my software stack on a public resume?

Generally, no. Listing standard software tools, languages, and frameworks on a resume does not violate a standard NDA. However, you must avoid disclosing proprietary internal tools, trade secrets, or specific project architectures that are not public knowledge. Your goal is to demonstrate your technical proficiency without revealing the 'secret sauce' that gives your former employer a competitive edge.

Understanding the Scope of Your NDA

Most employment NDAs are designed to protect 'Confidential Information.' In the context of software engineering, this is rarely about the fact that you used Python or AWS. Instead, it is about the specific implementation, architecture, and data that you handled while using those tools.

What You Can Safely List

• Standard Languages: Python, Java, C++, JavaScript, etc.
• Public Frameworks: React, Django, Spring Boot, Kubernetes.
• Cloud Infrastructure: AWS, Azure, GCP (provided you do not disclose specific architectural diagrams).
• Methodologies: Agile, Scrum, CI/CD, TDD.

What You Must Keep Confidential

• Internal Tooling: Proprietary software built in-house that is not available to the public.
• Project Codenames: Referring to unreleased products by their internal project names.
• Specific Data Structures: Unique database schemas or proprietary algorithms that provide a market advantage.
• Security Protocols: Specific details regarding internal security vulnerabilities or custom encryption methods.

Key takeaway: If a tool or language is listed on a job description or a public website, it is generally safe to list on your resume. If you had to sign a separate document to access the tool, it is likely confidential.

Risk Assessment: Public vs. Private Information

To determine if you are in the clear, use the following table to evaluate your resume entries:

Action Item: Audit your resume for any mention of internal project names. If you find one, replace it with a generic description like 'Internal enterprise resource planning system.'

Best Practices for Resume Compliance

You can effectively market your skills while remaining legally compliant by focusing on the impact of your work rather than the mechanics of the proprietary system.

1. Focus on Outcomes: Instead of saying 'Used proprietary Algorithm X to increase speed,' say 'Optimized backend processes to improve system latency by 15%.'
2. Use Industry Standards: Stick to the terminology used in job postings. If a recruiter recognizes the term, it is almost certainly not a trade secret.
3. Avoid Specifics: Never include screenshots of internal dashboards, code snippets, or specific configuration files.
4. Check Your Contract: Review the 'Confidential Information' definition in your original employment agreement. It is usually found in the first three pages.

When to Seek Legal Counsel

If you worked in highly sensitive sectors such as cybersecurity, high-frequency trading, or government contracting, your NDA may be significantly more restrictive. In these cases, even mentioning the tools you used could be considered a breach if the mere existence of that tool is a trade secret.

Key takeaway: If you are unsure, err on the side of caution. A resume is a marketing document, not a technical manual. You do not need to disclose the specific tools to prove your competence.

Navigating the fine line between showcasing your expertise and honoring your legal obligations is critical for your career longevity. TermScore can automatically analyze your employment contracts to identify restrictive covenants and confidentiality clauses, giving you a clear, plain-English summary of what you can and cannot disclose on your resume. Upload your contract to TermScore today to ensure your professional branding is both impressive and legally sound.