UX Copywriter

UX Copywriter

Bask Health is building the infrastructure that powers modern telehealth businesses. Our platform enables healthcare companies to launch, operate, and scale digital care experiences, from patient onboarding and clinical workflows to prescriptions, payments, subscriptions, fulfillment, and ongoing care. We're looking for a UX Copywriter to make complex healthcare and software experiences feel clear, human, and easy to navigate.

This isn't a marketing copywriting role. You'll work directly inside the product alongside Design, Product, and Engineering, shaping how Bask communicates with users at every step of their experience.

As a UX Copywriter at Bask, you'll own the words that help people understand what's happening, what they need to do, and what happens next. You'll work across both sides of our platform: the businesses and healthcare teams operating on Bask, and the patients interacting with the experiences those businesses create.

That means writing everything from navigation, buttons, forms, empty states, errors, and onboarding flows to questionnaires, treatment experiences, transactional communications, and AI-powered interactions.

But this role isn't simply about making copy sound better. You'll work with designers to solve product problems through language, challenge unnecessary complexity, identify when a UX problem can't be fixed with copy alone, and help establish the systems that allow Bask to communicate consistently at scale.

We value writers who are concise, highly collaborative, comfortable with complex products, and opinionated about clarity.

• Partner closely with Product Designers from early exploration through production rather than joining the process after designs are complete.

• Write clear, concise, and useful product copy across onboarding, navigation, forms, settings, dashboards, workflows, errors, empty states, confirmations, notifications, and other product surfaces.

• Shape patient-facing experiences including account creation, intake flows, checkout, order management, subscriptions, and ongoing care.

• Write for complex operational experiences used by healthcare businesses, providers, and internal teams without exposing unnecessary technical complexity to users.

• Help users understand what is happening, what action they need to take, and what they can expect next—especially during high-friction or high-stakes moments.

• Work with designers to improve information architecture, hierarchy, naming, navigation, and interaction patterns through language.

• Identify when unclear copy is actually a symptom of a larger product or design problem and work with the team to solve the underlying issue.

• Develop terminology and naming systems for new features, concepts, statuses, actions, and workflows.

• Create and maintain content guidelines that establish consistent voice, tone, terminology, grammar, and writing patterns across Bask.

• Build reusable content patterns for common product situations such as errors, confirmations, destructive actions, permissions, empty states, and system feedback.

• Collaborate with Product Research to understand how users interpret terminology, instructions, and product concepts.

• Test and iterate on product language using research, product data, experimentation, and user feedback.

• Partner with Engineering to ensure content works across different states, edge cases, responsive layouts, and dynamic experiences.

• Help define how Bask communicates through AI-powered experiences, including prompts, generated content, explanations, recommendations, confirmations, and conversational interfaces.

• Use AI tools to accelerate exploration, iteration, audits, and content operations while maintaining strong human judgment over clarity, accuracy, context, and tone.

• Contribute to scalable content systems that allow teams to create consistent experiences without requiring a writer to manually review every string.

At Bask, copy isn't something we add to a design when it's almost finished. Language is part of the interface. A button label can change how someone understands an action. An error message can prevent a support ticket. The right terminology can…