UX writer role-specific interview questions

As asked

Walk me through how you decide what to write for a call-to-action button. What makes one CTA stronger than another, and how do you test your instincts?

Sample answer outline

Strong answers cover specificity over vagueness ("Save your report" beats "Submit"), verb-first construction, alignment with the user's mental model of what happens next, and the role of A/B testing or usability studies to validate copy choices. Candidates should mention how context (risk level, reversibility) shapes tone.

Expect these follow-ups

• Give me a before-and-after example from your own work where changing a CTA meaningfully improved conversion or user confidence.
• How do you handle a stakeholder who insists on "Learn More" everywhere?

As asked

Describe the components of a good error message. If a user's payment fails, what does your ideal error message say, and why?

Sample answer outline

A strong answer identifies: what went wrong (plain language, not system jargon), why it happened if known, what the user can do next, and reassurance where appropriate. Candidates should address tone, avoiding blame, avoiding technical codes in consumer-facing text, and the difference between validation errors and system errors.

Expect these follow-ups

• How would your error message change if the payment failed due to a known bank outage versus an incorrect card number?
• What do you do when engineering can only expose a generic 500 error?

As asked

A lot of teams confuse voice and tone. How do you explain the difference to a new designer you are onboarding, and how does that distinction change your day-to-day writing decisions?

Sample answer outline

Voice is consistent and represents brand personality, tone shifts with context and user emotional state. A strong answer gives a concrete analogy (same person speaks differently to a nervous customer versus a celebrating one), then explains how this maps to product surfaces like error states, onboarding, and success screens.

Expect these follow-ups

• Give me an example of a moment in a product where the tone should be noticeably different from the general brand voice.
• How do you document this distinction so it is usable for a non-writer on the team?

As asked

You are writing copy for a five-screen onboarding flow for a new productivity app. How do you think about what each screen needs to say, how to pace information, and what to defer?

Sample answer outline

Strong answers show understanding of progressive disclosure, the cost of cognitive overload in onboarding, deferring non-essential setup to contextual moments, and keeping copy anchored to user value rather than feature explanation. Candidates should mention working with UX researchers on drop-off data to iterate.

Expect these follow-ups

• How do you decide what is essential to show in onboarding versus what can wait until first use?
• How do you write for users who skip onboarding entirely?

As asked

What is the difference between a field label and placeholder text, and when should you use each? What is the most common mistake you see teams make with placeholder text?

Sample answer outline

Candidates should explain that labels are persistent and essential, placeholder text disappears on focus and fails accessibility standards when used as the sole label, and the most common mistake is using placeholder text instead of a label. Strong answers mention contrast, screen-reader support, and the pattern of persistent labels with optional helper text below.

Expect these follow-ups

• How do you handle a design that has no space for a label above a field?
• What do you put in placeholder text when you do use it alongside a label?

As asked

Walk me through how you actually work in Figma on a day-to-day basis. What does your contribution look like at different stages of design, and how do you handle reviewing or editing copy in a complex file?

Sample answer outline

Candidates should describe familiarity with editing text layers directly, using plugins like Content Reel or Figma's own variables for copy, leaving annotations on frames, using the Figma comment system for async review, and how they manage copy in component libraries versus one-off designs.

Expect these follow-ups

• How do you handle a design file where the copy is split across 50 frames and you need to audit it for consistency?
• Have you used any Figma plugins that changed how you work with copy?

As asked

Show me or describe a piece of copy in your portfolio where you significantly improved the original. What was broken, what was your process for diagnosing it, and what changed?

Sample answer outline

Strong answers identify a specific user or business problem the copy was causing (confusion, drop-off, support tickets), explain the research or heuristic that diagnosed the issue, walk through the revision with reasoning rather than just showing the result, and name a metric or signal that confirmed the improvement.

Expect these follow-ups

• What did you have to cut that you wanted to keep?
• Who challenged your revision and what was their concern?

As asked

Tell me about a time a PM or designer pushed back strongly on copy you had written. What was the disagreement, how did you handle it, and what was the outcome?

Sample answer outline

Candidates should show they listen to understand the underlying concern rather than defending the copy on gut instinct, use evidence or user research to support their position, propose testing when genuinely unsure, and pick their battles strategically rather than fighting every disagreement.

Expect these follow-ups

• When did you concede a copy argument and did you regret it?
• How has your approach to stakeholder disagreements evolved over your career?

As asked

An engineer drops a ticket in your queue with a one-line description and a Figma link. No context, no PRD. What do you do before you write a single word?

Sample answer outline

Candidates should describe their intake process: reading the ticket and Figma for context, reviewing any linked research or PRD, identifying what user problem this solves, checking for existing patterns in the style guide, and scheduling a quick sync only if the written materials leave genuine ambiguity. They should avoid over-meeting.

Expect these follow-ups

• What is the minimum information you need before you can start writing?
• What do you do if the engineer who wrote the ticket has left the company?

As asked

You are writing product copy for a settings flow that will ship in 12 languages. What do you do differently from day one?

Sample answer outline

Write concise but complete strings that do not depend on English word order, humour, or visual position. Avoid concatenated fragments because many languages need different grammar, gender, pluralisation, or sentence order. Provide translators with context: screenshots, character limits, tone notes, and variable meanings. Work with design to allow text expansion and with engineering to support ICU-style plural and select rules. Candidates often mention translation late; senior UX writers design the content model and review workflow so localisation is not a last-minute string export.

Expect these follow-ups

• How do you handle a button label that grows by 40 percent in German?
• What context should a translator receive for an error message?
• How would you review machine-translated UX copy?

As asked

Empty states get ignored in a lot of products. How do you approach writing one, and what do you think about when the empty state could apply to three different user situations?

Sample answer outline

Strong answers distinguish between first-time empty (onboarding opportunity), cleared empty (task complete), and error-caused empty, then explain how each warrants different copy. Candidates should mention the value of a clear next action, the risk of hollow motivational text, and how to advocate for contextual empty states with engineering.

Expect these follow-ups

• How do you decide whether to include an illustration or just copy in an empty state?
• Have you ever had to argue for separate empty-state strings rather than one generic fallback?

As asked

You have been handed a 200-word terms-of-service summary that legal has already approved. It is full of passive voice and jargon. How do you work through simplifying it without losing the legal meaning, and how do you manage legal's review of your revision?

Sample answer outline

Candidates should mention reading level targets (typically 8th grade for consumer products), reading the original to identify the core obligation or right being communicated, stripping passive voice, replacing jargon with plain equivalents, then co-reviewing with legal by showing the original intent is preserved. The process of building trust with legal over time is a differentiator.

Expect these follow-ups

• What tools or frameworks do you use to measure reading complexity?
• Describe a time legal pushed back on your plain-language revision and how you resolved it.

As asked

You are designing copy for a modal that needs to display a warning, show three options, and explain consequences of each. How do you decide what order the content goes in and what level of detail each piece needs?

Sample answer outline

Strong answers reference the inverted pyramid (most critical information first), the user's decision-making need, scanning versus reading patterns, and how visual hierarchy and copy hierarchy should reinforce each other. Candidates should also discuss what to cut versus move to a secondary disclosure or tooltip.

Expect these follow-ups

• How do you handle a PM who wants to add a fourth option to that modal?
• What is your approach when the consequences are asymmetric in severity?

As asked

Push notifications are easy to abuse. What principles guide how you write notification copy, and how do you decide what belongs in a notification versus an in-app message versus an email?

Sample answer outline

Candidates should articulate channel fit based on urgency and relevance, cover character constraints and front-loading for truncation, mention permission fatigue and how notification copy affects opt-out rates, and show awareness of OS-level conventions (iOS and Android differ in character limits and tone norms).

Expect these follow-ups

• How would you advocate for reducing the volume of notifications when the business wants more?
• Give me a notification you rewrote that you believe reduced opt-outs.

As asked

When do you choose a tooltip over inline helper text, and when does neither work and you need to rethink the design instead?

Sample answer outline

Candidates should explain that inline text is for primary, always-visible guidance for unfamiliar concepts, tooltips are for supplementary context on demand for familiar users, and neither is a substitute for a UI that self-explains. Strong answers note accessibility issues with hover-only tooltips and advocate for design changes when tooltips become load-bearing.

Expect these follow-ups

• How do you handle a form where every field seems to need a tooltip?
• What is your accessibility argument against a design that relies on hover tooltips for essential info?

As asked

You have just joined a team with three years of accumulated microcopy written by various people with no style guide. How do you approach a content audit, and how do you prioritise what to fix first?

Sample answer outline

Candidates should describe inventorying strings by surface or user journey, flagging inconsistency, accessibility failures, off-brand tone, and clarity failures separately, then prioritising by user impact and engineering cost. The best answers mention building the style guide from the audit findings rather than in a vacuum.

Expect these follow-ups

• How do you get engineering buy-in to fix copy that does not affect functionality?
• How do you manage the scope creep risk when the audit reveals bigger IA problems?

As asked

You are the first UX writer at a startup. Leadership asks you to create a style guide. Where do you start, what goes in version one, and what do you deliberately leave out?

Sample answer outline

Strong answers focus on writing to current usage patterns first rather than prescribing ideal ones, including the highest-leverage entries (numbers, dates, button labels, capitalisation rules, error message formula), and leaving deep voice guidance until the brand is more stable. Candidates should mention making the guide searchable and example-led rather than rule-heavy.

Expect these follow-ups

• How do you get buy-in from designers and PMs to actually use the guide?
• How do you evolve the guide when the product direction changes significantly?

As asked

Your product shows prices, percentages, file sizes, and dates across multiple surfaces. Walk me through how you would define the formatting rules for each, and what exceptions you would account for.

Sample answer outline

Candidates should address locale-awareness (comma vs period as decimal separator, DD/MM versus MM/DD), the difference between UI copy norms and editorial norms, truncation for space-constrained contexts, rounding conventions, and accessibility considerations for screen-reader pronunciation of numbers and dates.

Expect these follow-ups

• What happens when your formatting convention conflicts with an engineering constraint like a date returned in ISO format?
• How do you handle currency formatting for a product launching in five markets?

As asked

Some teams use title case for navigation, others use sentence case everywhere. How do you decide which to recommend, and how do you handle the debate that almost always follows?

Sample answer outline

Candidates should favour sentence case for most UI contexts citing reduced cognitive load and reading research, acknowledge title case traditions in navigation and product names, explain how to handle proper nouns and trademarks as exceptions, and describe how to socialise the decision with a brief rationale rather than a mandate.

Expect these follow-ups

• How do you handle a design system where components are already built with title-case labels?
• What is your rule for feature names, and does that differ from UI label rules?

As asked

You are writing notification copy for iOS. You know the headline truncates at about 45 characters on most devices. How do you write the copy, and what is your process for testing truncation across devices?

Sample answer outline

Candidates should explain front-loading the most important information, testing on real devices rather than only simulators, building a truncation review step into the copy production process, and advocating with engineering for dynamic truncation points or flexible string design where possible.

Expect these follow-ups

• How do you handle a product name that is itself 40 characters?
• What is your process for reviewing translated strings that may be longer than the original English?

As asked

An engineer tells you the loading screen just says "Loading..." and you have time to improve it. What questions do you ask first, and what options do you consider?

Sample answer outline

Candidates should ask about duration (under two seconds rarely needs copy, over five does), whether progress is deterministic (percentage vs indeterminate), what the user is waiting for, and whether there is an opportunity for useful context. Strong answers note that gimmicky loading messages can feel patronising and context matters.

Expect these follow-ups

• How would your approach differ for a loading state that sometimes takes 30 seconds versus one that is almost always under two seconds?
• What do you write when the loading fails halfway through?

As asked

A user is about to permanently delete their account. Walk me through how you write the confirmation dialog, including the button labels, and how you make sure the user understands what they are doing without adding so much friction they give up on a legitimate task.

Sample answer outline

Strong answers cover specificity ("Delete account permanently" not "Are you sure?"), the case for avoiding generic Yes/No in favour of action-confirming labels, explaining the consequence clearly without being alarmist, considering the undo option or a grace period, and balancing protection against undue friction for users who genuinely want to proceed.

Expect these follow-ups

• How do you decide when to require typing a phrase like "DELETE" to confirm?
• How do you write the post-deletion state after the account is gone?

As asked

You are writing the purpose string for a camera permission request on iOS. What makes a good purpose string, what are the platform constraints, and how do you test whether your string actually improves the grant rate?

Sample answer outline

Candidates should mention that Apple does not publish a hard character limit for NSCameraUsageDescription strings, but in practice shorter, specific strings render better on smaller devices and in system dialogs. The purpose string should answer 'why this feature needs this permission' rather than restating the permission name generically. Candidates should also mention A/B testing grant rates where volume allows, and acknowledge that vague strings sometimes trigger App Store review concerns even without a published rule.

Expect these follow-ups

• How would you write the camera permission string differently for a social app versus a document scanner?
• What do you do if the grant rate is low despite a well-written string?

As asked

What should a success message actually tell the user, and how do you avoid the trap of generic "Success!" messages that give no useful information?

Sample answer outline

Strong answers distinguish between confirming what just happened, indicating what happens next, and providing a path forward or back. Candidates should address inline confirmation versus toast versus page-level feedback, the timing of message display, and avoiding unnecessary repetition of information the user already knows.

Expect these follow-ups

• When is a success message unnecessary and potentially annoying?
• How do you handle a success message for an action that has a delayed effect?

As asked

A settings screen has 40 options. Half are for power users. How do you structure the copy and IA to make this screen usable for both casual and advanced users?

Sample answer outline

Strong answers cover grouping by task rather than technical category, using section headers with clear scope, putting the most common actions first, hiding advanced options behind a secondary disclosure, writing option labels that are self-explanatory without needing a description, and advocating for progressive disclosure of the settings themselves.

Expect these follow-ups

• How do you name section headers when the groupings are not obvious?
• How do you handle a toggle whose label is genuinely ambiguous about what the on state means?