Presenting Project Evidence Without Exposing Customer Data
Updated · Tech checked
You can prove delivery without leaking: anonymize names and numbers where needed, show log shapes not values, use synthetic replays, and state explicitly what was changed and why - a redaction discipline hiring managers trust, and NDAs require.
The short answer
Interviewers and portfolio readers don't need your customer's name - they need the shape of the work. Anonymize identifiers, aggregate or scale numbers, replace real payloads with synthetic ones that keep the structure, and say you did so. Undisclosed sanitization is worse than either extreme.
The redaction rules
| Original | Publish as | Never as |
|---|---|---|
| Customer name | "a European logistics company" | initials, logo, "you know who" |
| Revenue-impacting numbers | scaled: "~€1.2M ARR affected" → "eight-figure ARR" or permission-first | invented precision |
| Real log lines | shape-preserved synthetic: same fields, fake values | the actual line "sanitized" by eye |
| Schemas with PII columns | same shape, renamed columns (email → contact) | DDL dumps |
| Internal URLs/hosts | api.internal | anything resolvable |
The disclosure line
Every sanitized artifact gets one line: "Details anonymized per NDA; structure preserved." This converts sanitization from suspicion into professionalism.
What you must never publish
- Personal data (emails, names in logs, IPs of real users).
- Credentials, tokens, internal hostnames - even "expired" ones.
- Security-findings specifics before the customer has disclosed/fixed.
- Anything your NDA doesn't clearly permit - when unsure, ask; the ask itself signals maturity.
The synthetic replay trick
For demos and screenshots: record the structure of a real incident (fields, sequence, timing), then generate a synthetic replay with fake data. You get authentic-looking evidence with zero leakage - and a reusable demo asset.
In interviews
Offer the anonymized artifact set from the deployment documentation guide; state the anonymization upfront. The honesty + structure combo is precisely what the "communication" dimension of hiring scorecards rewards.
Continue: Portfolio guide · Deployment docs