Does an employment NDA prevent me from disclosing my specific technical contributions to a recruiter?
Does an NDA prevent you from discussing technical work with recruiters? Learn the legal boundaries and how to protect your career with TermScore analysis.
Does an employment NDA prevent me from disclosing my specific technical contributions to a recruiter?
No, a standard employment NDA does not prevent you from discussing your professional experience, skills, or the general nature of your work. You are legally entitled to describe your contributions to a recruiter, provided you avoid disclosing specific trade secrets, proprietary source code, or non-public business strategies that provide your employer with a competitive advantage.
Understanding the Scope of Confidentiality
Most employment agreements distinguish between general professional knowledge and proprietary information. Courts generally view an employee's "general skill and knowledge" as their own property, which they are free to carry to future employers. However, specific technical implementations are often protected.
What You Can Safely Disclose
- The programming languages, frameworks, and tools you utilized.
- The high-level architecture of systems you helped build.
- The methodologies used (e.g., Agile, CI/CD pipelines, TDD).
- Your specific role, team size, and project management responsibilities.
- Publicly available metrics or outcomes (e.g., "improved page load speed by 20%").
What You Must Keep Confidential
- Proprietary source code or internal API documentation.
- Unreleased product roadmaps or future feature specifications.
- Internal data sets or customer lists.
- Specific algorithms that are not public knowledge and provide a unique market advantage.
- Internal financial performance data or sensitive business strategies.
Key takeaway: If you can explain the "what" and the "how" without revealing the "secret sauce" (the specific proprietary logic), you are generally safe. Focus on the problem-solving process rather than the internal implementation details.
How to Evaluate Your NDA Risk
Before speaking with a recruiter, perform a self-audit of your contract. Look for specific definitions of "Confidential Information." If the definition is overly broad—covering "all information learned during employment"—it may be legally unenforceable in many jurisdictions, but it still poses a risk of litigation.
| Category | Safe to Discuss | High Risk |
|---|---|---|
| Technical Stack | Languages & Frameworks | Proprietary internal tools |
| Project Scope | General goals & outcomes | Unreleased features |
| Data | Publicly available metrics | Internal customer data |
| Process | Methodologies (e.g., Scrum) | Internal security protocols |
Steps to Safely Communicate Your Experience
- Review the NDA: Identify the specific definition of "Confidential Information" in your contract.
- Sanitize Your Resume: Remove references to internal project codenames or proprietary technology names.
- Use High-Level Descriptions: Describe the challenge, the action you took, and the result (the STAR method) without referencing specific internal codebases.
- Ask for Clarification: If you are unsure, ask your current HR or legal department for a "letter of clearance" regarding specific project descriptions, though this is rarely recommended if you are actively job hunting.
- Consult Counsel: If your work involves highly sensitive IP, consult an employment attorney before updating your LinkedIn or resume.
Jurisdictional Nuances
In jurisdictions like California, non-disclosure agreements that effectively function as non-competes are heavily scrutinized. Under California Business and Professions Code Section 16600, any contract that restrains an individual from engaging in a lawful profession is void. However, this does not grant you a license to misappropriate trade secrets. Always check your local state laws, as protections for employees vary significantly between states like New York, Texas, and California.
Practical Action Item
Before your next interview, draft a "sanitized" version of your project descriptions. If you find yourself struggling to describe a project without using internal terminology, that is a clear indicator that the project details are likely proprietary. Focus your narrative on the transferable skills you gained rather than the specific output you produced.
TermScore can automatically analyze your employment contracts to identify overly broad confidentiality clauses and highlight specific definitions of trade secrets. By uploading your document, you can receive an instant assessment of your legal obligations, ensuring you can confidently discuss your career achievements without violating your agreements.
TermScore Research
Our legal AI analyzes thousands of contracts to surface market standards, common pitfalls, and actionable insights for anyone who signs agreements.