The Experience Section: Describing Engineering Work Without Violating NDAs

The Experience Section: Describing Work Without Violating NDAs

The single hardest part of writing an engineering resume isn’t formatting or quantifying impact — it’s describing work that lives behind NDAs, confidentiality agreements, or unannounced products. Engineers at FAANG, AI labs, defense contractors, and finance firms routinely face this: the work is substantial, the impact is real, but the specifics are not yours to share. The wrong moves are obvious — leaking confidential details on a public resume, or reducing your bullets to such vague platitudes that the work loses signal. The right moves are subtler. This guide covers what you can describe, what you can’t, and how to communicate the substance of confidential work without crossing the line.

What’s Actually Confidential

The categories vary by employer, but generally:

• Unannounced products and features. If your work hasn’t been publicly released, naming it is typically a breach.
• Specific revenue or business metrics not in public filings. “Lifted ARR by $14M” is fine if your company publishes that detail; it’s a breach if not.
• Customer names not publicly associated with your company. “Worked with our top 5 customers” is fine; “led integration with [unnamed-but-confidential customer]” is not.
• Specific architectural details that constitute trade secrets. “Built the distributed query planner” is usually fine; “implemented our novel X algorithm using Y proprietary technique” may not be.
• Internal team structure / org details at firms that consider these confidential.
• Pre-IPO financial projections, fundraising details, partnership negotiations.

The general test: if a competitor reading your resume could derive a specific competitive insight from your bullets, you’ve leaked something you shouldn’t.

What’s Almost Always Fair Game

• Public-facing scale numbers. If your company published “we serve 500M MAU,” referencing that scale is fine.
• Generic technical descriptions. “Built a distributed event-processing system” doesn’t leak anything specific.
• Your role and seniority, dates of employment.
• Open-source contributions that came out of work projects (those are public by definition).
• Publicly shipped products you worked on, including roughly when they shipped.
• Conference talks you gave on the work (since the talk is public).
• General descriptions of impact at proportional scale (“substantial reduction in latency,” “significant cost savings”) when specific metrics are not public.

The Translation Patterns

Pattern 1: Use public-equivalent metrics

If your company publishes scale (“we handle 1B events per day”), you can use that scale to anchor your work, even if the specific service you worked on handles a smaller portion.

Confidential bullet: “Built feature X for unannounced internal billing system handling $850M in annual transactions.”

Translated: “Built core component of internal billing infrastructure at [Company] (multi-billion-dollar transaction processing scale per public filings).”

Anchors scale to public information. Doesn’t leak specifics.

Pattern 2: Describe the technical pattern, not the product

You can describe what you built technically without naming the unreleased product.

Confidential bullet: “Built recommendation engine for [Unannounced Product Y] that generated 15% of company revenue in beta.”

Translated: “Designed and built large-scale recommendation system using two-tower retrieval and learned-to-rank, deployed to production for new product surface.”

The technical work is described; the unreleased product remains unnamed.

Pattern 3: Describe outcomes generically when specifics are confidential

“Reduced latency by an order of magnitude” or “doubled throughput” works when you can’t share exact numbers.

Confidential bullet: “Cut p99 latency on [proprietary internal service Z] from 312ms to 28ms by reimplementing in C++ with custom memory pools.”

Translated: “Cut p99 latency on a critical internal service by an order of magnitude (from hundreds to tens of milliseconds) by rewriting in C++ with custom memory management.”

Magnitude communicates the scale of improvement without exact numbers.

Pattern 4: Use “project at [Company]” framing

For NDA-heavy work, framing as “led project at [Company]” without naming the specific project is acceptable.

Confidential bullet: “Led migration of [unannounced internal platform W] to Kubernetes, reducing deployment time from 4 hours to 8 minutes.”

Translated: “Led migration of a major internal platform to Kubernetes; reduced deployment time from hours to minutes.”

Less specific but still substantively meaningful. Honest about NDA constraint without overstating.

What You Cannot Translate Around

Some work is so specific that any meaningful description leaks confidentiality. For these projects:

• Don’t include them on the resume.
• Or describe them in extremely generic terms (“contributed to multiple internal systems”) and lean on bullets from non-confidential work for substance.
• Save the substance for in-interview discussion, where confidentiality conventions are different (you can describe more under NDA).

The trap is over-claiming on the resume because “I want them to know how impressive my work was.” If the impressive work can’t be described without leaking, you have to find other ways to demonstrate seniority.

Defense, Government, and Cleared Work

The strictest category. Common conventions for cleared engineers:

• Use “DoD,” “IC” (intelligence community), or “Federal client” rather than agency names if the agency itself is sensitive.
• Describe technical work generically: “developed signal-processing systems for classified mission applications.”
• List clearance level (Secret, TS, TS/SCI, etc.) only on resumes you submit directly to defense employers; don’t put clearance level on a public LinkedIn profile.
• If in doubt, ask your security officer before publishing. They’ve seen many resume drafts and can advise.

Pre-IPO and Stealth Startups

For pre-launch startup work:

• If the company itself is in stealth, list it as “Stealth-mode startup” or similar.
• If the company is named but the product isn’t yet public, describe the product category generically.
• Once the company exits stealth or the product launches, you can update your resume with specifics.

Big Tech with Strict NDAs

FAANG and similar generally allow:

• Naming the company you worked at
• Generic technical descriptions of work
• Public-facing scale numbers
• References to publicly-launched products

FAANG generally restricts:

• Specific internal metrics (revenue impact, A/B test results) not in public filings
• Code-level details about proprietary algorithms
• Names of unreleased projects
• Customer names if not in public partnerships

If you’re at one of these companies and unsure, ask your manager or HR. Many engineers over-restrict themselves; many under-restrict. A 5-minute conversation prevents both errors.

The “Selected Projects” Section as a Workaround

For engineers whose primary work is heavily NDA-protected, a “Selected Projects” section featuring open-source, side projects, or publishable research can balance the resume. Three substantive open-source projects can demonstrate seniority and technical depth even when your day-job bullets are generic by necessity.

This works especially well for:

• Defense and intelligence engineers (where day-job is hard to describe)
• Pre-IPO startup engineers in stealth mode
• Research lab engineers whose internal work is unreleased

What the Interview Stage Allows

Confidentiality conventions in interviews are looser than on resumes:

• You can describe work in more detail under NDA discussions during phone screens and onsite (most companies have unspoken understandings about this).
• You should not share trade secrets, customer names, or specifics that would damage your current/former employer.
• You can describe your own contributions, design decisions, and lessons learned at much greater depth than the resume allows.

Use the resume to anchor what you can defend in detail later. The resume is the bait; the interview is where the substance comes out.

Frequently Asked Questions

See also: Software Engineer Resume Guide 2026 • Quantifying Impact on Engineering Resumes • Resume Mistakes That Get Filtered Out