Portfolios & Work Samples: The Complete Guide (2026)

A portfolio is a curated set of work samples — case studies, code, writing, or designs — that prove you can do the job before an employer takes your word for it. Some fields expect one by default; others treat it as an optional edge over similar-looking resumes.

Quick Answer: Portfolios are close to required in design, writing, and engineering; a valuable differentiator in marketing, product, data, and teaching; and rarely expected in finance, law, HR, or operations. Build one anyway if you have 3–6 pieces of work you’re proud to walk someone through.

Who Actually Needs a Portfolio, by Field

Whether you need a portfolio depends almost entirely on how your field evaluates skill. Design, writing, engineering, and other visibly-produced work fields treat a portfolio as close to mandatory, because the output itself is the proof. Fields built around judgment, relationships, or regulated process — finance, law, HR, operations — rarely expect one at all.

Fields Where a Portfolio Is Essentially Required

Graphic design, UX/UI design, writing and content, software engineering, photography, and video or motion work all treat a portfolio as a baseline, not a bonus. In these fields a resume alone can’t demonstrate craft, and hiring managers routinely pass on strong-sounding resumes that arrive with nothing to look at.

Where a portfolio is table stakes:

• Graphic/UX/UI design — case studies with process, not just final screens
• Software engineering — a GitHub profile or shipped, linkable projects
• Writing and content — a folder of published or representative samples
• Photography and video/motion — a curated visual reel or gallery

O*NET’s occupational skill profiles for these roles explicitly define output-based competencies, which is part of why employers in these fields ask to see the output itself rather than take it on faith. NACE’s research on what employers screen for consistently ranks demonstrated skills and problem-solving above credentials alone — and for visibly-produced work, a portfolio is the fastest way to show both. If you’re building a design-specific resume alongside your portfolio, our guide to graphic designer resume examples covers how the two should reference each other.

Fields Where a Portfolio Is a Differentiator, Not a Requirement

Marketing, product management, teaching, data analytics, and communications roles don’t require a portfolio to land an interview, but candidates who bring one routinely stand out. Work in these fields is often embedded in systems, decks, or dashboards you can’t fully hand over, so a portfolio becomes a curated highlight reel instead of a complete archive.

Common versions by field:

• Marketing: a campaign case study with the brief, creative, and directional results
• Product: a write-up of a shipped feature, including trade-offs you considered
• Teaching: sample lesson plans and anonymized examples of student progress
• Data/analytics: a public dataset analysis or a dashboard walkthrough

LinkedIn has publicly encouraged job seekers to add project and media links to their profiles, which lines up with how recruiters actually browse: skimming visual proof before reading further. A portfolio in these fields doesn’t replace your resume — it backs it up.

Fields Where a Portfolio Rarely Matters

Finance, accounting, law, human resources, operations, sales, and most regulated or compliance-heavy roles rarely expect a portfolio, because the work is confidential, relationship-based, or governed by rules that make sharing deliverables impractical. A resume, references, and interview performance carry far more weight here.

That doesn’t mean you should show up empty-handed. Keeping a private “brag document” of your accomplishments — the kind of detail you’d use to quantify achievements on a resume — gives you the same preparation benefit without needing a public-facing gallery. It’s a portfolio in spirit, just not in format.

How to Tell When Your Field Is Shifting Toward Expecting One

Watch job postings for phrases like “portfolio required,” “writing samples requested,” or “GitHub link preferred” — that’s the clearest real-time signal a field is shifting. The World Economic Forum’s Future of Jobs research points to a broader move toward skills-based, evidence-based hiring across industries, not just the traditionally creative ones.

Freelancers and contractors tend to feel this shift first, since clients hire them project-to-project based almost entirely on prior work. ZipRecruiter’s labor-market reporting on freelance and contract postings shows portfolio or work-sample requests appearing more often in listings outside the traditionally creative fields, too. If freelance work makes up part of your history, see our guide on how to list freelance work on a resume for how to frame it alongside a portfolio link.

What Belongs in a Portfolio (and What to Cut)

A strong portfolio includes three to six pieces of your best, most relevant work, each framed with context about the problem and your specific contribution — not a comprehensive archive of everything you’ve ever made. What doesn’t belong: unfinished work, pieces you can’t discuss in depth, and anything that doesn’t match the role you’re targeting.

The Core Building Blocks of a Strong Portfolio

Every strong portfolio contains the same core elements regardless of field: a short bio framing who you are, three to six curated samples, context for each piece, and an obvious way to reach you. Everything past that — testimonials, a blog, a downloadable resume — is optional polish, not a requirement.

Minimum viable portfolio checklist:

1. A one- or two-line bio stating what you do and for whom
2. Three to six samples, each with a short caption explaining context
3. A visible way to contact you (email, LinkedIn, or a simple form)
4. Working links, tested on both desktop and mobile

Signals That Actually Impress Hiring Managers

Hiring managers respond to specificity and range more than volume: a portfolio that shows your process, names your exact contribution on team projects, and demonstrates more than one type of problem solved reads as far more credible than a long list of similar-looking pieces. Depth beats breadth almost every time.

Glassdoor’s research on interview and hiring trends has repeatedly found that candidates who can clearly explain their own role in past work — rather than describing team accomplishments in the collective “we” — come across as stronger interviewees. McKinsey’s writing on skills-based hiring points to the same broader pattern: employers increasingly weigh demonstrated, specific ability over polish or pedigree alone.

• Range: more than one type of problem or medium
• Process: sketches, drafts, or decision points, not just finished output
• Named contribution: your role is explicit, not implied
• Recency: most pieces reflect your current skill level, not skills from years ago

Common Inclusions That Backfire

The most common portfolio mistakes are padding it with tutorial-level work, including pieces you can no longer explain in detail, and leaving in outdated or embarrassing early work out of sentimentality. Any one of these can undercut the credibility your strongest pieces have built.

Watch for these specific traps:

• Clone projects or tutorials with no personal twist
• Group work with no clarity on who did what
• Dead links, broken embeds, or missing images
• Work built on tools or platforms no longer relevant to your target role
• Pieces you haven’t looked at in over two years and can’t speak to confidently

How Much Is Enough (and When You Have Too Much)

Most job seekers need three to six strong samples, not twenty — quality and relevance beat volume every time you’re competing for a hiring manager’s limited attention. If your count creeps past eight or ten, that’s a sign it’s time to prune rather than add a filter menu to sort through it.

A useful mental model: keep a private “master” archive of everything you’ve ever built, the same way our guide to building a master resume recommends keeping every accomplishment in one long document. Your public portfolio is simply the curated, role-specific pull from that larger archive — never the whole thing at once.

Choosing a Platform: Personal Site vs. GitHub vs. Behance vs. PDF

The right platform depends on your field and how much control you want. A personal website gives full control and brand but takes the most upkeep; niche platforms like GitHub, Behance, or Dribbble put you in front of an audience that already looks there; a PDF or Notion one-pager is the fastest thing to send straight to a recruiter.

Personal Website — Best for Full Control and Brand

A personal website is the most flexible option because you control the design, structure, and narrative completely, which matters most for designers, writers, and senior professionals building a lasting personal brand. The tradeoff is upkeep — a stale or broken personal site actively hurts more than having no site at all.

Simple builders (Squarespace, Webflow, Notion-as-a-site, or a lightweight static site) all work fine; the platform matters far less than whether it stays current. A personal site also doubles as a hub for the kind of visibility covered in our guide to personal branding and industry networking — it’s often the landing page people reach after finding you elsewhere.

Niche Platforms (GitHub, Behance, Dribbble) — Best for Built-In Audience

Platform-specific portfolios — GitHub for engineers, Behance and Dribbble for designers, Contently or Muck Rack for writers — put your work in front of recruiters who already browse those platforms and understand the format. The tradeoff is less control over presentation and a layout that looks similar to every other candidate’s.

When niche platforms make the most sense:

• You’re early-career and don’t want to invest in a full site yet
• Your field has one dominant platform recruiters already check
• You want discovery, not just a link you send directly

The PDF One-Pager and Notion Doc — Best for Speed and Application-Ready Formats

A PDF one-pager or a Notion doc is the fastest format to attach directly to an application or email, and it works well for roles where a full website would be overkill — marketing, product, data, and teaching candidates use this format most. It’s also the easiest format to swap in a different case study for each employer.

This format has one underrated advantage: it travels well. It attaches cleanly to an email, survives being forwarded to a hiring committee, and doesn’t depend on a link staying live for years.

Matching Platform to Field and Career Stage

Early-career candidates in tech or design often do best starting on a free niche platform before investing in a personal site, while senior professionals and consultants benefit more from a site that doubles as a long-term professional hub. Match the platform to how actively you’re job searching versus how much you’re building an ongoing presence.

Don’t overlook LinkedIn itself as a fifth option: its Featured section can host work samples directly on a profile recruiters are already viewing. Our guide to LinkedIn optimization for your job search covers how to set that section up alongside the rest of your profile.

Handling Confidential and NDA-Protected Work

Most professional work is covered by some form of confidentiality agreement, but that doesn’t mean you can’t show it — it means you have to reframe it. The safe approach redacts identifying details, describes outcomes directionally instead of with exact figures, and leans on case-study framing rather than reproducing the actual deliverable.

What You Can Usually Show Without Breaking an NDA

You can almost always describe the problem you solved, the process you used, and the skills you applied without reproducing the actual client deliverable, client name, or proprietary data. Most NDAs restrict disclosing confidential business information and trade secrets — not the fact that you know how to do the work.

Generally safe to share: your role, the tools and methods you used, the general category of problem, and any outcome that’s already been made public elsewhere. Generally unsafe: client names, exact internal figures, proprietary code or design files, and anything about an unreleased product.

SHRM’s guidance on hiring and workplace practices frequently touches on how organizations balance confidentiality with the reality that employees need to describe their work to future employers — the two aren’t actually in conflict as often as candidates assume.

Redaction Techniques That Preserve Credibility

Effective redaction blurs or removes identifying names, logos, and exact figures while keeping the structure and reasoning of the work fully visible, so a reviewer can still evaluate your thinking. The goal is to protect the client, not to hide your own contribution behind vague language.

Turning a precise, identifying claim into a protected one is usually a simple substitution. Replace “[Client]'s revenue grew 20% in Q3” with “[a mid-size client] saw a double-digit percentage increase in a core revenue metric over one quarter” — same credibility, none of the exposure.

Case-Study Framing as an Alternative to Raw Deliverables

When you can’t show the actual file, screenshot, or code, a written case study that walks through the problem, your approach, and the general shape of the result lets you demonstrate judgment without exposing anything confidential. This format works especially well for product managers, consultants, marketers, and engineers on proprietary codebases.

Framing it as a case study also sets the right expectation with whoever’s reviewing it — they understand upfront that some details have been altered or generalized, so nothing reads as a gap or omission.

When to Just Ask Your Former Employer

Sometimes the simplest solution is asking your former manager or an HR contact for written permission to share a specific piece, especially for older projects or ones that are already public. Many companies grant permission for anonymized or previously published work when asked directly and specifically.

Be precise in the ask: name the exact piece, describe how you plan to redact it, and request a short written yes. A specific, low-effort request is far more likely to get approved than a vague “can I use some of my old work?”

Structuring a Case Study That Actually Persuades

A persuasive case study follows a simple arc: state the problem clearly, explain your approach, name your specific contribution separate from the team’s, and frame the outcome honestly — including its scope and limits. Skipping any one of these four steps is the most common reason portfolio pieces fall flat under interview questions.

The Problem → Approach → Contribution → Outcome Framework

This four-part framework works across every field because it mirrors how interviewers actually evaluate work: what was broken, what you did about it, what part was specifically yours, and what changed as a result. Structure each case study around these four sections in order, even if some sections are just a sentence or two.

Being Honest About Your Specific Role on a Team

Interviewers probe team projects specifically to find out what you did versus what your team did, so naming your role precisely — “I designed the onboarding flow; a teammate built the backend” — builds more trust than a vague “we” that implies more credit than you can defend.

Harvard Business Review’s writing on interview credibility and self-presentation consistently notes that specific, checkable claims read as more trustworthy than broad, unverifiable ones. That principle applies directly to how you narrate a group project in a case study.

Framing Outcomes Without Overclaiming

Frame outcomes with the scope you can actually defend under follow-up questions: attribute results partially when other factors contributed, use ranges instead of false precision, and separate what you measured from what you assumed. A believable, modest claim beats an impressive one you can’t back up in an interview.

If you’re unsure how specific to get with numbers, our guide on how to quantify achievements on a resume walks through the same honesty-versus-precision trade-off in more depth — the same rules apply to a case study as to a resume bullet.

A Short Case-Study Example Structure

A minimal template you can fill in for any field looks like this:

[Project Name] — [Client type or product area]

Problem: [One or two sentences on what was broken or needed.]
Approach: [What you tried, why, and what you considered but rejected.]
My role: [Specifically what you did vs. what teammates did.]
Result: [What changed, scoped honestly — use a range if precision isn't available.]

Keep each section short. A one-page case study that’s easy to skim beats a five-page one that only a fully engaged reader will finish.

Portfolios in the Application vs. Work Samples in the Interview

Your application should include a portfolio link or one or two samples that are easy to skim in under a minute; save deeper, more sensitive, or more numerous samples for after you’ve been asked — typically once you reach the interview stage. Sending everything upfront overwhelms a resume screener who’s spending seconds, not minutes, on your application.

What to Link in Your Resume and Cover Letter

In your resume or cover letter, include a single link to your portfolio or your single strongest sample — not five separate links — and make sure the link itself is short, working, and doesn’t require a login. A cluttered header full of links reads as unfocused rather than thorough.

Indeed Hiring Lab’s research on recruiter behavior points to consistently short attention windows during resume review, which is exactly why one clean, working link outperforms a scattered handful every time.

What to Bring (or Send) After You’re Asked

Once you’ve been asked to share more, you can go deeper: bring a laptop with three or four additional samples to an in-person or video interview, or send a short follow-up email with two or three targeted pieces plus one line of context each. Match the depth of what you share to the depth of the question being asked.

A simple rule of thumb:

• Application stage: one link or one sample
• Phone screen: be ready to describe two or three, verbally
• Onsite/final round: bring three to five, tailored to the role
• After an explicit request: send exactly what was asked for, nothing more

Tailoring Which Samples You Show to Which Employer

Which pieces you show should shift by employer — a fintech company wants to see your handling of complex data or compliance-adjacent work, while a consumer brand wants storytelling and visual polish, so keep more samples in reserve than you ever show any single employer at once.

Once you’re applying to several employers with different portfolio cuts, it’s easy to lose track of who saw which version. CareerJenga’s application tracker and Target Role keep every application, status, and follow-up on one board while your Target Role tailors each resume — so you can note which case studies went to which employer right alongside the rest of your search.

Following Up Without Being Pushy

If an interviewer asks for samples and you don’t hear back within a week, one short follow-up email referencing the specific piece you sent is appropriate; more than that risks seeming anxious rather than organized. Keep the follow-up focused on your availability to answer questions about the work, not on checking status.

Curating, Pruning, and Keeping Your Portfolio Accessible

A portfolio needs regular maintenance — pruning outdated pieces, checking links, and swapping in recent strong work — on roughly the same cadence you’d update a resume, ideally every three to six months or after any major project. An untouched, years-old portfolio signals inactivity even if you’ve been working hard the whole time.

How Often to Prune and What to Cut First

Review your portfolio every time you update your resume, and cut the oldest or weakest piece whenever you add a new one, so the total stays in the three-to-six range instead of growing indefinitely. Cut first: anything more than two to three years old unless it’s still your best work, anything you can no longer speak to in detail, and anything built with tools no longer relevant to your target roles.

Accessibility and Hosting Basics Nobody Talks About

A portfolio that’s slow to load, requires a login, or breaks on mobile loses hiring managers before they see the work itself, so basic hosting hygiene matters as much as the content. Use a reliable host, compress your images, add alt text, and test on a phone before sending the link anywhere.

Pew Research’s data on how widely mobile devices are used for everyday browsing is a good reminder that a portfolio which only works well on desktop is cutting off a meaningful share of the people who might open it.

A quick hosting checklist:

• Loads without a login or paywall
• Images are compressed and have descriptive alt text
• Text has enough contrast to read comfortably
• Layout holds up on a phone screen, not just a laptop

Keeping a Portfolio Fresh Between Job Searches

The best time to update a portfolio is right after finishing a strong piece of work, not months later when you suddenly need it — the details fade from memory, and any redaction or permission conversation gets harder over time. Treat portfolio updates as part of finishing a project, not part of job hunting.

Gallup’s ongoing research on the U.S. workforce has found a substantial share of employees stay at least passively open to new opportunities at any given time — exactly the population a continuously updated portfolio is built to serve. Waiting until you’re actively searching means starting from a deficit.

How a Portfolio Differs from Your Resume’s Projects Section

Your resume’s projects section is a compressed, text-only summary designed to survive an applicant tracking system and a six-second scan; your portfolio is the expanded, visual, often interactive version of that same proof, meant for someone already interested enough to click through. They should tell the same story at two different zoom levels, not contradict each other.

For the narrower how-to on writing that resume section itself — formatting, word choice, and what to include line by line — see our guide to adding a projects section to your resume. Think of this guide as the wide-angle version and that one as the close-up.

Key Takeaways

• Portfolios are close to required in design, engineering, and writing; a differentiator in marketing, product, data, and teaching; and rare in finance, law, HR, and operations.
• Curate three to six strong, relevant samples rather than a comprehensive archive — quality and range beat volume.
• Match your platform to your field: a personal site for control and brand, niche platforms like GitHub or Behance for built-in audience, PDF or Notion for speed.
• NDA-protected work can usually still be discussed — redact names and exact figures, and lean on case-study framing instead of raw deliverables.
• Structure case studies around problem, approach, your specific contribution, and an honestly scoped outcome.
• Link one strong sample in your application; save deeper or more sensitive samples for after you’re asked.
• Prune your portfolio every three to six months, and update it right after finishing strong work rather than waiting until you need it.
• Basic hosting hygiene — fast load times, no login walls, mobile-friendly layout — matters as much as the work itself.
• A portfolio and a resume’s projects section should tell the same story at different zoom levels, not compete with each other.

FAQ

Do I need a portfolio if I’m not in a creative field?

No — most non-creative fields don’t require a portfolio, but a short, curated set of work samples or a case-study document can still differentiate you in marketing, product, data, teaching, and similar mixed fields. In finance, law, HR, and operations, a resume and strong references typically carry more weight than a portfolio ever would.

How do I share work samples that are under NDA?

Redact client names, logos, and exact figures, describe outcomes directionally instead of precisely, and frame the piece as a case study about your process rather than a reproduction of the deliverable itself. When in doubt on an older or already-published project, a short permission email to your former employer resolves most gray areas.

What if I have no professional work to show yet?

Build a small number of self-directed projects that mirror real work in your target field — a redesign of an existing product, an analysis of a public dataset, or a short writing piece on a topic in your industry — and frame them honestly as self-initiated rather than professional. Hiring managers value demonstrated initiative and skill more than the label of who assigned the work.

Should my portfolio be a website, or is a PDF enough?

A PDF or Notion one-pager is enough for most application-stage sharing, especially in marketing, product, and data roles, while a personal website is worth the extra effort for designers, writers, and senior professionals building a longer-term personal brand. Start with whichever format you can actually keep updated — an abandoned website is worse than a clean PDF.

How many work samples should I include?

Most portfolios work best with three to six strong, relevant pieces rather than a comprehensive archive — enough to show range without diluting your best work. If you’re tailoring to a specific employer, two or three especially relevant samples usually outperform a longer, generic list.

Can I use the same portfolio for every job application?

You can keep one core portfolio, but the samples you lead with should shift based on what each employer is likely to value — reorder or swap in different case studies rather than rebuilding from scratch every time. Keeping a running note of which version went to which employer helps you stay consistent when you’re asked about it in an interview.