UX Designer Job Description Template 2026

UX Designer Job Description Template 2026

Last updated: April 26, 2026

A UX designer researches user needs, builds wireframes and prototypes in Figma, runs usability testing, and partners with product and engineering to ship interfaces that work, with U.S. base salaries running $85,000 to $115,000 for mid-level and $120,000 to $155,000 for senior roles in 2026. Below is a job description you can paste, edit, and post tomorrow, salary numbers from five independent sources with the variance explained, and the section most other templates skip: the parts of the JD that quietly screen out the candidates you actually want.

Gregg Flecke, Senior Talent Acquisition Partner at KORE1. Almost thirty years placing technology talent. UX is one of the roles where the resume volume looks generous and the qualified pipeline almost never does. Hiring managers who lean on a stock template usually get fifty applicants in the first week. The portfolios are fine. The portfolios are also interchangeable. By week three the team is reading the same case studies told the same way, and the search has lost its momentum without anybody quite noticing. Quietly. No alarms.

The fix isn’t a longer JD. Most of the postings I see are too long already. The fix is being specific about the kind of designer the team needs, the product surface they’ll own, and what a good first ninety days looks like.

One disclosure. KORE1 places UX designers through our digital and creative staffing practice, and we earn a fee when a hire happens through us. The template below works whether you call us or not.

What Is a UX Designer?

A UX designer owns the experience of using a product. Not the look, exactly. The behavior. What happens when someone clicks. What they expect to happen. What goes wrong when those two don’t match, and how to fix it before launch instead of in a Slack thread the morning after. Different problem.

The day-to-day is a mix of research, design, and testing. Interviews with real users. Wireframes and clickable prototypes in Figma. Usability sessions where five people in a row trip on the same step, which tells you something the analytics never would. Design system contributions. Handoff notes for the engineers who’ll build the thing. The order of those tasks shifts depending on the team and the week, but the core mandate is constant: make the product easier to use, and prove it with evidence.

UX, UI, and product designer are not the same job, although the titles get used interchangeably in postings and even on LinkedIn profiles. UI designer is closer to visual craft: typography, color, component states, motion. UX designer is closer to behavior and research: flows, friction, mental models. Product designer usually means a hybrid of both with a heavier strategy lean. At a 12-person startup, one person does all three. At a Series C company, those are three separate hires reporting to a design lead. A JD that lists every responsibility from each of those roles is what you write when nobody on the hiring side has decided which one they actually need.

The 2026 version of this role looks different in two ways that matter for the JD. First, AI tools are now part of the workflow. Most product designers I talk to use a mix of generative tools alongside Figma for early ideation, asset generation, and copy testing. A candidate who has never opened any of them is not disqualified, but a candidate with a real point of view on which AI tools belong inside a design process and which create more cleanup than they save is much more valuable to a team trying to ship faster. Real opinions matter here. Second, accessibility has moved from a nice-to-have section at the bottom of a checklist to a baseline expectation. The DOJ’s April 2024 update to ADA Title II rules made WCAG 2.1 AA effectively the floor for state and local government digital services, and private-sector legal exposure on accessibility complaints has been climbing for several years. A senior UX designer who can’t speak fluently about contrast, focus order, and screen reader testing is going to struggle on any team building for a regulated industry.

UX Designer Job Description Template

This template covers a full-time mid-level to senior UX designer at a product company with an existing design team. Adjust scope, reporting structure, and tool requirements for solo-designer roles or for in-house design teams at non-product companies. The compensation range reflects mid-level to senior; see the salary section below for level-by-level context.

Core UX Designer Responsibilities in Depth

The bullets above are the surface. Here is what the job actually looks like once a designer is on the team, because the gap between the JD and the day-to-day is where most mismatches surface.

Research is where the strongest UX designers separate themselves from the rest. Most candidates can run a usability test. Fewer can decide which kind of research the team needs in this particular sprint, scope it down to something feasible, recruit five reasonable participants, and turn the results into a one-page document the engineering team will actually read. The designers who do that well almost always can describe a specific moment when their research changed a roadmap decision. Not a generic answer. A real one. Ask candidates for a study they ran where the finding contradicted what the team expected, and listen for what they did next. The vague answers tell you something. So do the specific ones. Both are signal.

Prototyping is the other place where seniority shows up clearly. A junior designer hands off a static screen mock and waits for feedback. A senior designer ships a clickable prototype that already addresses the three obvious objections and surfaces the two non-obvious tradeoffs the team needs to discuss. Same Figma file. Different posture. The seniority is in what’s already been considered before the review meeting starts. A useful interview question: ask the candidate to walk you through the most ambitious prototype they’ve ever built, and pay attention to whether they describe the interactions or the rationale.

Design system work is the responsibility most often missing from JDs that should include it. If your team has a design system, every UX designer on the team is going to spend some percentage of their time using, extending, or arguing with it. A candidate who has never worked inside a real design system tends to design as if every screen is greenfield. That posture creates real cost downstream: components proliferate, the engineering team rebuilds the same modal three different ways, and the design system maintainer pulls late nights three weeks before a major release reconciling everything back together. If your design system is mature, hire for someone who has worked inside one. If it’s nascent, hire for someone who has built one. Either way, the JD should say so. Be explicit.

Accessibility is the responsibility where I see the biggest skill gap in the candidate pool, even at the senior level. A surprising number of designers with eight years of experience can’t tell you what a focus indicator should look like or how a screen reader announces a modal opening. That gap was tolerable in 2018. It is not tolerable now. The designers who can speak fluently to WCAG 2.1 AA, who know which AAA criteria are practical to hit and which are not, and who design with assistive tech assumptions baked in from the start are the ones who keep the team out of accessibility remediation cycles that nobody enjoys and nobody budgets for. If the role is at a regulated company, the JD should make this requirement explicit. If it’s at a startup, the JD should at least signal that you’ll be testing for it in the interview.

UX Designer Salary in 2026

Five sources. Real variance between them. Here’s what each one is actually measuring.

The BLS number lumps UX designers in with web developers and digital interface designers, which dilutes the median. PayScale skews early-career and self-reported, which pulls its number down. Glassdoor reflects a wide cross-section that probably matches what the average mid-level designer actually earns at a non-FAANG company. Built In trends toward funded tech, which is why it lands a bit higher. ZipRecruiter’s senior figure is the most useful comparison for any role posted at the senior level.

By level and market, the working ranges I see in active KORE1 searches:

• Junior (0–2 years): $70,000 to $90,000 base in most U.S. metros. New York, San Francisco, Seattle, and the Boston corridor run higher. Junior compensation in 2026 is more compressed than the rest of the market because the entry-level pool is much larger than the senior pool.
• Mid-level (3–5 years): $85,000 to $115,000 base nationally. Tier-one tech metros add 15 to 25 percent. Industry premium for fintech and healthcare regulated work is real but smaller than candidates often expect.
• Senior (5+ years): $120,000 to $155,000 base. Lead and staff levels run higher, with total comp in the $170,000 to $220,000 range at well-funded companies in major markets.
• Lead / Principal: $150,000 to $200,000+ base. At this level, total comp including equity and bonus often clears $250,000 at growth-stage and public companies.

For a market-by-market breakdown including remote-only versus hybrid premium, the specific industry adjustments for healthcare and fintech, and the level-by-level total comp ranges for major metros, see the KORE1 UX Designer Salary Guide, which is updated quarterly against active KORE1 placement data.

What Most UX Designer Job Descriptions Get Wrong

Four patterns come up across nearly every UX search where the initial posting didn’t produce the candidates the team needed.

The first is the everything-designer JD. The job description lists user research, visual design, motion, prototyping, design systems, content design, and front-end coding, all under one role at a $90,000 comp band. That hire exists at exactly two kinds of company: a 10-person startup where the designer is genuinely doing all of it, and a company that doesn’t yet know what the role is supposed to be. If you’re the second kind, the qualified candidate pool is going to look strange. The candidates with depth in any one of those areas will pass on the role because the JD signals the team doesn’t know what it values. The candidates who apply will be generalists with a breadth that doesn’t really exist at the level you’re hoping to hire. Decide what you actually need.

The second is the years-of-experience trap. The JD asks for eight years of UX experience and proficiency in Figma. UX as a defined discipline didn’t really exist with that name in widely-posted job titles eight years ago, and Figma’s adoption only became dominant in product design starting around 2019. The most useful UX designers on the market right now have between four and seven years of focused experience, often with a transition story from a related field. Asking for ten or twelve years of pure UX experience filters for people who have spent that decade in the same job title at large enterprises, which is sometimes the right hire. Usually it isn’t, and the JD is leaving the actual best fits sitting on the sidelines.

The third is the missing portfolio guidance. Every UX posting asks for a portfolio. Most postings give no instruction whatsoever about what the team wants to see. The strong candidates have multiple versions of their portfolio depending on the role they’re applying for, and they’re going to send the version they think you want to see. If you say “show us your process for one project, end to end, including a moment when you changed direction based on research,” you’ll get something useful in the first review. If you say “include link to portfolio,” you’ll get a curated highlight reel that tells you almost nothing about how the candidate actually works.

The fourth is hiding the team. UX designers ask three questions in the first conversation. Who’s the design lead. How big is the design team. What does the relationship with product and engineering look like. A JD that doesn’t answer any of those questions reads as either disorganized or evasive, and good designers self-select out before they ever apply. Two sentences about the team is enough. Who they’ll work with day-to-day. Whether design has an established voice in the roadmap. The good candidates are reading for those signals.

Common Questions

What’s the Real Difference Between a UX Designer and a Product Designer in 2026?

Product designer is the title that’s quietly absorbed UX designer at most growth-stage and tech-leaning companies. The same person doing user research, wireframes, and visual design five years ago is now called a product designer at the same kind of company. UX designer is still the more common title at agencies, regulated industries, and traditional enterprises. The skill set overlaps almost entirely. The strategic posture and roadmap influence usually run higher under the product designer title. Pay attention to which title the JD uses, because it tells you something about how the company thinks about the function.

Do I Actually Need to Specify Figma in the Job Description?

Yes. Figma is the working tool for somewhere around 90 percent of in-house product design teams in 2026. Sketch is mostly legacy at this point, and Adobe XD has lost most of its remaining ground. Asking for Figma fluency in the JD is not a flex, it’s a baseline. If your team uses something else, say so explicitly, because it’s now the unusual case and candidates will need to know. Don’t bury it.

How Should the Portfolio Review Actually Work?

Two stages. First, an asynchronous review where the candidate sends a written walkthrough of one project, end to end, with the framing question they were solving and one specific design decision they’d revisit. Second, a 45-minute live presentation where the designer talks through one case study and answers questions about it. The combination tells you what the candidate can do alone and what they can do under pressure. Reviewing only the portfolio link without a structured walkthrough is how teams end up hiring designers whose actual work product looks nothing like the case studies they show.

Is It Worth Hiring a Junior UX Designer Right Now?

If your team has the senior bandwidth to mentor, yes. Junior UX talent is plentiful and underpriced relative to the value they generate after about nine months. The mistake is hiring junior because the senior comp band feels expensive, then putting that junior on work that would challenge a senior. That ends with a junior designer leaving inside eighteen months and the team starting over. If your senior designers are already underwater, hire senior or hire contract. Junior is the right call when the path to senior is real and the manager has the calendar to actually walk that path with someone.

Should the JD Include Specific Salary Ranges?

In states with pay transparency laws (California, Colorado, Washington, New York, Illinois, Connecticut, Maryland, Nevada, and a growing list), legally yes. Outside those states, including a range still measurably improves the quality of your applicant pool. Candidates with strong options self-select out of postings without ranges, because ambiguous comp signals an ambiguous hiring process. A wider band is better than no band. Posting $95K to $145K with the qualifier “depending on level and location” is more useful than leaving the line blank.

How Long Does a UX Designer Search Realistically Take?

Four to eight weeks for a focused search with a clear scope and a hiring manager who is responsive. Longer when the role definition is ambiguous, the comp band is below market, or the portfolio bar drifts upward halfway through. KORE1’s average time-to-hire across IT and digital roles is 17 days for contract and direct hire roles. Senior in-house design searches typically run on the longer side of that average because portfolio review and stakeholder interviews add cycle time that you don’t see in roles where the screen is more credentials-based.

Where Are the Best UX Candidates Coming From in 2026?

The strongest pipelines I see are designers who left a strong in-house team during the 2023–2024 product layoffs and have been doing contract or freelance work since. They are interview-tested, current on tooling, and used to making the case for their decisions in a room of skeptics. Bootcamp-only candidates are still part of the pool but the variance is wider, and the bootcamp brand on a resume tells you less than it did three years ago. The other quietly underrated source is internal: existing UI designers, content designers, or PMs with design instinct who are coachable into a UX role. That path requires real mentorship, but the retention numbers are better than external senior hires when it works.

What’s the Single Most Common UX Job Posting Mistake?

Writing the JD for a designer who can do everything well, instead of a designer who can do the specific thing the team needs done. The everything-designer posting reads as a wishlist. The strong candidates can tell. They apply somewhere else, and the team interviews a long list of generalists who can fake every section of the JD just well enough to make the hiring manager’s job harder, not easier. Pick the work the role exists to do. Write for that.

If you’re working through a UX or product design search and want a sanity check on the JD, the comp band, or the candidate pipeline, reach out to our team. KORE1’s digital and creative staffing practice places UX, UI, and product designers across more than thirty U.S. metros, with a working memory of which JDs close and which ones don’t.