Resume for a graphic designer moving into product design
You already do research, iteration and design under constraints. Your resume just hides it behind the polish. One designer, rewritten section by section, so the page shows the user and the process.
Product design, in this guide, means designing software: apps, websites, the screens people tap through to get something done. Not chairs, not toasters. The job is less about how a screen looks and more about whether the person using it can do what they came to do.
If you are a graphic designer eyeing that job, here is the good news. You have done most of the work already. You have talked to the people your designs were for. You have made ten versions and killed nine. You have shipped inside brutal constraints: a print budget, a brand book, a sign that has to read from across a parking lot.
The problem is your resume says none of that. It lists deliverables. Product teams hire for problems solved. The move is mostly a translation job, and this guide does the translation on one real-shaped resume, section by section.
Meet Dana
Dana is fictional, but you have met her. She is a senior graphic designer on the in-house team at Harvest Lane, a regional grocery chain. Over the last few years she has refreshed the brand, designed weekly sale campaigns, redone the in-store signage, built a social template kit, and made the promo banners that show up in the grocery app.
On the side, she took an online UX course (UX is user experience: the study of how people move through a product) and redesigned the volunteer signup for her neighborhood food bank.
Her current resume is competent. It is also invisible to a product design hiring manager, because every line describes an artifact and none describes a person using it. Let's fix it from the top down.
The title line: name the job you want
The line under your name is the first claim you make. If it says "Graphic Designer," a product design recruiter files you as a graphic designer and moves on. Use the role you are targeting, plus the parts of your background that make it believable.
One honesty rule. The headline is where you are going, so it can say "Product Designer." Your job titles in the experience section are where you have been, so they stay exactly as your employer wrote them. Never rename a past job. A reference check will catch it, and it reads as a lie even when the work was real.
"Interaction design" is the part of product design about how a thing behaves when you use it: what happens when you tap, scroll, make a mistake. Only claim it if you have done some, even in a course. Dana has, so it goes in.
The summary: lead with the user, not the eye
Graphic design summaries tend to sell taste. Product design summaries sell judgment about people. Same designer, different pitch.
Notice what the rewrite does. It names the switch out loud instead of hoping nobody notices. It names a user ("shoppers in a hurry"). It points at the one piece of work that is already product design, the signup flow, so the reader knows to look for it.
"Keen eye" goes. Your portfolio proves your eye. The resume's job is to prove your thinking.
The experience bullets: from deliverable to problem
This is where most of the translation happens. Every graphic design bullet has the same shape: designed X. A product design bullet has a different shape: solved Y problem for Z people, and ideally, here is how I know it worked.
You don't need new projects for this. You need to remember the parts of the old projects you left off the page. Who complained about the old version? What did you show people before launch? What did the team stop doing afterward?
Here are Dana's Harvest Lane bullets, one at a time.
Wayfinding is navigation design. That is a product problem wearing a print costume. Dana watched people get lost, made a cheap prototype (a test version built fast to learn from), and measured whether it helped. That is the core loop of product work. She had just never written it down.
This is the bullet closest to software, so it earns the most detail. If you have touched anything that lives on a screen and gets clicked, find it and make it specific. Hiring managers read these bullets for signs you already think in screens and behavior.
A brand system is a close cousin of a design system, the shared library of components and rules a software team builds screens from. Say "system." Name who used it. Show what got easier for them. The logo can stay in the portfolio, where it looks better anyway.
Look at the pattern across all four. Each rewrite adds a person, a problem, something Dana tried, and a change she can point to. None of them mentions how anything looked. That is not because visuals don't matter in product design. It is because the resume is the wrong place to prove them.
No numbers? Use the change in behavior instead. "Staff stopped answering the same question" is a real outcome. So is "the team adopted it as the default." Don't invent a metric to fill the slot.
Try it on your own work
Pick one thing you made. The translator below asks the four questions a product team would ask about it, then hands you a sentence frame. The frame is scaffolding. Rewrite it until it sounds like you talking.
Turn a deliverable into a product design bullet.
Pick something you have shipped. Answer four questions in your own words. Then edit the sentence until it sounds like you.
Pick a deliverable to see the questions.
Which projects go first
Inside each job, order bullets by how close the work sits to software, not by how proud you are of it. Dana's order changes completely.
- First: anything on a screen people act on. App banners, email layouts, a landing page, a kiosk. Even small screen work beats big print work here.
- Second: systems other people used. Brand guidelines, template kits, a component library in Figma. These show you design for other designers and non-designers, which is most of product work.
- Third: navigation and information problems. Wayfinding, menus, forms, packaging that has to communicate fast. These show you think about people finding things.
- Last, or cut: purely visual work. Posters, illustration, a campaign that was mostly a mood. Keep it in the portfolio if you love it.
The brand refresh was the bigger project. It still drops to third. A product design reader scanning the top of the page should hit screens and users first, then the system work, then the rest.
A short "Relevant work" section
A UX course or side project is real evidence, but it gets lost if you bury it under Education. Give it a small section of its own, right under your summary or right after your current job. Two or three entries, each written like a job bullet, with a problem and a result.
"Usability testing" means watching real people try to use your design while you keep quiet and take notes. If you did it even once, name it. It is the single clearest signal that you design for people and not for a portfolio shot.
The course can still appear, one line, under Education. The project is what goes in Relevant work, because the project is what you did.
Point to case studies, not a gallery
Product design hiring runs on the case study: a portfolio page that walks through one project from problem to research to rough versions to final, with what you learned. A gallery of finished images does not do that job, however good the images are.
Your resume should hand the reader straight to those case studies. Put one portfolio link in the contact line, and make sure the projects in your bullets have matching case studies with matching names.
One link, and it goes somewhere built for this job. Behance and Dribbble are fine places to keep work, but sending a product team four visual platforms tells them you think of yourself as a visual designer. Which is the thing you are trying to move past.
What to cut
Two habits from graphic design resumes work against you here.
Software lists as decoration
Skill bars, dot ratings, a grid of app icons. They take up space and say nothing a reader can use. List the tools a product team cares about, in plain text, at the bottom, with a word on how you use the important one.
Dot ratings also backfire on their own terms. Dana's old version gave Figma two dots, the one tool a product team cares most about, and announced her weakest skill in the place a recruiter looks. If you are still learning Figma, learn it on your side project and describe what you built with it.
Visual-only awards up top
Design awards for posters, packaging or campaigns are nice. They are also judged on looks, which is the part of your work a product team is least worried about. Move them to a single line near the bottom.
Keep the page plain
A designer's resume does not need to be a poster. It needs to be easy to read, which is itself a design skill, and the one a product team is hiring for.
Use one column, real text (not text baked into an image), a readable type size, and section headings a stranger could predict. Many companies run resumes through an ATS (applicant tracking system, the software that stores applications and lets recruiters search them). Fancy layouts can scramble when that software reads them, and a scrambled resume is a resume nobody finds. Your restraint is the portfolio piece here.
Dana, before and after
Same person. Same jobs. Same projects. The old page said "here is what I made." The new one says "here is who I made it for, what was broken, what I tried, and what changed." That second sentence is the product design job description.
Your turn. Open your resume in the free editor, change the title line, and rewrite your three closest-to-software bullets with a person and a problem in each. Your words, not AI. If you want a second read once it is done, the $2.99 Career Analysis Review checks your resume against a specific product design posting and tells you where the gaps are.