Staff Technical Writer

<div class="content-intro"><p><strong>About Viam&nbsp;</strong></p> <p>Founded by Eliot Horowitz, co-founder and former CTO of MongoDB, Viam is a novel robotics engineering platform that lets you configure, control, and manage robots intuitively and quickly. We’re inspiring a generation of engineers to solve complicated automation problems with our uniquely powerful suite of software tools.<br><br>We’re a ~100-person company headquartered in New York City.</p></div><p><strong>Role summary</strong></p> <p>As a Staff Technical Writer, you'll own the quality and consistency of Viam's developer-facing documentation. Your work spans all four documentation types: reference docs, explanations, tutorials, and how-to guides. You'll transform rough drafts, working code, and technical walkthroughs into polished, publishable content that helps developers understand and adopt Viam. You’ll also develop docs from scratch through close collaboration with product engineering teams.</p> <h2>What you'll do</h2> <ul> <li>Write and edit documentation that helps developers integrate Viam into their projects, from first API call to production deployment</li> <li>Maintain documentation standards and style guidelines that ensure consistency as content scales</li> <li>Contribute to and improve our documentation toolchain, including our Hugo framework, GitHub Actions workflows, and Vale linting configuration</li> <li>Review code samples for accuracy and clarity, working with engineers to resolve issues</li> <li>Contribute to information architecture decisions—how content is organized, navigated, and discovered</li> <li>Ensure documentation stays current as the platform evolves, identifying gaps and outdated content proactively</li> <li>Build robots and write programs using Viam yourself—we believe the best documentation comes from firsthand experience with the platform</li> </ul> <h2>What you bring</h2> <ul> <li>Experience writing documentation for developers, with a portfolio that demonstrates your ability to explain technical concepts clearly</li> <li>Enough technical fluency to work through tutorials independently, run code samples, and identify errors—you don't need to be an engineer, but you need to be technically curious and comfortable at the command line</li> <li>Experience with docs-as-code workflows: Git, Markdown, static site generators (Hugo experience is a plus)</li> <li>Familiarity with documentation automation—linting tools like Vale, CI/CD pipelines, GitHub Actions, or scripting to improve workflows</li> <li>Strong opinions about what makes documentation good, backed by experience seeing what works and what doesn't</li> <li>The ability t