Resume vs portfolio: how they divide the work

Two documents, two jobs

The resume gets you past screening — parsers and recruiters checking structured facts. The portfolio wins the human review — proof you can actually do the work. For creative and many technical roles you need both, and each fails at the other’s job.

Who genuinely needs a portfolio

Designers (product, graphic, motion), writers and content marketers, photographers and video editors, front-end developers, architects, illustrators, and increasingly data folks (analysis notebooks, dashboards). If hiring managers in your field open work samples before deciding, you need one.

The resume still comes first

Almost every portfolio-heavy role still routes applications through an ATS that parses resumes, not Behance pages. A weak resume means the portfolio never gets opened. Keep the resume complete and parser-safe on its own — never write "see portfolio" in place of real content.

Put the link where parsers find it

Your portfolio URL belongs in the resume contact block as real text (yourname.com or behance.net/you), exported as a clickable link. Avoid link shorteners (they look disposable and can rot) and QR codes (parsers ignore images).

Curate hard: 4–8 pieces

A portfolio is not an archive. Show your best 4–8 pieces, most relevant first, each with a short case note: the problem, your role, the decision you made, the outcome. Hiring managers spend minutes, not hours — depth on few pieces beats breadth on many.

Tailor the portfolio like the resume

Applying for a mobile-app design role? Lead with mobile work. Content role in fintech? Lead with financial writing. The same tailoring logic you apply to resume bullets applies to portfolio ordering — the first two pieces decide whether they keep scrolling.

Formats by field

Design: a personal site or Behance/Dribbble with case studies. Writing: a simple page of linked published pieces (or PDFs where rights allow). Development: GitHub with pinned repos plus 1–2 live demos; a README is your case note. Data: notebooks or dashboards with a paragraph of context each.

The case-study skeleton

For each piece: one line of context (client/team/constraint), one line on your specific contribution ("my role: interaction design and prototype"), one honest outcome ("shipped to 40k users" only if true and checkable). Claiming solo credit for team work is checkable and fatal — credit collaborators.

Rights and confidentiality

Only show work you have the right to show. NDA work can appear as an anonymized case study ("a payments company") with sensitive numbers removed, or be described in the interview instead. Never publish confidential assets to win a job — the employer reading it notices what you would do with theirs.

Keep it fast and reachable

A portfolio that loads slowly or 404s is worse than none: test the link from a phone on mobile data, keep images compressed, and re-verify every link each time you send applications. If the domain lapses, update the resume everywhere it is listed.

What stays on the resume

Dates, employers, titles, education, skills, quantified outcomes — the checkable skeleton recruiters cross-reference. The portfolio shows how the work looks; the resume proves where and when you did it. Contradictions between the two (different titles, different dates) read as dishonesty.

A quick pre-send audit

Resume parses cleanly (test it in our free ATS checker) · portfolio link in the contact block as text · first two pieces match the job · every case note has your role and an honest outcome · all links open from an incognito window · nothing confidential. Then send.