Software Development · Austin, TX

On-site Full-time

Software Engineer, Facilities

Fluidstack · Austin, TX · Posted Jul 17, 2026

This posting comes from Fluidstack. Confirm the details on their site before applying.

Overview

Examples of key problems the team is working on: You'll build the production services behind this work: telemetry pipelines, equipment models, control APIs, and test orchestration. Most of our services use Go, NATS, ClickHouse, Redis, and Protobuf/gRPC, and run on Kubernetes.

Responsibilities

  • Build and own the services other teams depend on. Device integrations, telemetry pipelines, equipment models, and APIs need to work together across sites.
  • Design the messaging and state layer. Preserve ordering where it matters, handle consumers falling behind, and recover after a restart without losing data or applying an action twice.
  • Own the data contracts and engineering standards others build against. Make device identity, units, timestamps, and data quality explicit, and evolve schemas and APIs without breaking consumers.
  • Build the path from a control request to a confirmed result. Enforce authorization, deadlines, and equipment constraints, track state changes, and make retries safe.
  • Build observability that explains failures. Measure ingestion lag, dropped data, stale readings, query latency, and command completion so an operator can tell where a problem started.
  • Prove behavior across the whole system. Use unit tests, integration tests, and simulated devices to exercise failure and recovery before changes reach live equipment.

Requirements

  • You've shipped production code in Go, Python, or TypeScript, and you pick up whatever language the problem demands.
  • You have worked with high-throughput messaging systems such as NATS or Kafka. You understand ordering, delivery guarantees, backpressure, and the tradeoffs between concurrency and correctness.
  • You have designed data models for large volumes of time-stamped data. You can reason about slow queries and explain the tradeoffs between write throughput, query performance, retention, and schema evolution.
  • You have instrumented production services with metrics, logs, and profiling. You can show how that instrumentation helped you find a bottleneck or explain an incident.
  • You design before you build. You can explain the alternatives you considered, why you chose a particular design, and when you changed it because it stopped fitting the problem.
  • You define interfaces and failure boundaries deliberately. You know what happens when a dependency is unavailable, and your tests exercise those failures and the recovery path.
  • You have followed data from its source through services and storage. You account for missing, duplicate, late, and invalid data, and handle a stale value differently from a wrong one.
  • Bonus: Prior datacenter or controls experience.
  • Our stack: Go, NATS, Redis, ClickHouse, Protobuf/gRPC, Kubernetes, and ArgoCD. Prometheus and Grafana for production observability.
  • Industrial protocols such as Modbus or OPC UA.

Benefits

  • Bonus, Commission

Great fits start here.

Whether you're looking for your next role or your next team member, give people and possibilities a place to meet.