Dear [Hiring Manager Name],
I came across the UX Designer opening at [Company] through [where you saw it], and the line in the JD that stuck with me was “[specific phrase, e.g. ‘designers who own research end-to-end’].” That’s the work I want to be doing next.
Two pieces of my portfolio that map to your role:
- {Checkout 2.0} at [Previous Company]. Ran 8 diary studies with 24 participants over six weeks, identified three drop-off points the analytics team had missed, then shipped a redesign with our checkout PM and two engineers. Cart abandonment fell 18% in Q1; mobile completion climbed from 41% to 58%.
- {Onboarding rewrite} at [Earlier Company]. Replaced a 7-step modal with a progressive disclosure pattern after usability testing with 12 first-time users. Day-7 activation rose 22%.
The part I’m proudest of in both is not the Figma file — it’s that I worked the engineer + PM + research triad from kickoff. I wrote the research plan with the PM, walked the engineer through the prototype before handoff, and reviewed the analytics with them four weeks after launch. That loop is where I want to spend the next two years.
Happy to send a Loom walkthrough of either project if it helps you assess fit faster.
Best,
[Your name]
[Portfolio URL] · [Email] · [LinkedIn]
Expanded version · 400 words
Dear [Hiring Manager Name],
I came across the UX Designer role at [Company] on [source]. The reason I’m writing — instead of just dropping a portfolio link — is that the JD describes the exact shape of work I’ve been chasing: a designer embedded in a small product triad, owning research through ship, with the autonomy to push back on PRDs when the data says push back.
A bit of context on the last two years at [Previous Company]:
When I joined, the checkout flow had a 38% mobile abandonment rate and three competing hypotheses about why. The analytics team had instrumented every click; nobody had talked to a user in nine months. I proposed a six-week mixed-methods study — 8 diary studies, then a moderated usability round with 12 participants on the highest-friction screens. The diaries surfaced two pain points the funnel data had hidden: a silent address-validation failure on Safari, and a coupon field that looked like a price input. Neither was on the PM’s roadmap. Both became P0.
I designed the redesign in lockstep with our checkout PM and two engineers — daily 15-minute syncs during build, weekly with the wider product group. We shipped the v2 flow in March; cart abandonment dropped 18% by end of Q1 and mobile completion went from 41% to 58%. See the {Checkout 2.0} case study in my portfolio for the full process, including the two ideas we tested and killed.
Earlier at [Earlier Company], I rewrote the new-user onboarding from a 7-step modal to progressive disclosure inside the empty state. Day-7 activation rose 22% after a four-week ramp. The harder win, honestly, was convincing the founder that fewer screens was the right call — I did that with five recorded usability sessions, not a slide deck.
What I want next is the same loop — research, design, ship, measure — on a product I use myself. [Company]‘s work on [specific feature/principle] looks like exactly that. I’d love a 30-minute call to learn what’s actually at the top of the design team’s queue this quarter, and to walk you through how I’d approach it.
Best,
[Your name]
[Portfolio URL] · [Email] · [LinkedIn]
How to customize this in 20 minutes
The templates above will not land if you paste them and swap company names. They land when each paragraph is grounded in a real project from your portfolio. Here is the 20-minute customization loop most designers underuse:
- Pick the portfolio project first, not the template. Read the JD twice. Find the project in your portfolio that maps closest to the work described. That project becomes the anchor for the entire letter — every claim references it.
- Find the number. UX hiring is moving toward outcome-led portfolios; lovable.dev’s 2026 review of senior portfolios found the ones that got callbacks led every case study with a metric in the first line. If you don’t have a clean number, use a qualitative proxy: “moved from 3.2 to 4.4 average task-completion rating across 12 usability sessions” counts.
- Name the triad. Mention the engineer, the PM, and the researcher (or your own research). Hiring managers are reading for collaborative signal as much as design taste — NN/g’s research is explicit that “truthfulness about individual contributions and the parts requiring teamwork” is what separates senior candidates from mid candidates.
- Cut anything that could appear on a marketing designer’s letter. If a paragraph would still read fine for a graphic designer, brand designer, or content designer role, it’s not earning its space.
What hiring managers actually skim for
A UX hiring manager opens your application with three tabs already open and a deadline. Here is the order they scan:
- Portfolio link in the first three lines. If it’s buried at the bottom, half of them never get there. Put
[Portfolio URL] next to your name in the signature and reference at least one case study by name in the body.
- One outcome number in the first paragraph. “Cut cart abandonment 18%,” “raised activation 22%,” “shipped to 400k users.” If the first paragraph is process language with no number, the next click is the back arrow.
- Evidence you worked with engineers and PMs. A designer who can only describe the Figma file looks junior, regardless of years of experience. Name the partners. Name the handoff format. Name the post-launch review.
- A specific reference to their product. Not “I love your mission” — something a competitor’s designer couldn’t write. The component you noticed. The empty state that surprised you. The blog post about a redesign that didn’t ship.
- Brevity. NN/g’s portfolio research applies word-for-word here: hiring managers prefer scannable over comprehensive. The 250-word version is the default; expand only when the role is senior or the JD explicitly asks for depth.
Common mistakes (and the fixes)
“I’m passionate about user-centered design.” Every applicant says this. It signals nothing. Replace with the specific moment you became a UX designer — the project, the user interview that changed your mind, the metric that moved.
Listing tools instead of outcomes. “Figma, FigJam, Maze, Dovetail, Lyssna” is a resume detail, not a cover letter detail. The cover letter version is: “ran a 12-participant unmoderated study in Maze that killed our planned redesign before engineering started.”
Talking about the design without talking about the research. A senior UX letter that skips the research phase reads as a visual designer in a UX costume. Name the method. Name the sample size. Name what the research changed.
Talking about the research without talking about ship. The opposite failure. If every case study ends at “and then we shared the findings,” the hiring manager assumes nothing got built. Always close the loop: what shipped, what moved, what you’d do differently.
Generic openers. “I’m writing to apply for the UX Designer role advertised on LinkedIn” is a wasted opening line. The 30–60 second window starts at word one — open with the project, the number, or the specific thing about their product that pulled you in.
One letter, fifty applications. UX hiring managers spot a templated letter inside 10 seconds — the tell is usually a vague “your innovative approach to design.” If you cannot point at something specific on their product surface, you have not researched the company enough to write the letter yet.
The goal is not a perfect letter. The goal is a letter that gets a hiring manager to open your portfolio, find the case study you referenced, and read the first screen. Everything in the templates above is built around that single conversion.