How to Tailor Your UX Portfolio to Each Job Without Rebuilding It
Quick answer: To create a job-specific UX portfolio without rebuilding it, split it into a fixed core and a swappable layer. The core is your intro, two anchor case studies and your contact details, written once. The swappable layer is the headline line, which case study comes first, a third case study chosen for the role, and the order of your skills. Keep two to four versions, one per kind of role, and spend about ten minutes per application on order and wording. UX postings differ more than most designers expect: in the 1,744 live UX postings we read, two picked at random shared no emphasis at all 4 times in 10. To see which UX roles your work already fits, Career Mode matches your profile against live postings.
Image credit: Pixabay / Pexels
Where the numbers come from: this analysis uses Seera's job index as it stood on November 3, 2026: 402,956 open roles that 36,000+ employers published on their own career sites. From those, we took the 1,744 written in English whose job title is a UX role, from UX, UI/UX and product designer to interaction, service and experience designers and UX researchers. Industrial and other physical-product designers are not included. Each posting was tagged with the emphases it names anywhere in its text, such as design systems, AI products or a regulated domain like fintech, using keyword patterns we checked by hand against sample postings. Benefits wording ("medical, dental", "health insurance") does not count as a domain. Because the tags come from keywords, treat every share as approximate. Only totals are published; no employer is named.
Key Takeaways
| Question | Short answer |
|---|---|
| Do UX postings ask for the same thing? | No. 547 different combinations of emphasis across 1,596 postings; the most common one covers 3.4% |
| Two postings picked at random | Share no emphasis 42% of the time; identical emphases 1.3% |
| Most common emphases | Design systems 53%, AI products 41%, research-led work 36% |
| What changes with seniority | Design systems 48% mid → 67% staff/principal; AI products 34% → 59% |
| A new portfolio for every job? | No: one core, two to four versions, ten minutes per application |
| What to change per application | Headline line, first case study, third case study, skills order |
Table of Contents
- Why one fixed UX portfolio fits few jobs
- The core-and-swap UX portfolio structure
- Read the posting: which case study to lead with
- How many versions you actually need
- Step by step: create a job-specific UX portfolio
- Tailor the portfolio presentation for the interview
- UX portfolio review before you send it
- Doing this on Seera
- Frequently Asked Questions
- Useful sources and further reading
Why One Fixed UX Portfolio Fits Few Jobs
"UX designer" sounds like one job. Read a few hundred postings and it splits into many: a design-systems role at a SaaS company, a designer for an AI assistant, a researcher-heavy role in public services, a checkout specialist at a retailer. Here is how often each emphasis shows up in live UX postings, by the seniority in the title:
| Postings that name… | Mid | Senior | Staff / principal | All UX |
|---|---|---|---|---|
| Design systems or a component library | 47.7% | 55.7% | 67.0% | 53.4% |
| AI products (AI-powered or AI-native features, LLMs, conversational design) | 34.2% | 40.8% | 59.1% | 40.7% |
| Research you run yourself (usability testing, user interviews) | 37.6% | 36.4% | 28.1% | 35.7% |
| Visual, motion or interaction polish | 32.9% | 35.4% | 35.5% | 33.9% |
| B2B, enterprise or SaaS, complex workflows | 30.0% | 34.3% | 39.4% | 33.2% |
| Dashboards or data visualisation | 19.1% | 17.4% | 18.2% | 17.8% |
| Mobile apps (iOS, Android) | 19.3% | 18.6% | 11.8% | 17.6% |
| Growth: A/B tests, conversion, onboarding | 13.8% | 17.0% | 11.3% | 15.2% |
| Accessibility (WCAG, inclusive design) | 13.4% | 15.7% | 15.8% | 14.5% |
| Fintech, banking or payments | 12.1% | 13.8% | 21.2% | 13.8% |
| E-commerce, checkout or marketplaces | 9.9% | 15.2% | 11.8% | 12.6% |
| Health: clinical, patients, health tech | 7.8% | 7.4% | 7.4% | 7.3% |
| Postings | 644 | 741 | 203 | 1,744 |
Titles with no seniority word are counted as mid-level. Intern and junior postings are counted in All UX only, because there are too few of them to split. Three findings matter for your portfolio:
- Almost every posting has its own mix. The typical posting names three of these emphases, and 56% name three or more. Across the 1,596 postings that name at least one, we counted 547 different combinations. The most common combination covers just 3.4% of postings, and the five most common together cover 13.3%.
- Two postings rarely want the same portfolio. We drew 200,000 random pairs of UX postings. In 42% of pairs, the two postings shared no emphasis at all, and only 1.3% had identical sets. A portfolio ordered for one posting is, more often than not, ordered wrong for the next one you open.
- Seniority moves the target. Design systems rise from about half of mid-level postings to two thirds of staff and principal ones, and AI products from about a third to nearly 6 in 10. Research you run yourself goes the other way, from 38% to 28%, as senior roles ask you to lead research more than do it.
None of this means a separate portfolio per application. The overlap is real too: the same handful of emphases come back again and again. It means the order and the lead case study should change, while most of the content stays put.
The Core-and-Swap UX Portfolio Structure
Think of your UX portfolio as three layers that change at different speeds.
| Layer | What it holds | How often it changes |
|---|---|---|
| Core | Your name and role, a short about section, two anchor case studies that show your broadest strengths, education, contact, resume link | Rarely: when you finish a new project |
| Track | A headline line naming the kind of role (for example "Product designer for B2B and AI tools"), the lead case study, a third case study chosen for that track, the order of your skills | Once per kind of role: two to four versions |
| Application | The order of the case studies, one domain word in the intro, a short note in your application that points to the most relevant case study | Every application, about ten minutes |
The anchor case studies do most of the work. Pick two that each touch several emphases at once: a design-system project that also shipped in a B2B product, or a research-led redesign that moved a conversion number. Those two stay in every version. The swappable third case study is where you show depth in whatever the posting cares about most.
Write each case study so its first screen stands alone: the result, the problem and your role in the opening lines. Then moving it up or down the page costs nothing, because no case study depends on the one before it for context.
Read the Posting: Which Case Study to Lead With
Spend five minutes on the posting before you touch the portfolio. Start with the job title, the opening paragraph and the first few requirements, and note which emphasis comes up first. Of the postings we read that name at least one emphasis, the one mentioned first is AI products in 24% of cases, research in 12%, design systems in 12%, visual polish in 10% and B2B workflows in 8%. Then match what you find to the case study you lead with:
| If the posting stresses… | Lead with a case study that shows… |
|---|---|
| Design systems | Components or tokens you built or governed, how many teams adopted them, and what got faster |
| AI products | Designing for uncertain output: how users see confidence, correct mistakes and stay in control |
| Research | A finding that changed the direction of a project, and the method that produced it |
| Visual or motion polish | Final UI and interaction details, ideally a short prototype recording |
| B2B, enterprise or SaaS | A complex workflow you simplified, with roles, permissions or power users in the picture |
| Dashboards or data | The decision the dashboard supports and how you chose what to show and what to leave out |
| Mobile | Platform conventions, small-screen trade-offs and how the design handled offline or interrupted use |
| Growth or experiments | An experiment with its hypothesis, the variant and the measured result, including tests that lost |
| Accessibility | The standard you designed to, what an audit found and what you changed |
| Fintech, health or another regulated domain | How you designed within the rules: compliance reviews, consent, error states where mistakes are costly |
| E-commerce | Checkout, search or product pages, and what happened to conversion or drop-off |
If a posting stresses something none of your case studies shows, say so plainly in a short line rather than stretching a project to fit. A posting with a long list of emphases you cannot match is also a signal: the five-minute eligibility check is a quick way to judge whether the role is worth an application.
To see which skills and requirements one specific posting names, paste it with your resume into the free resume match checker. It shows the named skills your resume is missing, which is a quick way to spot what the posting cares about before you choose the lead case study.
How Many Versions You Actually Need
Most designers need two to four versions, not one per application. The five emphases that most often come first in a posting (AI products, research, design systems, visual polish and B2B workflows) are the first one mentioned in about two thirds of the UX postings we read that name any emphasis. If you apply mostly to two of those, two versions cover most of your applications.
Building a fresh portfolio for every job sounds thorough, but it rarely pays. In a Nielsen Norman Group interview with a design recruiter, the article puts it this way:
"Tailoring every resume and portfolio you send out sounds ideal, but Hang cautions that doing so for every job isn’t always sustainable or the most strategic use of your time."
The same article recommends deciding who your primary audience is and focusing there. In portfolio terms: choose the tracks you are aiming for, build one version per track, and keep per-application changes small.
Step by Step: Create a Job-Specific UX Portfolio
- Collect ten postings you would apply to. List the emphases each one names, using the rows in the table above.
- Group them into tracks. Two to four groups that share a lead emphasis, for example "AI and B2B tools" and "research-led consumer products".
- Pick your two anchor case studies. The ones that touch the most emphases across all your tracks. These go in every version.
- Pick one swap case study per track. The project that shows the track's lead emphasis most directly.
- Rewrite the opening lines of each case study so the result, the problem and your role come first and the case study makes sense on its own.
- Build one version per track. Change the headline line, the case-study order and the skills order. Leave the rest alone.
- Per application, spend ten minutes. Check the order against the posting, add one domain word to the intro if it fits, and point to the most relevant case study in your application note.
- Keep a simple log. Which version went to which posting, so a recruiter's follow-up question never catches you looking at the wrong one.
Tailor the Portfolio Presentation for the Interview
The interview is where the job-specific version matters most, because you choose what to show and for how long. A portfolio presentation usually covers one or two projects in depth, so pick them the same way you picked the lead case study:
- Open with the project closest to the posting's first emphasis. If the posting led with design systems, so does your presentation, even if your favourite project is a mobile app.
- Restate the job in your first minute. One sentence that connects the role to the project you are about to show ("You're building AI features for finance teams; here is how I designed for uncertain output in a reporting tool").
- Show the decision, not just the deliverable. Two options you weighed, why you picked one, and what happened after launch.
- Keep a backup project ready. Interviewers often ask "anything with more research?" or "anything on mobile?". The swap case studies from your other tracks are your answer.
UX Portfolio Review Before You Send It
Before each application, run a two-minute review with the posting open next to the portfolio:
- ✅ The headline line uses the posting's own words for the role or the domain.
- ✅ The first case study answers the posting's first emphasis.
- ✅ Each case study states the result, the problem and your role in its opening lines.
- ✅ Every link works on a phone, including prototypes and any password-protected pages.
- ✅ Every role and project is dated, so a reader can tell how recent the work is.
- ❌ No case study still describes the last company's domain in its intro.
- ❌ No skill is listed that the case studies never show.
Dates matter more than they look. Readers estimate your experience from them, and so do matching tools: when we tested AI job recommendations, removing the dates made a profile count as zero years of experience.
Doing This on Seera
Seera builds a portfolio from your resume in about a minute. For the core-and-swap method, this is what it does and doesn't do today:
- Reorder and hide whole sections on every template, from the Customize panel: move Projects above Experience for a portfolio-led application, or hide Education for a senior role.
- Case-study order: the Dossier template has up and down arrows for individual projects. On the other templates, projects appear in the order they are entered, so put the lead case study first when you edit.
- One version per track: the free plan has one portfolio; Pro (€5.99 a month, or €4.99 a month billed yearly) has no limit, so each track can have its own address. There is no duplicate button yet, so each version starts from a resume upload and is then edited.
- Which roles your work fits: Career Mode matches your profile against live jobs from employers' own career sites, which tells you which tracks to build first. It costs €29.99 once for 90 days and includes Pro.
If you are still choosing where to host the portfolio, our check of free UX portfolio website builders against UX job postings compares six free plans, and the UX portfolio builders roundup covers the paid options.
Pick your tracks from live UX roles that match you →
Frequently Asked Questions
What is a job-specific UX portfolio?
A version of your UX portfolio arranged for one kind of role: the case study that best matches the posting comes first, the headline line names the role or domain, and the skills are ordered to match. Most of the content underneath is shared between versions. In 1,744 live UX postings we read, the most common combination of emphases covered only 3.4% of postings, which is why the order matters more than most designers expect.
Do I need a different UX portfolio for every job application?
No. Keep one core with two anchor case studies, build two to four versions for the kinds of role you apply to most, and spend about ten minutes per application on order and wording. The five emphases most often mentioned first in a posting (AI products, research, design systems, visual polish and B2B workflows) open about two thirds of the UX postings that name any emphasis, so a few versions cover most applications.
Which case study should come first in a UX portfolio?
The one that answers the posting's first emphasis. If the posting opens with design systems, lead with a component or design-system project; if it opens with AI products, lead with work on uncertain or generated output. Among the UX postings we read that name an emphasis, AI products came first in 24%, and research and design systems in about 12% each.
How do I prepare a UX portfolio presentation for a specific job?
Pick one or two projects that match the posting's first emphasis, connect the role to the project in your first minute, show the decision you made and what happened after launch, and keep a backup project from another track ready for follow-up questions such as "anything with more research?".
How do I review my UX portfolio before applying?
Open the posting next to the portfolio and check five things: the headline uses the posting's words for the role, the first case study answers its first emphasis, each case study opens with the result and your role, every link works on a phone, and every role is dated. Remove any skill your case studies never show.
Related Reading
- Best Free UX Portfolio Website Builders, Checked Against 1,750 UX Job Postings
- 7 Best UX Portfolio Builders in 2026 (for Case Studies)
- Handshake UX Portfolio Upload Requirements and the URL Workaround
- Product Designer Portfolio Example
- Should You Apply? How to Check Your Eligibility for a Job in Five Minutes
- How to Check Your Resume Against a Live Job Posting
- AI Job Search That Starts From Your Resume
- How to Match Your Portfolio to a Job Description (With AI)
Useful sources and further reading
- Nielsen Norman Group: UX Hiring: Insights from a Design Recruiter (Megan Chan, January 16, 2026) — a design recruiter on why UX applications get rejected and where to focus effort
- Seera: AI Job Search — Career Mode matches your resume and portfolio to live jobs from employers' own career sites
- Seera: Resume Match Checker — free check of your resume against one job description
- Seera job index, read November 3, 2026 — 402,956 open postings from 36,000+ employers' career sites; 1,744 English-language UX and product-design postings tagged by emphasis, by level (aggregate counts only; no employer named)
- Seera: Editorial standards — how we use our own data and write about our product