parity - Documentation Engineer (Builder Experiences)
Requirements
• Technical writing with code fluency: You can read a Rust crate or a TypeScript SDK, understand what it does, and write a tutorial that a developer can follow end-to-end without getting stuck. Show us documentation you've written where the code examples actually work - not pseudocode, not hand-waving, but tested, runnable examples. In this role, you will touch almost everything that Polkadot has to offer through the developer documentation and you are expected to ramp up, understand the code and then document it in user journey based tutorials. • Docs-as-code engineering: You've worked with static site generators (MkDocs, Docusaurus, or similar), written CI/CD pipelines for documentation, and built automation that catches problems before they reach production. You think of docs infrastructure the same way a developer thinks of application infrastructure. • AI adept: This is a team that believes we need to win with AI. You have practical experience using AI tools in your writing or engineering workflow - not just prompting ChatGPT, but integrating AI into documentation pipelines, automated review, or content quality systems. • Developer empathy through evidence: You've tested your documentation with real developers and changed it based on what you found. You can point to a time where you identified that developers were struggling with existing docs, diagnosed the root cause, and restructured the content to fix it. You think of documentation as a product and make it accessible to the users.
Responsibilities
• Documentation Ownership: Own the full developer documentation portfolio - reference docs, tutorials, guides, cookbooks, and code snippets spanning smart contracts, parachains, chain interactions, node infrastructure etc. You won’t be expected to write everything alone, so you’ll need to guide the other engineers on how to create content, striving for accuracy, completeness, and quality. • Automation & Testing: Build and maintain automated pipelines that validate code snippets, detect broken links, flag stale content, and enforce style consistency. Treat documentation like code - if a tutorial's example breaks after an SDK update, you should know before a developer does. • User Journey Design: Map and curate developer user journeys end-to-end. Analyse where developers get stuck, restructure information architecture based on real usage patterns, create analytics and derive actionable insights from them. • Cross-Team Collaboration: Work directly with protocol engineers, SDK teams, and ecosystem tool maintainers to document new features as they ship. Extract knowledge from engineers and translate it into documentation that external developers can actually follow. Also empower other engineers to be able to contribute to the documentation. • AI-Enhanced Workflows: Leverage AI to scale documentation quality - automated style-guide enforcement on PRs, AI-assisted content drafts, web MCPs, llms.txt, intelligent search and retrieval over the docs corpus. Keep up to date with the latest and greatest in AI and leverage it to reduce the lag between code shipping and docs being updated.
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT