Senior Applied Scientist, Amazon Leo, Amazon Leo Networking Software

Amazon Leo is building a low Earth orbit satellite broadband network to deliver fast, affordable connectivity to customers around the world, including those underserved by traditional infrastructure. Operating a live constellation and its ground network at scale means service disruptions are an inevitable reality, and how quickly we detect them, understand them, and prevent them from recurring defines the trust we earn as a connectivity provider.

We are seeking a talented Senior Applied Scientist to build the next generation of observability and availability science for the Leo network. Leo already detects outages, notifies affected customers, and restores service. The frontier is prediction and prevention: reasoning over complex network and ground-segment telemetry to autonomously detect anomalies before they reach customers, attribute root cause automatically across a sprawling event surface, and rationalize a large, still-maturing metric set so responders trust what the system tells them.

In this role you will work backwards from the needs of customers and operations teams. You will own the scientific direction end to end, partnering closely with network engineers, the Network Operations Center, and the Incident Management team, and the Software and Networking orginization to translate a long-term science vision into concrete research and delivery roadmaps.

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

• Own the observability and availability science end to end, from long-term vision to research roadmap to production delivery, working backwards from the needs of customers, the NOC, and network engineering.
• Develop time-series and graph-based models with dynamic baselining that detect network and ground-segment anomalies before they cross the High Severity threshold, enabling proactive investigation rather than reactive response.
• Reason over complex, multi-system telemetry to attribute cause automatically during live HSEs and LSEs, so Call Leaders and engineers spend time mitigating, not hunting.
• Provide the science behind the network"s bucketed availability decomposition (geometric and satellite coverage, ground and network segments, customer terminals, payload, and planning), attributing every movement to a true cause rather than noise, so leadership steers on signal and engineering effort lands where it actually moves availability and throughput.
• Deliver the models, analyses, and metrics that feed the daily system readiness and validation review consumed by senior leadership and product and engineering, turning availability and throughput data into a defensible, evidence-based read on progress against GA entry criteria.
• Own the recurring, fleet-wide "hot topic" investigations that span ASIC, firmware, payload, network, and planning, separating correlated symptoms from true root cause across thousands of nodes, quantifying how much availability or throughput each is costing, and answering whether it is a launch-blocking risk and whether it is improving.
• Deliver alert correlation and deduplication, false-positive reduction, and metric-quality scoring so responders trust what the system tells them, directly supporting a large, still-maturing KPI set.
• Tie your science to the unit the org actually measures: reduce detection and attribution time, raise availability against the network"s bar, and increase the share of events prevented before customer impact.
• Partner day to day with the Network Operations Center, Network Engineering, and the Incident Management (Call Leader) program; sit on live HSE/LSE bridges as the science partner and turn event learnings into model improvements.
• Feed COEs and RCAs back into detection and attribution so recurring signatures are caught earlier, and help design and score gamedays that stress-test both the network and your models against real, closed events.
• Build and deploy production pipelines on AWS (e.g., SageMaker, Bedrock, Glue) with model validation, monitoring, drift detection, and explainability, because operations teams must be able to trust and act on model output under pressure.
• Set data-science standards, mentor scientists, and drive best practices across the Leo networking organization as the science function scales.
• Produce explainable output and written narratives that let responders and leaders three or more levels up act on your models during and between events.