What a UI/UX resume must prove
Recruiters need to understand what you can do, how you think, and where to inspect the work. Lead with a short role statement, then support it with two or three relevant case studies.
- Target role and level
- Research, interaction, visual, and prototyping skills
- Tools used in context, not as a software inventory
- Clear ownership of each project
- Link to a readable case study
Project entry template
Write each project as: problem → contribution → method → decision → result or learning. If the project is a self-directed exercise, label it honestly. Do not present a classroom brief as client work or invent business outcomes.
Example structure
Improving a service-booking flow: mapped the existing journey, interviewed three target users, tested two navigation concepts, and documented the trade-off behind the final flow.
Resume mistakes to remove
- Large tool lists without evidence
- Generic claims such as “creative team player”
- Unlabelled speculative redesigns
- Dense paragraphs that hide your contribution
- Broken portfolio links or password-protected work with no access instructions
Final checklist
Match the top third of the resume to the role, proofread every link, export a text-readable PDF, and ask someone unfamiliar with the project to explain what they think you did. Use this guide with the UI/UX case-study guide and interview question guide.
Build the work behind the resume
Review the ISS UI/UX curriculum, weekly commitment, and online delivery details.
View UI/UX Design curriculum →Editorial scope
This is a practical writing guide, not a hiring guarantee. Course projects, freelance work, and employment experience should be labelled accurately.