Does an employment NDA prevent me from listing specific project technologies on my portfolio?

Does an employment NDA prevent me from listing specific project technologies on my portfolio?

An employment NDA generally does not prevent you from listing the technologies you used, such as programming languages, frameworks, or cloud infrastructure. However, it strictly prohibits disclosing proprietary configurations, trade secrets, or non-public architectural designs. You can safely list the 'tools' while protecting the 'intellectual property' of your former employer.

Understanding the Scope of Confidential Information

Most NDAs define 'Confidential Information' broadly to protect the company's competitive advantage. It is critical to distinguish between general skills and proprietary assets.

What You Can Usually List

• Standard programming languages (e.g., Java, TypeScript, Go).
• Common frameworks and libraries (e.g., React, Spring Boot, TensorFlow).
• Cloud service providers (e.g., AWS, Azure, GCP).
• Methodologies (e.g., Agile, Scrum, CI/CD pipelines).

What You Must Keep Confidential

• Proprietary algorithms or unique business logic.
• Internal API documentation or private endpoints.
• Specific database schemas or data structures.
• Non-public security protocols or infrastructure configurations.

Key takeaway: If the technology is a standard industry tool, it is likely not confidential. If the technology is a custom-built internal tool or a unique implementation of a standard tool, it is likely protected.

Action Item: Review your NDA for a section titled 'Definition of Confidential Information.' If it explicitly lists 'source code' or 'technical specifications,' proceed with extreme caution when describing your contributions.

The Risk of 'Trade Secret' Misappropriation

Under the Defend Trade Secrets Act (DTSA) in the U.S., companies have significant legal recourse if an employee discloses information that provides them with an economic advantage. Listing a 'tech stack' is rarely a violation, but explaining how you solved a specific, novel problem using that stack can be.

How to Anonymize Your Portfolio

1. Focus on the Problem: Describe the business challenge you solved (e.g., 'Reduced latency by 20%') rather than the internal mechanism.
2. Generalize the Stack: Use broad terms like 'Cloud-native microservices' instead of 'Custom Kubernetes operator with specific internal security patches.'
3. Omit Metrics: Never include specific revenue figures, user counts, or internal growth percentages unless they are public knowledge.

Action Item: Draft your portfolio entry and ask yourself: 'Could a competitor use this information to replicate the company’s product?' If the answer is yes, redact the specific details.

Jurisdictional Considerations

Employment laws vary significantly by region. In California, for example, Business and Professions Code Section 16600 limits the enforceability of restrictive covenants. However, this does not override the protection of trade secrets. Regardless of your jurisdiction, the safest path is to obtain written consent from your former employer if you intend to showcase a high-profile project in detail.

Key takeaway: Always prioritize your professional reputation. Even if a disclosure is technically legal, an employer may still initiate a costly legal dispute if they perceive a breach of confidentiality.

Action Item: If you are unsure, send a brief, professional email to your former manager or HR department: 'I am updating my portfolio and would like to mention my work on [Project Name]. I plan to list the tech stack as [X, Y, Z]. Do you have any concerns regarding confidentiality?'

Leveraging AI for Contract Clarity

Navigating the nuances of an NDA can be daunting, especially when your career depends on showcasing your expertise. TermScore provides an automated analysis of your employment agreements, highlighting specific clauses that restrict your ability to share project details. By identifying these risks early, you can build your portfolio with confidence, knowing exactly where the boundaries lie between professional growth and legal liability.