THE TEAM
Mistral is building a sovereign AI cloud for Europe. Our customers in finance, healthcare, and the public sector run frontier models on European-jurisdiction infrastructure, and the Cloud Platform team builds the systems that make that possible — compute orchestration, Kubernetes, bare metal, storage, networking, and the datacenter fleet that runs it all.
We run it all on our own metal, our own network, our own datacenters — which means when something breaks, the fix is ours to write.
European Compute Units let enterprises commit to multi-year capacity on that infrastructure, and we are scaling toward a gigawatt of compute across Europe by 2030. You will design and ship the layer every sovereign AI deployment depends on.
THE ROLE
You will build storage on our cloud.
Block, filesystem, and object storage for training runs, sandboxed workloads, and general compute: you help decide what we build, what we buy, and how it adds up to storage our customers can bet a business on. Some layers we deploy and harden from best-in-class vendors. The ones that matter most we write ourselves in Go — S3-compatible object storage, tiering, backup and recovery, caching layers that put cold data on cheap spinning disks.
Storage is a strategic bet for this org: the systems you build will define how a gigawatt of European compute stores its data.
WHAT YOU WILL DO
- Build the storage stack — block, file, object — for training, sandbox, and general compute workloads.
- Design and write our own services in Go: S3-compatible APIs, tiering, backup and recovery, caching layers.
- Own the data plane: allocation, duplication, tiering, backup and recovery.
- Plan capacity across datacenters and across failure domains — petabytes, not terabytes.
- Partner with Product Managers to shape the storage roadmap and make the technical and business tradeoffs.
WHAT WE'RE LOOKING FOR
- You have built storage systems — object, block, or distributed filesystems — not just operated them. You know what happens when a disk dies mid-write and when a rebalance collides with a backup window.
- Deep distributed-systems fundamentals: durability, consistency, replication, erasure coding, failure domains.
- You have shipped production systems in Go. Systems engineers coming from C++ or Rust who are ready to write Go daily should still talk to us.
- You are comfortable with hardware reality: HDD, SSD, and NVMe tiers, and the economics of each.
- 5+ years building backend or infrastructure systems.
- You have partnered with product, design, and business teams to ship software that reached real users.
- A low-ego, team-first mindset. We care less about your exact domain and more about whether you are the kind of technical force other engineers want to work alongside.