Staff MaaS Backend Engineer at Bitdeer Technologies Group
Austin, TX
—
Aug 19, 2026
Austin, TX
Sep 25, 2026
What this job asks for AI summary
A Staff Backend Engineer role focused on re-architecting an existing Model-as-a-Service (MaaS) platform into a commercially hardened, globally distributed, multi-tenant token service capable of supporting millions of monthly active users. The position co-owns system design with a Principal Architect while holding full delivery accountability — writing and shipping Go services, owning SLOs and on-call for a revenue-bearing API, and setting backend engineering standards for the MaaS team. Strong emphasis on inference gateway design, LLM serving performance, exactly-once metering/billing, and zero-downtime brownfield migrations.
Staff level · 8+ years
Quick apply — this platform usually takes a CV and a few fields.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Aug 20, 2026. It is a model, not a headcount.
Why we read it this way (6)
The posting is headquartered in Singapore with data centers across multiple countries; no specific work location or remote policy is stated. The role has been treated as location-unspecified and the US-based flag defaulted to true, but candidates should confirm the primary work location.
The 8+ years of backend engineering experience is the stated overall floor; the 3+ years owning a high-traffic multi-tenant API platform is a sub-requirement within that, not a separate role-level gate.
OpenAI API and Anthropic API compatibility are called out as wire-format contracts the role must own; OpenAI API is listed as a representative skill for that requirement.
LoRA multiplexing appears in the responsibilities section as a specific technical capability to integrate, not in a formal qualifications block — listed as preferred accordingly.
OAuth appears in the responsibilities section (API key and OAuth credential lifecycle) rather than the qualifications block — listed as preferred accordingly.
No compensation range is disclosed in the posting.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.