User Experience (UX) Designer Job Description

A User Experience (UX) Designer decides how a digital product behaves from the user's side of the screen: what a person sees first, how a task unfolds step by step, what happens when they make a mistake, and how quickly they can get back on track. BLS describes the broader group this way: "Digital designers develop, create, and test website or interface layout, functions, and navigation for usability." O*NET adds that people in the occupation may design and test interfaces that "maximize the usability of digital devices, websites, and software."

Research comes first

The job starts with evidence about real people. A UX designer schedules user interviews, watches someone attempt a task in a moderated usability session, reads support tickets, and pulls funnel data from tools such as Amplitude or Google Analytics. The point is to find the exact moment a person hesitates, backtracks or quits. Synthesis is where the skill shows: turning pages of notes into a short list of problem statements specific enough that a product manager can prioritize them and an engineer can estimate them.

Structure, flows and prototypes

With a problem framed, the designer works out structure. Card sorts and tree tests settle navigation labels. Task flows and journey maps show every branch a user can take, including the unhappy paths: expired sessions, failed payments, empty search results. Wireframes come next, usually in Figma or FigJam, followed by clickable prototypes that get put in front of users within days. Cheap, rough prototypes exist so a team can be wrong early, when a bad idea costs a sketch instead of a sprint of engineering work.

Handoff and build

A design file is a proposal until it ships. Good UX designers annotate interaction states (hover, focus, loading, error, disabled), describe responsive behavior at each breakpoint, and write the microcopy that explains a confusing field. During the build they sit in on standups, answer questions in the ticket, and review staging builds against the spec. Accessibility belongs in this loop as well: color contrast, focus order, keyboard paths and screen reader labels are design decisions, not cleanup tasks for QA.

Systems and new surfaces

On mature teams the designer also feeds a design system: shared components, tokens for color and spacing, and written guidance on when to use a modal versus an inline message. Products with AI features add their own problems: the designer must decide how to show confidence, how to let a person correct a wrong answer, and how much of the machinery to expose.

Where the role sits

In-house UX designers report into a design or product organization and often work in a trio with a product manager and an engineering lead. Agency and consultancy designers rotate across client accounts. Where UX ends and visual interface design begins depends on the size and habits of the team.

Education

There is no single required degree. BLS notes that educational requirements for web developers and digital designers vary, ranging from a high school diploma to a bachelor's degree. In practice, a bachelor's degree in HCI, interaction design, graphic or industrial design, cognitive science or psychology is the most direct route. Designers who switch careers can come from graphic design, front-end development, technical writing, customer support or market research, usually after a structured course or bootcamp and a stretch of self-directed project work. A master's in HCI is useful for research-heavy roles but is not a prerequisite for design work.

The portfolio does the hiring

A UX portfolio should read like a set of case studies, not a gallery. Each one should state the problem, the constraints, what research was done and what it found, the options considered and rejected, what shipped, and what happened after launch. A few deep case studies with honest tradeoffs say more than a wall of polished screens. Redesign exercises are fine for a first job if the process is documented with real user input.

Core skills

• Research: interview guides, moderated and unmoderated usability testing, survey design, affinity mapping and synthesis
• Information architecture: card sorting, tree testing, sitemaps, labeling and search behavior
• Interaction design: task flows, state design, error handling, forms and microcopy
• Tools: Figma (components, auto layout, variables, prototyping), FigJam or Miro for workshops, Maze or a similar testing platform, Dovetail or a research repository
• Accessibility: WCAG success criteria, contrast checking, keyboard and screen reader testing
• Data literacy: reading product analytics dashboards, conversion funnels and experiment results
• Front-end literacy: enough HTML, CSS and component-framework knowledge to have a precise conversation with engineers

Experience levels

Junior designers typically spend their first 1 to 2 years executing within defined problems under a senior's review. Mid-level designers, usually with 3 to 5 years behind them, own a feature area end to end, from research through launch review. Senior and staff designers frame the problems themselves, influence the roadmap, mentor others, and often own part of the design system.

Credentials worth knowing

No license is required to practice. Credentials that some designers pursue:

• UX Certification from Nielsen Norman Group, earned by completing its courses and exams
• Certified Professional in Accessibility Core Competencies (CPACC) from the International Association of Accessibility Professionals, useful for anyone doing public-sector or accessibility-heavy work
• Google UX Design Certificate from Google, an entry-level course sequence

Treat these as structure for learning and a signal of seriousness. The portfolio and interview performance remain the deciding evidence.

What BLS projects

BLS groups this role with web developers in its Occupational Outlook Handbook. Overall employment of web developers and digital designers is projected to grow 5 percent from 2025 to 2035, faster than the average for all occupations, with about 13,600 openings for the combined group projected each year over the decade. Web and digital interface designers held about 132,700 jobs in 2025. Among their largest employers, the information industry accounted for 27 percent, self-employed workers for 13 percent, and computer systems design and related services for another 13 percent, followed by finance and insurance at 6 percent.

BLS also flags a drag on that growth. Improving development tools and increasing use of artificial intelligence may soften employment growth, the Handbook says, because these tools may make the workers more productive and may let some people in other occupations handle basic web development tasks.

The hiring market in 2026

Nielsen Norman Group's State of UX in 2026, published January 16, 2026, describes a market that began to stabilize from late 2024 through 2025. The recovery is uneven: senior practitioners and generalist roles are recovering faster than entry-level positions, which remain scarce and highly competitive. NN/g expects 2026 to stay competitive, with the supply of aspiring UX professionals still outpacing open roles, especially at the junior level. For a new designer, the practical response is a sharper portfolio, contacts inside product teams, and adjacent skills such as research operations or content design.

The same report argues that UI will gradually become less of a differentiator, and that in many products people spend less time navigating the interface and more time delegating to a layer sitting on top of it, such as an assistant inside the product or an agent that completes tasks. That raises its own design questions: deciding what an agent is allowed to do, how a person reviews and reverses its actions, and how a product explains what it just did.

How practitioners feel about AI

NN/g's AI in UX survey, published October 23, 2026, collected responses from 521 UX practitioners. Designers in the sample rated their job security at a mean of 2.99 on a 5-point scale, from 1 (very insecure) to 5 (very secure). Still, 65 percent of respondents expected their roles to remain important or grow, and only 18 percent thought their role would shrink or be eliminated. The takeaway for designers: AI is a tool to get fluent in, and the parts of the job that require judgment about people are the parts worth deepening.

Career paths

The individual contributor track runs from UX designer to senior, then staff or principal designer, where the job is mostly setting direction across several teams. The management track runs through design lead and design manager to head of design. Lateral moves run in several directions: into UX research, content design, design systems engineering, or product management, where a designer's habit of starting from the user carries over directly.

Dear Hiring Manager,

I am applying for the UX Designer opening on your payments team. For the past four years I have designed for a mid-sized accounting software company, where I own the invoicing and vendor-payment flows used by small business bookkeepers.

The project I would most like to walk you through is our vendor onboarding redesign. Bookkeepers were starting the setup and then disappearing, and our support queue was full of the same question: where do I find the vendor's tax form? I ran interviews with bookkeepers at a handful of client firms and watched them attempt the flow over screen share. The pattern was obvious once I saw it. We asked for documents halfway through the process that people did not have at their desks. I moved the document checklist to the first screen, split the flow into a save-and-return structure, and rewrote every field label in the language bookkeepers actually use. Completion went up noticeably in the first month, and the tax-form question nearly vanished from support.

I stay close to engineering through the build. I review every staging release against the spec, file my own tickets for gaps, and pair with our front-end lead on component changes. I also maintain our form patterns in the design system, including error states and keyboard behavior, and I test each new component with a screen reader before it is published.

I would bring the same habits to your team: start with the people doing the work, prototype early, and stay in the room until the thing ships correctly. I would welcome the chance to talk about the problems on your roadmap.

Sincerely, Jordan Avery