We look for Backend Engineers who have designed and operated services that survive contact with real workloads. If you can reason about queues, schemas, and failure modes the way other people reason about UI components, you will love what we are building.
You will own large portions of our backend, from the APIs that drive operator tooling, to the data pipelines that ingest production telemetry, to the infrastructure that keeps it all observable. Expect to make calls about consistency, latency, and cost, and to defend them with data.
Comfort with distributed systems, modern cloud infrastructure, and at least one strongly typed language is essential. Familiarity with time-series data, streaming pipelines, or fleet management systems is a plus.
If you have a strong opinion about when to keep things boring and when to introduce something new, we want to hear it.