UX Writer / Content Designer

A UX writer, or interface writer, shapes the words in a digital product to help people understand what they see and complete a task. Their work covers labels, forms, error messages and other text encountered along a user journey. The title “content designer” can cover this work, but it can also mean designing content or an entire service. The scope of the role therefore needs to be specified when hiring.

In this profile, the role focuses on the words in a product interface. It is not limited to shortening sentences at the end of a project: decisions about terminology can begin during design and evolve in response to feedback on how the product is used. A button should make its action clear. An error message should make the problem understandable and tell the person what they can do next. Wording always depends on the product context and the stage of the journey.

Depending on the organisation, the UX writer works with people who design interactions, study how the product is used and decide how it develops. They can use research findings and user feedback to improve text without necessarily leading the research themselves. They also help keep terminology and the product voice consistent when several screens or teams are involved. Final responsibility for the text, and the approval process, must be defined for each role.

UX writer, product designer and UX researcher: who does what?

• UX writer: chooses and revises the words that guide actions in the interface.
• Product designer: designs the interactions and the structure of the product journey; they work with the UX writer on wording when content affects how a screen is understood.
• UX researcher: studies how people use the product and provides observations that the UX writer can use to choose or revise wording.

These responsibilities can overlap in a small team. A job title alone does not tell you who conducts research, approves a design decision or publishes text.

The words in an interface guide the decisions of the people using it. A vague button label leaves the next action uncertain; a poorly named form field can make a request hard to understand. The hiring challenge is to put these choices in the hands of someone who can connect them to the user journey and users’ needs, then improve them as feedback comes in. Clarity is a goal to assess in the product, not an outcome guaranteed by a particular phrase.

Hypothetical example: someone enters information in a form, receives an error and does not know which field to correct. The UX writer could revise the field label and message to make the problem and next action explicit. The result needs to be tested in that context: concise wording on another screen will not necessarily solve this difficulty.

Hiring also requires a decision about scope. If the need concerns the words in a product journey, look for someone who can write within the constraints of an interface and work with design colleagues. If it extends to a content strategy for a service, the content designer title may describe broader responsibilities. Define the screens involved, this person’s part in decisions and how their text will be approved. Without that clarity, the team risks hiring a general writer for a product design problem, or expecting the UX writer to lead user research alone.

Consistency matters when several teams change the same journeys. A glossary, voice guide or content rules can then help them use the same terms for the same actions. These resources are useful if they support the team’s decisions and can be revised. They do not replace reviewing a real screen or hearing from the people who use it. The UX researcher job profile helps define the separate need to study how people use the product.

• Design labels for buttons and actions across product journeys.
• Write form guidance and error messages that help users take the next action.
• Take part in designing the journey before the text is finalised.
• Revise text in response to feedback on use or changes to the product.
• Use available research findings to choose wording that fits the context.
• Maintain consistent terminology and voice across the screens concerned.
• Explain wording choices to design colleagues and product stakeholders.

No single degree defines entry into this profession. Accounts gathered by Content Design London describe people coming into the role from journalism, marketing, communications or publishing. They show possible paths, without establishing a required route or guaranteeing that general writing experience alone prepares someone for interface work.

When assessing a candidate, look first for work in which words support an action in a product. A portfolio might show a form, button or error message before and after revision, along with the original comprehension problem and the chosen solution. What matters is seeing how the person adapts wording to the user’s context, the space available and the way the screen works. A polished sentence on its own does not show this reasoning.

Writing or communications experience can bring a command of language and editing skills. You still need to assess the ability to work within a journey, explain an action label, keep terminology consistent and use feedback on how the product is used. Design experience can make it easier to discuss interactions, but does not remove the need to demonstrate the quality of the text. For a broader content design remit, also examine how the candidate structures and improves a body of content.

Compare the responsibilities candidates have actually held: the text they produced, their autonomy in making choices, their coordination with other disciplines and their ability to revise after feedback. Someone may be skilled at a specific deliverable without yet having been responsible for consistency across an entire journey.

To assess this profile, use the following steps as hiring guidance. Adapt the exercises to the types of text, the people they will work with and the decisions involved in the role.

1. Define criteria before the interviews

Specify the content the person will need to design: buttons, forms, errors or consistency across a journey. Distinguish writing quality, understanding of how people use the product and the ability to work with design colleagues. If the role also covers a broader content strategy, say so explicitly. Prepare the same framework for comparing candidates against the expected abilities, without confusing verbal fluency with the quality of their writing.

Decide who will approve wording and how feedback from teams will be incorporated. A positive sign is a candidate who asks about the context of a screen before suggesting words. A warning sign is a universal answer to a problem when the product and its users have not been described.

2. Review past work

Ask for an example of interface text before and after revision. Have the candidate explain the original problem, the options they rejected and the reason for the final choice. A clear button should make the action understandable; an error message should explain the problem and guide the next step. Look for decisions connected to the journey, rather than just a list of effective phrases.

Ask the candidate to describe the feedback they received and the changes it led to. If they have no numerical results, their explanation can still show what they observed and what they changed. Pay attention to their actual contribution, especially when others led the research or design.

3. Set an exercise close to the role

Present a short journey and a specific comprehension problem. Hypothetical example: a form rejects an entry without identifying the field to correct. Ask the candidate to suggest a useful label or message, then explain the next action it makes clear. Provide enough context so they do not have to guess the product rules.

Notice whether the person asks what the user sees, distinguishes an error from a simple screen state and considers revising the text after feedback. Brevity is a strength only if the meaning remains clear. A warning sign is elegant text that omits a possible action or assumes information missing from the exercise.

4. Assess collaboration and communication

Ask about a discussion with a designer, someone responsible for the product or a content lead. How did the candidate explain their choice and handle disagreement? Look for a reasoned decision and an ability to accept feedback without sacrificing clarity for the user. If the role involves maintaining shared terminology, ask how they would document a decision for reuse.

If your team lacks this expertise, involve someone who can assess text in a product context. They can help distinguish a wording problem from an interaction problem. Use the same criteria and exercise for every candidate.

5. Check scope and references

With the candidate’s consent, ask a referee about the responsibilities they actually held: writing, revision, coordination or final decision-making. Ask for an example of a change made after user feedback or a product constraint. A helpful reference confirms a specific role and can give a clear account of how the candidate worked. A vague answer about “creativity” alone does not establish the ability to design interface text.