← Sottava, jobs the hour they open
Posted 2 h ago
Distributed Systems Engineer
Posted by Relace on 21 October 2026. Still on their Ashby board when we checked 53 min ago. Half of Relace's roles come down within 358 days.
What the posting is about
Build and maintain a globally distributed inference cloud. Work on routing layer and fleet management. Requires 5+ years in low-latency systems. Competitive compensation and equity.
Read out of the posting
Levelsenior
Experience asked5+ years
EmploymentFull time
LocationSan Francisco
RemoteNot stated
Visa sponsorshipNot stated
SalaryNot published, and most postings do not
Posted2026-10-21
Found viaashby, direct from their system
We had it within the hour it went up.
The posting, as the company wrote it
About Relace
Relace is building a globally distributed inference cloud. Customers send us requests, we run them on our own fleet of GPUs across the world, and we compete on price, speed and reliability against companies far larger than us. We have customers and revenue today, we’re venture backed, and the team is still small, so roles come with a lot of responsibility and room to grow.
We build our own stack, and the fleet runs on Kubernetes across multiple clouds. Performance here is the business: making the system ten percent faster makes the company roughly ten percent more money, and we can show you the number.
Some numbers: we process 800B+ tokens a day, we’ve grown 3x in the last three months, we are regularly one of the top providers by volume on OpenRouter, and we raised a $23M Series A led by Andreessen Horowitz, with Matrix Partners and Y Combinator.
The role
You would work on how the globally distributed inference runs: the routing layer deciding which machine handles a request, what happens when more work arrives than we have capacity for, and how the fleet grows and shrinks across clouds as demand moves. A lot of it is our own Rust service and the Kubernetes services that manage a multi-cloud fleet.
What we need to see
- Around five or more years building real production systems where latency and failure behaviour mattered: serving systems, control planes, schedulers, databases, networking, trading systems. Not data pipelines or analytics.
- A systems language you know well. Rust, C++ or Go is good.
- Real ownership of something that ran under load, and the ability to talk through a production failure you debugged yourself, in detail.
- Kubernetes at the level of someone who has extended it, particularly on low-reliability infrastructure.
Nice to have
Experience with a scheduler or load balancer as a real project rather than a side task; work with spot or preemptible capacity; any exposure to AI serving systems, which is genuinely optional. We can teach you our domain, but we can’t teach distributed systems instincts.
Working here
San Francisco, in person, five days a week. This is a senior role, with competitive compensation plus equity.
Copied from Relace’s own board, not rewritten. Original ↗
Also open at Relace
Why this page exists
We read companies’ own hiring systems every hour, 1,805 of them, and show a job the hour it opens instead of when a job board gets around to indexing it. We had it within the hour it went up.
The feed is free. No card, no trial to expire.
Apply at RelaceA free account first, no card