Can You Use Work From Your Job in a Portfolio Safely?
Can You Use Work From Your Job in a Portfolio Safely?
Career portfolios and work samplesCreateCV Editorial TeamAug 19, 2026قراءة 7 دقيقة
الصورة الرئيسية
Wanting to show professional work in a portfolio is reasonable: recruiters and hiring managers often need evidence of what you can do. The difficult question is not only whether you created the work. It is whether you have permission to publish it, whether the work belongs to your employer, and whether it contains confidential information.
A safe approach is to separate your contribution from the employer’s files and information. You can often explain your skills, decisions, process, and results without uploading source code, customer data, internal dashboards, pricing, credentials, or unreleased product details. This guide gives you a practical green, yellow, and red framework for deciding what to show and what to replace.
Before you write a case study, review your employment agreement, confidentiality policies, and any instructions about company materials. The guidance here is practical, not legal advice. If the answer is unclear, ask the employer for written permission or obtain advice appropriate to your situation.
The key distinction: skills are not company secrets
The U.S. Department of Justice describes trade-secret protection as concerning information with economic value because it is not generally known and because the owner has taken reasonable measures to keep it secret. It also distinguishes protected information from an employee’s general knowledge, skills, and experience. That gives you a useful line for portfolio writing: describe what you learned and how you work, but do not disclose information that the company treats as secret.
For example, a product designer may be able to describe a user-research method, a prototyping approach, or a general accessibility consideration learned at work. That does not automatically mean the designer can publish unreleased screens, research transcripts, customer identities, or the product roadmap. A developer may explain an architectural decision or testing method without posting proprietary source code. An analyst may describe how they defined a metric without sharing the internal dashboard or underlying customer-level data.
This distinction is supported by the . It is not a blanket permission to publish work. It is a way to ask whether your proposed portfolio page demonstrates your transferable capability or reveals the employer’s protected information.
Classify each potential work sample before you upload, attach, or link to it. The categories below turn broad confidentiality principles into a practical screening tool. If an item could fit more than one category, use the more cautious category until you have permission or clarification.
A practical risk framework for portfolio materials
Category
Typical examples
What to do
Green
Public work; material already approved for public release; independently created samples
Confirm that it is genuinely public or independently created, then identify your contribution accurately.
Yellow
Employer work that may be owned by the company; work covered by an agreement; material that could be shared only after review
Read the agreement and request written approval. Consider an employer-approved redaction or anonymized version.
The red category includes obvious warning signs, but confidential information is not always marked with a large “do not share” label. The USPTO identifies practical signals such as restricted access, confidentiality agreements, confidentiality markings, employee training, controlled digital access, and instructions to return or destroy materials when employment ends. Treat those signals as reasons to pause rather than as details to work around.
If you answer yes to any of these questions, do not assume that removing a company logo makes the material safe. Ask whether the underlying information remains identifiable or commercially sensitive. The USPTO Trade Secret Intellectual Property Toolkit is the relevant source for these confidentiality signals and safeguards.
Remember that creating the work does not settle ownership
A common assumption is: “I made it, so I can show it.” That assumption can be unsafe. Under the U.S. Copyright Office’s work-made-for-hire guidance, a work created by an employee within the scope of employment may be owned by the employer, which is treated as the author for that work. Ownership and permission to display are related questions, but they are not the same question.
This matters across roles. A marketer may have written campaign copy, a consultant may have built a client presentation, and a developer may have written an application. Their work may demonstrate real ability, but the employer or client may control the artifact and its publication. Check the agreement that governs the work before treating a job-created file as a personal asset. The U.S. Copyright Office’s work-made-for-hire guidance explains the employer-ownership principle.
You should also distinguish work created within employment from a genuinely independent project. An independently created sample still needs to avoid copying confidential information, using restricted assets, or implying that an employer approved it. Label personal reconstructions honestly so a reviewer understands what is original, what is fictional, and what reflects your professional experience.
Written approval is the clearest route when you want to show an employer-owned artifact. Be specific about the audience, format, access level, redactions, and duration. A vague request to “use this in my portfolio” may leave important details unresolved.
You can adapt this short message: “Hi [name], I would like to include a short case study about my contribution to [project] in a private portfolio shared with prospective employers. I would show [specific screens, diagrams, or results], remove [customer, pricing, and internal details], and avoid posting source files. May I use this version? Please let me know any required wording, redactions, or access restrictions.” Save the approval with the final version it covers.
2. Use an approved redacted or anonymized version
Redaction is more than covering a logo. Remove or replace names, contact details, account identifiers, customer records, credentials, unreleased features, pricing, and other details that could identify protected information. If the employer reviews the result, follow its requested changes and keep the approved copy separate from the original.
An anonymized case study can focus on the challenge, your role, the decisions you made, and an outcome expressed at a level the employer approves. For instance, instead of showing an internal dashboard, you might describe the metric definition, the analysis workflow, and an approved high-level result. Do not invent a number or present an estimate as an actual company result.
3. Recreate the approach with fictional material
When the original file is too sensitive, build a new sample that demonstrates the same type of thinking. Use fictional data, a different visual design, and a clearly stated label such as “Personal reconstruction using fictional data; not the employer’s original work.” Do not copy proprietary source code, internal text, customer records, or unreleased designs into the reconstruction.
A personal reconstruction works best when it explains the transferable method. A data analyst could create a small fictional dataset and show how they would choose metrics and communicate a finding. A developer could build a small independent feature that demonstrates testing and architecture. A designer could create a new interface for a fictional brief. The point is to show how you solve a problem, not to disguise an employer file as personal work.
4. Write a contribution-only case study
You can often prove value without attaching the artifact. Structure the page around what you did and learned, while leaving out confidential inputs. This approach is especially useful when a project is impressive but every deliverable is owned by an employer or client.
Context: describe the industry or general problem without naming restricted customers, products, or internal plans.
Your role: state your responsibilities and collaboration clearly. Do not claim ownership of the whole team’s work.
Decision: explain the options you considered and the principle or constraint that shaped your choice.
Method: describe your process at a transferable level, such as research, testing, prioritization, analysis, or implementation.
Outcome: include only results you are allowed to share, and identify whether they are exact, approved, or qualitative.
Evidence: link to a public release, approved sample, personal reconstruction, or no artifact if none can be shared.
This format also helps you avoid a portfolio full of unexplained screenshots. If you need examples of how application materials can present evidence of your work, compare the structure of resume examples and cover letter examples, then adapt the evidence to your field and confidentiality limits.
A final decision process before you share anything
Run each proposed sample through the following sequence. It is designed to stop a rushed application from turning into an avoidable disclosure.
Identify the owner: is the material yours, an employer’s, a client’s, or unclear?
Check the agreement: look for ownership, confidentiality, portfolio, publication, and return-or-destroy terms.
Screen the content: remove anything that could reveal a secret, restricted identity, credential, internal metric, pricing detail, or unreleased information.
Choose the least risky proof: public work, written permission, approved redaction, fictional reconstruction, or contribution-only explanation.
Label accurately: distinguish employer work, approved work, and personal work. Never imply that a reconstruction is the original artifact.
Keep an evidence trail: retain the permission, approved version, and any restrictions that apply to the sample.
Recheck the audience: a private link shared with a hiring manager is still a disclosure, so apply the same care as you would to a public page.
If you cannot obtain permission and cannot create a safe substitute, leave the original out. A concise explanation of your role, method, and approved outcome is stronger than a risky screenshot. Your portfolio’s purpose is to help a reviewer understand your capability, not to reproduce an employer’s information.
For more guidance on presenting career evidence, you can also review CreateCV.io’s portfolio and career resources. Build each sample around honest contribution, careful labeling, and the minimum information needed to demonstrate your work.