Neuraphic's products sit at the intersection of AI and security — two domains where the learning curve is steep and the stakes for getting integration wrong are high. The quality of our documentation, tutorials, and developer experience will determine whether people adopt these tools or give up halfway through the quickstart. This role exists to make sure it's the former.
What you'll work on
You'll own the documentation for Prion, Claeth, and Workers end to end. Not just writing it — structuring it, maintaining it, and making hard calls about what belongs in a reference guide versus a tutorial versus an inline code comment. Good documentation is an editorial problem as much as a technical one, and you'll approach it that way.
You'll create tutorials and integration guides that take developers from zero to a working implementation. These need to be honest about complexity — not oversimplified walkthroughs that fall apart in production, but realistic examples that show how the products actually behave. You'll build sample projects, write technical blog posts, and produce content that helps developers understand not just how to use our tools but why they work the way they do.
Community building is part of this too. Neuraphic is pre-launch, which means the developer community doesn't exist yet — you'll be creating it. That means being present where developers are, answering questions with care, gathering feedback that shapes product decisions, and building trust through consistently useful, clearly written content.
What we're looking for
Someone who writes with precision and empathy. You've explained complex technical concepts to developers before — in documentation, blog posts, talks, or open-source projects — and you know the difference between writing that informs and writing that actually teaches. You can read an API, build something with it, and then explain the experience in a way that saves the next person hours of confusion.
You code well enough to build real projects, not toy examples. You've worked with APIs, SDKs, or developer tools in a professional context. You care about the details that make developer experience good or bad: error messages, response formats, naming conventions, the time from signup to first successful API call. If you've worked in AI, security, or infrastructure — that context helps, but strong writing and genuine technical fluency matter more.
How to apply
Email [email protected] with the subject line "Developer Advocate." Include your resume, a link to the best piece of technical content you've created (documentation, tutorial, blog post, video — any format), and a brief note on what you think most developer documentation gets wrong.