UX writer behavioral interview questions

As asked

Tell me about a time you were given a vague or incomplete brief for a copy project. How did you get what you needed, and what happened?

Sample answer outline

Candidates should describe asking targeted questions rather than asking for a rewritten brief, triangulating from what was available (user research, existing copy, product goals), making documented assumptions before writing, and surfacing risks early rather than surfacing them at review.

Expect these follow-ups

• What assumption you made turned out to be wrong?
• How has this experience changed how you kick off a project?

As asked

Tell me about a time you had to write copy for a significant feature with very little time. What did you do to deliver something good under that constraint?

Sample answer outline

Candidates should show they prioritise the highest-impact copy first (CTAs, error messages, empty states), make trade-off decisions explicitly rather than just rushing, know where to find existing approved patterns to reuse, and flag quality risks to stakeholders rather than silently cutting corners.

Expect these follow-ups

• What did you not have time to do, and how did you communicate that?
• Looking back, what would you change about how you handled that sprint?

As asked

Tell me about a time you had to influence a product or design decision outside your direct team specifically because of a content or copy concern. How did you make the case, and what happened?

Sample answer outline

Strong answers show they build relationships proactively rather than showing up only when they need something, frame content concerns in terms of user or business impact, bring evidence (research, data) rather than opinion, and know when to escalate versus accept a decision.

Expect these follow-ups

• What would you do differently now?
• How do you maintain trust with a team you had to push back against?

As asked

Tell me about a piece of copy you shipped that did not work as intended. How did you find out, and what did you do about it?

Sample answer outline

Strong answers show intellectual honesty, describe a specific failure (not a vague "it could have been better"), explain how it came to their attention, what the fix was, and most importantly what changed in their process to prevent the same error. Candidates who claim nothing has ever failed are a red flag.

Expect these follow-ups

• How long did the bad copy live in production?
• What did you learn about your own assumptions that this revealed?

As asked

Describe a time legal or compliance blocked or significantly changed your copy. How did you handle the review, and what was the final outcome?

Sample answer outline

Candidates should show they understand the legal concern before arguing against it, find creative solutions that satisfy the legal requirement without destroying clarity, and build a relationship with legal over time so reviews become collaborative rather than adversarial.

Expect these follow-ups

• How do you prepare copy for legal review to reduce back-and-forth?
• Has legal ever been right in a way that genuinely improved your copy?

As asked

Tell me about a time business goals or stakeholder pressure pushed you toward copy that you believed would confuse or mislead users. What did you do?

Sample answer outline

Strong answers show candidates take user advocacy seriously and have a principled stance, can articulate the risk in business terms (increased support contacts, churn, trust erosion), escalate when needed, and know the difference between a dark pattern and a legitimate marketing choice.

Expect these follow-ups

• What happens when you escalate and the decision still goes against users?
• Have you ever left a role over an ethics disagreement like this?

As asked

Tell me about a time you shipped copy you were not happy with because of constraints beyond your control. How did you communicate the risk, and did you ever get the chance to fix it?

Sample answer outline

Candidates should show they document compromises and their risk at the time, track the backlog item proactively, and use data (if it materialises) to re-prioritise the fix. Strong answers show ownership across ship and post-ship phases.

Expect these follow-ups

• How do you balance accepting constraints versus continuing to advocate for better copy?
• How do you keep track of all the compromises across a complex product without losing them?

As asked

Tell me about a time you worked on a design project with a team spread across time zones. How did you make your copy contributions work in an async environment?

Sample answer outline

Candidates should describe specific async practices: detailed Figma comments with rationale, content specs that pre-answer likely questions, clearly communicated review deadlines, and proactive status sharing. Strong answers show they take ownership of communication rather than waiting for it.

Expect these follow-ups

• What was the hardest part of async copy review for you?
• How do you handle a design that has changed while your copy comments were waiting for review?

As asked

Tell me about something specific you did in the last year to improve your UX writing craft, not your process or tools but the actual writing itself. What prompted it and what changed?

Sample answer outline

Strong answers are specific (studied a particular plain-language framework, got feedback from a writer they admire, analysed competitor microcopy, joined a critique group) and show genuine reflection on what changed in their writing as a result. Vague answers about "always learning" are a weak signal.

Expect these follow-ups

• What is the next thing on your list to work on?
• How do you solicit honest feedback on your writing when your team always says it looks good?

As asked

Design wants to call a feature 'spaces', marketing wants 'work hubs', and engineering calls it 'projects' in the API. How do you resolve the terminology?

Sample answer outline

Start by identifying the user mental model and the jobs the term must do in navigation, onboarding, help, and support. Audit existing product language and competitor patterns, then test comprehension if the choice is risky. The chosen term should be clear before it is branded, and internal implementation names should not leak into the UI unless they help users. Document the decision in a content style guide or taxonomy so it sticks. Strong answers show facilitation and evidence, not personal taste dressed up as writing judgement.

Expect these follow-ups

• When would you choose a distinctive branded term over a plain one?
• How do you migrate terminology already used by customers?
• What if the API name cannot change?

As asked

Tell me about a time you helped onboard or mentor a more junior UX writer or content designer. What specifically did you focus on for their writing craft and process, what did you get wrong, and what did you learn?

Sample answer outline

Candidates should describe concrete support (sharing copy specs templates, reviewing their work, explaining the decision rationale not just the decision, giving feedback that develops judgment not just fixes the copy), acknowledge what they did not do well, and show genuine investment in the other person's growth.

Expect these follow-ups

• How do you give feedback on copy that is technically correct but misses the voice?
• What did you learn about your own practice by explaining it to someone junior?

As asked

Tell me about a time you had to write copy for a sensitive topic, such as financial hardship, health, bereavement, or safety. How did you approach it, and what made it difficult?

Sample answer outline

Strong answers demonstrate empathy-first thinking, research into how the affected community prefers to be addressed, review with subject-matter experts or advocacy groups, awareness of what not to say as much as what to say, and the emotional labour involved in this kind of writing.

Expect these follow-ups

• What resources did you use to ensure you were not inadvertently causing harm?
• How do you protect your own wellbeing when writing about difficult topics regularly?