How to evaluate a UX writer

The request that reveals everything

“The error message is confusing. Can you make it friendlier?” It is the most common request a UX writer receives and it is almost always the wrong one.

A confusing error message is usually a symptom. The flow asked for something impossible, or failed silently three steps earlier, or is reporting a problem the user cannot act on. Rewriting the sentence makes the symptom pleasant and leaves the cause.

Give them exactly that request, with enough context to see the flow, and watch whether they reach for the sentence or for the screen.

Destructive actions

Ask them to write the confirmation for permanently deleting something with no undo. It is a small brief that contains most of the craft.

Weak versions are either jokey — which is a catastrophe on an irreversible action — or so hedged that the user cannot tell what will happen. Strong versions name exactly what disappears, say whether it can be recovered, and put the consequence in the button rather than in the paragraph nobody reads.

The constraint they cannot remove

Every product has sentences that legal or compliance will not let you change. Give them one, badly worded and mandatory, and ask what they would do.

The failure is to fight it or to give up. The good answer works around it: put the required wording where it is legally sufficient, and carry the actual meaning in the parts of the screen that are free — the heading, the button, the microcopy underneath.

Reader or brand?

Ask for a time the brand voice was wrong for the moment.

Every product has states — a failed payment, a lost draft, an account locked — where playfulness reads as contempt. A UX writer who has never overridden the voice guide has either not been in those moments or was not allowed to be, and both are worth knowing before you hire them.

What they decide not to say

Show them a screen with too much copy and ask what comes out.

This is the skill that separates the role from editing. Weak answers tighten every sentence; the screen ends up shorter and just as busy. Strong answers delete a whole element — a label that repeats the heading, a helper text that explains a field that should have been self-evident, a reassurance nobody asked for — and can say why each was doing no work.

Why this role is the hardest one to hire badly and notice

A weak engineer produces bugs. A weak designer produces screens someone will question. A weak UX writer produces copy that reads fine and quietly costs you conversions, support tickets and trust, and nobody on the team can point at the sentence responsible.

That invisibility runs both ways in hiring. It is very easy to hire a writer whose portfolio reads beautifully and who cannot work inside a system, and equally easy to reject one whose samples look plain because the product they worked on demanded plain.

So the evaluation has to target the decisions rather than the prose. Good product writing frequently looks like nothing at all — which means judging it on how it reads is close to judging it backwards.

The exercise that works, and it takes fifteen minutes

Take a real screen from your product. Strip nothing, fix nothing. Give it to the candidate with three pieces of context: who is on this screen, what they were doing immediately before, and what the business needs to happen next.

Then ask for two things — what they would change, and what they would deliberately leave alone. The second half is the important one and almost nobody asks for it.

A weak candidate rewrites everything, because rewriting is the demonstration they think you want. A strong one changes two or three things, leaves the rest, and can tell you why each untouched line is already doing its job. That restraint is the whole skill, and fifteen minutes of a real screen surfaces it more reliably than any portfolio review.

Run it identically for every candidate. The comparison is the point, and the moment you customise the screen for someone senior you have lost it.

Five signals in what they hand back

Ordered by how much they predict, from what teams report after hiring.

• They asked a question before writing. What happens if this fails? What is the longest realistic string here? Who else writes in this product? A writer who starts producing copy without asking anything will do the same on your team.
• They wrote for the state that goes wrong, not just the happy path. Empty, loading, error, permission-denied. This is where product writing earns its salary and where most portfolios have nothing.
• They kept a constraint they were not allowed to remove. If the legal line has to stay, does their solution work with it there, or does it quietly assume it is gone?
• They noticed a conflict between what the reader needs and what the business wants, and named it instead of resolving it silently in the brand's favour. Naming it is the senior move.
• They can defend a deletion. Anyone can add a helpful sentence. Knowing which existing sentence is doing nothing, and being able to say why, is much rarer.

What to ignore, and it is most of what gets presented

Three things that look like evidence of a good UX writer and are not.

Portfolio polish. A content designer's portfolio is a marketing artefact about a person who writes marketing artefacts for a living, and since 2024 it is also generatable end to end. It tells you they can present. It does not tell you they can work inside a design system with a legal team attached.

Voice and tone documents. Everyone has one, they all say the same six adjectives, and writing one is not the hard part — holding it across four hundred strings written by six people is. Ask how they enforced it, not whether they wrote it.

Awards and long-form writing samples. Both are evidence of writing ability, which is real and is not the constraint. The constraint is judgment about what to say inside forty characters when the developer is waiting.

Do you need a UX writer or a content designer?

The titles are used interchangeably at most companies and genuinely differ at a few, and the difference matters when you write the job ad.

Where it is real: a UX writer is handed the flow and makes the words work. A content designer is expected to argue about the flow — to say that this screen should not exist, or that the sequence is wrong, and to change the structure rather than the sentence.

The settling question is the same one that separates UX from product design: when the flow is wrong, is this person expected to say so? If yes, you need someone who will push back on structure, and you should assess for that argument rather than for prose quality. If no, you are hiring for craft inside constraints, and the exercise above is most of what you need.

Frequently asked

Can a product designer do the writing?

Often, up to a point. What a dedicated writer adds is noticing that a confusing screen is a broken flow rather than a wording problem, and having the standing to say so. If your designers are shipping copy nobody reviews, you do not have a writing problem yet — you will.

Should I ask for a portfolio or a writing test?

A portfolio shows final sentences, which is the least informative part. If you run an exercise, give a real screen with a real problem and ask what they would change — including what they would remove and what they would escalate rather than write around.

How do you judge writing if you are not a writer?

Read the button. It is the hardest thing on the screen to get right and the easiest to judge: does it say exactly what happens when you press it? Everything else about a writer’s judgment shows up in that one string.

Should a UX writing test be paid?

If it uses a real screen from your product and takes under twenty minutes, no — it is short and produces nothing you can ship. If it takes an afternoon, or if you would actually use what comes back, pay for it. The line is not the format, it is whether you are getting work out of it.

How do I evaluate a UX writer without one on the team?

Weight the reasoning rather than the prose. You cannot reliably judge whether a microcopy line is well made, but you can absolutely judge whether someone's explanation of a trade-off is sound — that is a general skill. Ask them to explain each change and each deliberate non-change, and score the explanations.

Is UX writing being replaced by AI?

The drafting is, largely. Producing forty variants of a button label is now free. What did not become free is deciding which variant is right for this reader in this state given this legal constraint, and noticing that the screen is asking the wrong question in the first place. That was always the job; it is now more visibly the job.