Founders ask me this more than almost any other hiring question. It’s often phrased as some version of "do we need a writer for buttons?" I have designed more than fifty websites over my career, several for companies that went on to be worth a great deal of money, and the honest answer is that the words inside a product decide whether the design works at all. A screen with a confusing label is a broken screen, no matter how good it looks.
A UX writer is responsible for the language a user reads while they are trying to get something done. That includes button labels, empty states, form hints, error messages, onboarding sequence, permission prompts, confirmation screens, and settings descriptions. It is a product role that happens to be performed with words, which is why it sits closer to design than it does to marketing.
I learned this the slow way. My first writing job was documenting video editing software at New Blue when I was twenty-three, which meant sitting with editors who had cut top-tier films and translating what they knew into language a new user could follow. Years later, when I started building my own software, I found myself writing the interface copy first and working backwards to the engineering. The Squibler homepage promise of turning an idea into a book inside a chat existed as copy before it existed as a product. That is the part of the job most people miss.
What a UX Writer Is Responsible For
The clearest way to describe the role is by naming the surfaces it owns. A UX writer writes the text that appears inside the product itself, sometimes called microcopy because each piece is short. The volume is deceptive. A mid-sized application can carry thousands of individual strings, and every one of them is a chance to either move a user forward or stall them.
In most teams, the writer is responsible for navigation and menu labels, calls to action on buttons, form field labels and helper text, validation and error messages, empty states before a user has any data, onboarding and setup flows, tooltips, confirmation dialogs, notification copy, and the tone rules that keep all of it consistent. Nielsen Norman Group defines the practice as writing information that addresses people's contexts, needs, and behaviors, which is a useful reminder that the job is not decorative wordsmithing.
There is a second responsibility that seldom appears in job descriptions and matters just as much. A UX writer maintains the shared language of the product. If your app calls the same object a project on one screen, a document on another, and a file in the billing email, users will assume they are three different things. Keeping that vocabulary stable across a growing product is closer to the discipline behind content design than to copywriting.
The Process I Would Expect a UX Writer to Run
When I evaluate someone for this work, I care far less about their portfolio prose than about whether they have a repeatable process. Good interface copy is the output of a method, and the method looks something like this.
Learn the user and the product constraints together
Before writing anything, the writer needs to know who is on the screen, what they came to do, what they already understand, and what the system can and cannot do. At New Blue, I could not write a single tutorial until I understood colour grading well enough to talk about it the way an editor would. The same rule applies inside a product. If the writer does not understand the underlying mechanic, the copy will describe a fantasy version of the feature.
Define the decision each screen has to support
Every screen exists to help someone make or complete one decision. Naming that decision out loud is the highest leverage minute in the whole process. Once you can say "this screen exists so a first-time user knows which plan to pick," the copy stops being decoration and starts being an argument with a job to do.
Gather evidence instead of guessing at wording
Research for a UX writer means support tickets, session recordings, search queries inside the product, sales call notes, and short usability sessions where someone reads the screen aloud. The phrasing users already use is almost always better than the phrasing the team invented internally. I have watched teams argue for a week about a label that a single support inbox search would have settled in ten minutes.
Draft inside the design rather than in a document
Interface copy written in a separate document seldom survives contact with the layout. Strong UX writers work in the design file, write several options for each string, and check how each one behaves when the container is narrow, when the language is translated, and when the user has a very long name. Length is a design constraint, not a stylistic preference.
Test the wording against behavior, not opinion
This is where I have spent most of my own UX writing time. I have run a great many conversion tests on pages I designed, and the lesson that stuck is that copy tests have to be read across the whole journey rather than at a single step. I have seen wording lift the immediate click and then damage what happened afterwards, because the promise on the button set an expectation the next screen could not meet. A UX writer who only optimizes the first tap is doing marketing, not product work.
Turn the winning patterns into rules
Once a phrasing works, it should become a documented pattern so the next writer and the next engineer do not relitigate it. This is the part of the job that looks like documentation, and it is why so many UX writers come out of the practice of technical writing. Published style guides such as the Microsoft Writing Style Guide exist for this reason, and most product teams build a smaller internal version of one.
The Copy Types That Fill Most of the Week
If you shadowed a UX writer for a week, the work would look less glamorous than the title suggests. Error messages alone can absorb days. Nielsen Norman Group's guidance on error messages asks for messages that are visible near the source of the problem, constructive about what to do next, and respectful of the effort the user already spent. Writing one that satisfies all three in the space of a single line is hard.
Empty states are the second underestimated category. A user who opens a brand new workspace sees nothing, and the words in that void decide whether they take the first action or close the tab. Onboarding sequences are the third, because they have to teach without lecturing and every extra sentence costs completion. Permission prompts, billing confirmations, and cancellation flows round out the list, and each of those carries legal and trust weight that ordinary marketing copy never touches.
Accessibility sits underneath all of it. The Web Content Accessibility Guidelines require that labels or instructions are provided when content requires user input and that, where the system can detect the problem, input errors come with a suggested correction. Those are not stylistic notes. They are the baseline a writer has to meet for a product to be usable by everyone, and they often decide how a form is worded.
Where the Role Sits Next to Everyone Else
UX writers work in the same room as designers, researchers, product managers, engineers, and legal reviewers. The boundary that confuses people most is the one with marketing. A marketing writer is trying to bring someone to the product and is measured on attention and acquisition. A UX writer is trying to help someone who is already inside the product finish a task, and is measured on completion, error rates, and support volume. I have written a longer breakdown of how the two roles differ in practice because the overlap causes so many mis-hires.
Title inflation makes this worse. Some companies call the role content designer, some call it product writer, and large organizations often split the work across several people. The clearest public example is Google, where the discipline is formalized. I have covered what the job looks like inside Google. Read the responsibilities in any job posting rather than the title, because the two often disagree.
There is also real overlap with documentation. The help article a user reaches after failing on a screen is part of the same experience, so writers who understand how user documentation is planned and maintained tend to make better decisions about what belongs in the interface and what belongs in a support page.
How the Work Gets Judged
The measurable side of the job is task completion rate, form abandonment, error frequency, support tickets about a specific screen, and time to first successful action. Those numbers move when copy improves, and a writer who can point at them will always be more valuable than one who can only argue about tone.
The immeasurable side is trust. Copy that overpromises produces a customer who feels tricked two screens later, and that damage does not show up in the test that the writer just won. My rule is simple. If the sentence would embarrass me when the user finds out what it meant, it does not ship, no matter what the click rate says.
How People Get Into This Role
Most UX writers arrive from adjacent work rather than from a dedicated degree. Technical writers, journalists, support leads, and marketers all convert into the role by rebuilding real screens from products they use and showing the reasoning behind each decision. If you are starting from zero, the practical route is covered in my walkthrough of breaking in without prior UX experience, and the longer view is in the way UX writing careers progress.
Structured training helps if you need a portfolio and a vocabulary fast. The UX Writing Certification Course I built at Technical Writer HQ is self-paced, is designed around four hours a week over ten weeks, and finishes with capstone projects and an instructor-reviewed portfolio and resume. If you want to compare it against other programs before committing, my overview of what the available UX writing certifications include lays out the options. The capability that matters more than any certificate is the specific skill set the role demands.
The short version of the answer I give founders is this. A UX writer is not there to make the product sound nice. They are there to remove the moments where a user hesitates, guesses, or gives up, and to keep the language of a growing product coherent while dozens of people add to it. On the products I have worked on, that work paid for itself faster than almost anything else on the roadmap.
If you are hiring, judge candidates on how they reason about a broken screen rather than on how pretty their sample sentences are. If you are becoming one, start by rewriting a real flow you already use, document why each change is better, and be ready to defend it with something other than taste.
Final Thoughts
Technical documentation is about helping people complete tasks without needing to ask for help. The best documentation is clear, practical, and kept up to date as the product changes. If the reader can follow it and know when they have succeeded, it has done its job.
Related Resources
FAQ
Here are the answers to the most frequently asked questions about what a UX writer does.
Is a UX writer the same as a content designer?
In many companies, the two titles describe the same work, and in others, content design is treated as the broader discipline that includes information architecture, content structure, and end-to-end flow design, with UX writing as the wording layer inside it. Read the listed responsibilities in a job posting rather than trusting the title.
Do UX writers need to know design tools?
Yes, at a working level. Copy has to be drafted inside the layout it will live in, so writers are expected to open the design file, edit strings in context, leave comments, and understand components and states. Nobody expects a UX writer to build the interface, only to work inside it with confidence.
Does a UX writer need coding skills?
Not in the sense of shipping features. Comfort with version control, structured content files, and basic markup is useful because strings often live in the codebase, and understanding how a feature works makes the copy more accurate. Deep programming ability is seldom part of the job.
How is UX writing measured?
Through behavior rather than opinion. Teams look at task completion, form abandonment, error frequency on specific fields, time to first successful action, and support contacts tied to a screen. The important discipline is reading those numbers across the full journey instead of celebrating a lift at one step.
What does a UX writer produce besides interface copy?
A voice and tone guide, a terminology list that keeps product vocabulary consistent, reusable patterns for common message types, annotated design files explaining copy decisions, and research notes that justify the wording. These artifacts are what let a product stay coherent as the team grows.
Can one person cover UX writing and marketing copy?
At an early stage, yes, and many founders do it themselves. The risk appears as the product grows, because the two jobs optimize for different outcomes and the marketing instinct to promise more tends to leak into screens where accuracy matters most. Splitting the roles becomes worthwhile once a product has steady traffic and real support volume.