Lead with product outcomes
Put your most recent senior design role first, then use the summary to name the product setting and the kinds of problems you solve. In each bullet, connect the design work to an observable result, such as fewer steps in a workflow, less support contact, or faster task completion. Explain the measure briefly so readers can tell whether it came from research, product analytics, or delivery data.
Show how you made decisions
Senior designers are expected to frame problems as well as deliver screens. Include examples of how interviews, analytics, support patterns, or usability sessions changed a flow or priority. State the audience and method where useful, then describe the design decision and its outcome. Avoid listing activities like “conducted research” without showing what the findings helped the team do.
Make your portfolio easy to review
Add a portfolio link near your contact details and choose case studies that show different parts of the work, such as discovery, complex interaction design, or a shared system. Explain your role, collaborators, constraints, and what shipped. Use password instructions only when needed, and remove confidential customer details, internal metrics, or work you are not authorized to share.
Describe accessibility and tools
Name tools such as Figma when they are relevant, but give more space to your design judgment and shipped work. If accessibility is part of your practice, describe the checks you performed, such as keyboard review, contrast review, or screen reader testing, and the changes that followed. List only standards or methods you can discuss confidently; a UX/UI role does not require a universal license.