Role Overview
Nominal's backend runs on Platform teams that own ingesting, storing, and serving hardware telemetry data at scale. You will design and build distributed infrastructure for ingestion, storage, and validation.
Responsibilities
- Architect and evolve distributed systems for high-frequency telemetry and sensor data.
- Design storage and indexing strategies for large time-series and event-driven datasets.
- Tackle scalability, backpressure, fault tolerance, and data consistency.
- Optimize hot paths, reduce tail latency, and improve reliability.
- Collaborate with product, infrastructure, and customer-facing engineers.
- Influence backend architecture, mentor teammates, and raise system design bar.
Requirements
- 3+ years building distributed systems where performance, reliability, and operational simplicity matter.
- Strong experience in Go, Rust, or Java, with emphasis on correctness and long-lived systems.
- Deep familiarity with cloud infrastructure (AWS, GCP, or Azure) and production tooling like Kubernetes, Docker, and Terraform.
- Hands-on experience designing or operating storage systems: time-series databases, columnar formats, or analytics engines.
- Experience with streaming or data processing technologies such as Kafka, Apache Arrow, Flink, or Spark.
- Comfort reasoning about distributed systems tradeoffs.
- Clear technical communication and bias toward ownership.