NDA Before a Job Interview: Should You Sign It? What to Watch
You get a calendar invite for a technical screen. Attached is a PDF. It's an NDA — and the company wants you to sign it before you talk.
This happens more often than most candidates realize, especially at startups, tech companies protecting product roadmaps, and firms in regulated industries. Getting an interview NDA is normal. Not every clause in it is.
Most pre-interview NDAs are short, reasonable documents that protect sensitive business information shared during the hiring process. Some are not. A few include language — usually copied from a vendor NDA or an employee agreement — that gives the company far more than confidentiality. Knowing the difference takes about ten minutes. Signing without checking takes ten seconds. That gap matters.
Why Companies Ask Candidates to Sign NDAs
When a company brings you in for an interview, it often shares information it can't share publicly: product plans, technical architecture, unreleased features, financial projections, or strategic direction. Without some protection in place, a candidate could walk away from the process and share that information with a competitor, a journalist, or their current employer.
The NDA is how companies manage that risk. From their perspective, it's a standard precaution — not a signal of distrust, not an attempt to trap you, just a documented agreement that what's discussed in the room stays in the room.
That logic is sound. The problem comes when the NDA goes beyond what the interview context actually requires. A document drafted to govern a vendor relationship or a full-time employment engagement has different assumptions than a two-hour interview. When those templates get repurposed without editing, candidates sometimes end up signing things the company didn't even intend.
What's Normal in a Pre-Interview NDA
A well-scoped pre-interview NDA has three defining characteristics. If your document hits all three, it's almost certainly fine to sign.
The scope is limited to the interview itself. The confidentiality obligation should cover information disclosed to you during the interview process — not information you already knew, not information that becomes public, not your own ideas. Language like "information disclosed by the Company to Candidate during the interview process" is clean. Language that says "all information related to the Company's business" is not, because that's undefined and potentially enormous.
The duration is 1–2 years. A pre-interview NDA covering things discussed in a few conversations doesn't need a ten-year term. One to two years from the date of the interview is market standard. Anything over three years for an interview-only engagement warrants a question, if not a negotiation.
There's no non-compete and no IP assignment. These two clauses have no place in a pre-interview NDA. You haven't been hired. There's no employment relationship. No legitimate company needs you to agree not to work for competitors before they've offered you a job — and if they're capturing intellectual property rights from conversations, something is seriously wrong with the document.
If your NDA matches this profile — confidentiality only, scoped to the interview, limited duration — you can sign it without significant concern.
Red Flags in Pre-Interview NDAs
Most problematic pre-interview NDAs aren't written by lawyers trying to take advantage of candidates. They're templates repurposed without thought. That doesn't make the language less binding. Watch for these three issues.
Non-compete clause. This is the clearest red flag. A non-compete in a pre-interview NDA says you agree not to work for competitors — either immediately, or for some period after the interview. You haven't accepted any employment, you haven't been paid, and the company has no legitimate basis to restrict your future work at this stage. Non-competes in pre-employment documents are unenforceable in many jurisdictions and a sign that the company is either using a template carelessly or is being genuinely overreaching. Either way, don't sign it as written.
IP assignment on take-home test work. Some companies ask candidates to complete a technical assessment, a design challenge, a writing sample, or a case study as part of the interview. If the NDA includes an IP assignment clause, work you submit during the process may become the company's property — whether you get the job or not. This isn't hypothetical. Companies have used interview assignments commercially without compensating or crediting candidates. If there's any IP assignment language and there's a take-home component, flag it before you submit anything.
Penalty clauses for breach. Standard NDAs specify that breach entitles the other party to seek injunctive relief — a court order stopping the disclosure. Some NDAs go further and specify a fixed dollar amount as liquidated damages for breach. In a pre-interview context, this is excessive. You're agreeing to protect information disclosed over a few hours. A clause that exposes you to $50,000 in damages if you accidentally mention something is not proportionate to that risk.
The Take-Home Test IP Problem
The intersection of pre-interview NDAs and take-home assignments deserves specific attention because it's where candidates get hurt most often.
Here's the pattern: company sends NDA, NDA includes IP assignment language, candidate signs without reading closely, candidate completes take-home assignment, candidate doesn't get the job, company retains ownership of the work product.
The work product in question might be a feature design, a piece of code, a marketing plan, or a financial model. It might be genuinely good work. You did it, you won't be compensated for it, and the company now owns it.
To protect yourself before submitting any take-home work:
First, read the NDA before you start the assignment. If there's IP assignment language, raise it before you submit anything — not after. Once the work is submitted, you've likely lost any practical leverage.
Second, keep your own copy of everything you submit and document when you submitted it. If a dispute ever arises, a timestamped record of your original file matters.
Third, if the assignment is substantial — more than a few hours of work — it's reasonable to ask whether the company pays for assignments. Many do, and asking isn't unusual. It signals that you take your work seriously, not that you're being difficult.
Fourth, limit the scope of what you submit. If the assignment asks you to solve a real business problem, solve a simplified or hypothetical version. Don't submit work that could be deployed directly. This is standard practice among experienced candidates.
Can You Negotiate a Pre-Interview NDA?
Yes — and doing so is less risky than most candidates assume.
The fear is that asking for changes signals you're difficult, litigious, or not actually interested in the role. That fear is mostly unfounded. Recruiters at companies that use NDAs routinely see candidates ask questions about them. A specific, professional request to modify a clause reads as competence, not obstruction.
The key is to be specific and constructive. Don't say "I'm not comfortable with this NDA." Say "I'd like to adjust section 3 to limit the IP assignment to information specifically disclosed by the company rather than work product I create during the assessment — is that something you can accommodate?"
If the change you're asking for is reasonable (removing a non-compete, narrowing an IP clause, adding a carve-out for your pre-existing work), most companies will agree without much friction. If they refuse a clearly reasonable request, that tells you something worth knowing about how they operate.
One practical note: direct your request to the hiring manager or recruiter, not legal. Legal's job is to protect the company's interests. The hiring manager's job is to close candidates. They have more motivation to find a workable solution.
Should You Refuse to Sign?
Refusing to sign entirely is a higher-stakes move than negotiating, and the calculus depends on what's in the document.
Refusing is reasonable when:
- The NDA includes a non-compete with no room for modification
- There's IP assignment language covering take-home work and the company won't remove it
- The scope is so broad it would restrict how you discuss your existing career
- The penalties for breach are disproportionate and non-negotiable
In these cases, refusing is a legitimate response. You're not being difficult — you're protecting yourself from a document that gives the company more than any interview context justifies.
Refusing may send the wrong signal when:
- You've confused a standard confidentiality clause with something more aggressive
- You're refusing on principle rather than because of a specific clause
- The role is competitive and your refusal will read as a risk signal without a clear reason attached
If you decide not to sign, say why. "I'm not able to sign an NDA that includes a non-compete before any employment offer — I'd be glad to sign a version limited to interview confidentiality" is a professional response that keeps the conversation open. Walking away without explanation closes it.
Counter-Language for Pre-Interview NDAs
If you need to propose modifications, here are clean, professional alternatives to common problem clauses.
For overly broad scope, replace language like "all information related to the Company" with:
"Confidential Information" means information disclosed by the Company to Candidate specifically in connection with the interview process, and marked or identified as confidential at the time of disclosure or confirmed in writing as confidential within seven (7) days of disclosure.
For IP assignment covering take-home work, add an explicit carve-out:
For the avoidance of doubt, this Agreement does not assign to the Company any intellectual property rights in work product created by Candidate independently and not derived from Confidential Information disclosed by the Company.
For non-compete clauses, propose deletion with an explanation:
Candidate respectfully requests the removal of Section [X] (Non-Competition). As no employment relationship exists at this stage, a restriction on competitive employment is not proportionate to the interview context. Candidate agrees to be bound by the confidentiality obligations in all other sections.
These changes are reasonable on their face. If a company rejects all three, that's meaningful information.
FAQ
Is it common to receive an NDA before a job interview?
Common in some industries, not universal. Startups, tech companies, financial firms, and healthcare companies use them most frequently. Government contractors sometimes require them due to the nature of the work discussed. In professional services, management consulting, and investment banking, pre-interview NDAs appear regularly. If you're interviewing in one of these sectors, receiving one is not surprising.
Can a pre-interview NDA affect my current job?
It can, if the scope is broad enough. An NDA that requires you to disclose all other existing confidentiality obligations could surface your current employer's sensitive arrangements. A non-compete that runs from the interview date could technically overlap with your current role. These are unusual but not unheard of. Read the document with your current employment in mind, not just future employment.
What if the company says the NDA is non-negotiable?
"Non-negotiable" is sometimes true and sometimes a negotiating position. If the document is standard and your objection is minor, pushing back may not be worth it. If the document has a material problem — a non-compete, an IP assignment covering your take-home work — it's worth asking once even if they've said it's final. The worst outcome is they confirm it's non-negotiable and you decide whether that's acceptable. The better outcome is they make a quiet exception.
Does signing a pre-interview NDA affect my ability to discuss the interview publicly?
Potentially. If you're asked to keep the product roadmap confidential, you can't describe it in a blog post. If you're asked to keep the interview process itself confidential, you may not be able to post about it on LinkedIn or discuss it with peers. Standard NDAs don't prohibit you from confirming you interviewed at a company — but poorly drafted ones might try to. Check the scope clause specifically.
What if I signed and now I'm worried about something I disclosed?
Assess the risk proportionately. Casual mentions of an interview in conversation with a close contact are unlikely to constitute breach. Sharing technical details about an unreleased product with a competitor's employee is a different matter. If you're genuinely concerned about a specific disclosure, a consultation with an employment attorney is worth it — most offer a short initial consultation at low cost. If the NDA is in your jurisdiction and the disclosure was inadvertent, the realistic risk is usually low unless there's a demonstrable harm to the company.
If you want to understand the specific clauses in an NDA you've received — whether before an interview, a freelance engagement, or a job offer — NDA Guard can review it in minutes. Upload the document, get a plain-English breakdown of the key terms, and know what you're actually agreeing to before you sign.
Related reading: