The Facility Software Automation TeamExamples of key problems the team is working on- We do not just watch infrastructure run. We use the signals we collect to build automations that act on it -- compressing the time between a facility coming online and compute being in customers' hands. Detect, decide, act. If we fail to do any one of those three, we lose the trust of the customers who depend on us to keep the frontier moving.
- Bad telemetry is a trust failure at gigawatt scale. Every facility Fluidstack operates runs on the data we collect. A missed signal is a missed alert. A missed alert is a customer running frontier AI workloads on infrastructure that cannot see itself. At the scale we are building, that is not a monitoring gap -- it is an outage.
- The platform has to scale as fast as the build does. Fluidstack delivers gigawatts of compute in six months -- a fraction of the industry's 18 to 24 month timeline -- and every new site adds more devices, more signals, and more automation decisions that depend on clean data. The telemetry platform either grows ahead of the business or it becomes the constraint that slows it down.
Role Scope- Build and own production services across the telemetry collectors, ingesters, and automation stack that every downstream Automation and Operations team depends on.
- Design and evolve the messaging and time-series data layer that ingests real-time telemetry from device signals across the global compute fleet.
- Own the software infrastructure and data lake underpinning the platform, setting the data contracts and engineering standards other teams build against.
- Build the APIs and dashboards that surface telemetry to commissioning, operations, and leadership teams in real time.
- Drive the integration between device-level data streams and the automation API layer as the platform scales to new sites.
What We're Looking ForThe below is a starting point. We always make space for exceptional people, so if you don't fit this role exactly, tell us where you would.- You've built and owned production services that other teams depend on, and you don't ship code you wouldn't want to be paged for at 3am.
- You treat telemetry pipeline health and data integrity as non-negotiable, because the automation decisions that deliver compute to customers are only as good as the signal underneath them.
- You've worked with high-throughput messaging systems (NATS, Kafka, or equivalent) at real scale and know where the failure modes show up before they hit production.
- You've designed time-series data models in ClickHouse, TimescaleDB, or a comparable system, and can walk through the tradeoffs between write throughput, query performance, and schema evolution.
- You've instrumented production services with observability tooling (Prometheus, Grafana, or equivalent) and treat metrics and alerting as part of shipping, not an afterthought.
- You've worked across the full signal chain from device to database, and you design pipelines backwards from device-level constraints so they're correct by design.
- You move toward a broken pipeline in production with urgency and without drama.
- Bonus: Kubernetes and ArgoCD for production service deployment. ClickHouse schema design for time-series workloads. Compute or critical infrastructure telemetry environments. Real-time dash-boarding with Grafana or equivalent.
Compensation: $250,000 - $300,000 per year, depending on experience, skills, qualifications, and location. Offers equity in the form of stock options.
We are committed to pay equity and transparency.
