Is it legal to discuss my previous job duties in technical interviews if I signed an NDA?

Yes, you can discuss general job duties, but avoid proprietary data. Use TermScore to analyze your NDA and identify protected information today.

August 6, 2026TermScore Research611 words

Is it legal to discuss my previous job duties in technical interviews if I signed an NDA?

Yes, you can legally discuss your professional experience and general job duties in a technical interview. An NDA is designed to protect a company's trade secrets and proprietary information, not to prevent you from discussing your own skills, career history, or the general nature of your work.

Key takeaway: Your NDA protects the employer's specific intellectual property, not your right to describe your professional capabilities or the technologies you have mastered.

Understanding the Scope of Your NDA

Most NDAs are drafted broadly, but courts generally interpret them in the context of protecting legitimate business interests. You are not legally barred from discussing your employment history, the job title you held, or the general software stacks you utilized. The restriction applies strictly to confidential information.

What You Can Safely Discuss

  • Your job title and core responsibilities.
  • The programming languages, frameworks, and tools you used.
  • General methodologies (e.g., Agile, Scrum, CI/CD pipelines).
  • Soft skills, leadership experience, and team management.
  • Publicly available project outcomes or industry-standard achievements.

What You Must Keep Confidential

  • Proprietary source code or specific internal algorithms.
  • Non-public architectural diagrams or system designs.
  • Internal financial data, customer lists, or pricing strategies.
  • Unreleased product roadmaps or strategic business plans.
  • Specific security vulnerabilities or internal incident reports.

Action Item: Before your interview, review your NDA to identify if it contains a 'Definition of Confidential Information' section. If it does, compare your planned talking points against those specific categories.

Risk Assessment: NDA vs. Professional Growth

When interviewing, the goal is to demonstrate competence without crossing the line into proprietary disclosure. The following table outlines the difference between safe professional discussion and high-risk disclosure.

TopicSafe DiscussionHigh-Risk Disclosure
Codebase'I worked with a microservices architecture using Go.''I wrote the specific authentication module for our internal API.'
System Design'I optimized database queries to handle 10k requests per second.''I designed the schema for our proprietary customer data warehouse.'
Project Success'I led a team to migrate our legacy stack to AWS.''I migrated our internal data to a server with these specific IP addresses.'

Action Item: If you feel a question is pushing you toward proprietary details, pivot the conversation to the technical challenge you solved rather than the specific data involved.

How to Answer Technical Questions Safely

To remain compliant while still impressing interviewers, use the 'Abstraction Method.' This involves describing the technical problem at a high level, focusing on the engineering principles rather than the specific implementation details of your previous employer.

  1. Identify the Principle: Focus on the underlying technical challenge (e.g., latency, scalability, security).
  2. Abstract the Context: Describe the environment in general terms (e.g., 'a high-traffic e-commerce platform' instead of 'Company X's internal checkout system').
  3. Focus on Your Contribution: Emphasize your decision-making process and the tools you selected.
  4. Avoid Specifics: Never mention proprietary names, internal project codenames, or specific data volumes that are not public knowledge.

Key takeaway: If you are ever unsure, err on the side of caution. You can always say, 'I am bound by an NDA regarding the specific architecture of that project, but I can explain the general principles of the technology we used.'

Jurisdictional Considerations

While NDAs are common, their enforceability varies by region. In California, for example, Business and Professions Code Section 16600 generally prohibits non-compete agreements, and courts are often skeptical of overly broad NDAs that effectively function as non-competes. However, trade secret protection remains robust under the Defend Trade Secrets Act (DTSA). Regardless of your location, disclosing a former employer's trade secrets is a serious legal liability that can lead to litigation.

Action Item: If you are concerned about a specific clause in your contract, do not guess. Use a tool like TermScore to automatically analyze your NDA for restrictive covenants and identify exactly what is defined as confidential, allowing you to interview with confidence and legal clarity.

T

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.

Keep reading

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