About the role
Documentation is a product here, not an afterthought appended to a release. For a developer-facing platform, docs are frequently the reason someone chooses Yobibyte and the reason they stay once they have. We want them to be genuinely good rather than merely present.
This is a contract engagement owning the documentation surface for the Yobibyte platform, the GPU cloud and InferenceBench. You will work directly with engineers and product, and you will be expected to read source code and verify what you write instead of transcribing what someone tells you. Getting a tutorial wrong costs a developer an afternoon, so accuracy is the standard.
What success looks like
- A new developer can go from landing page to a working result without needing to ask anyone.
- Docs stay accurate as the product changes, because updating them is part of shipping.
- Support and sales stop answering the same questions by hand, because the answer is documented.
Responsibilities
- Own the documentation surface across the platform, GPU cloud and benchmarking products.
- Write and maintain quick-starts, tutorials, how-to guides and conceptual explanations, keeping the types distinct rather than blurring them.
- Produce and maintain API reference material, keeping it synchronised with the actual interface.
- Verify every procedure by running it yourself, and treat anything unverified as a draft.
- Establish and hold voice, tone and structural consistency across the whole documentation set.
- Work with engineering to make documentation part of the definition of done for a change.
- Use support questions and user feedback to find the gaps, and close them.
Requirements
- A portfolio of technical documentation for a developer-facing product, which we will want to read.
- Ability to read TypeScript or Python source and explain accurately what it does.
- Demonstrated command of documentation structure, for example the distinction between tutorial, how-to, reference and explanation.
- Comfort working in a docs-as-code workflow with Git, Markdown and pull-request review.
- Enough command-line and API fluency to test the instructions you publish.
- Precise written English and the discipline to cut words that are not working.
- Self-direction, since this is a contract role where you will set much of your own agenda.
Nice to have
- Familiarity with AI and machine learning concepts, particularly inference and model deployment.
- Experience documenting OpenAPI-described interfaces or generating reference material from schema.
- Background in developer relations or developer education.
- Experience with information architecture for a docs site that has outgrown its original structure.
Role reference: YJ-00008