Design · Mid-level
Graphic designers are tempted to make the resume itself the portfolio piece: columns, icons, skill bars, a custom typeface. That works for the human who eventually opens it, but many applications pass through an ATS first, and decorative layouts are exactly what those parsers scramble. Your portfolio carries the visual proof; the resume has a different job.
That job is to show range, judgment and results in plain text: what you designed, for whom, under what constraints, and what changed because of it. The example below keeps a clean single-column layout, links the portfolio at the top, and writes bullets about outcomes rather than a list of deliverables.
Graphic Designer with 6 years across in-house brand and agency work, most recently owning visual design for a consumer subscription brand. Led a brand refresh across packaging, web and paid social, and built the template system that lets a 5-person marketing team ship on-brand assets without a designer in the loop. Strong in typography, layout and production for print and digital.
Place one short, working URL next to your email and phone. Recruiters for design roles often open the portfolio before reading the resume, so make it impossible to miss and make sure it loads quickly on a phone.
Use a single column, standard headings and real text rather than icons or skill bars. You can show taste through spacing, type hierarchy and restraint, which survive an ATS. Graphics, text in images and multi-column grids often do not.
Write "Adobe InDesign", "Figma" and "After Effects", not "Adobe suite" or "design tools". Many screens match these terms literally, and postings often differ in which ones they require.
Yes. Most applications still go through a resume screen before anyone opens a portfolio, and the resume is where you explain context the work cannot show: your role on a project, the constraints and the result.
Lightly. A clear type hierarchy and good spacing show your eye without breaking ATS parsing. Save heavy visual treatment for the portfolio, or send a designed PDF only where a person, not a system, will read it.
Measure what the design changed: turnaround time, campaign performance, consistency across a team, production errors, or how widely a system was adopted. If you do not have a number, describe the scope and who relied on the work.
Start from this structure in the free editor, then run the ATS check to verify it parses.