• Set the standard and make it the default. Define Bolt's product voice, terminology, and patterns for the moments that repeat: prompts, errors, empty states, permissions, billing, settings. Then put it where the work happens, in the design system, in components, in internal agents, so good copy holds up at the speed we ship.
• Raise the bar on everyone's words. Review writing from across the company and give feedback that improves people's judgment, not only the sentence in front of you.
• Own the content strategy. Bring a point of view on what we should say, when, and how much. Shape product direction from problem definition rather than copy-editing at the end.
• Ship content-led features end to end. Feature onboarding, in-product education, the moments where a value prop has to land. You're the design DRI: you scope it, design it in Figma or build it with agentic tools, and drive it through implementation without a product design partner.
• Work across the whole lifecycle. Partner with Marketing and CX so that what we say before someone arrives, inside the product, and after they hit a problem all reinforce each other.

💡 Qualifications

• A portfolio of product content work with at least two examples where you can show the problem, your reasoning, what you rejected, and what changed after it shipped. Complex products, real scale. We care more about judgment than polish.
• You can take a content-led feature from problem to shipped without a product designer. That means designing it in Figma, or building it with agentic tools, to a standard we'd actually ship. If your process depends on someone else turning your words into screens, this role will frustrate us both.
• You've built a standard, a system, or a set of guidelines that other people actually used. Bonus points if you've watched one fail and can explain why.
• You can give feedback that lands, including to people outside design who didn't ask for it and don't share your vocabulary, and to other writers as a peer rather than a manager.
• Strong verbal and written English communication skills are required, as this role involves frequent collaboration with team members, stakeholders, and customers where English is the primary working language.

🎯 Bonus Points

• Startup or small team experience. You are not just one of many!
• Experience shaping AI tools, or writing for products where the interface is a conversation.
• Experience writing for product, marketing and support content, or migrating knowledge between them.
• Consumer product experience.

📌 A Few Notes

• You do not need a college degree to apply

• You do not need to be located in the U.S. — we’re remote-friendly

• You do not need to meet every qualification listed above

Originally posted on Himalayas