UX designer resume tips
A UX resume should name a workflow and what changed for the person using it. Tool fluency and a tasteful case-study cover are not the job. Reviewers want the problem, what you learned by watching, and what you handed off to build.
Cover letter for a UX designer
What to put first
Say the product type: a consumer app, a clinical tool, an internal admin screen, a checkout. Then your role: research, flows, interface, or all of those if you truly did all of them. Put the closest workflow to the posting first.
The workflow
Name the task the person was trying to finish. A refund, a booking, a charting step, an approval. "Improved the experience" names nothing.
What you learned from
Say whether you watched people, read support notes, or worked from a stakeholder's opinion. Those are different inputs. Do not claim research you did not do.
The handoff
Describe what engineering or development received: a flow, a prototype, a spec, annotated screens. If you also built it, say so. If you did not, do not imply the code was yours.
An example line
Adapt this only where it is true for you. It is a shape for a bullet, not a claim that a particular person did this work.
Mapped the refund task in a consumer app from support notes and two observed sessions, then handed engineering a shorter flow and the empty and error states.
What to leave off
Leave off a wall of tools, case studies you cannot talk through, and outcomes you cannot connect to the change. Leave off research participants' private details. Leave off visual polish described as if it were the research.
Questions
- Do I need a case study?
- A short one you can walk through is more useful than many shallow links. The resume should still name the workflow if the link breaks.
- What if I did both research and interface design?
- Say both, and give one example of each kind of decision so it is clear you are not using the words loosely.