The posting
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 its own reliability bar.
- Support-Ticket-Driven Gap Closure: Monitor ticket volume and topic trends with the support team and treat sustained spikes on any feature as a signal that documentation, not the product, needs to change. Ship the fix, then track whether ticket volume on that topic actually drops, closing the loop rather than treating the doc update as done on merge.
- Cross-Functional Engineering Engagement: Read design docs and PRs that touch public interfaces early enough to document features before launch, not after the first confused customer. Partner with product and engineering to ensure new capabilities ship with getting-started coverage and reference docs on day one, and flag when a proposed API or CLI change would be difficult for a customer to self-serve.
How you will stand out:
- Bring 2+ years of technical writing experience for a developer-facing API, cloud, or infrastructure product, with direct ownership of API reference and getting-started documentation for paying customers. Experience documenting Kubernetes, GPU infrastructure, or other complex control-plane systems is strongly preferred.
- Demonstrate hands-on technical fluency: you can read Go or TypeScript well enough to verify a documented behavior against source, work directly from OpenAPI specs, and run the CLI, SDK, and Terraform provider yourself to confirm every example actually works before publishing it. You are comfortable in a Kubernetes environment (kubectl, Helm, cluster provisioning) rather than documenting it secondhand.
- Show proven experience running a docs-as-code pipeline — git-based content, CI build and lint, versioned publishing synced to a software release cadence — including selecting and maintaining the toolchain (static site generators, OpenAPI-driven reference generation, doc versioning). You should be able to point to a specific pipeline you built or significantly improved.
- Have a track record of writing release notes and breaking-change communication for an API that customers depend on in production, precise enough that customers can act on them without opening a ticket. You understand how to structure a deprecation notice or migration guide so it prevents support escalations rather than triggering them.
- Be able to work from support-ticket data to prioritize documentation work, partnering with support and engineering to identify where missing or unclear docs are driving ticket volume. You communicate directly with engineers about upcoming API changes and can hold a technical conversation about design trade-offs, not just document the outcome.
What you will experience working with us:
- A culture that values authenticity and diversity of thoughts and backgrounds;
- An inclusive and respectable environment with open workspaces and exciting start-up spirit;
- Fast-growing company with the chance to network with industrial pioneers and enthusiasts;
- Ability to contribute directly and make an impact on the future of the digital asset industry;
- Involvement in new projects, developing processes/systems;
- Personal accountability, autonomy, fast growth, and learning opportunities;
- Attractive welfare benefits and developmental opportunities such as training and mentoring.
--------------------------------------------------------------------
Bitdeer is committed to providing equal employment opportunities in accordance with country, state, and local laws. Bitdeer does not discriminate against employees or applicants based on conditions such as race, colour, gender identity and/or expression, sexual orientation, marital and/or parental status, religion, political opinion, nationality, ethnic background or social origin, social status, disability, age, indigenous status, and union.
#LI-ST1
