When your best work is classified, the natural instinct is to be vague. That hurts you because recruiters hire outcomes, not secrets. The fix: describe what you accomplished without naming the product, client, or technology that is under NDA.
For example, instead of "Led development of the Fusion-7 encryption module for a top-three defense contractor," write "Led a 5-engineer team that built a high-security data pipeline, achieving 99.97% uptime in a zero-trust environment." The first version breaks your NDA; the second proves your impact. Recruiters see the same signal: leadership, uptime, security, scale.
If you worked on a proprietary fraud-detection algorithm for a fintech unicorn, do not name the model. Write: "Designed and deployed a real-time anomaly detection system that reduced false positives by 40% and saved $2.1M annually." Every recruiter knows what anomaly detection is. The number proves the value.
You can always say the industry (healthcare, defense, finance), the general problem (supply chain optimization, user retention, latency reduction), and the impact (dollars saved, hours cut, errors eliminated). NDA language almost never covers these three layers—it protects the means, not the effects.
Add a section at the bottom of your resume called "Selected Projects" or "Key Contributions." For each NDA-restricted project, write one bullet line that includes:
Then in a single italicized disclaimer, append: Details of this project are under NDA and available upon signed mutual agreement. This signals honesty and shows you know how to handle restricted information. It also stops recruiters from pressing for illegal disclosure.
Before (violated NDA): Optimized TensorFlow pipeline for Project Xanadu, a $12M DoD contract, using proprietary on-device ML models.
After (safe, recruiter-readable): Optimized a real-time ML inference pipeline for a government security application, cutting inference time from 120ms to 18ms while maintaining a 99.5% accuracy floor.
One line of watermark is fine. Repeating it 15 times makes you look like you have nothing else. Spread the bullet count across non-NDA work as well.
Never change your job title to hide a project. Leave the title as-is. If the title gives away the project scope (e.g., "Principal Architect, Xanadu"), change nothing—the title itself is not secret. The content under it is what you sanitize.
Some people delete entire jobs they cannot write about. That creates a gap that gets you rejected faster than a sanitized bullet. Always keep the job; describe only the public part of your responsibilities.
Download a free US-style resume template (NDA-friendly formatting included)
That is rare but valid. Say you have permission to discuss work after a mutual NDA is signed, and offer to provide a reference who can verify the project without violating confidentiality. Most recruiters accept this.
Yes, but check the exact text. Many NDAs are narrow—they hide the how, not the whom. If your NDA says "do not disclose the methodology," you can still name the client. Read your specific agreement; do not assume.
Only if the sample is scrubbed of all identifying metadata, comments, and names. Better to create a new, public project that demonstrates the same skillset. A fresh open-source repo carries no legal risk.
Write a summary paragraph that describes your role and impact in purely functional terms: "Responsible for system architecture of a high-availability platform serving 5M+ users, managing a team of 12, and achieving 99.99% SLA compliance." Avoid any specifics that could tie back to the contract.
If you need a clean US-style resume template that handles NDA sections gracefully, start with our free downloadable templates.
Wondering how your own resume holds up?
Check it free — no sign-upProve your remote work impact with concrete metrics and before/after comparisons. Includes a real bullet rewrite example, a checklist, and exact formatting tips to overcome proximity bias when your…
Write a resume for clearance-required jobs without one. Learn the honest rule, how to handle security sections, keyword strategy, and common mistakes.
Stop listing 60+ hour weeks on your US resume. Rewrite 996-era bullets to show impact: lead time reduction, team size growth, or process improvement. Includes before/after examples and a checklist.
Loading…