> Markdown version of [/jobs/ext/2635125-software-engineer-backend](https://www.wearedevelopers.com/jobs/ext/2635125-software-engineer-backend). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer - Backend - **Company:** Nominal, Inc. - **Location:** New York, NY, United States - **Experience:** Experienced - **Salary:** $130,000.0 - $230,000.0 - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Amazon Web Services, Apache HTTP Server, Microsoft Azure, Cloud Computing, Databases, Distributed Systems, Fault Tolerance, Performance Tuning, Software Architecture, Data Streaming, Parquet, Data Processing, Real Time Systems, Data Ingestion, Database Optimization, Apache Spark, Backend, Build Management, Kubernetes, Druid, Low Latency, Influxdb, Apache Flink, Apache Kafka, Vertica, Terraform, Docker - **Published:** August 3, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=7fe6854abfb40355 ## About the Role * 3+ years building distributed systems where performance, reliability, and operational simplicity matter. * Strong experience in Go, Rust, or Java, with an emphasis on correctness, clarity, 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 (e.g., ClickHouse, TimescaleDB, Druid, InfluxDB, Parquet). * Experience with streaming or data processing technologies such as Kafka, Apache Arrow, Flink, or Spark. * Comfort reasoning about distributed systems tradeoffs: latency vs. throughput, consistency vs. availability, abstraction vs. control. * Clear technical communication and a bias toward ownership: you design it, build it, ship it, and operate it. ## Description Nominal's backend runs on a set of Platform teams that own everything below the product surface: ingesting and storing the world's hardware data, making it queryable at scale, and keeping the whole system running across cloud, on-prem, and air-gapped environments. As a Backend Software Engineer, you'll join one of these teams and design and build the distributed infrastructure that powers the telemetry and validation platform, systems that ingest multi-modal data (time series, video, point clouds, asset and run catalogs), serve it back at high scale, and hold up under real production load from customers. This role is ideal for engineers who enjoy working close to the metal of distributed systems, reasoning about throughput, latency, data models, and failure, and who want to see their work directly enable real-world hardware. You'll own critical backend systems end to end, from ingestion pipelines to storage engines to performance tuning in production. What you'll do: * Architect and evolve distributed systems that ingest, process, and persist high-frequency telemetry and sensor data. * Design storage and indexing strategies for large, time-series, and event-driven datasets with strict performance and correctness requirements. * Tackle hard problems around scalability, backpressure, fault tolerance, and data consistency in real-time systems. * Optimize hot paths, reduce tail latency, and improve reliability as the system scales with new customers and use cases. * Collaborate closely with product, infrastructure, and customer-facing engineers to solve domain-specific problems for cutting-edge hardware teams. * Influence backend architecture and technical direction, mentor teammates, and raise the bar for system design across the org. ## Related Videos - [Docker Compose: Rediscovered](https://www.wearedevelopers.com/videos/1978-docker-compose-rediscovered) - [How building an industry DBMS differs from building a research one](https://www.wearedevelopers.com/videos/768-how-building-an-industry-dbms-differs-from-building-a-research-one) - [Docker build without Docker](https://www.wearedevelopers.com/videos/100114-docker-build-without-docker) - [Maximising Cassandra's Potential: Tips on Schema, Queries, Parallel Access, and Reactive Programming](https://www.wearedevelopers.com/videos/1167-maximising-cassandra-s-potential-tips-on-schema-queries-parallel-access-and-reactive-programming) - [Scaling: from 0 to 20 million users](https://www.wearedevelopers.com/videos/676-scaling-from-0-to-20-million-users) - [Docker network without Docker](https://www.wearedevelopers.com/videos/1418-docker-network-without-docker) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [20 Essential Tools For Backend Development](https://www.wearedevelopers.com/magazine/218-20-essential-tools-for-backend-development) - [What’s the Difference Between Frontend and Backend Development?](https://www.wearedevelopers.com/magazine/240-what-s-the-difference-between-frontend-and-backend-development) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)