PORTFOLIO & EVIDENCE
How to use past work in a portfolio without sharing confidential information
A strong portfolio shows your judgement and contribution. It does not require you to copy a former employer's files, client records, internal metrics or source code into a new hiring process.

Separate your capability from the original files
Start with the outcome you can honestly explain: the problem, your role, the constraints, the decisions you made and the result you observed. Those points can often be described without attaching a live dashboard, customer list, proprietary deck or internal repository.
Check the agreements and policies that applied to the work. Confidentiality clauses, NDAs, client terms and intellectual-property rules differ by role and jurisdiction. If you are unsure whether a specific item may be shared, treat it as restricted until you have permission or appropriate advice.
Build a safe case-study version
Replace identifiable client names, private data, non-public pricing, internal dates and exact commercial metrics with approved or high-level descriptions. A case study can say that you improved a process or supported a launch without disclosing the material a competitor could use.
Use recreated visuals, synthetic data or a personal demonstration project when the original artifact cannot be shown. Label a recreation clearly. Do not present a mock-up as a live company document or imply access to information you are not entitled to share.
Keep source material out of personal tools
Do not forward former-employer files to personal email, upload them to a public portfolio platform or paste them into an AI tool merely to create an application sample. Screenshots can expose names, account numbers, system URLs, code, comments or hidden metadata even when the main content looks harmless.
The World Intellectual Property Organization notes that confidentiality duties and trade-secret protections can continue beyond the end of employment, subject to the applicable contract and law. Your general skills and experience remain valuable, but copying a protected artifact is a different risk.
Explain boundaries confidently in the interview
You can say that a past example is confidential and then walk through your individual contribution, decision process and measurable lesson at an appropriate level. A thoughtful boundary is usually more credible than an impressive-looking file that should not have left a previous workplace.
If a recruiter asks for a live client deliverable, source code or internal report, offer an anonymised case study, a permitted public example, a skills discussion or a new short exercise instead. Keep the request and your response in writing when the scope is unclear.
Use this portfolio-safety check
- Read any confidentiality, NDA and intellectual-property terms that apply to the sample.
- Describe your own role, decisions and outcome without copying a restricted file.
- Remove client names, personal data, internal systems, source code and non-public metrics.
- Use a clearly labelled recreation or synthetic demonstration when needed.
- Check screenshots and exported files for hidden comments, metadata and account details.
- Do not upload former-employer material to personal storage or unapproved AI tools.
- Offer a safe alternative when a recruiter requests material you cannot share.
Build clear portfolio evidence from your real experience →Check ownership and confidentiality in a take-home task →Browse current checked roles →
New roles first
Use the board for live opportunities.
Telegram is the fastest route for new RemoRoute role updates. The site is where we keep the context and practical guidance.
Join Telegram ↗
Join Telegram ↗