Teams hire for the design process, not just pretty screens
UX research, interaction design, design systems, product design, and visual design overlap, but each opening may emphasize different work. Choose one target function before sending a generic portfolio to everybody.
An effective case study makes it obvious what problem you tackled, what constraints existed, what you personally changed, and what you learned. Don't imply a class concept was shipped to real customers.
Design leaders may appreciate thoughtful work but still not recruit directly. Your goal is to connect with a relevant team and find the appropriate process, not force a portfolio review from a stranger.
Make your portfolio useful to a hiring team
Give the reader enough to understand your decisions without making them hunt through dozens of screens.
Explain the user problem
Describe the users, their friction, and what evidence led to the project. Don't invent user interviews or testing.
Show alternatives and decisions
Include a meaningful tradeoff in flows, accessibility, research methods, or design system choices.
Separate your contribution
For team projects, state which research, wireframes, prototypes, or testing you directly handled and what remains confidential.
Who is worth contacting?
Different people can help in different ways. Check each person’s actual function before you send a message.
Design recruiter
Prioritize someone hiring UX, product designers, or research roles in the target organization.
Design manager or director
A functional leader may know the design skills and team structure, even if they aren't the official hiring manager.
Designer in the product area
A peer on a relevant product can offer context and may know where to direct the application.
Five steps you can take
- 01
Select one design direction
Distinguish between product design, UX research, content design, and design systems when choosing job postings.
- 02
Pick your strongest matching case study
Use one project that matches the employer's product or user problem, with an obvious explanation of your contribution.
- 03
Make the portfolio easy to skim
Confirm links and mobile access. Use clear headings and avoid long introductions before the actual work.
- 04
Find design-specific contacts
Research the design recruiting lane and a leader or peer on the relevant product team.
- 05
Ask a specific, modest question
Introduce the work you enjoy, share a relevant case study if suitable, and ask who handles hiring for those roles.
A message that sounds like a person
This is an illustrative example, not a verified contact or a promise of an opening. Tailor it to your own truthful experience.
What to avoid
- Sending a portfolio with no explanation of the work
- Claiming a fictional redesign was shipped by the company
- Overstating your role in a team case study
- Demanding free portfolio feedback from people you've just met
Questions people ask
How many projects should my portfolio include?
Prioritize a few relevant, comprehensible case studies over a large gallery. Quality and relevance matter more than a fixed count.
Is a UI mockup enough?
Some visual roles emphasize craft, but many UX/product roles also evaluate reasoning, research, constraints, and collaboration.
Can I include NDA work?
Only publish what you're authorized to disclose. Use a permitted summary or an independent project instead.
Who should I message first?
A design recruiter is useful for process; a relevant design peer or leader can help with team context. Verify their function first.