How to Write Resume Bullets When Your Work Is Confidential
How to describe impact on a resume when NDAs, classified projects, or proprietary systems limit exactly what you can name.
Confidentiality limits detail, not impact
Engineers under NDA often default to vague bullets out of caution, but scope and outcome can usually be described without naming the client, product, or proprietary system.
What you can typically still say
- The type of system or domain (payments infrastructure, trading platform, internal analytics) without naming the company or client
- Team size, scale of usage, and your specific role, even if the product name is withheld
- Relative or percentage-based outcomes instead of exact figures if raw numbers are sensitive
Example transformation
Before: Worked on a confidential project, cannot share details.
After: Rebuilt a core transaction-processing service for a fintech platform (details confidential), reducing processing latency by roughly 40% for a system handling millions of daily transactions.
When in doubt, check your agreement
Most NDAs restrict naming clients, proprietary architecture, or exact financial figures, not the general existence of the work or your role. When unsure, favor scope and outcome language over specific names or numbers.
Next steps
Use ReuseMe to store the full, unredacted context of confidential work privately, then generate a resume-safe version for each application.