Skip to content

Product & Design · Cover Letter

UX Designer Cover Letter Example

A UX cover letter should prove you run research with rigor and translate insights into shipped design — not that you love creating beautiful experiences. This example shows how to lead with a specific research finding, tie it to a design decision, and quantify the outcome.

The full cover letter

[Your Name] · [Email] · [Phone] · [City, ST]

April 21, 2026

Dear Hiring Manager,

I'm applying for the Senior UX Designer role on your Platform Experience team. The case study your team posted on the disaster-recovery onboarding redesign — especially the part about discovering that 60% of admins couldn't articulate why they were backing up data — is the kind of research-first thinking I've been trying to push at Atlassian, and I'd love to keep doing that kind of work on your team.

At Atlassian I led UX for the Jira admin settings area, a surface used by 180,000 workspace admins and one that historically had a 38% support-ticket rate on permissions alone. I ran a mixed-method discovery over six weeks — 18 moderated interviews, a 1,400-admin Maze unmoderated study, and a diary study with 12 enterprise admins — which surfaced that admins weren't confused by our permissions model; they were confused by the vocabulary. 'Project role' and 'group' looked identical in our UI but meant totally different things. I redesigned the information architecture around a decision tree (not a taxonomy), prototyped it in Figma with variables-driven state, and validated it through three rounds of moderated usability testing. After launch, permissions-related support tickets dropped 44% and admin task completion time on new permission setup moved from 7.2 minutes to 2.4.

Before Atlassian I was the second designer at a consumer health startup (Eight Sleep) where I owned the end-to-end design for the mobile app — research, interaction design, visual design, motion, and the accessibility audit. That generalist foundation, and specifically the habit of running research before I open Figma, is what I'd bring here. Your team's decision to embed a researcher inside every design pod — rather than siloing research into its own function — is the structure I've been lobbying for at Atlassian, and it's the main reason I'm applying. Portfolio with process writeups is at mary-designer.com/work.

I'd love to walk you through the Jira admin research artifacts and hear how your team is approaching the decision-tree-vs-taxonomy problem on your own permissions work. I can share the full research report or jump on a portfolio review whenever fits your schedule.

Sincerely,

[Your Name]

Why each passage works

Line-by-line breakdown of the sentences that earn the letter its space.

“the part about discovering that 60% of admins couldn't articulate why they were backing up data — is the kind of research-first thinking I've been trying to push at Atlassian”

Why it works: References a specific, unusual research finding from the company's case study and aligns with the candidate's own advocacy. This is a research-to-research handshake — the highest-value opener for a UX role.

“I ran a mixed-method discovery over six weeks — 18 moderated interviews, a 1,400-admin Maze unmoderated study, and a diary study with 12 enterprise admins”

Why it works: Names three distinct research methods with specific sample sizes. UX hiring managers look for rigor, and the mix of moderated, unmoderated, and longitudinal research signals a mature research practice.

“admins weren't confused by our permissions model; they were confused by the vocabulary. 'Project role' and 'group' looked identical in our UI but meant totally different things.”

Why it works: A specific, concrete research insight that reframes the problem. The detail about vocabulary vs model shows the candidate can distinguish symptoms from root causes — one of the hardest UX skills.

“permissions-related support tickets dropped 44% and admin task completion time on new permission setup moved from 7.2 minutes to 2.4.”

Why it works: Two outcome metrics tied directly to the research-informed redesign. Support tickets are a business-legible metric; task completion is a UX-native metric. Including both signals the candidate speaks to both audiences.

“Your team's decision to embed a researcher inside every design pod — rather than siloing research into its own function — is the structure I've been lobbying for at Atlassian.”

Why it works: Makes an organizational-level observation and takes a position. Shows the candidate thinks about how design works, not just what to design. Distinguishes senior candidates from mid-level ones.

Strong phrasing

  • “I led UX for the Jira admin settings area, a surface used by 180,000 workspace admins.”
  • “I ran a mixed-method discovery over six weeks — 18 moderated interviews, a 1,400-admin Maze unmoderated study, and a diary study with 12 enterprise admins.”
  • “I redesigned the information architecture around a decision tree (not a taxonomy).”
  • “I'd love to walk you through the Jira admin research artifacts.”

Weak phrasing to avoid

  • “I am a passionate UX designer who loves creating beautiful and intuitive experiences.”
  • “I am skilled in Figma, Sketch, Adobe XD, InVision, and Miro.”
  • “I am a user-centered designer who cares deeply about solving user problems.”
  • “I have strong collaboration skills and work well with cross-functional teams.”
  • “I believe good design has the power to change people's lives.”

Writing tips for this role

  • ·Lead with a research finding, not a design output. UX is a research-led discipline; the insight is more interesting than the pixel.
  • ·Name three methods. Moderated interviews, unmoderated usability, diary studies, surveys, card sorts — listing three signals you run a real research program, not just occasional tests.
  • ·Tie your design to a business-legible metric. Support ticket reduction, conversion lift, NPS movement, task-completion time. 'Delightful experience' is not a metric.
  • ·Include your portfolio URL in the opening or closing paragraph. Not in the footer. For UX roles the portfolio is half the application; make it impossible to miss.
  • ·Reference the company's design or research culture explicitly — how they structure research, which studies they've published, what their design system looks like. Shows organizational curiosity.

Common mistakes

Tool-first identity

'Proficient in Figma, Sketch, Adobe XD, Miro, Axure, Framer' reads as a skills dump. Every UX designer in the pool knows Figma. Make the letter about what you designed in it, not the tool itself.

No research rigor

UX letters that describe only design outputs (wireframes, mockups, prototypes) without research methodology read as UI-decorator work. Even one sentence on your research practice separates you from the 'visual UX' crowd.

Portfolio buried at the bottom

For UX roles, the portfolio is the primary artifact. Link to it in the opening or early-body paragraph, not in a footer the hiring manager might miss.

Design adjectives instead of outcomes

'Clean, intuitive, delightful, elegant, minimal' are all opinions. Replace with metrics: task completion time, error rate, NPS, support-ticket deflection, conversion lift. Designers who measure their own work are rare and memorable.

No accessibility mention

A11y is core UX practice in 2026, not a specialist area. One sentence on WCAG, screen-reader testing, or cognitive-accessibility work signals a complete practice rather than a partial one.

FAQ

Do UX designers need a cover letter if the portfolio is strong?

At most companies, yes. The portfolio shows craft; the cover letter shows judgment, communication, and fit. A well-written letter is often what gets a borderline portfolio a first interview. Don't skip it unless the posting explicitly says no cover letter.

Should I describe my process framework (Double Diamond, IDEO, etc.) in my cover letter?

No — every designer knows those frameworks and citing them reads as junior. Instead, describe the specific process you used on one project. 'I ran discovery for six weeks, then prototyped, then did three rounds of moderated testing' is more credible than 'I follow the Double Diamond.'

How do I handle the UX designer vs product designer title question?

Match the letter to the posting's title. If the role is UX Designer, lead with research depth and usability testing. If it's Product Designer, lead with end-to-end ownership and business outcomes. The titles overlap but the emphasis shifts.

Should I mention AI design tools (Figma AI, Galileo, Uizard) in my cover letter?

Only if you have a specific, concrete use case. 'I use Figma AI to generate first-draft layouts I then refine' is fine. Vague mentions of 'AI-augmented design' signal you're trying to seem current. Senior designers describe craft first, tools second.

Related UX Designer Resources

UX Designer Resume ExampleUX Designer Interview QuestionsUX Designer Salary Guide

Write your UX Designer cover letter in minutes

Rolevanta generates a tailored cover letter from your resume and the exact job description. Edit, download as PDF, apply.

Write Cover Letter Free