Does an employment NDA prevent me from discussing technical project methodologies during a job interview?

Does an employment NDA prevent me from discussing technical project methodologies during a job interview?

No, a standard employment NDA does not prevent you from discussing your professional skills, methodologies, or general experience. You are legally entitled to describe your expertise and how you solve problems. However, you must avoid disclosing specific, non-public trade secrets, proprietary source code, or confidential client data.

Understanding the Legal Boundary

The primary purpose of a Non-Disclosure Agreement (NDA) is to protect a company’s competitive advantage, not to prevent an employee from pursuing future career opportunities. Courts generally view overly broad NDAs that restrict an individual's ability to practice their profession as unenforceable.

Trade Secrets vs. General Skill

Distinguishing between what you can and cannot say requires understanding the legal definition of a trade secret. Under the Defend Trade Secrets Act (DTSA) in the U.S., information qualifies as a trade secret only if it derives independent economic value from not being generally known.

• Protected Information: Proprietary algorithms, specific customer lists, internal financial projections, and non-public product roadmaps.
• Permissible Information: General methodologies, software development lifecycles (SDLC), management styles, and technical frameworks you utilized.

Key takeaway: If you can explain a concept without referencing your former employer’s specific data or proprietary tools, it is almost certainly safe to discuss.

Action Item: Review your NDA for a "Definitions" section. If the definition of "Confidential Information" is so broad that it includes your general knowledge, that specific clause is likely legally overreaching.

How to Discuss Technical Projects Safely

When interviewing, you can demonstrate your value without violating your contract by focusing on the abstraction of your work. Follow these steps to ensure compliance:

1. Abstract the Problem: Instead of saying, "I built a database for Company X to track Y," say, "I architected a scalable database solution to optimize high-volume data retrieval."
2. Remove Proprietary Context: Strip away any mention of specific internal tools, proprietary software names, or sensitive client metrics.
3. Focus on Outcomes: Emphasize the results of your methodology—such as a 20% increase in efficiency or a 15% reduction in latency—rather than the specific technical implementation details.

Action Item: Prepare three "safe" project stories that focus on your problem-solving process rather than the specific proprietary environment in which they occurred.

Identifying Red Flags in Your NDA

Some companies draft NDAs with "chilling effects" intended to scare employees into silence. If your contract contains the following, you should be cautious:

• Broad Non-Solicitation Clauses: Clauses that prevent you from working with any company in the same industry.
• Vague Definitions: Definitions of confidential information that fail to exclude "general knowledge and skill."
• Perpetual Duration: NDAs that claim to protect information indefinitely, even after it becomes public knowledge.

Key takeaway: A contract that attempts to restrict your "general knowledge, skill, and experience" is a red flag. In many jurisdictions, including California, such clauses are void as a matter of public policy.

Action Item: If you are unsure about a specific clause, do not guess. Use a tool like TermScore to automatically scan your contract for restrictive language that may be unenforceable or overly broad.

Conclusion

You have the right to market your skills. By focusing on your methodologies and professional growth rather than specific proprietary data, you can navigate interviews confidently. TermScore provides an automated analysis of your employment agreements, highlighting potential risks and clarifying your obligations so you can interview with peace of mind.