How do you approach writing UX microcopy such as buttons, empty states and error messages?

What the interviewer wants to hear

• Understand the user's task and context at that moment
• Be clear, short and specific over clever
• Use consistent terms across the product
• Error messages explain what happened and how to fix it
• Test with users and work closely with designers

Model answer

I start with the user's task: what they are trying to do, how they feel and what they need to know at that moment. Microcopy should be clear first, short second and clever only if that does not cost clarity. Buttons say what will happen, like "Save draft" rather than "Submit". Error messages explain what went wrong and how to fix it, without blame or codes. Empty states tell users why the screen is empty and give one helpful next step. I keep a terminology list so the product uses the same word for the same thing everywhere. I work inside the design files with designers, check copy in context and at different screen sizes, and test key flows with real users, because small words often decide whether people succeed.

More medium Content Writer questions

• How do you use AI writing tools in your work, and where do you draw the line?
• How do you measure whether a piece of content is successful?
• How do you adapt your writing to different brand voices or clients?
• How do you work with an SEO specialist without making content sound robotic?
• How would you plan a three-month content calendar for a new product?
• You have a one-hour transcript from a technical expert. How do you turn it into a clear article?
• A client rewrites your copy into something you believe is weaker. How do you handle it?
• You join a company with 300 old blog posts and flat traffic. How would you run a content audit?
• How would you create a style guide for a growing content team?