Staff Content Designer

<h4 data-start="233" data-end="248">🚀 About Us</h4> <p data-start="250" data-end="267">We’re Bolt.new by StackBlitz!</p> <p data-start="269" data-end="558">We’re the team that brought you WebContainers, the first-of-its-kind technology that made it possible to run Node.js right inside your browser. That breakthrough kicked off our journey in 2019, and it’s what powers the blazing-fast online IDE used by over 1 million developers every month.</p> <p data-start="560" data-end="1013">But we didn’t stop there. We doubled down on everything we learned and built <a class="" href="https://bolt.new" target="_new" data-start="637" data-end="669"><strong data-start="638" data-end="650">Bolt.new</strong></a> — the fastest way to go from idea to production without writing traditional code. It’s a next-gen, AI-powered app builder that helps you create, edit, and deploy full-stack web and mobile apps instantly, right in your browser. No installs. No setup. Just smart automation and instant dev environments that let you move at the speed of thought.</p> <p data-start="1015" data-end="1161">We’re a fully remote team, globally distributed, deeply collaborative, and seriously passionate about building the future of software development.</p> <p data-start="1163" data-end="1342">This is your chance to join a small team with a big vision. If you love shipping fast, solving real problems, and pushing the boundaries of what’s possible, we’d love to meet you.</p> <h4 data-start="1349" data-end="1377">✨ About This Opportunity</h4> <p>Bolt is a product made of language. People describe what they want in words, an agent builds it, and they judge the result without ever reading the code. That makes our words load-bearing in a way they aren't in most products. It also means there's real craft available in nearly every surface, because we've grown fast and written as we go. Nobody is ahead of you in deciding what great looks like.</p> <p><strong>You'll be the first content designer at Bolt, and the job has two halves.</strong></p> <p><strong>Own content as a discipline.</strong> Define the standard: the voice, the patterns, the vocabulary, and the reasons behind them. Then raise the bar on everyone else's words, most of which come from people who aren't designers. Your value here is leverage, not volume. Success looks like PMs and engineers writing better content without you in the room.</p> <p><strong>Ship content-led features end to end, on your own.</strong> Not on day one. We have real content debt, and your first months go to the standard. After that, this becomes the other half of the job: feature onboarding, in-product education, the moments where a value prop has to land. Nobody is assigned to turn your thinking into screens. You're the design DRI, in Figma or with agentic tools, through to shipped.</p> <p>We move fast, and the problems are ambiguous. If the second half reads as daunting rather than fun, this isn't your role. If it's the job you've been waiting for someone to hand you, we should talk.</p> <h4 data-start="1545" data-end="1567">🛠️ How You'll Contribute&nbsp;</h4> <ul> <li><strong>Set the standard and make it the default.</strong> 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.</li> <li><strong>Raise the bar on everyone's words.</strong> Review writing from across the company and give feedback that improves people's judgment, not only the sentence in front of you.</li> <li><strong>Own the content strategy.</strong> 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.</li> <li><strong>Ship content-led features end to end.</strong> 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.</li> <li><strong>Work across the whole lifecycle.</strong> 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.</li> </ul> <h4 data-start="1663" data-end="1706">💡 Qualifications</h4> <ul data-start="1708" data-end="1843"> <li><strong>A portfolio of product content work</strong> 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.</li> <li><strong>You can take a content-led feature from problem to shipped without a product designer.</strong> 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.</li> <li><strong>You've built a standard, a system, or a set of guidelines that other people actually used.</strong> Bonus points if you've watched one fail and can explain why.</li> <li><strong>You can give feedback that lands,</strong> 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.</li> <li>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.</li> </ul> <h4 data-start="1850" data-end="1873">🎯 Bonus Points&nbsp;</h4> <ul> <li>Startup or small team experience. You are not just one of many!</li> <li>Experience shaping AI tools, or writing for products where the interface is a conversation.</li> <li>Experience writing for product, marketing and support content, or migrating knowledge between them.</li> <li>Consumer product experience.</li> </ul> <h4 data-start="1974" data-end="1992">📌 A Few Notes</h4> <ul data-start="1994" data-end="2199"> <li data-start="1994" data-end="2043"> <p data-start="1996" data-end="2043">You do <strong data-start="2003" data-end="2010">not</strong> need a college degree to apply</p> </li> <li data-start="2044" data-end="2134"> <p data-start="2046" data-end="2134">You do <strong data-start="2053" data-end="2060">not</strong> need to be located in the U.S. — we’re remote-friendly</p> </li> <li data-start="2044" data-end="2134"> <p data-start="2046" data-end="2134">You do&nbsp;<strong data-start="2144" data-end="2151">not</strong> need to meet every qualification listed above<br><br></p> </li> </ul>