"Should I have a portfolio?" gets asked across fields where the honest answer is genuinely different depending on the work — a portfolio is close to mandatory for a designer, situational for a writer or marketer, and often unnecessary or even a distraction for many other roles. Building one because it feels like a generically good idea, without a clear sense of what it needs to demonstrate, tends to produce a weak version of a tool that only helps when it's strong.

When a portfolio is close to essential

Fields where the actual work product is visual, written, or otherwise directly showable — design, photography, writing, video editing, front-end development, architecture — benefit from a portfolio because a resume genuinely cannot convey the quality of the work itself. A resume can say "designed marketing materials for three product launches"; only a portfolio can show whether those materials were actually any good.

When a resume alone is usually enough

For most operational, analytical, managerial, and many technical roles, the actual work product is either confidential, not visually presentable, or meaningless without deep context a portfolio page can't provide (a financial model, an internal process redesign, a sales pipeline). In these cases, a resume with specific, quantified outcomes does the job a portfolio would try to do, without the extra effort of building and maintaining a second document.

When a portfolio can actively hurt

A thin portfolio — two rushed projects, inconsistent quality, or work that doesn't represent your current skill level — can do more damage than no portfolio at all, because it becomes the first thing a reviewer judges instead of your resume. If you're going to build one, it needs enough genuinely strong, representative work to hold up under scrutiny; a placeholder portfolio with mediocre content signals less readiness than simply not having one yet.

What belongs in a strong portfolio

  • A small number of your best work, not everything you've ever made. Three to six strong pieces beat fifteen mixed-quality ones — reviewers form an impression from the first couple of pieces and rarely make it through a long list anyway.
  • Context for each piece, not just the finished result: what the goal was, your specific role if it was collaborative, and what the outcome was, where you can share it. Work presented with no context makes a reviewer do the work of guessing what you actually contributed.
  • Recent work, prioritized over older work, even if the older piece is technically more polished — reviewers are trying to assess your current skill level, not your best moment three years ago.

A middle-ground option: a work sample, not a full portfolio

If your field doesn't clearly require a portfolio but you have one or two genuinely strong, shareable examples, offering them as supplementary material — a link in your application, or a mention in a cover letter — captures some of the benefit without the overhead of maintaining a full site. See our guide on building a simple portfolio website without design skills if you decide a lightweight version is worth the effort.

How this interacts with your resume

A portfolio supplements a resume; it doesn't replace the need for one to be genuinely strong on its own. Even in portfolio-heavy fields, most reviewers still screen the resume first to decide whether to click through at all — see our guide on writing a resume summary that actually works and run your resume through our Resume Checklist Generator regardless of whether a portfolio is also part of your application.

The honest decision rule

Build a portfolio if your field's hiring managers routinely ask for one, or if you have genuinely strong, presentable work that a resume alone can't communicate. Skip it, at least for now, if neither is true — a resume that's actually excellent will do more for you than a portfolio that exists mainly because it seemed like the thing to do.