Step 1
Audit Each Project for Research Method, Decision, and Outcome
Go through each significant design project and answer three questions: What research method did you use to understand the problem? What specific design decision did that research drive? What measurable outcome resulted from the design change? This audit produces the raw material for your strongest resume bullets. Projects where you have all three elements become your lead examples; projects where you have only deliverables need either more context added or should appear in the portfolio but not the resume.
Step 2
Create a Skills Section Organized by Tool Category
Organize your UX skills section into clear categories: Design Tools (Figma, Sketch, Adobe XD), Research Methods (user interviews, usability testing, card sorting), Prototyping (Figma interactive prototypes, InVision, ProtoPie), and Collaboration Tools (Miro, FigJam, Confluence). Organized groupings help ATS systems correctly identify your proficiencies and make your full-stack UX skill set legible at a glance to reviewers skimming quickly.
Step 3
Identify Keywords From the Specific Job Description
UX job descriptions vary significantly between product companies (who emphasize research, metrics, and collaboration with engineering) and agency roles (who emphasize deliverable speed, client communication, and breadth of output). Read the specific job description and identify which research methods, tools, and collaboration patterns it emphasizes. Reorder your skills section and adjust your experience bullets to lead with the terminology and evidence most relevant to that specific role's emphasis.
Step 4
Add Accessibility and Design System Context If Applicable
If you have WCAG accessibility experience or design system contributions, add specific context. For accessibility: name the standard you designed to, describe the specific accessible patterns you implemented, and note whether the product passed an accessibility audit. For design systems: describe the scope (how many components, how many teams consuming, what problem it solved) and your contribution level (built from scratch, contributed components, maintained and documented). Both are increasingly required for senior UX roles.