A UX writer writes the words people read while they use an app or a website: the buttons, the error messages, the onboarding screens, the settings and the notifications. The job is to help someone finish what they came to do, with as few words as the task allows and in a voice that sounds like the product.
Most UX writers moved over from another kind of writing. What gets them hired is a portfolio of interface copy they rewrote, with the reason for each change, more than any degree or certificate.
UX writers write the words that help people finish a task
A UX writer works with a product designer, a product manager and often a researcher. A typical week includes writing copy for new screens in a design file, reviewing copy that engineers or designers drafted, testing two versions of a message, and keeping the team’s style guide and word list up to date.
The writing itself is short. A button label is one to three words, an error message one or two sentences. The hard part is deciding what the reader needs at that moment, which means understanding the product, the person using it and what can go wrong. A writer who knows that a payment failed because the card expired can write “Your card has expired. Add a new one to finish paying.” A writer who doesn’t ends up with “Something went wrong.”
Content designers and technical writers do neighboring jobs
The titles overlap, and companies use them in different ways. Read the job description, since the title alone often doesn’t tell you which of these jobs it is.
| UX writer | Content designer | Technical writer | |
|---|---|---|---|
| Main output | Interface copy: labels, messages, flows | What content goes on a screen and in what order, plus the copy | Documentation: help articles, guides, API docs |
| Works most with | Product designers | Product designers and researchers | Engineers and support |
| Starts | Once the screens are designed, at many teams | When the problem is defined, before screens exist | Once the feature works |
| Common background | Copywriting, journalism, editing | UX writing, research, information design | Engineering, support, science writing |
Content design is often the same job as UX writing with an earlier seat at the table. Many companies renamed their UX writers to content designers so that writers join projects at the start, when the team decides what a screen should say as well as how to phrase it.
The skills that matter are clarity, structure and working with designers
Good UX writing reads as if it took no effort. These skills are behind it:
- Writing short, plain sentences that a stressed reader on a phone can follow, including readers with English as a second language.
- Structuring information in the order a person needs it, so the most important thing comes first.
- Keeping terms consistent across a product, so a “workspace” doesn’t turn into a “project” two screens later.
- Working inside design tools, mainly Figma, where you write in the mockups and comment on them.
- Running simple tests of copy, such as a comparison of two versions or a quick comprehension check with five people.
- Explaining your choices to a team, since each word on a screen has an owner who may disagree.
Accessibility belongs on that list too. Screen readers read button labels and image descriptions out of context, so “Click here” fails a blind user in a way “Download the invoice” doesn’t. Writers who know the basics of accessible copy stand out in hiring.
Build a portfolio of before-and-after rewrites
A UX writing portfolio shows interface copy and the thinking behind it. Each piece shows the screen before, the screen after and a short paragraph on why you changed it. Three to five pieces are enough.
Good material for a portfolio:
- Rewrite a confusing flow in an app you use, such as sign-up, password reset or a cancellation screen. Show the original screenshots, your version as a mockup and the reasoning.
- Write the error messages for one feature, covering each case: no connection, wrong input, a payment that failed, a server problem.
- Write an onboarding sequence for a product you know well, with a note on what each screen tells a new user and what it leaves for later.
- Draft a short style guide for a made-up product, with voice, terms and three message patterns.
- Show copy you wrote at work, with the details changed if it is confidential.
Keep the reasoning short and specific. “Changed ‘Submit’ to ‘Send request’, since the person is asking a landlord for a repair, and ‘Submit’ doesn’t say what happens next” shows judgment. “Made it clearer and friendlier” gives a reader no reason to trust the change.
The same rules for showing confidential work apply here as in a research portfolio: change the product name, rebuild screens as mockups and leave out anything unreleased. The UX research portfolio guide covers that in more detail.
Most hiring loops include a copy exercise
UX writing interviews usually follow the same steps:
- A recruiter call about your background and the kind of product you want to work on.
- A portfolio review with the hiring manager, where you walk through two or three pieces and answer questions about your choices.
- A copy exercise, either a take-home with a few days to finish or a live session. You get a few screens or a brief, and you rewrite the copy and explain why.
- Interviews with designers and product managers about how you work with them, how you handle disagreement and how you get the team to follow a style guide.
In the exercise, the reasoning counts as much as the words. Show two or three options for the hardest string with the trade-off of each, stay within any length limit the brief sets, and say what you would test. If a take-home asks for more than a few hours of work, it is fine to ask how long the team expects you to spend.
Copywriters, journalists, support agents and technical writers move in most often
UX writing has no single route in. The backgrounds that lead to it most often:
- Copywriters already write short and know brand voice. The shift is from persuading to helping, and from campaigns to products.
- Journalists and editors are used to tight word counts, plain language and deadlines. They often adapt fastest to the editing side of the job.
- Customer support agents know where users get stuck better than anyone on the product team, and they can show it with real examples of confusing messages.
- Technical writers already explain products to users. Moving from help articles into the interface itself is a short step, and many companies hire for both.
- Teachers, translators and localization specialists bring plain language and an ear for how words land with different readers.
Moving inside your current company is often the fastest way in. Offer to review the copy in a feature, fix the error messages your support team gets asked about, or start a word list. That work becomes portfolio material and puts you in front of the design team.
The same work goes under five job titles
Employers post this work as UX writer, content designer, product writer, UX content strategist and, at some companies, product content designer. Senior roles often add content strategy, which covers voice, terminology and how content is planned across a product.
Search for all of these titles, since a search for one finds only part of the open jobs. The UX writing jobs page collects them, and UX and product design jobs lists the designer roles you would work beside. Researchers and writers often share a team, and how to become a UX researcher covers the neighboring path.
