A reliable UX designer resume layout begins with verified qualifications, relevant experience and readable evidence, not a decorative template. Start with name, a professional email, a concise location line when useful, and a direct portfolio URL that opens the intended work. A LinkedIn or GitHub profile may belong here if it actually supports the vacancy. Avoid a decorative QR code as the only way to reach samples: some reviewers work from a printed document or text-only extraction. A short headline like “UX Designer — Research and Interface Prototyping” is better than vague claims about being a visionary creative problem solver.
Place a working portfolio link where reviewers expect it
Use a one-column arrangement and familiar section labels. Put Professional Experience and Selected UX Projects above long tool inventories when you have credible design work. A new designer can lead with project experience and formal training, clearly marking course projects as such. Penn’s career guidance recognizes project and portfolio links for relevant fields; the key is making those links contextual rather than crowding the header with every account you own.
Treat resume bullets as doors into case studies
A resume cannot explain every research decision, constraint and revision. It should give a reader enough orientation to choose the right portfolio case. For each selected project, make the resume entry answer: what problem or product context, what you specifically did, which evidence you evaluated, and what deliverable followed. The case study can then provide the process, artifacts you are allowed to show, and a candid discussion of limitations.
Keep the case names consistent across the resume and portfolio. If a bullet says you conducted usability sessions, the case should not reveal that you merely read another team’s research summary. If a project was a classroom assignment, name that context. A truthful linked pair is stronger than a polished project with no explanation of individual ownership. Test links while signed out and on a phone, and consider whether the landing page exposes confidential documents.

Make the research-to-design sequence visible
Interface and digital designers may work on functionality, navigation, layouts, testing and prototypes, according to the Bureau of Labor Statistics. Your resume should show which of those stages you touched instead of listing “end-to-end UX” automatically. A researcher might have moderated interviews and synthesized findings while another colleague chose the final interface. A visual designer might have prototyped navigation options and handed off specifications without approving product strategy.
The fictional example “Worked on an app redesign” hides everything useful. A more specific hypothetical line is: “Synthesized approved interview notes into a navigation issue list and revised clickable prototypes for team review.” This identifies a research input, a design output and a review boundary without inventing launch metrics. Only claim measurable task completion, adoption, or conversion effects if you can trace the measurement to the project and you have permission to share it.
Arrange projects by evidence, not by tool popularity
A compact Selected Projects section can help when work history includes operations, internships, freelance assignments, or class exercises. Each entry should identify a project and its type, the timeframe when it matters, your role and a practical artifact. Arrange projects according to relevance to the opening, not just chronological order. For a research-heavy role, a well-documented study may deserve more space than a beautiful interface mockup.
Mention Figma, research tools, analytics platforms or accessibility testing only if you actually used them and can explain what you did. A row of logos is visually appealing but unhelpful to a recruiter reviewing text. Tool skill is not the same as research judgment, and a completed prototype is not proof that a feature shipped. Separate academic work, speculative concepts, and paid client work by clear labels that the employer can verify.

Preserve ownership and ethical limits in portfolio samples
Most professional UX work involves collaborators. Use accurate verbs: facilitated, analyzed, designed, documented, recommended or partnered with. If product management made the final scope decision, you can say your team used your research rather than you personally decided what shipped. If the company prohibited sharing work, describe the high-level challenge and your method, or use a wholly independent practice case that does not reproduce protected material.
A case study should not expose unreleased product direction, customer statements, participant identities, analytics exports or internal documents. Remove identifying information and confirm the organization’s rules before posting samples. Even synthetic screen designs can accidentally resemble a client’s proprietary interface; label demonstrations as recreations when appropriate. The portfolio can explain your thinking while the resume remains a concise, public, factual career record.
Choose an accessible layout and clear visual hierarchy
Use readable type, consistent margins and visible section boundaries. A designer may be tempted to demonstrate expertise with intricate columns, colored progress rings, small captions and custom fonts. Those elements can reduce readability in an application portal. CareerOneStop recommends simple, consistent formatting. You can demonstrate craft through alignment, spacing, typography and considered order rather than decorative complexity.
Keep text selectable in the exported file. Avoid placing all content inside a single image. Review at ordinary screen width, print preview and text-copy view. The PDF and editable source should agree; if an employer specifies DOCX or plain text, deliver that rather than trying to force a preferred portfolio-style export. Confirm live links, any accessibility of hosted case studies, and the first line of each role at both desktop and mobile widths.
Tailor one version for a researcher and another for a designer
A UX research opening may reward interview planning, synthesis, study limitations and communication with stakeholders. A product interface role may prioritize prototype iterations, interaction constraints, handoff and collaboration with engineering. Read the actual advertisement instead of assuming all UX labels refer to identical authority. Move a section or two to highlight the matching evidence; do not swap titles, dates or outcomes merely to echo a keyword.
For each vacancy, identify the top two responsibilities, choose one project showing each, and ensure the resume and portfolio use consistent scope language. If your only relevant evidence is a simulated practice case, say so. The better result is a reviewer who understands your transferable skills, not a resume that sounds senior but cannot survive a discussion of research methods or design reviews.

How We Research portfolio-centered resume layouts
We use CareerOneStop guidance for legible resume structure, Bureau of Labor Statistics descriptions of digital interface design work, and Penn career advice on linking projects and portfolios. These sources support a practical structure, but they do not promise that any design will pass a specific applicant tracking system. See CareerOneStop formatting, BLS digital designers, and Penn project guidance.
Examples are fictional and should be rewritten from your actual research record. Ask permission before publishing client artifacts. See JobAsk’s disclosure policy for information about site recommendations and relationships.
More Resume and Cover Letter Guides
Not necessarily. A clean one-column resume may communicate experience more reliably than complex columns or visual skill charts. Use the portfolio for interaction details and expressive design, and obey any application-specific file instructions.
Choose a small set that matches the role and that you can discuss accurately. The number is less important than a clear connection between your responsibility, research evidence, design decisions and the work accessible at the link.
Only when you have permission and have respected confidentiality, privacy and contract requirements. A safe narrative can describe your method and decisions without uploading unreleased screenshots, customer data or proprietary research.
In bullets under the role or project where they occurred. State whether you planned, moderated, observed, analyzed or presented testing, and distinguish recommendations from changes that were actually implemented.
Use a truthful title. If your employer called the role something different, preserve the official title and describe the relevant UX responsibilities rather than relabeling yourself as a higher-level decision maker.
