Most NDA advice assumes an employment relationship already exists, or is about to. A candidate NDA is different: it gets signed by someone who might never work for you, in exchange for nothing more concrete than the chance to interview. That changes what a court will treat as reasonable, and it changes what actually needs to be in the document. An NDA drafted for an employee, then handed to a candidate before a second-round interview, is usually broader than it needs to be and, in a few specific ways, weaker than the employer assumes.
When Asking a Candidate to Sign Is Reasonable
The trigger for a pre-employment NDA should be what the candidate will actually see during the process, not the seniority of the role. A candidate interviewing for a senior engineering position who will walk through unreleased architecture, a product roadmap, or a live demo of code that hasn’t shipped is a reasonable case: real confidential information is changing hands before any offer exists. The same is true of a final-round executive candidate who gets shown board materials, financial projections, or an acquisition target as part of evaluating whether they can do the job. A take-home technical assessment built from real, non-public data (an actual customer dataset, a real production bug) is another case where the exposure is genuine.
Most interviews don’t reach that bar. A first-round screen, a behavioral interview, a portfolio review, or a technical assessment using synthetic or public data doesn’t expose anything an NDA needs to protect, and asking every candidate at every stage to sign one is the kind of overreach that reads as a red flag to experienced candidates and adds friction to a process that doesn’t need it. The document should follow the information, not the org chart.
Why Consideration Is the Real Complication
Every enforceable contract needs consideration, something of value exchanged on both sides, and this is where a candidate NDA runs into a problem an employee NDA doesn’t have. For a current employee, continued employment (or, in states that require it, a signing bonus or other independent benefit) is the consideration. For a candidate who isn’t employed yet and has no offer, there’s no employment to exchange. The consideration has to be something else: access to the confidential information itself, or the opportunity to participate in a competitive interview process the company didn’t have to extend.
Courts generally accept access to real confidential information as sufficient consideration, which is exactly why the “what will they actually see” question above matters twice over. It determines whether the NDA is reasonable to ask for, and it’s also the thing that makes the NDA enforceable in the first place. An NDA presented to a candidate who is shown nothing beyond a generic slide deck and a job description is thin on both counts: there was little to protect, and there’s a real argument the candidate received nothing of value in exchange for signing.
What Scope Holds Up If They’re Never Hired
This is the part that catches employers off guard, because a candidate NDA has to work as a standalone document regardless of the hiring outcome, and most of the time the outcome is no. A few things determine whether it survives that stress test.
The definition of confidential information needs to be tied narrowly to what was actually disclosed during the process, not written as a general catch-all covering “any information about the company.” A candidate who interviews, doesn’t get the job, and goes on to work at a competitor six months later is not violating a properly scoped NDA by using their general knowledge of the industry, their own resume history, or skills they’d have regardless of the interview. They violate it only if they disclose or use the specific material they were shown, the actual roadmap slide, the actual codebase walkthrough, the actual financials. An NDA that tries to restrict more than that (their ability to work in the field at all, or to use general industry knowledge) starts to function like an unsigned non-compete, and courts are far less willing to enforce that kind of restriction against someone the company never employed. For how that line gets drawn more generally, NDA vs Non-Compete Agreement covers the difference between protecting information and restricting where someone can work.
The duration also needs to be reasonable on its own terms, not borrowed wholesale from an employee agreement. A multi-year confidentiality period tied to interview materials, most of which lose their sensitivity within a year or two as the product ships or the roadmap changes, is harder to justify than the same period tied to a genuine trade secret an active employee has ongoing access to. And the NDA should say plainly that it does not create any obligation to hire, and does not restrict the candidate’s ability to interview elsewhere or accept another offer while the process is ongoing. Silence on that point invites a candidate’s attorney to argue the NDA was functioning as an informal, one-sided lock-up.
- Candidate agrees not to disclose any information about the Company
- Confidentiality obligation continues indefinitely
- No statement of what the candidate actually saw or received
- Silent on whether the candidate can interview elsewhere
- Names the specific roadmap, code, and financial materials reviewed
- Confidentiality obligation runs two years from the date of disclosure
- References the interview session and materials as the consideration
- States plainly: no obligation to hire, no restriction on other offers
How a Candidate NDA Differs From an Employee NDA
Candidate NDA vs employee NDA
| Candidate NDA | Employee NDA | |
|---|---|---|
| Consideration | Access to specific interview materials | Continued employment or compensation |
| Scope | Narrow: only what was shown | Broader: ongoing access across the role |
| Typical duration | 1 to 2 years from disclosure | 2 to 5 years, or indefinite for secrets |
| Whistleblower (DTSA) notice required | ||
| Risk if overbroad | Reads as an informal non-compete | Narrowed by a court to fit |
| Should state no obligation to hire |
One difference worth calling out on its own: the Defend Trade Secrets Act’s whistleblower notice requirement (18 U.S.C. § 1833(b)) applies to agreements with employees and contractors governing trade secrets, and skipping it costs an employer access to exemplary damages and attorney’s fees in a federal trade secret claim against that person. A candidate who is never hired never becomes an employee or contractor under that provision, so a standalone candidate NDA doesn’t carry the same requirement, though many companies include the notice anyway as a matter of habit, or because the same template later gets reused for a signed employee.
The Decision Path
Drafting It as Its Own Document
The cleanest approach is to treat the candidate NDA as its own short, standalone agreement rather than a lightly edited copy of the employee version, since the two documents are doing different jobs under different legal footing. If the candidate is later hired, a separate employee NDA or a confidentiality clause in the offer letter takes over prospectively; the candidate NDA doesn’t need to be stretched to cover a relationship it wasn’t written for. Our NDA generator builds a one-way agreement from a short set of questions about the relationship and what’s being disclosed, which is the more relevant structure here since the flow of information runs from the company to the candidate, not the other way around. If you’re weighing whether a full standalone NDA is the right tool at all versus a shorter confidentiality clause folded into an offer letter, NDA vs Confidentiality Clause covers how to make that call.
