For designers, the cover letter's job is to earn the click through to the portfolio — which means it should point to one specific project and the problem it solved, not describe your general design philosophy.
Example cover letter
I noticed your team is rethinking onboarding for a technical audience, which is almost exactly the problem I solved last year — redesigning our product's onboarding flow after 25 usability sessions revealed a confusing setup step, which lifted activation by 24% once fixed.
That project is the second case study in my portfolio (linked below), and it's representative of how I like to work: research first, then design, then validate with real usage data rather than opinion. I also built and documented the design system now used across three product teams at my company, which taught me a lot about designing for consistency at scale rather than one screen at a time — something your posting's mention of a growing multi-product suite suggests you're navigating too.
I'd love to walk you through that case study and hear more about the specific onboarding challenges your team is facing.
Common mistakes to avoid
- Not linking directly to the portfolio, or linking to one that isn't current — this is often the first thing a hiring manager checks.
- Describing your design philosophy in the abstract instead of pointing to one specific, provable project.
- Listing tools (Figma, Sketch) as if they were the differentiator, when process and outcomes are what actually stand out.
Frequently asked questions
How prominently should the portfolio link appear?
Right in the opening or body paragraph where it's directly relevant, not just in your signature — for design roles it's often the single most important link in the whole letter.
Should I mention specific design tools in the cover letter?
Only briefly if at all — the letter is better spent on the story and outcome of a project; save the tools list for the resume's skills section.