Technical Writer - Managed K8s at Bitdeer Technologies Group in 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 the documentation surface for our AI Cloud Kubernetes platform — the API reference, SDK and CLI docs, Terraform provider guides, getting-started paths, and release notes that let customers provision and operate self-serve GPU clusters without opening a support ticket. This is not a proofreading role: you will read the control-plane API, SDK, CLI, and Terraform provider source and diffs directly, verify every documented request and response against a running environment, and update documentation the moment an interface changes rather than after a customer files a ticket about it. You will run a docs-as-code pipeline — versioned alongside the codebase, built and linted in CI, published in lockstep with each release — so documentation ships the same day as the feature, not weeks later. Release notes are treated as a contract: every breaking change, deprecated field, and altered default must be called out precisely enough that a customer can patch their integration in minutes rather than debug a mysterious failure in production. You will treat rising support-ticket volume on any topic as a leading indicator of a documentation gap, tracing repeat tickets back to missing steps, wrong defaults, or undocumented edge cases across cluster lifecycle, provisioning, console workflows, IaC, billing, and security, and closing the gap. The role sits close to engineering: you'll read PRs that touch public interfaces and push back when an API ships without a documented migration path. What you will be responsible for: API, SDK, and CLI Reference Documentation : Own reference documentation for the control-plane API, SDK, CLI, and Terraform provider, writing directly against the OpenAPI spec and source rather than secondhand descriptions from engineers. Verify every request, response, and error code against a live environment before publishing, and regenerate reference pages automatically from schema where possible so drift cannot silently accumulate. Getting-Started and Self-Serve Guides : Build and maintain the onboarding paths that take a new customer from signup to a running GPU workload — cluster creation, provisioning, console navigation, IaC setup — without a support interaction. Structure guides by customer persona (platform admin standing up a cluster versus application developer deploying a workload) so each reader lands on the shortest path to their outcome. Release Notes and Breaking-Change Communication : Own the release notes cadence, writing precise, customer-actionable entries for every breaking change, field deprecation, default-value change, and new capability shipped by the platform. Coordinate with engineering ahead of each release to confirm migration steps are documented and tested, not assumed. Docs-as-Code Pipeline Ownership : Build and operate the docs-as-code pipeline — content versioned in git, built and linted in CI, deployed on the same cadence as product releases — so documentation is never a manual, out-of-band step. Maintain the toolchain (static site generation, doc versioning, search, example validation) as a piece of engineering infrastructure with i