Does a standard employment NDA prevent me from referencing my contributions to proprietary software on a public GitHub profile?

Does a standard employment NDA prevent me from referencing my contributions to proprietary software on a public GitHub profile?

Yes, a standard employment NDA almost certainly prohibits you from referencing proprietary software contributions on a public GitHub profile. Even if you do not post the actual source code, disclosing project names, specific architectural patterns, or internal technical challenges often constitutes a breach of confidentiality. Most NDAs define 'Confidential Information' broadly enough to include any non-public information regarding the employer's business, products, or technical processes.

Key takeaway: If the information is not publicly available on the company's website or a press release, assume it is confidential. Disclosing it on GitHub can lead to immediate termination and potential litigation.

Understanding the Scope of Your NDA

Employment agreements are designed to protect 'Trade Secrets' and 'Proprietary Information.' When you sign an NDA, you are entering a legally binding contract that restricts your ability to share information about your work. In the context of software engineering, this covers more than just the lines of code you wrote.

What is Typically Protected?

• Proprietary Algorithms: Unique logic or mathematical models developed by the company.
• System Architecture: The way internal services communicate or the specific stack configuration.
• Project Names and Roadmaps: Internal codenames or upcoming features that have not been announced.
• Technical Challenges: Specific bugs or performance bottlenecks that reveal the company's internal infrastructure.

The Risk of 'Metadata' Disclosure

Even if you don't upload code, your GitHub profile might reveal sensitive metadata. For example, listing a project like 'Lead Developer for Project X' on your resume or GitHub bio can be a breach if 'Project X' is a confidential internal initiative. Courts in jurisdictions like California (under the Uniform Trade Secrets Act) have historically sided with employers when employees disclose non-public technical details that provide a competitive advantage.

Action Item: Review your employment contract specifically for the 'Confidentiality' or 'Proprietary Information' clause. Look for definitions that include 'technical data' or 'business operations.'

Comparing Public vs. Private Disclosure

How to Showcase Your Work Safely

You can demonstrate your expertise without violating your NDA. The goal is to focus on your skills and methodologies rather than the specific proprietary implementation.

1. Focus on Public Technologies: Highlight your proficiency in languages (e.g., Rust, Go) and frameworks (e.g., React, Kubernetes) rather than the company's internal tools.
2. Use Generic Descriptions: Instead of 'Built the proprietary payment engine for Company X,' use 'Led the development of a high-throughput, distributed payment processing system.'
3. Seek Written Permission: If you want to list a specific project, ask your manager or legal department for a written 'Letter of Authorization' or a simple email approval.
4. Contribute to Open Source: Build your reputation by contributing to public repositories. This provides verifiable proof of your coding ability without touching proprietary code.

Key takeaway: Always prioritize your career longevity over a single GitHub entry. If you are unsure, do not post it. The risk of being labeled a 'leaker' of trade secrets far outweighs the benefit of a GitHub star.

Legal Consequences of Breaching an NDA

Breaching an NDA is not just a workplace policy violation; it is a breach of contract. Employers can pursue several remedies:

• Injunctive Relief: A court order forcing you to remove the content immediately.
• Damages: Financial compensation for any harm caused to the company's competitive position.
• Termination: Immediate firing for 'Cause,' which may impact your eligibility for unemployment or severance.
• Reputational Damage: Being known as an employee who cannot be trusted with sensitive information is a significant career hurdle.

Action Item: If you have already posted information you suspect might be confidential, remove it immediately and document the removal. Consult with an employment attorney if you believe the company is threatening legal action.

Leveraging Technology for Contract Clarity

Navigating the fine print of employment agreements is complex, and standard legal language is often intentionally opaque. TermScore provides an AI-powered solution to analyze your employment contracts, identifying restrictive covenants and confidentiality clauses that could impact your public-facing work. By using TermScore, you can gain a clear understanding of your obligations before you hit 'publish' on your next GitHub project.