Technical Writer - MaaS at Bitdeer Technologies Group in Singapore; Penang

Job description

About Bitdeer: Bitdeer is a world-leading technology company for Bitcoin mining and AI cloud. Bitdeer is committed to providing comprehensive Bitcoin mining solutions for its customers. Apart from designing industry-leading ASIC chips and manufacturing mining rigs, the Group handles complex processes involved in computing across the value chain. This includes equipment procurement, transport logistics, datacenter design and construction, equipment management, and network and facility operations. Bitdeer also offers advanced cloud capabilities to customers with a high demand for artificial intelligence. Headquartered in Singapore, Bitdeer operates globally with a diversified 3 GW energy portfolio, and deploys Bitcoin mining and HPC datacenters in the United States, Bhutan, Norway, Canada, Malaysia, and Ethiopia. About the role We are seeking a Technical Writer to own end-to-end developer documentation for Bitdeer AI's MaaS platform, spanning API reference, getting-started guides, and release notes for a fast-moving catalog of hosted chat, completion, embedding, and fine-tuning endpoints. Today, developers integrating against our inference API frequently have to reverse-engineer request and response shapes from internal Postman collections, ask engineering directly in Slack, or discover breaking parameter changes only after their integration fails in production, which slows time-to-first-successful-call and generates avoidable support load on the engineering team. This role fixes that by turning our OpenAPI specifications, model catalog, and endpoint behavior into accurate, versioned, always-current documentation that developers can trust as the single source of truth, and by establishing a release notes cadence that keeps pace with model and endpoint updates. The person who succeeds here is comfortable reading Go service code and API diffs well enough to write precisely about them, treats documentation as a product with its own release cycle rather than an afterthought, and can work independently across multiple engineering teams to pull accurate technical detail out of people who are not naturally inclined to write it down themselves. What you will be responsible for: API Reference Ownership : Maintain and continuously improve the OpenAPI-driven API reference covering chat/completions, embeddings, fine-tuning, and model routing endpoints. Verify that documented request/response schemas, error codes, and rate limits match actual service behavior by testing against staging and production endpoints. Work directly with backend engineers to capture new parameters, deprecations, and behavioral edge cases before they ship to customers. Getting-Started and Onboarding Guides : Design and maintain the guides that take a new developer from signing up to making their first successful inference call, including authentication, SDK quickstarts, and common integration patterns across supported languages. Continuously identify drop-off points in the onboarding funnel through support tickets and developer feedback, and rewrite the weakest steps first. Keep sample code runnable and tested against the live API rather than left to go stale. Release Notes and Changelog Discipline : Establish and run a recurring release notes process tied to model catalog updates, new endpoints, pricing changes, and breaking API changes, so developers are never surprised by a change in production. Coordinate with product and engineering release cadences to publish notes before or at the moment of rollout, and clearly flag deprecations, migration steps, and timelines for removal. Docs-as-Code Pipeline and Information Architecture : Own the documentation toolchain (Markdown/MDX, Git-based review, OpenAPI spec linting and generation) so that docs are versioned, reviewable, and testable the same way code is. Organize the growing surface area of models, endpoints, and guides into an information architecture that stays navigable as the model catalog expands. Reduce duplic