Can an employment NDA legally prevent me from discussing my job responsibilities in a technical interview?

Can an NDA stop you from discussing job duties in interviews? Learn the legal limits of confidentiality and how to protect your career with TermScore.

June 7, 2026TermScore Research634 words

Can an employment NDA legally prevent me from discussing my job responsibilities in a technical interview?

No. An NDA cannot legally prevent you from discussing your general job responsibilities or professional experience. It can only protect specific trade secrets, proprietary code, or confidential business strategies. You have a legal right to describe your skills and work history to secure future employment.

Key takeaway: Courts generally view non-disclosure agreements that prevent an employee from discussing their own professional experience as unenforceable restraints on trade. You are entitled to talk about your work, provided you do not disclose proprietary data.

Understanding the Legal Boundaries of NDAs

Most employment NDAs are designed to protect a company's intellectual property, not to prevent you from being employable. When you are in a technical interview, you are expected to explain your contributions to past projects. If an NDA were interpreted to prevent this, it would effectively function as a non-compete agreement, which is increasingly restricted or banned in many jurisdictions, including California (under Business and Professions Code Section 16600) and under recent FTC rulings.

What You Can Safely Discuss

  • Technologies and Tools: You can always discuss the programming languages, frameworks, and cloud infrastructure you utilized.
  • Methodologies: Explaining your use of Agile, Scrum, or specific CI/CD pipelines is standard professional discourse.
  • General Challenges: You can describe the types of problems you solved, such as 'optimizing database latency' or 'scaling microservices,' without revealing the specific proprietary architecture.

What You Must Protect

  • Source Code: Never share proprietary code snippets, internal API keys, or private repository links.
  • Internal Data: Do not disclose non-public financial metrics, user data, or unreleased product roadmaps.
  • Specific Trade Secrets: Avoid discussing unique, patented, or secret algorithms that provide the company with a competitive advantage.

Action Item: Before your next interview, draft a 'safe-to-share' summary of your past projects that focuses on the how and why of your work, rather than the specific internal data of your employer.

Comparing Confidentiality vs. Trade Secrets

CategoryWhat it CoversIs it Discussable?
General ExperienceSkills, tools, and methodologiesYes, always.
Proprietary CodeInternal source code and scriptsNo, never share.
Business StrategyUnreleased roadmaps and pricingNo, keep confidential.
Public KnowledgeInformation available on company blogsYes, it is public.

Identifying Overly Broad NDAs

Some employers draft NDAs that are intentionally vague to discourage employees from leaving. If your contract contains the following, it may be legally suspect:

  • Lack of Definition: The contract fails to define 'Confidential Information' and instead labels 'everything learned during employment' as confidential.
  • No Exclusions: The agreement does not explicitly state that information known to the public or acquired through general skill development is excluded.
  • Perpetual Duration: The NDA claims to last forever, even for non-trade secret information.

Key takeaway: If an NDA is so broad that it prevents you from describing your job duties, it is likely unenforceable. However, you should never rely on an unenforceable contract as a defense; always aim to be discreet rather than litigious.

How to Navigate Technical Interviews Safely

If you are concerned about your NDA, follow this three-step process to ensure you remain compliant while showcasing your expertise:

  1. Abstract the Details: Instead of saying 'I optimized the X-100 algorithm for Company Y,' say 'I optimized a high-throughput sorting algorithm to reduce latency by 20%.'
  2. Focus on Outcomes: Emphasize the results you achieved (e.g., 'improved system uptime by 15%') rather than the internal mechanisms used to achieve them.
  3. Check Public Sources: If your company has published a tech blog or white paper about the project, you are generally safe to discuss the information contained within those public documents.

Action Item: Review your current employment contract specifically for the 'Confidential Information' definition. If it is overly broad, prepare a script for interviews that focuses on your personal contribution rather than the company's proprietary data.

Navigating the intersection of professional growth and legal obligations is complex. TermScore can automatically analyze your employment contracts to identify overly broad confidentiality clauses, non-compete traps, and restrictive covenants, giving you the clarity you need to advance your career with confidence.

T

TermScore Research

Our legal AI analyzes thousands of contracts to surface market standards, common pitfalls, and actionable insights for anyone who signs agreements.

Don't guess. Get your TermScore.

Upload your lease, employment contract, or agreement and let our AI flag every risk in seconds.

Score my document free