Replace the [bracketed] placeholders with your own details - or open it in the editor and do it there.
Dear Hiring Manager,
I am applying for the UX Designer position at [Company Name]. For the past four years I have designed software interfaces the way I believe they must be designed: starting from evidence, deciding with the team, and measuring what shipped. The project that best represents my work is a checkout redesign that raised conversion by 18 percent - and the research that got us there matters more than the screens.
Our checkout had a 70 percent abandonment rate, and the team's instinct was visual polish. I ran ten usability sessions and found the real problem: users could not tell shipping costs before entering payment details, and trust collapsed at exactly that step. I reframed the project around cost transparency, prototyped three approaches in Figma, tested them with users, and worked daily with two engineers during the build to keep the design honest against technical constraints. We shipped, measured, and iterated once more on the mobile layout.
That project is typical of how I work. I maintain a lightweight research practice - five user sessions a month, every month - so decisions never start from zero. I design in systems, contributing components back to our shared library. And I write: research summaries and decision docs short enough that people actually read them.
I am drawn to [Company Name] because your product serves users in high-stakes moments, where clarity is not a nicety but the product itself. That is the kind of design problem I want to spend my next years on.
Thank you for your consideration. My portfolio is at [portfolio URL], and I would be glad to present the checkout case in depth.
Sincerely,
[Your Name]
Run your finished letter through these checks before you send it.
The letter is built like a case study
A 70 percent abandonment rate, ten usability sessions, a reframe, three prototypes, a build, a measurement, one more iteration on mobile. The reader gets the whole arc of a project in a paragraph and knows exactly what to ask about.
It contradicts the team's first instinct
The team wanted visual polish; the sessions found that shipping costs were invisible until the payment step, and trust collapsed there. That finding is the actual evidence of craft, because anyone can claim to be user-centered and few can name what they learned.
Research appears as a habit, not a phase
Five user sessions a month, every month, so decisions never start from zero. A cadence signals a designer who will keep the practice alive after the first sprint pressure arrives, which is what separates maturity from method.
Collaboration is described mechanically
Working daily with two engineers during the build to keep the design honest against technical constraints, contributing components back to the shared library, writing decision docs short enough to be read. Those are the reasons designs ship rather than sit in a file.
The 18 percent is tied to a cause
The conversion lift is not floated as a badge; it follows a diagnosis, a change, and a measurement, so a hiring manager can trace it. A number that arrives with its mechanism survives the interview that follows.
Use the case you would present live
The project in the letter should be the one in your portfolio review, told in the same order. A letter that promises one story and a presentation that delivers another wastes the only continuity you have across the process.
Replace the metric with something you can attribute
If you cannot claim the conversion change honestly, use what you can: task success in testing, a drop in support contacts about the flow, a reduction in steps. Say what you measured and over what period, and let the smaller number be true.
State the research practice you actually run
Monthly sessions is one version. Session recordings, support ticket reviews, sales call listening, and analytics funnels are all legitimate evidence bases. Name the one you maintain and how often, because interviewers will ask you to walk through the last study.
Match the vocabulary to the team's maturity
A five-person startup and an enterprise design org read the same words differently. If the posting emphasizes design systems, accessibility, or design operations, move that sentence up and give it the space the shared-library line currently has.
Describing screens instead of decisions
I redesigned the dashboard tells a reviewer nothing about the problem, the constraint, or the alternative you rejected. The design is the visible residue of the decision, and the decision is what the interview will interrogate.
Claiming a lift you cannot explain
If you cite a conversion or retention change, be ready to say how it was tested, over what window, and what else shipped that month. An unexplained number invites the exact question you do not want to answer badly.
A portfolio of polished screens with no reasoning
Visual sets with no problem statement, no constraint, and no outcome read as visual design applied to a product. UX reviewers are looking for how you thought, and a rough sketch with a rationale often beats a perfect mockup.
Treating research as something that ended
Letters that put research in the first phase and never mention it again describe a waterfall. Show that evidence kept arriving during the build and after launch, as this example does with the mobile iteration.
Use the ones that are true of you, in the sentences where you describe the work - not as a list bolted to the end. Matching a job description's vocabulary helps a keyword filter find you; it is not what convinces the person who reads the letter afterwards.
How is the cover letter different from my portfolio case study?
The case study is the full argument with artifacts; the letter is the trailer plus the parts a case study rarely holds - how you work with engineers, what you write down, why this company. Use the same project in both so the reviewer arrives at your portfolio already oriented.
What if the redesign I am proudest of never shipped?
Say so and describe it anyway. Explain the problem, the evidence, the decision, and the reason it stopped: a roadmap change, a technical constraint, a reorganization. Unshipped work is ordinary in product design, and a candidate who narrates it honestly reads as more experienced, not less.
Should I put my portfolio password in the letter?
Yes, put it directly beside the link, in both the letter and your resume header. A reviewer working through a stack of applications will not email you for credentials. If a client agreement forbids sharing, keep that case out and lead with work you can show.
I am moving from graphic design or front-end into UX. What do I lead with?
Lead with a decision you made from evidence, whatever your title was at the time. Usability feedback that changed a layout, an analytics finding that reordered a flow, a support pattern you designed around. The transferable proof is reasoning from user behavior, not the tools you used.