Amazon Leo is Amazon's low Earth orbit satellite network. Our mission is to deliver fast, reliable internet connectivity to customers beyond the reach of existing networks. From individual households to schools, hospitals, businesses, and government agencies, Amazon Leo will serve people and organizations operating in locations without reliable connectivity. The Leo Antenna team is looking for a Software Development Engineer who is excited to work at the intersection of large-scale data systems, Amazon Web Services cloud services, data analysis, and radio frequency hardware. In this role, you will design and build Customer Terminal Fleet Health, the system that keeps a daily hardware health record for every customer terminal Leo operates and flags terminals whose hardware is starting to fail. You will turn telemetry from millions of satellite contacts a day into clear, trustworthy signals that tell engineers which terminals need attention and why. You do not need to come in as a radio frequency expert, but you should have a strong software engineering foundation, experience building data pipelines on Amazon Web Services, a high learning velocity, and the drive to understand phased array antennas, satellite links, and how hardware failures show up in telemetry. This is an individual contributor software development role for someone who enjoys ambiguous technical problems, can learn across disciplines, and wants to build data systems that directly improve the reliability of a satellite network. Export Control Requirement Due to applicable export control laws and regulations, candidates must be a U.S. citizen or national, U.S. permanent resident (i.e., current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum. Key job responsibilities Design and build data pipelines on AWS (Step Functions, Athena, Glue, Iceberg, Lambda, S3) that process daily telemetry for the full fleet of customer terminals. Define and own the data model for fleet health: daily per-terminal aggregates, per-satellite views, and the history engineers use to investigate a single terminal. Partner with RF and antenna engineers to understand signal quality, temperature, reboot, and link metrics well enough to separate hardware failures from network, weather, and satellite effects. Develop and validate the rules and models that flag failing hardware, and measure how well they work against terminals returned for repair. Build infrastructure as code with AWS CDK, with deployment pipelines, monitoring, alarms, and integration tests that keep the system reliable. Build dashboards and tools that let engineering and operations teams explore fleet health, compare groups of terminals, and track the effect of software and hardware changes. Apply strong security and data-handling practices to sensitive customer and device data, including least-privilege access, encryption, and privacy controls. Collaborate with data platform and customer terminal software teams to onboard new data sources and improve the telemetry the system depends on. Write high-quality, maintainable code and documentation that other engineers and teams across Leo can build on. A day in the life You may start the day reviewing the overnight fleet health run, checking that every data source arrived and looking at which terminals were newly flagged. You might then sit down with antenna and radio frequency engineers on a group of terminals whose signal quality dropped, digging through the data together to decide whether it points to failing hardware, a software release, or something outside the terminal. Later, you may meet with the data platform and customer terminal software teams to onboard a new telemetry source, then write the infrastructure and pipeline code that brings it into the daily run with tests and alarms in place. You might finish the day with field operations, comparing the watch list against recent hardware returns to see which failures the system flagged early, which it missed, and what each returned terminal can teach the rules. Across all of it, your work helps engineers spot failing hardware before customers notice and measure the effect of software and hardware changes across the fleet. This role requires curiosity, technical depth, and the ability to move between data engineering, cloud infrastructure, and hardware context. You will not just write code; you will help define how Leo understands the health of every terminal in its fleet. About the team The Leo Customer Terminal Software Team supports the devices that connect customers to the Leo satellite network. We provide embedded application software and the underlying Linux system software for these terminals. We work hand in hand with hardware, product, and operations teams to deliver a great experience for our customers. As Leo moves toward full-scale production and global deployment, this is a compelling time to join and help shape how millions of people get online for the first time.
