An NDA-friendly portfolio is one that proves your skills and results while disclosing nothing your agreement protects. In practice that means three moves: read the contract to learn what is actually restricted, de-identify or recreate the work that is, and move the rest of the proof into process, role and measurable outcomes. Done well, a confidentiality clause limits what you display, not how convincingly you can document what you did.
TL;DR
- Whether you may show NDA work depends on the wording of your agreement. Some NDAs permit portfolio display, others prevent it, and written consent can change the answer.
- Strip company names, logos, brand colors, internal dashboards and unreleased details, then rebuild the story around problem, insight and outcome.
- Where visuals are off limits, evidence of process, decisions and impact carries the case. Private, permissioned sharing handles what cannot be public.
- Unauthorized disclosure can bring a warning, a demand letter, loss of the client or legal action. Take a specific contract to a qualified attorney.
Table of Contents
- Start with the contract, not the portfolio
- Ask for permission the way a client can say yes
- De-identify the project
- Show process and impact when you cannot show the work
- Share privately when public is not possible
- Know the risks, and the limits of an NDA
- Our perspective: treat evidence as queryable, not displayed
- Build the NDA-safe profile in Alloquy
- A pre-publication checklist
- FAQ
- Sources
Start with the contract, not the portfolio
The most common mistake is treating “NDA” as a single rule. It is a category of contracts, and the answer to “can I show this?” sits in the specific clauses you signed. A freelance marketplace’s own help documentation illustrates the split: whether NDA-protected entries can appear in a portfolio depends on the type of NDA, and if the client declined to allow portfolio display, participants cannot show their entries there.
Before you draft anything, locate these items in the agreement, as outlined in a checklist for confidential client work:
- The definition of “Confidential Information.” Broad definitions capture almost everything; narrow ones list specific categories.
- Publicity or portfolio clauses. Some contracts explicitly grant or deny the right to reference the engagement.
- Intellectual property ownership. If the client owns the deliverable, displaying it is a separate question from having made it.
- Disclosure limits and approval processes. Look for a named contact and a written-consent mechanism.
- Duration. Confidentiality often continues after the project or employment ends.
The client’s name is a frequent blind spot. Some NDAs protect the client’s name and even the existence of the engagement; many do not. You cannot assume either way, so read the clause.
If you are still employed, the stakes are higher. A company blog on employment contracts notes that displaying unreleased features, proprietary algorithms or internal metrics without authorization is a breach of contract that can lead to claims for injunctive relief. An employer’s legal team, not a blog post, has the final word on your agreement.
Clarify scope before you sign the next one
The IEEE Computer Society advises professionals to clarify the scope and duration of an NDA before signing. Two lines of negotiation protect your portfolio in advance:
- Ask for a clause allowing you to describe your role and the nature of the work in general terms.
- Ask for a defined path to written consent for specific assets after launch.
The American Bar Association’s business-tort newsletter makes the underlying point from the drafting side: NDAs should be tailored, since a one-size-fits-all approach can be overly broad, protecting little of real value while restricting the professional unfairly. Asking for specificity is a normal request, not an adversarial one.
Ask for permission the way a client can say yes
A “no” to the question “may I show this?” is often a “no” to the question as framed. Rocket Lawyer’s guidance observes that portfolio use of confidential work may require prior written consent, depending on the exact wording. So make consent easy to grant.
One workable pattern is tiered disclosure. Guidance on client work suggests offering options from a named case study down to a method-only description so the client can choose the level they are comfortable with. Adapted to a portfolio request, the tiers look like this:
| Tier | What you show | What the client must approve |
|---|---|---|
| 1. Named case study | Client name, visuals, results | Everything, in writing |
| 2. Anonymous case study | Industry, scope, your role, de-identified visuals and metrics | The metrics and any recreated visuals |
| 3. Method only | Your process, tools and decisions, with no product detail | Usually a short confirmation |
| 4. Private walkthrough | Live discussion in an interview, nothing published | Nothing, provided you disclose no protected detail |
Send the draft with the request. A client reviewing three paragraphs and two redacted images will answer faster than one reviewing a vague promise. Keep the approval email: it is the evidence that your portfolio entry was authorized.
De-identify the project
When consent is unavailable or unnecessary because the content is not confidential, the standard approach is de-identification. A Forbes Communications Council article recommends removing company names, locations and proprietary assets and structuring the story around problem, insight and outcome.
A practical sweep covers four categories:
- Identity: company name, product name, team names, customer names, office locations.
- Visual identity: logos, brand colors, distinctive typography, screenshots with recognizable layouts.
- Data: internal dashboards, research data, non-public experiments, exact revenue or user counts.
- Timing: unreleased features, roadmap references, launch details that have not been announced.
A coaching resource on this topic advises you to remove company names, logos, brand colors and identifiable visual elements and avoid internal dashboards and non-public experiments. For visuals, it suggests blur effects, redactions or recreated mockups that omit proprietary brands and data.
Note the order of preference. Recreated mockups beat blurred screenshots, because a blur can be reversed or can still reveal layout and structure the client considers sensitive. If the interface itself is the secret, do not show an interface. Show the wireframe logic, the decision tree or a generic stand-in that makes the same point.
Generalize, but do not hollow out
Over-redaction produces a portfolio nobody can evaluate. “A fintech company” is fine. “A company” tells the reader nothing. Keep the industry, the scale band (“a team of eight engineers”), your role, the constraints and the type of outcome. Replace exact figures with ranges or relative change only where the exact figure is itself protected, and only if the client’s contract allows even the relative number.
Show process and impact when you cannot show the work
The hardest part of an NDA portfolio is not hiding things. It is proving value with the artifact missing. Designers and developers at a studio that has published its own guidance put it simply: focus on process rather than product, explaining your approach to problem-solving, research and handling feedback, with the scope, role, goals and outcomes described without the client’s assets.
A reviewer evaluating you for a senior role wants to see judgment. These elements carry it without a single protected pixel:
- The problem statement. What was failing, for whom, and how was that known?
- Constraints. Time, legacy systems, regulatory limits, headcount, competing stakeholder demands.
- Options considered. Two or three alternatives you rejected, with the reason.
- Your decisions. Where you overruled a default, and what happened.
- Outcome in the form you may share. Direction and magnitude of change, time saved, error rates reduced, expressed as ranges if exact numbers are restricted.
- What you would do differently. This signals maturity more than any screenshot.
For engineers, this often means describing architecture patterns, trade-offs and failure modes at a conceptual level. If you prepare for senior technical interviews, system design interview preparation rests on the same skill: explaining a design’s trade-offs without leaning on a proprietary codebase. For a deeper look at how hiring teams read engineering work, see our guide to developer portfolio examples that get interviews, and for design roles, evidence-backed UX portfolio examples.
Build a parallel body of public work
When a project must remain entirely confidential, the answer is to broaden the evidence base. The IEEE Computer Society recommends that professionals maintain an inventory of off-hours, non-confidential work such as personal projects or open-source contributions, which also documents independent development. A public repository, a published teardown of a public product or a self-initiated redesign gives reviewers something inspectable. Our article on building a live demo portfolio recruiters trust covers how to make that kind of work credible.
Keep the boundary clean. Personal projects built on your own time with your own resources and no confidential inputs are far easier to defend than ones that echo an employer’s unreleased product. If a side project resembles your day job, review your employment agreement’s invention-assignment and confidentiality terms first.
Share privately when public is not possible
Not every credential needs a public page. A personal-blog source on presenting design work under NDA lists anonymizing details, focusing on methods and contributions, and sharing in interviews or on a password-protected site as workable strategies. Note that password protection is a distribution control, not a legal permission. If the material is confidential, a password does not make disclosure authorized. Use it for content that is already cleared and that you want to limit to serious reviewers.
Before sending anything to a recruiter, run a short pre-send check on access, expiry and what each file reveals. Our secure portfolio sharing checklist covers five of those checks in detail.
Know the risks, and the limits of an NDA
The downside of an unauthorized disclosure is concrete. Practical guidance lists a warning, a demand letter, loss of the client or legal action as possible results, and advises consulting a qualified attorney about a specific NDA or dispute. For a contract you have already signed, that is an employment or contracts attorney licensed in your state.
The law also sets limits on how far confidentiality can reach. Three points a US reader should know:
- Trade secrets require reasonable secrecy efforts. The USPTO states that trade secret owners must make reasonable efforts to maintain secrecy, which is why companies write broad NDAs and enforce them.
- Overbroad agreements can be challenged. According to the American Bar Association’s newsletter, courts may treat overly broad confidentiality agreements as de facto non-compete agreements if they effectively keep a person from working in their industry, which can be voided under certain state policies.
- Severance confidentiality has been restricted. In the 2023 McLaren Macomb decision, the NLRB held that offering severance agreements with overly broad confidentiality provisions is an unfair labor practice, because such clauses chill employees’ Section 7 rights.
None of this entitles you to publish a former employer’s confidential material. It means that a restriction’s reach is a legal question, and an attorney can tell you whether a particular clause is enforceable in your state.
Our perspective: treat evidence as queryable, not displayed
We built Alloquy around an observation about NDA work: the portfolio’s job is to answer a recruiter’s questions credibly, and a gallery of screenshots is only one way to do that. A static page forces a binary choice between showing the artifact and saying nothing. An interactive profile permits a third option: attach the evidence you are entitled to share, link it to each claim, and let a recruiter ask targeted questions about role, decisions and outcomes.
Our approach is designed around that idea. You connect documents from Google Drive or add evidence manually, and the AI assistant answers recruiter questions grounded in those materials rather than in unsupported claims. For an NDA-constrained professional, the implication is practical. You curate what goes into the evidence set, so only cleared, de-identified material becomes answerable. The recruiter gets specific, contextual replies about your process and impact, and you keep control over the boundary.
We also think the generated materials matter. Tailored resumes and cover letters that trace back to your own linked source documents are less likely to drift into claims you cannot support, which matters when every sentence about a confidential project should survive scrutiny. The discipline is the same one this article recommends: write what you can substantiate, from material you are permitted to use.
— Alloquy Team
Build the NDA-safe profile in Alloquy
If you want a profile that answers recruiter questions from cleared evidence, you can start with the free profile on Alloquy and add only the de-identified case studies, public work and approved documents you choose. Plan details are on the pricing page.
Related reading on structuring a profile: custom portfolio sections that make recruiters notice and a no-code portfolio that cites its sources.
A pre-publication checklist
Run every NDA-related entry through these questions before it goes live:
- Have I read the confidentiality, publicity and IP clauses of the exact agreement?
- Is the client’s name, or the existence of the engagement, protected?
- Do I have written consent for any asset that is not clearly public?
- Have I removed logos, brand colors, internal dashboards and unreleased details?
- Could a reader identify the client from the combination of industry, scale and timeline?
- Does each outcome claim come from a number or fact I am allowed to state?
- Is there a private channel, such as an interview walkthrough, for details that cannot be public?
- Have I kept the approval email or contract excerpt on file?
Item five is the one most often missed. De-identification fails when individually harmless details combine to point to one company. If a small industry, a distinctive feature and a launch window together make the client guessable, generalize one of them further.
FAQ
Can I put a project I did under NDA in my portfolio?
Sometimes. It depends on the agreement: some NDAs allow portfolio display, others prevent it, and many allow it with written consent. Read the confidentiality and publicity clauses, ask the client in writing if the text is unclear, and show only what you are cleared to show.
Can I list the client’s name?
Only if the contract does not protect it. Some NDAs cover the client’s name and the fact of the engagement, while many do not. When in doubt, describe the client by industry and size and ask for permission to name them.
How do I show impact without revealing numbers?
Use the form of the result that is not restricted: direction of change, a range, a time frame or a qualitative outcome. Anchor it in your decisions and process, and confirm with the client whether even relative figures are permitted.
What if my NDA seems unreasonably broad?
Treat it as a legal question rather than a portfolio question. Courts can treat overly broad confidentiality agreements as de facto non-competes in some circumstances, and the outcome varies by state. A qualified employment or contracts attorney can review the specific wording.
Is a password-protected portfolio safe for confidential work?
Not by itself. A password limits who can view the page, but it does not authorize disclosure of material your NDA protects. Use it for cleared content, and keep truly restricted details for private conversation.
Sources
- Can I add my entries from an NDA-protected project to my portfolio (crowdspring help)
- Portfolio rights for confidential projects (Rocket Lawyer)
- How to Show Confidential Client Work in Your Portfolio (Walllet)
- Can you show NDA protected work in your portfolio? (freelancermap)
- Does an employment NDA prevent me from listing specific projects (TermScore)
- Three Things to Know Before You Sign an NDA (IEEE Computer Society)
- Best Practices for Negotiating and Entering into Nondisclosure Agreements (American Bar Association)
- Getting permission to show AI work publicly (Versely)
- Six Steps To Telling A Powerful Success Story With An NDA in Place (Forbes)
- Signed an NDA? How to Still Showcase Your Work in a Portfolio
- How to Create a Portfolio When Your Work is Restricted by NDAs (Devonshire)
- Presenting Confidential Design Work Under NDA
- Trade Secret Intellectual Property Toolkit (USPTO)
- NLRB: Non-Disparagement, Confidentiality Provisions and Activity Rights (American Bar Association)
- System Design Interview Prep: Mid-Level vs Senior (MeetAssist)