Does a UX designer's cover letter actually get read?

Where it actually lands

For most UX roles, the cover letter is the third thing a hiring manager looks at, if they look at it at all. The first thing is your portfolio link. The second is often your resume, scanned for titles, tools, and whether you've shipped anything at a company they recognise. By the time someone reaches the letter, they've usually already formed a view from the case studies. The letter either confirms it or it doesn't move the needle much either way.

This is different from fields where the letter is the primary writing sample. In UX, the primary writing sample is the case study — the way you frame a problem, show the research, and explain a decision you made under constraint. If your portfolio doesn't do that, no cover letter fixes it. If it does, the letter has less to prove than you think.

Where the letter still earns its place: smaller companies and startups where the hiring manager reads every application personally, roles that are ambiguous from the job title (is this "product designer" doing UI, research, or both?), and career changes — moving from graphic design, from front-end development, from a bootcamp into a first UX role — where the portfolio alone doesn't explain the trajectory. In those cases, someone has to read a sentence that says why you're a plausible hire, and the cover letter is the only place to put it.

At companies running UX hiring through Greenhouse, Lever, or Workday with a recruiter doing first-pass triage on volume, the letter is frequently not opened before a decision is made on portfolio and resume. That's not a guess about any specific employer's software — it's just how screening works when a role gets hundreds of applicants and one person has an afternoon. Nobody has published reliable figures on how often UX cover letters get read, and anyone quoting a percentage is making it up. What's true across the field is that the portfolio review happens first, structurally, because it's the fastest way to eliminate people.

The two things it has to answer

If you accept that the letter gets read some of the time and skimmed the rest, write it to do two jobs and nothing else.

Why this product, this problem, or this user base — specifically. Not "I'm passionate about creating user-centred experiences," which every hiring manager in this field has read several hundred times and which is true of literally every UX designer who has ever applied anywhere. Say something that shows you looked at what they actually build: a fintech onboarding flow, a clinical scheduling tool, a B2B admin console, a checkout with a churn problem. If you have relevant context — you've designed for regulated industries, you've worked on a product with a similar user base, you've dealt with the same kind of technical constraint (a legacy design system, a platform with no native components) — that's the sentence that does work. It tells the hiring manager you're not sending the same letter to forty companies, which most applicants are.

How you think, not just what you shipped. The portfolio shows the artefact — the flow, the screens, the prototype. It often doesn't show the reasoning under time pressure: why you chose to run five moderated usability sessions instead of a survey, why you pushed back on a stakeholder's request, how you handled a case where the research contradicted what the PM wanted to build. One sentence pointing to a specific case study and naming the decision you want them to notice — "the second case study on my site is about a redesign we shipped without user testing, because of a launch deadline, and what we did instead to reduce risk" — does more than a paragraph of adjectives. It also directs their attention, which matters if they're skimming a portfolio with six projects on it.

That's it. Not your five-year plan, not a list of tools (the resume covers Figma, FigJam, Sketch, Maze, UserTesting, whatever design system you've worked in), not a restatement of your job history. Two things: why this, and how you think.

What to leave out

A few things that show up constantly in UX cover letters and do nothing:

• "I'm passionate about solving problems for users." So is everyone else applying. It's not wrong, it's just not information.
• A summary of your resume. If the letter repeats your job titles and dates, it's wasted space; the hiring manager has the resume open in the other tab.
• Design philosophy statements — "I believe good design is invisible," or similar. These read as filler because they are filler; they don't tell anyone what you'd do differently on their product.
• Claiming ownership you didn't have. If you were one of three designers on a project, say that. UX hiring managers have run large teams and can usually tell when someone's case study language is doing more work than their actual role did. It surfaces badly in the interview if it doesn't surface in the letter.
• A tools list. Competence in Figma, prototyping, and whatever research tools are standard belongs on the resume. Naming them in the letter reads as padding.

Format, in practice

Keep it short enough that it fits above the fold in whatever system they're reading it in — three or four short paragraphs, not a page. Address it to a name if you can find one; "Dear Hiring Manager" costs you nothing but signals you didn't check. If the job posting names a specific product area, team, or problem ("we're rebuilding our design system," "this role owns onboarding"), use that exact language once — it shows you read the advert rather than a template of it, and it's one of the few things applicant tracking systems can match on if a human hasn't opened the file yet.

End with something concrete and low-effort for the reader: which case study to open first and why, or a one-line offer to walk through your process on a call. Don't end with a request for consideration of your candidacy — every letter ends with some version of that, and it's the least memorable sentence in the document.

Where the letter genuinely doesn't matter much

Be honest with yourself about this. If you're applying to a large tech company with a formal UX hiring pipeline — portfolio review, then a recruiter screen, then a design exercise or presentation — the letter is unlikely to change the outcome of the first two stages. What changes it is the portfolio: the clarity of the case studies, the evidence of process (research method, iteration, what you'd do differently), and whether the work matches the seniority the role is asking for. A weak portfolio with an excellent letter doesn't get through; a strong portfolio with a mediocre letter usually does.

Where the letter matters more is exactly the situations named above: small teams, ambiguous titles, career changes, or when your background needs one sentence of translation before the case studies make sense. In those situations it's worth the twenty minutes. In the rest, that twenty minutes is often better spent tightening the one case study that's carrying the whole application.

What to do next

Before you write another cover letter, open your strongest case study and read it as if you'd never met yourself. If it doesn't clearly show a problem, a method, a decision, and an outcome, fix that first — it will do more for your application rate than any letter will. Once the portfolio is doing its job, write the letter to answer the two questions above and stop. If what's actually slowing you down is the volume of tailoring this takes across different companies and job titles, that's a mechanical problem rather than a writing one — jobmarket.pro reads each advert and drafts the application from a single profile of your work, so the tailoring happens per job without you rewriting it each time.