Under an NDA? How to Write Resume Bullets for Confidential Work

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.

A fill-in-the-blank template

[Action verb] a [type of system] for a [industry] platform (details confidential), [measurable outcome] for a system supporting [scale descriptor].

Example: Rebuilt a fraud-detection pipeline for a payments platform (details confidential), cutting false-positive review time by roughly 30% for a system processing millions of transactions daily.

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.