A Portfolio Link Should Earn Its Place on Your Resume

Include a portfolio link on your resume only when it leads to accessible work samples that fit the job and you can explain honestly. Choose a small set of examples that show relevant skills, state your contribution, and check every link before you send the PDF. If permission or confidentiality prevents sharing, leave the link off and describe the work safely instead.

A portfolio link is not a decoration. It is a promise: click here and you will find evidence relevant to the role. Keep that promise. A strong link lets a reader inspect work that a resume can only describe. A weak one leads to a broken page, a private folder, unrelated projects, or material you cannot discuss.

The best default is selective. Put one clear link in the contact area when the samples strengthen your application. Do not add a portfolio just because you have a website, a social profile, or a collection of old projects. A link has to earn the space it takes and the attention it asks for.

Should you include a portfolio link on your resume?

Include one when the job involves work that can be shown, the samples are relevant, and the intended reader can open them without avoidable friction. Leave it off when the material is unrelated, inaccessible, confidential, or likely to raise questions you cannot answer. CareerOneStop recommends including a portfolio website link on a resume and checking links and overall appearance; that advice is most useful when the portfolio actually supports the application, not as a rule to link every personal site (CareerOneStop’s portfolio guidance).

A portfolio can be a website, a public profile, a carefully prepared PDF, or a small set of links to specific work. It need not be elaborate. The question is not whether you have a portfolio in the formal sense. It is whether a reader can use the link to verify or better understand a claim on your resume.

Use this quick test before adding the link:

1. Relevance: Do the samples show skills the target role needs?
2. Ownership: Can you explain what you personally did, and distinguish it from team contributions?
3. Access: Does the link open in a private browser window without requiring a special account or permission?
4. Safety: Are you allowed to share the work, and have you removed private or sensitive information?
5. Readiness: Would you be comfortable discussing every linked sample in an interview?

If any answer is no, fix the problem or omit the link. Do not ask a recruiter to troubleshoot your permissions or guess which project matters. A link that fails these checks can create more doubt than a missing link.

A portfolio is especially useful in fields where the work itself is part of the job: design, writing, photography, research, teaching, communications, software, and some operational roles. But occupation alone does not settle the question. A designer with no shareable work may have no useful link. An administrative professional with a polished, privacy-safe example of a process guide may have one. The work sample must fit the role and be safe to share.

CareerOneStop describes a portfolio as a collection of work samples that shows skills and qualifications and suggests explaining the project, the employer or client where appropriate, your contribution, and the results (CareerOneStop). The practical lesson is simple: a link should lead to evidence with context, not a pile of files.

What should a hiring reader learn from the link?

A useful portfolio answers three questions quickly: What is this work? What did you do? Why does it matter for this role? A visitor should not need to infer your part from a team logo, a project title, or a polished screenshot.

Start with the job requirement you want to support. If the posting asks for clear customer communication, a short help article may be stronger evidence than a visually impressive poster. If it asks for data reporting, a readable dashboard or a sanitized sample report may help more than a list of software names. If it asks for classroom planning, a lesson outline with goals and activities may be more relevant than a generic teaching philosophy.

For each sample, provide a compact label and context. A useful description can include:

• The setting or project type, described without disclosing protected information.
• The problem or task, in plain language.
• Your role and the boundaries of your contribution.
• The method or skill the sample demonstrates.
• A result only when you can support it and are permitted to share it.

Do not inflate the sample with claims it cannot prove. A screenshot of a landing page can show layout decisions; it does not, by itself, prove that the page increased sales. A lesson plan can show planning; it does not prove student outcomes. A chart can show how you presented data; it does not establish that your analysis caused a business result.

If you have a measured result, explain its scope and source. If you do not, say what the artifact shows instead. “Designed a three-screen checkout flow for a class project” is more credible than “Revolutionized e-commerce conversion” when the project was not launched or evaluated.

The sample need not be a finished commercial product. Coursework, a personal project, a volunteer deliverable, or a mock assignment can be useful when labeled accurately. Context changes how a reader interprets it. A concept project is not client work. A group project is not an individual achievement. A draft is not a published deliverable. Clear labels protect both your credibility and the reader’s understanding.

How many work samples should you choose?

Choose the smallest set that proves the important points. For many applications, a few well-explained samples are easier to evaluate than a large archive. There is no universal count that suits every field, role, or career stage. Use enough to show range where range matters, but stop before the reader has to search for the best evidence.

A practical selection process is to begin with a longer candidate list, score each item against the job, then keep only the strongest examples. Three carefully chosen samples can make a clearer case than twenty unrelated ones. That is a working editorial rule, not a claim that a fixed number improves hiring outcomes.

Build a candidate list from different sources:

• Paid work you are permitted to show.
• Volunteer or community work you are permitted to show.
• Coursework or training exercises, labeled as such.
• Personal projects that demonstrate a relevant skill.
• Publicly available work you authored or contributed to.
• A redacted, reconstructed, or hypothetical sample when actual work cannot be shared.

Then remove duplicates. If three samples all show the same skill at the same level, keep the strongest one unless repetition demonstrates meaningful progression. If one sample is visually impressive but unrelated, it does not deserve a place merely because you like it.

A strong group of samples usually has a reason for every item. One might show craft, another problem-solving, and another communication with a particular audience. But do not force variety for its own sake. If the target role calls for a narrow specialty, depth in that specialty can be more persuasive than a collection designed to look broad.

Use this sample-selection matrix

The matrix below turns a vague question, “Is this good work?”, into a more useful one: “Is this the right evidence for this application?” Rate each candidate from 0 to 2: 0 means weak or absent, 1 means partial, and 2 means strong. Permission and access are gates, not points. A high score cannot make confidential work shareable.

Before scoring, answer two separate questions: Do I have permission to share this? and Can the intended reader open it? If either answer is no, the sample is not ready for the public portfolio. Seek approval, prepare a genuinely safe version, or leave it out.

Add the points for a rough comparison, not as a mechanical verdict. A total can help you spot a weak candidate, but it cannot decide whether a sample is ethical to publish or strategically wise to show. Compare items against one another. If a sample scores well on appearance but poorly on relevance, choose the more relevant sample. If two items show the same skill, prefer the one with clearer ownership and context.

A useful final question is: “Which sentence on my resume does this sample help the reader believe?” If you cannot name the sentence or skill, the sample may be interesting but unnecessary. It could belong on a personal site without belonging in this application’s portfolio.

Example: choosing between samples for a product design role

The following examples are hypothetical. They do not describe real candidates or outcomes.

Suppose a job asks for interaction design, accessibility awareness, and collaboration with engineers. A candidate has four possible items:

The class prototype may be the strongest safe sample, even though it is not commercial work. The private employer screens do not become acceptable because they match the role. The personal review can help if it clearly distinguishes observation from official testing and does not imply a relationship with the site owner.

Choose samples for the job, not for your whole identity

A portfolio link on a resume should support the application in front of you. Your full body of work can live elsewhere. Tailoring does not mean hiding your identity or pretending to have done different work. It means choosing which truthful evidence deserves the reader’s limited attention.

Read the job posting and mark the requirements that can be demonstrated through an artifact. Some requirements, such as schedule availability or a particular certification, are not best proved by a portfolio. Others, such as visual communication, writing, analytical explanation, or technical problem-solving, may be. Match sample types to the requirements rather than matching every keyword to an artifact.

Use this sequence:

1. Select two or three requirements that matter most to the role.
2. For each, write down what observable evidence would support it.
3. List work you can legally and safely share that contains that evidence.
4. Compare those items with the matrix.
5. Remove samples that repeat a stronger example or need too much explanation.
6. Check that the final set presents an honest picture of your level and experience.

Do not add an item just because it contains a popular tool or fashionable technique. The tool name matters less than what the sample shows you doing with it. A spreadsheet is not evidence of analytical skill if the reader cannot tell what question it addresses. A code repository is not automatically useful if setup instructions are missing and the relevant work is buried. A design file may need a short explanation of its constraints and your choices.

Also consider the job’s level. A student or career changer may use class, volunteer, or personal work to demonstrate potential, provided each item is labeled correctly. An experienced applicant may need to show recent, role-relevant work rather than a large archive of older accomplishments. The standard is not “professional work only.” The standard is “truthfully represented work that helps answer this employer’s question.”

CareerOneStop’s occupation examples range from photographs and recordings to reports, lesson plans, and articles, which underscores that a portfolio is not limited to visual design (CareerOneStop’s sample ideas). The right medium follows the work. A spreadsheet can be a sample. So can a lesson plan, a short audio clip, a research summary, or a carefully redacted process map.

What samples make sense in different fields?

A useful sample is an artifact a reader can inspect and relate to the job. The format changes by field, but the selection rule stays the same: show relevant work, identify your part, and avoid claims beyond what the artifact supports. These examples are hypothetical and illustrate choices, not real candidate histories.

Design and creative work

A designer can select a compact set that shows more than attractive final screens. Include context that explains the brief, audience, constraints, and your contribution. A case study might show a before-and-after decision, a few process steps, or one key design tradeoff. Do not publish a client’s unreleased campaign, private analytics, or brand materials without permission.

A candidate applying for a visual design role might link to a selected gallery of identity work and one clearly labeled student project. For a product interface role, a detailed interface case study may be more useful than a gallery of unrelated posters. If team members contributed, name the team context and your role. “I led the visual system” is different from “I designed the entire product.”

Keep the work easy to scan. A visitor should be able to understand the project without clicking through a maze of full-screen images. Provide captions or short descriptions for work whose purpose is not obvious. If an image is decorative, do not pretend it proves a measurable outcome.

Writing, editing, and communications

A writer can link to published articles, newsletters, reports, grant proposals, or other permitted work. CareerOneStop includes articles and several forms of written materials among possible portfolio samples (CareerOneStop). Choose pieces that match the format, audience, and subject matter of the target role.

A hypothetical applicant for a nonprofit communications role might select one public newsletter, one short web article, and one plain-language explainer. That mix can show different formats without presenting a whole archive. If an article was edited by others, explain your role when it affects how the sample should be read. If you wrote a piece under a team byline, do not imply sole authorship.

Check whether you retain permission to share unpublished or commissioned work. A public URL is not proof that you own every right to republish or redistribute it. When you cannot safely show the original, describe the type of work and your contribution without reproducing protected text.

Software and technical roles

For a developer, an accessible code repository or a documented technical project can be more useful than a homepage full of claims. Choose a project that a visitor can understand without a long setup. Include a concise readme, the purpose, your contribution, and known limitations. Where possible, offer a small demo or representative excerpt that does not expose credentials, private data, or proprietary code.

A hypothetical junior developer could link to a personal task-tracking application and a small open-source contribution. The project page should distinguish personal practice from production deployment. If a group built the application, describe which parts the candidate implemented. A repository full of abandoned experiments may be honest, but it can also obscure the work that best supports the application. Pin or feature the relevant items if the platform allows it.

Never put API keys, passwords, private data, or employer code in a public repository. Inspect the files and revision history before sharing. Removing a secret from the latest version may not remove it from the repository’s history. If you are unsure whether code is yours to publish, do not publish it until you have checked the applicable agreement or obtained permission.

Research, data, and analysis

A researcher or analyst can show a report, paper, poster, visualization, or reproducible project where sharing is permitted. State the question, your method, your role, and what the sample does and does not establish. If the work uses restricted data, do not upload the underlying data or a screenshot that reveals it.

A hypothetical data analyst might choose a public dataset project with a short written explanation, a clear visualization, and a link to code using non-sensitive data. The candidate should say that the project is an independent analysis if it was not done for an employer. If results are exploratory, call them exploratory. Do not turn a correlation into a causal claim or an illustrative chart into proof of business impact.

For team research, specify your contribution. “Contributed to a team study” is vague. “Cleaned the survey export and drafted the methods section” is clearer, if true. The sample should reinforce that description rather than silently imply sole responsibility for the whole publication.

Teaching, training, and facilitation

A teacher or trainer can show a lesson plan, activity, presentation excerpt, or training resource. Remove student names, images, grades, and identifying details unless you have clear authorization to share them. A sample should reveal how you structure a learning experience, not expose learners’ private work.

A hypothetical applicant for a training role might share a one-page session plan and a short slide excerpt. The plan can name the learning objective, sequence, and intended audience. It should not claim that participants achieved a particular result unless the applicant has valid evidence and permission to report it.

A recording can be useful where speaking or facilitation is central, but consider who appears or can be heard. Obtain consent where needed, and do not assume that an internal training recording is public simply because it exists online. A safe excerpt or written outline may be a better choice.

Operations, administration, and customer support

Some roles produce work that is not visually striking but can still be demonstrated. A privacy-safe checklist, process map, instruction sheet, anonymized report layout, or customer-response example may show organization and clarity. CareerOneStop lists office materials such as reports, newsletters, and spreadsheets among possible samples, though the exact artifact should fit the target role (CareerOneStop).

A hypothetical operations applicant might create a sample process map based on a generic scenario rather than upload an employer’s internal procedure. Label it as a representative or independently created example. If the original workflow belongs to an employer, do not reproduce its steps or internal terminology without authorization.

For customer support, avoid sharing real customer messages, account details, or private tickets. A fictionalized response can demonstrate tone and problem-solving only if clearly labeled as a sample scenario. Do not pass fiction off as a real customer interaction.

Photography, performance, and other media

Photographers, musicians, actors, and other performers can use images, audio, or video. CareerOneStop gives photographs and recordings as examples of portfolio material for several occupations (CareerOneStop). Select a short, relevant set rather than a long feed that mixes unrelated work.

Check the rights and consent involved. A photograph may include people who did not agree to public promotion. A recording may include music, a venue, or collaborators whose permissions matter. Identify whether a performance was live, edited, rehearsed, or recorded for a class when that context changes what the sample demonstrates.

A hypothetical candidate applying for event photography might lead with a small, coherent gallery that shows the kind of event requested. A candidate applying for studio portrait work should not make the reader sort through unrelated vacation images to find one relevant session. Curation is part of the evidence.

Where should the link appear on the resume?

Place the portfolio link with your contact details near the top, where a reader can find it without searching. CareerOneStop lists a portfolio or LinkedIn link among possible contact details, and Florida Gulf Coast University’s Career Development Services similarly recommends placing a portfolio link at the top with contact information (CareerOneStop, FGCU Career Development Services). Keep the label short and the destination clear.

Use a readable label such as “Portfolio: example.com/name” or “Selected work: example.com/name.” If the link text is clickable, keep the visible text recognizable enough that the destination is not a mystery when the document is printed. Avoid a vague label such as “Click here.” Avoid a long tracking URL or a URL that wraps across multiple lines if you can use a stable, clean address instead.

One portfolio link is usually enough. If the role calls for a distinct platform, you might include a second specific link, such as a code repository for a software role or a publication page for a writing role. But every additional link competes for attention. Add it only if it offers different, relevant evidence. Do not list every social account simply because each contains some work.

Make sure the resume’s link destination is consistent with the text. If you label a link “Selected writing,” it should open selected writing, not a general profile where the reader must hunt. A short landing page can route to a few samples, but it must make the right items obvious. Do not rely on a QR code as the only route. A reader reviewing a PDF on a laptop should be able to open the ordinary link.

If you use a QR code as an additional convenience in a printed portfolio, include a written URL as well and test both. A QR code on a resume can take up space and may not help in a digital application. It should never replace a readable link or contact information.

How do you make a portfolio link easy to open?

Test the exact link from the final resume, not just the portfolio while you are logged in. A page that works in your own browser may be private to your account. CareerOneStop advises proofreading a digital portfolio and checking links and appearance before sending it; FGCU also recommends testing links (CareerOneStop, FGCU Career Development Services). Turn that advice into a repeatable check.

1. Copy the link from the final PDF or exported document.
2. Open a private or incognito browser window where you are not signed in.
3. Paste the link and confirm that it reaches the intended page.
4. Open each featured sample and confirm that it loads and is readable.
5. Check that a viewer does not need to request access, install an unusual application, or guess a password.
6. Test the page on a phone-sized screen and on a desktop-sized screen.
7. Check spelling, captions, file names, and any contact route on the page.
8. Repeat the check after making changes to permissions or replacing files.

A password-protected portfolio is not automatically wrong. It is a poor default for an application when the reader has not been told how to obtain the password. If confidentiality requires a protected sample, state briefly that a sanitized example is available on request, but do not include a link that leads nowhere useful. Follow any application instructions about access and attachments.

Avoid forcing a download when a browser preview would work. If the portfolio is a PDF, give the file a descriptive name and make sure it opens with the intended pages. If it is a folder, make sure the viewer can identify the relevant file without scanning a cluttered directory. A clean landing page or a single organized PDF is often easier to review than a shared folder full of drafts.

The link should be stable enough to survive the application period. If you use a free hosting service, public profile, or file-sharing tool, check that its address does not expire or change when you move files. If you later reorganize your work, update the resume link and test it again. A stale but technically live page is still a poor destination.

How do you protect confidentiality, privacy, and permissions?

Do not publish material just because you created it or can access it. Work may contain an employer’s confidential information, a client’s private data, unpublished work, student records, or material covered by an agreement. When in doubt, leave the original out until you have checked permission. A relevant but unauthorized sample is not worth the risk.

Inspect both the visible page and the underlying files. Look for names, email addresses, phone numbers, account numbers, internal project labels, unreleased plans, comments, tracked changes, hidden spreadsheet tabs, document metadata, and screenshots that reveal more than the main content. Redacting one visible name may not remove the same information from a file’s properties or embedded data.

Use a safe alternative only if it is genuinely safe. Options include:

• Ask the organization or client for written permission to show a specific artifact.
• Create a redacted version and confirm that the removed information cannot be recovered from the file.
• Rebuild a representative example from scratch using generic or public information.
• Describe the project, your role, and the skills involved without displaying the protected artifact.
• Offer to discuss the work at a high level during an interview, within the limits of your obligations.

Do not label a reconstructed sample as the original. Say “representative process map created for this portfolio” or “sanitized example based on common workflow patterns” if that is accurate. Avoid a reconstruction so close to a proprietary project that it reproduces protected content. A made-up sample is acceptable as an illustration only when you label it as a sample scenario, not as a client deliverable or measured result.

For team work, privacy also includes fair credit. Name the team context and describe your actual contribution. Do not present another person’s work as your own, and do not assume that a public team artifact means every contributor may republish it elsewhere. If your contribution is hard to separate, explain the collaboration instead of claiming sole authorship.

What if you cannot share your work?

Omit the portfolio link when confidentiality, permissions, or the role makes samples inappropriate. Then describe the work at a safe, truthful level in the resume. This is the strongest exception to the default recommendation. A resume does not need a portfolio link to be complete, and a refusal to disclose protected work can be a sign of sound judgment rather than a gap.

Use a description that tells the reader what you did without exposing what you must protect. For example, a hypothetical operations candidate could write: “Mapped a multi-step internal intake process and drafted a staff guide; details are omitted to protect company procedures.” That sentence describes the work category and contribution without disclosing the actual workflow or claiming an unverified result.

A hypothetical analyst might say: “Prepared recurring reports from restricted customer data; can discuss methods and responsibilities without sharing records.” A hypothetical designer might describe the type of interface and constraints but omit screens, product names, and unreleased features. These examples are not real accomplishments. Adapt the structure only to work you actually performed.

When a safe sample exists, present it separately and label it clearly. A generic exercise can show your method, but it cannot prove that you did the confidential project exactly as described. You might say, “The public sample below demonstrates my approach to accessible form design; employer work is not shown.” That is more honest than implying the public exercise is a sanitized copy of the employer’s product.

You can also prepare a verbal explanation for an interview: the problem type, your responsibilities, constraints, decisions, and what you learned. Keep the explanation within your obligations. Do not reveal confidential details because someone asks. If the interviewer presses for protected information, explain the boundary and offer a public or generic example instead.

A weak substitute is a portfolio page filled with blank boxes and repeated notices that everything is confidential. If you cannot show anything useful, the link may not help. Leave it off and let the resume carry the evidence it can safely carry.

What makes a portfolio link weaken an otherwise good resume?

The most common mistake is treating the link as a harmless extra. It is not harmless when it sends the reader to irrelevant, stale, inaccessible, or misleading material. The link adds a task. The destination should repay that task quickly.

Watch for these failure modes:

• The generic homepage: The reader has to search through every project to find the relevant one.
• The social feed: Personal posts and unrelated work crowd out the samples that support the application.
• The broken or restricted page: A login wall, expired share link, or access request interrupts review.
• The oversized archive: Quantity makes it harder to see what you consider your best work.
• The unexplained team project: The reader cannot tell which part you completed.
• The inflated claim: The caption credits you with a result the sample cannot establish.
• The confidential artifact: The material exposes information you should protect.
• The misleading label: A class exercise or fictional scenario is presented like paid client work.
• The outdated sample: The work no longer represents your current skills, with no explanation of its relevance.
• The link that competes with your resume: Multiple unrelated URLs make the contact block noisy.

Fix the problem before sending, not after someone asks about it. If the link is useful only after a long explanation, write a better landing page or choose a different sample. If the sample requires permissions the reader will not have, prepare a suitable public version or remove the link.

A polished resume cannot rescue a confusing portfolio. Nor does a polished portfolio excuse an inaccurate resume. Keep each document honest and make them support the same account of your experience.

How should you describe portfolio work on the resume?

The resume should state the work and the skill; the portfolio should provide detail. Do not make the link do all the explaining. A short project entry can tell the reader what they will find, while a portfolio caption adds context and shows the artifact.

For example, a hypothetical resume line might read: “Created a three-screen appointment-booking prototype for a course project; documented keyboard navigation and form states. Selected work: [portfolio link].” The line identifies the project as coursework, says what the candidate did, and avoids claiming that a real service launched or improved conversion.

A second hypothetical example for a writer might be: “Wrote and edited monthly volunteer updates for a neighborhood organization; selected public samples: [portfolio link].” Use that only if it accurately describes the candidate’s role and the items are actually public. If the candidate edited rather than authored the pieces, say so.

Keep the distinction between resume claim and portfolio evidence clear:

The portfolio can deepen the story, but it does not license a stronger claim than the work supports. If your contribution is limited, say so. If the sample is hypothetical, label it. If the result is unknown, do not imply it.

How should you check the PDF and its links before applying?

Check the exported resume after you add the link. A clickable link can look correct in an editor and still be clipped, mistyped, or hard to use in a PDF. Open the final file, click the link, and inspect the page at normal reading size. If the URL is visible, make sure it remains legible in print or when copied from the document.

Use this final pass:

1. Confirm the visible link text matches the destination.
2. Click the link from the exported PDF, not only the source document.
3. Confirm the portfolio opens while signed out.
4. Check every featured sample and any external link inside it.
5. Confirm the portfolio title, captions, and project descriptions are accurate.
6. Inspect the resume layout after export for wrapping, clipping, or reduced contact details.
7. Check that the portfolio and resume tell the same story about your role and project status.
8. Save the final version with a clear filename and keep a copy of the exact file you submit.

A neat resume layout makes this easier. If you need a starting point, the resumetemplate.co template gallery offers resume designs, and the free resume editor lets you prepare a document in your browser. The product stores resumes in that browser on that device; it does not provide central storage or cross-device sync. Download and check your final PDF yourself before applying. These tools help format the resume; they do not validate portfolio permissions or guarantee that an application system will handle a file in a particular way.

A practical decision checklist

Use this checklist for each target application, especially if you change the portfolio selection from one role to another.

Keep the link if all of these are true:

• The role benefits from seeing work samples.
• The linked page leads to the relevant work quickly.
• The samples are yours to share or are otherwise authorized.
• Your part is accurately described.
• The work is accessible without a confusing sign-in or request process.
• The samples are current enough or their age is explained.
• You can talk through the choices and limitations.
• The resume and portfolio do not make conflicting claims.

Leave it off if any decisive problem remains:

• The work is confidential and no safe version is available.
• You cannot establish permission to publish it.
• The page is broken or the samples are private.
• The content is unrelated to the target role.
• The sample implies more responsibility or results than you had.
• The portfolio is so broad or cluttered that the relevant evidence disappears.

If the decision is close, use the strongest exception as your guide: when privacy, permission, or role fit makes a sample inappropriate, do not force it onto the resume. A concise, truthful description is better than a risky link.

Frequently asked questions

Should I include a portfolio link if the job posting does not ask for one?

You can include it when it adds relevant, accessible evidence and fits the role. A request is not necessary for a useful work sample, but the absence of a request is a reason to be selective. Follow any application instructions that limit links or require materials in a particular format.

Should I link to LinkedIn or a portfolio?

Link to the destination that best supports the application. A complete, maintained professional profile can help a reader understand your background. A portfolio is stronger when the work itself matters and the selected samples directly support the role. Do not include both by habit; include both only if they serve different purposes and the resume remains uncluttered. CareerOneStop lists either a maintained LinkedIn profile or a work-related portfolio among possible contact details (CareerOneStop).

Can I include school projects?

Yes, when they demonstrate relevant skills and are labeled as coursework, a class assignment, or a student project. Do not present them as paid client work or imply that a prototype was launched. Explain the prompt or constraints briefly when that context helps the reader judge the sample.

What if my portfolio is a PDF?

A PDF can work if it is readable, organized, appropriately sized, and easy to open. Put a short contents page or clear labels near the beginning when needed. Test it in a browser or PDF reader while signed out, and make sure any internal links work. A PDF portfolio is not automatically easier than a website; choose the format the intended reader can access with the least friction.

Can I use a private or password-protected portfolio?

Use one only when the application process supports it and you can give the reader a practical way to access it. Do not make an unexplained password or access request the first step. If confidentiality prevents open access, a brief note that a safe sample is available on request may be more sensible than a link that cannot be used.

Is a QR code enough?

No. Use a readable web address or clickable link as the main route. A QR code can be an extra for printed materials, but it is less convenient when someone is already viewing the resume on a screen and cannot easily scan that same screen.

How often should I update the portfolio?

Review it before each application and whenever you replace, move, or change access to a sample. Remove items that no longer represent your work or that have lost permission to be shown. FGCU Career Development Services recommends refreshing portfolio content, removing weaker or outdated work, and testing links (FGCU Career Development Services). The useful cadence is tied to changes and applications, not an arbitrary calendar interval.

What if the sample is good but I cannot explain the outcome?

Show what you can substantiate. Explain the work, your role, and the method or decision visible in the sample. Do not invent results to make the project sound complete. If no outcome was measured, say so when the distinction matters, or omit outcome language entirely.

Make the link prove something specific

A portfolio link belongs on your resume when it lets a reader inspect relevant work without guessing, waiting for access, or questioning whether you had permission to share it. Choose samples for the role, explain your contribution, test the exact exported link, and remove anything that is confidential or misleading.

When you cannot safely show the work, leave the link off. Describe your responsibilities at a level you can defend. Then make the rest of the resume clear enough to stand on its own. If you are ready to format it, browse resume templates or use the free resume editor, then export and inspect the PDF you plan to send.