Adding a portfolio link to a resume makes sense when the link provides evidence that the resume alone cannot show as clearly. This is especially useful in fields where projects, work samples, code, research, writing, design, engineering, analysis, or other deliverables help demonstrate how a candidate applied their skills. Harvard's Mignone Center for Career Success highlights portfolios particularly for creative, technical, and engineering fields, while Berkeley Career Engagement presents projects and portfolios as ways to communicate skills and experience.
The key is not to use a portfolio as a dumping ground for links. To work as evidence, each project should let the person reviewing the application understand the problem, your role, the decision or action you took, the artifact that can be reviewed, and the result or learning produced by the work. When authorship, context, or outcome is unclear, the link may add little to the resume.
When a portfolio link tends to help
- When the job asks for samples or a portfolio. In that situation, the link is no longer merely supplemental and becomes part of the expected application materials. Always follow the specific application instructions.
- When the work produces something that can be reviewed. This may be an interface, code repository, report, article, presentation, analysis, technical drawing, research project, campaign, documentation, prototype, photograph, video, or another deliverable relevant to the target role.
- When the resume needs to prove project experience. A bullet can summarize an accomplishment; the portfolio can show the project logic, individual contribution, and available evidence.
- When formal experience is still limited. Academic, personal, volunteer, or research projects can be used if they are relevant and labeled honestly. Berkeley advises candidates to explain their own role, impact, and results in projects and research.
- When the material reinforces a skill required by the role. A shorter, targeted portfolio is generally more useful than a large collection with no clear connection to the opportunity.
When it is better to leave the link out
A portfolio is not mandatory in every career. Leaving the link out may be better when you do not yet have relevant material, when the projects do not represent the type of work required by the role, or when the site is outdated, broken, requires a login, or makes it difficult to understand what is yours. Do not publish internal materials, third-party personal data, documents restricted by contract, or content you are not authorized to expose.
Arizona State University recommends showcasing non-confidential work samples and projects. UMBC's guidance for writing samples also emphasizes protecting confidential information by removing or changing details that identify people or organizations when needed.
Where to place the link on the resume
If the portfolio is relevant to the application, make it easy to find. The link can appear in the contact area with a clear label such as “Portfolio,” “Projects,” “GitHub,” or another description of the destination, and it can also be associated with a specific project in the body of the resume. Berkeley notes that links to a personal website or other professional profiles may be included when appropriate.
Avoid long addresses that are difficult to interpret. Before sending the resume, open the link on another device or browser, confirm that the page is public when it should be public, and make sure the main content can be found without requiring the recruiter to hunt for it.
What each case study should make clear
| Case element | What it should answer | What to show |
|---|---|---|
| Problem or context | What situation needed to be addressed? | Goal, audience, constraint, or project setting. |
| Your role | What was your responsibility? | The scope of your work, including on team projects. |
| Decision or action | What did you do and why? | Method, choices, relevant steps, tools, or criteria used. |
| Artifact | What evidence of the work can be reviewed? | Image, excerpt, repository, document, prototype, chart, video, or other allowed material. |
| Result | What changed after the work? | A metric when available, completed deliverable, observed effect, validation, or relevant learning. |
| Public limit | What can be shown safely? | An anonymized version, authorized excerpt, or explanation without confidential content. |
A short template for presenting a project
A case study does not need to begin as a long report. Use a structure that quickly connects the project to the skill promised by the resume. A concise template is:
- Problem: [the situation or need that existed].
- Role: [your specific responsibility in the project].
- Decision: [what you chose to do and the main reason].
- Artifact: [what the reader can open, see, or review].
- Result: [change, deliverable, metric, validation, or learning].
- What can be shown: [public, anonymized, partial, or authorized version].
This format keeps the portfolio from depending only on the visual appeal of the final output. It also helps separate participation from authorship: the reader can understand what belonged to the team and what was your contribution.
How to present team projects
Collaborative projects can be strong examples as long as you do not claim other people's work as your own. State that the project was collaborative and describe your part concretely: research you conducted, a module you implemented, an analysis you performed, a decision you advocated for, text you wrote, a prototype you produced, or a process you coordinated. If an artifact was created by several people, explain how responsibilities were divided.
UMBC considers co-authored samples acceptable in appropriate contexts and recommends making the collaborative nature clear. The same logic works well in a project portfolio: transparency about authorship produces stronger evidence than an impressive piece with no explanation of contribution.
How to handle confidential work
Do not turn a portfolio into a risk for a client, employer, or colleague. If your best project contains restricted information, alternatives include removing names and identifying data, recreating an example with fictional data, showing only steps or decisions that can be public, describing the process without attaching the original document, or obtaining formal permission to publish a specific version.
If none of that is allowed, use the resume to describe the accomplishment at a safe level and choose a different project as the sample. Having no public artifact is better than improperly exposing confidential material.
Portfolio options when formal experience is limited
A project does not have to come from a paid job to demonstrate skill. Academic work, research, volunteering, personal projects, and independent exercises can work when they are relevant to the role and presented with enough context. Harvard recommends small projects or work samples as a way to demonstrate initiative in applications, and Berkeley includes projects and research among experiences that can provide evidence of skills.
The important point is to label the source accurately. A personal project should be called personal; coursework should be identified as academic; a collaboration should be described as collaborative. The strength of the evidence comes from what was done and explained, not from presenting a project as professional employment when it was not.
Checklist before sending the resume
- Does the project help prove an important skill or requirement for the role?
- Is the problem and your contribution easy to understand?
- Is the result described without exaggeration, with metrics only when they are real and verifiable?
- Does the link open and lead directly to the relevant content?
- Can the material be published without violating confidentiality, contracts, privacy, or authorship?
- Do team projects clearly distinguish collective work from individual contribution?
- Is the portfolio current and free of pieces that distract from the type of work you are targeting?
A practical rule for deciding
The link earns space on the resume when it adds relevant evidence, makes your contribution understandable, and can be shown ethically and safely. If the portfolio only repeats the resume, collects files without context, or forces the reader to infer what you did, improve the case studies first. The goal is not to prove that you own a portfolio; it is to use the portfolio to prove applied experience.
Sources and references
- Harvard FAS, Mignone Center for Career Success: Portfolio Tools
- UC Berkeley Career Engagement: Sample Resumes, Projects and Portfolio Experience
- Arizona State University Engineering Career Center: Portfolios
- UMBC Career Center: Selecting and Submitting Writing Samples
- UC Berkeley Career Engagement: The CV, Part 2, Elements
- Harvard FAS, Mignone Center for Career Success: How to Get an Internship in 2026
