UX writing is the practice of crafting the words users encounter inside products — button labels, error messages, empty states, onboarding flows, tooltips, notifications, and microcopy throughout the interface. The work is invisible when done well: users complete their tasks without friction. It's highly visible when done poorly: users get confused, abandon flows, or misinterpret what the product is asking.
Remote UX writing is well-established at tech companies. The work produces auditable artifacts (content, content specs, voice and tone guidelines) that integrate naturally into distributed product and design workflows. Demand for dedicated UX writers has grown significantly since 2018 as companies recognized that copy was being written by whoever had time rather than by someone skilled at it.
What UX writing work actually involves
Product copy and microcopy. You write the actual words in the UI: button labels that are clear and specific, headlines that orient users, form field instructions that prevent errors, confirmation messages that build trust. This sounds simple; it's not. Every word is a design decision that gets reviewed by product, engineering, legal, and sometimes accessibility teams.
Error messages and empty states. These are among the highest-leverage pieces of UX copy because they appear exactly when users are frustrated or confused. Good error messages tell users what happened, why, and what to do next. Empty states either motivate users or communicate that the product is broken. Most products have dozens of both that nobody wrote carefully.
Onboarding flows and contextual help. Users encounter onboarding once and don't re-read it. Helping users understand what to do, in what order, and why — without overwhelming them — requires significant iteration and testing. Contextual help (tooltips, popovers, in-app guidance) supports users at the moment of confusion, not in documentation they'll never find.
Content design and content strategy. Senior UX writers often take on broader responsibilities: defining the content architecture of a product, establishing voice and tone guidelines, running content audits, and aligning content decisions with business strategy. This is where UX writing overlaps with content strategy and content design as a discipline.
Collaboration with product and design. UX writers work alongside product managers, designers, engineers, and researchers. You're often in Figma before engineers touch the design, shaping how flows work by writing the words. You participate in user research and usability testing to understand whether the copy you wrote actually works.
Voice and tone documentation. Many UX writers own the company's voice and tone guidelines — the reference that tells other writers, marketers, and support teams how the brand communicates. Creating and maintaining these involves significant synthesis of brand, product, and user research.
The employer landscape
Large tech platforms (productivity tools, developer platforms, consumer apps) were early adopters of UX writing as a dedicated discipline and still hire the most UX writers. Companies like Figma, Atlassian, Notion, Stripe, and Shopify have well-developed content design practices.
Growth-stage B2B SaaS. The second major employer segment. These companies typically hire their first UX writer when the product has scaled to a point where ad-hoc copy has become a visible quality problem. The role is often broad (covering all of the above) at smaller companies.
E-commerce and consumer tech. High-traffic digital products where small copy changes have measurable conversion or retention impact. These teams tend to be more data-driven, running A/B tests on copy variants.
Fintech and healthcare tech. Regulated industries where clear communication has compliance implications. Error messages, disclosures, and informed consent flows require careful writing with legal review.
What separates strong candidates
Portfolio of product work. Not blog posts or marketing copy — actual screenshots of UI you wrote with context about the problem, your process, and the outcome. UX writing portfolios should show iterations: the first draft, the feedback, the revision, and why the final version is better.
Systems thinking about language. Strong UX writers think about consistency and patterns, not just individual pieces. Can you create a consistent vocabulary for your product? Can you recognize when different screens use different words for the same concept and know why that's a problem?
Comfort with ambiguity and feedback. Copy goes through many rounds of review. UX writers who respond defensively to feedback or struggle to iterate under constraints don't last long. The ability to justify copy decisions rationally while remaining open to revision is the professional posture.
Accessibility and inclusion awareness. Clear language is accessible language. UX writers increasingly apply plain-language principles, WCAG readability considerations, and inclusive language standards. This is no longer optional at most companies.
Research integration. Understanding usability testing, knowing how to run a content-specific test, and being able to interpret what user behavior says about copy effectiveness are differentiators at mid and senior levels.
Five things worth checking before you apply
Understand where UX writing sits in the org. Does UX writing report to design or to content/marketing? Design-aligned UX writers have more product access; marketing-aligned writers often produce more promotional copy in disguise.
Ask about the handoff process with engineers. How do content changes get into the product? Content specs? Direct Figma handoffs? A company where UX writers have to route every change through a PM creates friction and delays.
Ask about the content review process. How many stakeholders review copy before it ships? Legal, product, brand, and regional teams can each add rounds. Understanding the process helps you know how long things take and how much revision to expect.
Understand the tools. Figma is universal for design collaboration. Content-specific tools vary: ContentSnare, Contentful, Lokalise (for localization), and various internal content management systems. Knowing the stack ahead of time matters.
Clarify what "content design" or "UX writing" means to this company. At some companies, UX writing means product copy only. At others, it spans content strategy, information architecture, and design research. The job title tells you less than the actual responsibilities.
The bottleneck at each level
Junior (0–2 years): The bottleneck is usually portfolio depth. You may not have worked on product teams yet, which makes hiring managers uncertain. Building portfolio pieces through volunteer work, redesign exercises, or annotated case studies of existing products can bridge the gap.
Mid (2–5 years): You can write product copy competently. The bottleneck is usually strategic contribution — owning a content system, leading a content audit, establishing voice and tone guidelines that others use, and influencing product decisions earlier in the process (before design is complete).
Senior (5+ years): You're often expected to lead a content practice, manage other writers, and represent content design in leadership discussions. The bottleneck is organizational: making the case for content investment, defining standards across a large product, and scaling your work through others.
Pay and level expectations
US base ranges: Junior/Associate UX Writer (0–2 years): $70K–$95K. UX Writer (2–5 years): $95K–$140K. Senior UX Writer (5–8 years): $135K–$185K. Principal/Content Design Lead: $175K–$250K+. Varies significantly by company size and product maturity.
Europe adjustment: Subtract 20–40% depending on location. UK and Netherlands are at the higher end.
Market note: UX writing is less commoditized than content writing but more variable in compensation than engineering. At top-tier tech companies (Series C+, FAANG-adjacent), UX writing compensation is strong; at smaller companies, it's often lower than the role's strategic importance would suggest.
What the hiring process looks like
Most UX writing hiring processes include a portfolio review (often before or during the first interview), a writing exercise or take-home challenge (write microcopy for a given scenario, often with word count constraints), and a design/product team loop. Some companies run a live critique where you review existing product copy in real time. Total process: 3–5 weeks.
The portfolio and take-home are primary decision factors. Prepare multiple case studies with context, process, and outcome — not just before/after screenshots.
Red flags and green flags
Red flags:
- "We need someone to write copy for marketing and help with the product." This is two jobs, not one.
- No existing design process — UX writing without designers means you're writing copy for decisions already made.
- Copy is reviewed primarily by marketing or brand, not product and design. You'll be writing marketing copy.
- Engineers paste copy from Word documents. No Figma handoffs, no content specs, no review process.
Green flags:
- UX writers participate in design sprints and product discovery, not just final review.
- Dedicated Figma workflow with copy layer conventions and handoff process.
- Usability testing includes content-specific tests or moderated sessions where copy confusion is surfaced.
- Voice and tone guidelines already exist (or there's explicit mandate to create them).
Gateway to current listings
RemNavi aggregates remote UX writer jobs from design job boards, company career pages, and specialist content platforms refreshed daily. Filter by company size, product type, and seniority. UX writing roles move quickly when they open — set up alerts for new listings.
Frequently asked questions
Is UX writing the same as content writing? No. Content writing produces editorial content (blog posts, articles, guides) for external audiences. UX writing produces product copy (UI labels, error messages, onboarding flows) for users inside the product experience. Different skills, different workflows, different employers. There is some overlap — many UX writers can write long-form content and vice versa — but they're distinct disciplines.
Do I need a design background to be a UX writer? Not a traditional one, but you need to understand design process. The best UX writers think about information hierarchy, user flows, and interaction patterns. Many successful UX writers come from journalism, linguistics, copywriting, or technical writing — not visual design.
Is UX writing a growing field? It was growing rapidly from 2015 to 2023. In 2024-2025, hiring pulled back at many large tech companies (along with broader design layoffs). The discipline is still healthy but more competitive than at its peak. Differentiated portfolios matter more than they did three years ago.
Can AI replace UX writers? Partially for routine copy. AI tools generate plausible UX copy quickly, which has changed junior hiring. But the strategic elements — content systems thinking, user research synthesis, cross-functional influence, and voice consistency across a complex product — remain human work. The profession is evolving, not disappearing.
What's the best way to build a UX writing portfolio without experience? Redesign exercises: pick a real product with poor copy, document the problems, propose improvements, and show your reasoning. Case studies don't need to be from paid work. Volunteer work with nonprofits or open source projects also produces real samples.
Related resources
- Remote UX Designer Jobs — user experience design and research
- Remote Content Writer Jobs — long-form content and editorial
- Remote Product Designer Jobs — visual and interaction design
- Remote Technical Writer Jobs — documentation and developer content
- Remote Copywriter Jobs — persuasive marketing and sales copy