Is it legal to discuss previous job responsibilities during a technical interview if I signed an NDA?

Is it legal to discuss previous job responsibilities during a technical interview if I signed an NDA?

Yes, it is legal to discuss your professional experience, provided you do not disclose confidential information, proprietary trade secrets, or non-public data. You are legally permitted to describe your role, the technologies you utilized, and your general problem-solving methodologies, as long as you protect your former employer's intellectual property.

Key takeaway: An NDA protects a company's secrets, not your professional identity or your ability to earn a living. You are entitled to discuss your skills, but you must redact specific project details that could be considered proprietary.

Understanding the Scope of Your NDA

Most Non-Disclosure Agreements (NDAs) are designed to protect specific categories of information. They are not blanket bans on discussing your career history. To determine what you can safely say, you must categorize your past work into two buckets: public knowledge and protected information.

What You Can Safely Discuss

• General Technical Skills: Languages, frameworks, and tools you used (e.g., "I worked with React and AWS").
• Methodologies: Your use of Agile, Scrum, or CI/CD pipelines.
• Professional Achievements: High-level outcomes, such as "I led a team of five to improve system latency by 15%."
• Soft Skills: Leadership, communication, and project management styles.

What You Must Keep Confidential

• Proprietary Source Code: Specific algorithms or internal codebases.
• Non-Public Financial Data: Revenue figures, internal budgets, or specific client pricing.
• Internal Strategy: Future product roadmaps, M&A activity, or unreleased marketing campaigns.
• Client Lists: If the client relationship is not public knowledge.

The Legal Threshold: Trade Secrets vs. General Knowledge

Under the Defend Trade Secrets Act (DTSA) in the U.S., a trade secret is defined as information that derives independent economic value from not being generally known. If you discuss a process that is standard industry practice, it is not a trade secret. If you discuss a unique, proprietary method your company developed to gain a market edge, you are likely in breach.

Action item: Before your interview, review your NDA for a "Definition of Confidential Information" clause. If the definition is overly broad, assume that any internal documentation or non-public metrics are off-limits.

How to Pivot When Asked Sensitive Questions

Interviewers may inadvertently ask you to disclose protected information. You must be prepared to pivot without appearing evasive. Use the following techniques to maintain your professional integrity while respecting your legal obligations.

1. The "Generalization" Pivot: If asked about a specific proprietary architecture, respond: "I can't discuss the specifics of that internal system, but I can explain how I generally approach scaling distributed systems using similar technologies."
2. The "Outcome-Focused" Pivot: If asked about internal metrics, focus on the percentage of improvement rather than the raw data. "While I can't share the specific revenue impact, I can tell you that the optimization resulted in a 20% reduction in server costs."
3. The "Public Domain" Pivot: If you worked on a project that was eventually released to the public, clarify that: "That project is now public, so I can discuss the architecture we used for the launch."

Key takeaway: If you feel uncomfortable answering a question, state clearly: "I am bound by an NDA regarding that project, but I can speak to the technical challenges I solved during that time." This demonstrates integrity and respect for confidentiality.

Mitigating Risk During the Interview Process

To ensure you remain compliant, treat your interview preparation like a compliance audit. Do not bring physical or digital copies of your previous work to the interview. If you are asked to provide a portfolio, ensure that all code samples are either open-source or have been scrubbed of any company-specific identifiers.

• Scrub your resume: Remove project codenames or specific internal tool names.
• Avoid "Insider" jargon: Use industry-standard terminology instead of company-specific acronyms.
• Document your boundaries: If you are concerned about a specific project, write down what you can and cannot say before the interview.

Action item: Create a "safe-to-share" list of your past projects. If a project isn't on that list, prepare a generic description that focuses on the technology stack rather than the business application.

Leveraging TermScore for Contract Clarity

Navigating the nuances of an NDA can be daunting, especially when your career progression depends on it. TermScore uses advanced AI to analyze your employment agreements, highlighting restrictive covenants and confidentiality clauses in plain language. By uploading your contract to TermScore, you can instantly identify which areas of your past work are restricted, allowing you to interview with confidence and legal clarity.