Engineer, AI Cloud Software

Firmus Technologies

Firmus Technologies is a global leader pioneering the development and operation of efficient AI infrastructure across Asia Pacific.  

Founded in Australia in 2019, our mission is to create the most efficient AI infrastructure by combining cutting-edge technology with a steadfast commitment to sustainability. 

At Firmus, we are unique in our approach. We design, build, and operate a new class of digital infrastructure – the AI Factory. Through our model-to-grid technology approach, we have pushed the boundaries of multi-generational liquid cooling systems, energy management, AI software orchestration, and construction. For our customers, this approach allows us to make every watt count and deliver low-cost AI tokens globally. 

Firmus AI Cloud

Our large-scale GPU cloud platform, Firmus AI Cloud, is purpose-built to deliver energy-efficient AI compute at scale to customers. 

It empowers developers, enterprises, educational institutions, and government users to train and deploy AI models with unmatched efficiency and cost savings. With an ever-growing suite of services and applications, we are committed to delivering a cloud experience that is market-leading, proprietary, and built to scale. 

ROLE SUMMARY 

Firmus Technologies is seeking a Principal Engineer, AI Cloud Software to own the Firmus AI Cloud API and the control plane behind it. Customers, partner platforms, and AI agents use our API to provision and run GPU compute, and our console, SDKs, CLI, and Terraform provider are all built on it. You will set the technical direction for all of it. Everything you design must work across sites and scale to hundreds of thousands of GPUs in gigawatt-scale AI factories. 

KEY RESPONSIBILITIES 

Architecture and decisions 

• Own the overall design of the public API: the resource model, contracts, versioning, and the compatibility promise customers and partner platforms build against. Set one contract style, one identity model, and one versioning policy that every domain team follows. 

• Own the software architecture behind it: service boundaries and the control-plane model. Set a target architecture two to three years ahead and plan the steps from today's system to it. 

• Design the control plane to keep each region serving when another fails, protect it under load with per-tenant rate limits and fair queuing, and remove the limits that would block growth in tenants, resource types, sites, and request volume. 

• Lead design reviews for significant changes across the teams, sign off architecture decision records, and settle technical disputes escalated by engineers. Decide at pace with incomplete information, write down the assumptions, and revisit a decision when the evidence changes.