UX Writer Job Description
The UX writer role emerged as a distinct product design discipline when Google began hiring dedicated UX writers at scale in 2017, and demand has grown steadily — LinkedIn data shows UX writer and content designer job postings increased 43% between 2022 and 2024, while the practitioner pool remains small at approximately 12,000 in the United States [1]. Writing a job description that attracts qualified UX writers requires precision about the actual work: microcopy writing, design tool fluency, content systems development, and measurable impact on user outcomes. Vague descriptions that conflate UX writing with marketing copywriting or technical writing will attract the wrong candidates and repel the right ones.
Key Takeaways
- UX writer job descriptions must distinguish the role from copywriting, technical writing, and content marketing — the daily work is writing product interface text, not brand campaigns or documentation
- Specify design tools (Figma, Sketch) and research methods (usability testing, A/B testing) to signal that the role sits within the product design function, not marketing
- Include the product domain, user scale, and team structure — experienced UX writers evaluate opportunities based on product complexity and design maturity
- State the career level clearly: junior (screen-level microcopy), mid-level (feature ownership), senior (content systems and strategy), principal (organizational influence)
- Compensation transparency attracts stronger candidates — UX writers benchmark against Levels.fyi data and will skip postings without salary ranges
Job Overview
The UX writer is responsible for all user-facing text within the product interface — the words that guide users through tasks, explain what is happening, recover from errors, and establish the product's voice. This includes button labels, form field labels, error messages, success confirmations, empty states, tooltips, notifications, onboarding sequences, dialog copy, navigation labels, and settings descriptions. The UX writer works within the product design team, collaborating directly with product designers, product managers, and engineers from project discovery through post-launch iteration [1]. Unlike marketing copywriters who write to persuade or technical writers who write to document, UX writers write to enable — every string in the product interface exists to help users complete a task, understand their situation, or make a decision. The role requires design process fluency (working in Figma, participating in usability testing, contributing to the design system) alongside writing craft (concision, clarity, information hierarchy, voice and tone consistency) [2].
Core Responsibilities
Microcopy Writing
Write all product interface text across the application: button labels that describe the action ("Save changes," "Delete account"), form field labels and helper text, error messages that explain what happened and how to fix it, success confirmations, empty state messages that guide next actions, tooltip copy, notification text, onboarding copy, modal and dialog content, and navigation labels. Every string must be clear, concise, actionable, and consistent with the product's voice and tone guidelines [2].
Voice and Tone Development
Define and maintain the product's voice and tone system — the framework that governs how the product communicates across every context. This includes documenting 3-5 brand voice attributes with usage examples, mapping tone variations by context (onboarding is encouraging, errors are calm and helpful, success is briefly celebratory), establishing terminology decisions with rationale ("sign in" vs. "log in," "cancel" vs. "discard"), and creating reference documentation that designers and engineers can use to write consistent copy independently [2].
Design File Collaboration
Work inside Figma (or equivalent design tools) alongside product designers — creating text layers, using auto layout, accessing the component library, and participating in file organization. UX writers who work in design files are dramatically more effective than those who write in separate documents, because content decisions are design decisions that affect layout, hierarchy, and interaction patterns [1].
Content Component Libraries
Build and maintain reusable content patterns within the design system: standard button label conventions, error message frameworks (what happened → why → how to fix), empty state templates, tooltip patterns, notification formats, and confirmation dialog structures. These content components function like design components — they ensure consistency across teams and reduce the time spent writing common UI patterns from scratch [2].
Content-Specific User Research
Design and facilitate research protocols that specifically evaluate content comprehension. This includes usability testing where participants explain what they think messages mean, observing where users hesitate or reread copy, A/B testing copy variations to measure conversion and task completion impact, readability analysis against audience-appropriate targets, and content heuristic evaluation against established quality criteria [1].
Localization Readiness
Write English source strings that translate well across languages — avoiding idioms, cultural references, ambiguous pronouns, and humor that does not cross cultural boundaries. Collaborate with designers on flexible layouts that accommodate text expansion (German expands 30%, Finnish 50% relative to English). Work with localization platforms (Phrase, Lokalise, Crowdin) to manage translatable strings, write translator context notes, and review localized output [2].
Accessibility Compliance
Write content that meets WCAG 2.1 AA requirements: descriptive alt text that conveys meaning rather than just description, link text that makes sense out of context, clear and persistent form labels, error messages associated with specific fields, content that flows logically when read by a screen reader, and plain language appropriate for the target audience — typically 6th-8th grade reading level for consumer products [2].
Required Qualifications
Education
Bachelor's degree in English, journalism, communications, linguistics, human-computer interaction, psychology, or a related field — or equivalent professional experience. No specific degree is required for UX writing roles; hiring decisions are based on portfolio quality and demonstrated writing process [1].
Experience by Level
**Junior UX Writer (0-2 years):** Professional writing experience in any discipline (copywriting, technical writing, journalism, content marketing) with demonstrated interest in product and UI writing. Portfolio with 3-5 UX writing case studies (redesigns are acceptable for entry-level candidates). Familiarity with Figma or equivalent design tools [1]. **UX Writer (2-5 years):** 2+ years of experience writing product interface copy for a shipped digital product. Demonstrated ability to own content for entire features from discovery through launch. Experience conducting content-specific usability testing or A/B testing copy. Working proficiency in Figma [1]. **Senior UX Writer (5-8 years):** 5+ years of product UX writing experience. Proven track record of building voice and tone systems, content component libraries, or content style guides adopted across multiple teams. Experience mentoring junior writers. Demonstrated business impact through measured content improvements (conversion, task completion, support ticket reduction) [1]. **Principal / Staff Content Designer (8+ years):** 8+ years of content design experience with evidence of organizational influence — setting content design vision for product areas, establishing standards followed by multiple teams, representing content design at the executive level, and contributing to the discipline through publishing or speaking [1].
Technical Skills
- Figma proficiency (working within design files, not just reviewing)
- Content management platforms (Contentful, Phrase, Lokalise) — familiarity with at least one
- A/B testing platforms (Optimizely, LaunchDarkly, Google Optimize) — understanding of experiment setup and analysis
- Basic HTML/CSS understanding (sufficient to collaborate effectively with engineers)
- Accessibility standards (WCAG 2.1 AA content requirements)
Preferred Qualifications
- Experience writing for the specific product domain (fintech, healthcare, e-commerce, enterprise SaaS, developer tools)
- Localization experience — writing for products available in multiple languages
- Conversation design experience (chatbots, voice interfaces)
- Design system contribution experience
- Google UX Design Certificate, UX Writing Hub certification, or Content Design London training
- Experience with string management in codebases (understanding localization keys, conditional content, string interpolation)
Compensation
UX writer compensation varies significantly by company tier. Major technology companies (Google, Meta, Apple, Amazon) pay UX writers as members of the product design function, with total compensation (base + equity + bonus) 30-80% above base salary. Mid-level UX writers at FAANG companies earn $130,000-$155,000 base with $170,000-$220,000 total compensation. Senior UX writers at the same companies earn $160,000-$200,000 base with $250,000-$380,000 total compensation [3]. | Level | Base Salary Range | Total Comp (Major Tech) | |-------|------------------|------------------------| | Junior (0-2 years) | $65,000-$85,000 | $85,000-$120,000 | | Mid-Level (2-5 years) | $95,000-$135,000 | $130,000-$180,000 | | Senior (5-8 years) | $130,000-$180,000 | $180,000-$260,000 | | Principal/Staff (8+ years) | $160,000-$220,000 | $250,000-$400,000 | Geographic adjustments: San Francisco Bay Area (+35%), New York City (+25%), Seattle (+20%) above national median. Remote positions at some companies (Airbnb, Spotify) pay location-independent rates [3].
Work Environment
UX writers typically work within the product design organization, reporting to a content design manager, design manager, or head of design. The role involves daily collaboration with product designers (shared Figma files, design critiques), product managers (feature prioritization, content strategy alignment), engineers (string implementation, localization, conditional content), and user researchers (content-specific usability testing, comprehension studies). Most UX writing roles are remote-friendly — the work translates well to distributed teams through Figma, Slack, and video conferencing [1].
How to Apply
Submit your resume and portfolio link. The portfolio is the primary evaluation criterion — it should demonstrate your writing process (research, strategy, drafts, testing, iteration), not just final copy. Include 3-5 case studies showing before/after content comparisons, the user problem each project addressed, your rationale for content decisions, and measurable outcomes where available [1].
Frequently Asked Questions
What is the difference between a UX writer and a content designer?
At most companies, content designer is the evolved version of the UX writer title, reflecting a broader scope that includes content strategy, information architecture, and design system contribution alongside microcopy writing. Google, Meta, and Spotify have transitioned from "UX writer" to "content designer" without changing the role's core responsibilities or compensation bands. When writing job descriptions, either title is acceptable — use "content designer" if the role includes significant strategy and systems work, "UX writer" if the focus is primarily on writing product interface copy [1].
Should UX writer job descriptions require a specific degree?
No. UX writing has no gatekeeping credential. The strongest UX writers come from diverse educational backgrounds — English, journalism, communications, linguistics, psychology, design, and self-taught paths. Requiring a specific degree eliminates qualified candidates without improving hiring quality. Portfolio quality and demonstrated writing process are far more predictive of job performance than educational background [1].
How do you evaluate UX writer candidates beyond the resume?
The standard UX writer hiring process includes: portfolio review (primary filter), writing exercise or design challenge (timed prompt to write microcopy for a given scenario), content critique (evaluate and improve existing product copy), and cross-functional interview (assess collaboration with designers, engineers, and product managers). The portfolio review carries the most weight — candidates whose portfolios demonstrate process, rationale, and measured outcomes advance regardless of resume credentials [1].
**Citations:** [1] LinkedIn Economic Graph, "UX Writing and Content Design Job Market Report," linkedin.com, 2024. [2] Nielsen Norman Group, "UX Writing: Study Guide," nngroup.com, 2024. [3] Levels.fyi, "Content Designer and UX Writer Compensation Data," levels.fyi, 2025.