As a Technical Writer, Developer Documentation, you own the documentation that makes our developer platform usable. You translate complex systems—APIs, SDKs, hardware interfaces, communication protocols—into clear, accurate reference material, guides, and tutorials that developers can actually work from. You're as comfortable in a text editor as you are in a terminal, and you treat documentation with the same rigor an engineer brings to code.
Duties
Write, edit, and maintain developer-facing documentation: API references, integration guides, quickstarts, tutorials, and conceptual overviews
Work directly in source files—edit code, run scripts, and use command-line tools to pull, process, and publish documentation from the codebase
Own the docs toolchain: build documentation locally, troubleshoot pipeline issues, and keep output clean and consistent across formats
Create clear technical diagrams—system architecture, data flows, sequence diagrams—that complement written content
Collaborate with engineers to understand systems deeply enough to document them accurately, and push back when something isn't clear enough to explain
Review and edit engineer-written content for clarity, completeness, and consistency
Maintain a style guide and enforce documentation standards across the portal
Required Skills
Exceptional technical writing ability: clear, precise, and concise—no padding, no jargon for its own sake
Comfort working in a codebase: reading and editing source files, running build scripts, using Git for version control
Proficiency with Markdown and familiarity with docs-as-code workflows
Ability to read code in at least one language well enough to document it accurately—Python, JavaScript, C, or similar
Experience creating technical diagrams (draw.io, Lucidchart, Mermaid, or equivalent)
Solid understanding of REST APIs and developer tooling fundamentals
Nice to Have
Prior experience writing documentation for a developer portal, SDK, or hardware API
Familiarity with documentation frameworks such as Docusaurus, MkDocs, or Sphinx
Exposure to OpenAPI/Swagger for API reference generation
Experience in a robotics, embedded systems, or hardware-adjacent environment
Basic scripting ability in Python or Bash for documentation automation
Choose a new password (at least 8 characters, with uppercase, lowercase, a number, and a special character). Note: changing your password will log you out of all active sessions.