Is it legal to discuss job responsibilities in technical interviews if I signed an NDA?
Discussing job duties during interviews while under an NDA is generally legal, provided you avoid disclosing trade secrets. Use TermScore to verify.
Yes, you can legally discuss your job responsibilities in technical interviews despite signing an NDA. NDAs are designed to protect trade secrets and proprietary business information, not your professional experience or general job duties. You may describe your role, technical stack, and methodologies without violating your agreement.
Understanding the Scope of Your NDA
Most Non-Disclosure Agreements (NDAs) are narrowly tailored to protect specific categories of information. They are not blanket bans on discussing your career history. To determine if you are at risk, you must distinguish between 'General Professional Experience' and 'Proprietary Information.'
What You Can Safely Discuss
- General Tech Stack: Mentioning that you used React, AWS, or Python is standard industry practice.
- Methodologies: Explaining your use of Agile, Scrum, or CI/CD pipelines is acceptable.
- Job Title and Hierarchy: Your reporting structure and general scope of authority are public-facing information.
- Soft Skills and Leadership: Discussing how you managed teams or resolved conflicts is entirely outside the scope of an NDA.
Key takeaway: If the information is something you could reasonably put on a public LinkedIn profile, it is almost certainly safe to discuss in an interview.
Action Item: Review your NDA for a 'Definition of Confidential Information' section. If it does not explicitly list 'job duties' or 'daily tasks' as confidential, you are on safe ground.
Identifying High-Risk Disclosures
While your role is fair game, the specific implementation of that role at your current employer may be protected. You must avoid crossing the line into proprietary territory.
| Category | Safe to Discuss | High Risk (Avoid) |
|---|---|---|
| Code | Languages and frameworks used | Proprietary algorithms or source code |
| Architecture | General system design patterns | Internal network diagrams or API keys |
| Strategy | General market trends | Unreleased product roadmaps or internal KPIs |
| Clients | Industry sectors served | Specific client lists or contract terms |
The 3-Step Filter for Technical Interviews
- The Public Test: Is this information available on the company's website or in a press release? If yes, it is safe.
- The Competitive Advantage Test: Would this information give a competitor an unfair advantage? If yes, it is likely a trade secret.
- The Specificity Test: Are you describing a general process or a specific, non-public internal tool? If it is a proprietary internal tool, keep the description high-level.
Key takeaway: When in doubt, speak in abstractions. Instead of saying 'I optimized our proprietary SQL query for the X-100 database,' say 'I optimized complex database queries to improve latency by 20%.'
Action Item: Prepare a 'safe' version of your project descriptions that focuses on the technical challenges you solved rather than the specific data or internal systems you used.
Jurisdictional Nuances and Legal Reality
The enforceability of NDAs varies significantly by jurisdiction. For example, in California, Business and Professions Code Section 16600 generally disfavors broad restraints on trade. However, even in more restrictive states, courts rarely uphold NDAs that prevent an employee from describing their own skills and experience, as doing so would effectively prevent them from working in their chosen profession.
When NDAs Become Overly Broad
If an NDA is written so broadly that it prevents you from discussing your own job duties, it may be considered an 'unreasonable restraint on trade.' Courts generally strike down or narrow these clauses because they violate public policy by hindering an individual's ability to earn a living.
Practical Strategies for the Interview
You can demonstrate your technical expertise without triggering a breach. Use these strategies to stay compliant while impressing recruiters:
- Use Hypotheticals: 'In a previous role, I encountered a scenario where X happened, and I solved it by doing Y.'
- Focus on Outcomes: Emphasize the results (e.g., 'reduced server costs by 15%') rather than the internal mechanisms.
- Ask for Clarification: If an interviewer asks for specific details about a proprietary system, it is perfectly professional to say, 'I am bound by an NDA regarding the specifics of that internal system, but I can explain the architectural principles I applied.'
Action Item: Practice your 'NDA-safe' responses with a peer. If they can understand your technical contribution without needing to know the company's secret sauce, your explanation is likely safe.
Leveraging TermScore for Contract Clarity
Navigating the fine print 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 highlighting restrictive clauses and identifying potential risks in your non-disclosure obligations. By uploading your contract to TermScore, you can gain a clear, plain-English understanding of exactly what you are permitted to discuss, allowing you to 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.