The NDA-Safe Portfolio: What to Show Instead

You have shipped a payment reconciliation engine for a Fortune 500 bank, rebuilt a hospital system's patient intake pipeline, and cut a retailer's cloud spend by six figures. None of it is on your resume in any detail. None of it can be. Every client made you sign an NDA, and most of those agreements outlive the contract by years.

This is the quiet tax every consultant pays. Full-time employees at a single company can point to a shipped product. You have a stack of confidentiality agreements and a resume full of vague verbs like 'led' and 'optimized' with no artifact behind them.

The good news: hiring managers and technical screeners already know this about consultants. They are not expecting your GitHub to be full of client repos. What they are expecting is evidence that you can think, build, and communicate at the level your resume claims. You can produce that evidence without violating a single confidentiality clause, if you build it deliberately.

1. Know exactly what your NDA actually restricts

Before you build anything, reread the agreement. Most standard consulting and staffing NDAs restrict three things:

• Client name, brand, and any identifying business details
• Proprietary source code, architecture diagrams, and data
• Confidential business metrics tied to that specific client

What they almost never restrict is your own general knowledge, skills, and the technical patterns you used. You cannot say 'I built X for Acme Bank.' You can say 'I designed a real-time reconciliation pipeline for a large financial services client using Kafka and Postgres, processing roughly 40,000 transactions per hour.' The pattern is the asset. The client name is the liability.

2. Write sanitized case studies, not resume bullets

A one-paragraph resume bullet cannot carry technical weight. A one-page sanitized case study can. Structure each one the same way:

1. Situation - industry and problem, no company name ('a mid-size logistics provider needed to cut order-processing latency')
2. Constraint - what made it hard (legacy system, compliance requirement, tight timeline)
3. Your role - what you specifically owned, not the team
4. Approach - architecture and tools, described generically enough to avoid IP disclosure
5. Outcome - a defensible number: latency reduced by 60 percent, uptime moved from 99.1 to 99.9 percent, deployment time cut from four hours to twenty minutes

Build three to five of these covering different skill areas. Keep them to half a page each. Bring them to every technical interview as a leave-behind or a shared screen during the call.

3. Build the parts of your portfolio that were never under NDA

Some of your best evidence has nothing to do with client work at all. This is where an IT portfolio with no code from a specific employer becomes your strongest asset.

None of these require you to touch client IP. All of them are things a vendor screener or hiring manager can look up in under two minutes, which matters more than most consultants realize.

4. Open source is the single highest-leverage option

If you do one thing from this list tonight, make it this. A public GitHub profile with consistent, real commits is the closest thing to a live work sample you can offer. It does not need to be a massive project.

• Fix a documentation bug or a small issue in a library you already use at work
• Build a CLI tool that solves a problem you have hit on three different contracts
• Contribute a test suite to a project that clearly needs one

Recruiters and technical leads who review candidates weekly will check your GitHub before they check your resume bullets. A quiet but consistent commit history speaks louder than a paragraph of claimed accomplishments.

5. Talks and writing turn expertise into something you can cite by name

A 20-minute talk at a local meetup, a user group, or even an internal client lunch-and-learn (cleared for public sharing, unlike the underlying project) becomes a permanent, linkable asset. Record it if you can. Post the slides on SlideShare or your own site.

Same with writing. A 700-word post on how you approach a specific architectural tradeoff, written in your own words with no client detail, does two things: it demonstrates depth, and it gives you something concrete to link in your LinkedIn headline and resume header.

6. What to actually put on the resume and LinkedIn

Skip the vague verbs. Use this pattern instead: technology stack plus quantified outcome plus industry, with no client name.

• 'Reduced API response time by 45 percent for a healthcare claims platform using caching and query optimization (Java, Redis, PostgreSQL)'
• 'Migrated a 200-server on-prem environment to AWS for a manufacturing client, cutting infrastructure cost by roughly 30 percent'

Add a single line under each role: 'Portfolio and sanitized case studies available on request.' Then actually have them ready as a PDF you can send within the hour, not something you promise and never deliver.

A five-item checklist before your next interview

• Three sanitized case studies, one page each, covering different skills
• An active GitHub profile with at least one recent, real commit
• One piece of public writing or a recorded talk you can link
• Resume bullets rewritten with stack, metric, and industry, no client names
• A one-line NDA disclaimer ready to say out loud if asked directly about a client

Building this out takes an evening, not a month. Start with the resume rewrite tonight, then pick one open-source contribution to make this week.

If you want a second pair of eyes on how your portfolio reads to a hiring manager or a vendor screener, the team at Josh Pros LLC reviews consultant resumes and portfolios regularly as part of matching people to contract roles. Reach out at contact@joshpros.com or visit https://joshpros.com.

#ConsultantPortfolio #NDACompliance #ITConsulting #TechContractors #JobSearchTips #OpenSourceContributions #ResumeWriting #TechCareers #ContractWork #VendorScreens #TechnicalInterviews #CareerAdvice

Back to all insights