Is it legal to discuss job responsibilities in technical interviews while under an NDA?
Discussing job duties during interviews while under an NDA is generally legal, provided you avoid disclosing trade secrets. Use TermScore to verify.
Is it legal to discuss job responsibilities in technical interviews while under an NDA?
Yes, it is generally legal to discuss your general job responsibilities during a technical interview. NDAs are designed to protect proprietary trade secrets, not your professional experience or general skills. You are legally permitted to describe your role, the technologies you used, and your professional accomplishments, provided you do not disclose specific confidential data, proprietary source code, or non-public business strategies.
Understanding the Scope of Your NDA
Most Non-Disclosure Agreements (NDAs) are drafted to protect 'Confidential Information.' In a technical context, this typically includes:
- Proprietary source code or internal software architecture.
- Non-public financial data or business performance metrics.
- Unreleased product roadmaps or strategic initiatives.
- Specific client lists or sensitive customer data.
Crucially, an NDA cannot legally prevent you from discussing your own professional development or the general nature of your work. Courts generally view 'general knowledge, skill, and experience' as the property of the employee, not the employer. If an NDA were interpreted to prevent you from discussing your job duties, it would likely be deemed an unenforceable restraint of trade in many jurisdictions, such as California under Business and Professions Code Section 16600.
Key takeaway: Your NDA protects the company's secrets, not your career history. You have a legal right to describe your professional capabilities to prospective employers.
How to Discuss Technical Work Without Breaching Confidentiality
When interviewing, you must balance transparency with caution. Follow this framework to ensure you remain compliant while effectively demonstrating your value.
- Focus on Methodology: Describe the 'how' of your work. Instead of explaining a proprietary algorithm, explain the type of problem you solved (e.g., 'I optimized a high-latency data pipeline') and the tools used (e.g., 'I utilized Apache Kafka and Kubernetes').
- Use Publicly Available Information: If your company has published white papers or blog posts about their technical stack, you are safe to discuss those specific technologies and architectures.
- Abstract the Data: Never use real-world data sets or specific internal metrics. Use hypothetical scenarios or generalized percentages to illustrate your impact (e.g., 'I improved system throughput by 25%').
- Avoid Proprietary Names: If your company uses internal, custom-built tools, refer to them by their functional category (e.g., 'internal CI/CD orchestration tool') rather than their internal project name.
Comparison: Protected vs. Unprotected Information
| Category | Protected (Do Not Disclose) | Unprotected (Safe to Discuss) |
|---|---|---|
| Code | Proprietary source code/algorithms | Languages, frameworks, and libraries |
| Strategy | Unreleased product roadmaps | General industry trends and challenges |
| Data | Specific internal financial metrics | General scope of project responsibilities |
| Infrastructure | Internal network/security topology | Cloud providers and deployment patterns |
Action Item: Before your next interview, review your NDA for a 'Definitions' section. Identify the specific items labeled as 'Confidential Information' and ensure your talking points do not overlap with those specific categories.
Identifying Red Flags in Your NDA
Some NDAs are overly broad and may attempt to restrict your ability to work in the same industry or discuss your experience. Be wary of clauses that:
- Define 'Confidential Information' to include 'all information learned during employment.'
- Lack a clear expiration date for confidentiality obligations.
- Attempt to restrict your ability to use 'general skills and knowledge' acquired on the job.
If you encounter these clauses, they may be legally overbroad. However, you should never assume an NDA is unenforceable without professional legal review. If you are unsure about the specific language in your contract, you should seek clarification or legal counsel before proceeding with sensitive discussions.
Key takeaway: If a clause seems to prevent you from talking about your basic job functions, it is likely overbroad and potentially unenforceable, but you should treat it with extreme caution until verified.
Leveraging TermScore for Contract Clarity
Navigating the nuances of an NDA can be daunting, especially when your career progression is on the line. TermScore uses advanced AI to analyze your employment agreements, instantly flagging restrictive clauses and identifying potential risks regarding your ability to discuss your work. By uploading your contract to TermScore, you can gain immediate clarity on your obligations, ensuring you interview with confidence and legal peace of mind.
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.