# Data Scientist, Phased Array Antenna System Validation at Amazon

Amazon is hiring a Data Scientist, Phased Array Antenna System Validation. It pays $136k-$184k a year and Level rates it Little AI ●○○○; you can [apply on Amazon](https://jobsbylevel.com/go/97321f57-7b72-4f5f-a4be-eb7798ff2f38?utm_medium=ai-agent).

AI Level 1, AI centrality 16 out of 100. US, WA, Redmond.

## Details

- Company: [Amazon](https://jobsbylevel.com/companies/amazon)
- AI level: AI Level 1 (score 16 out of 100)
- Location: US, WA, Redmond
- Salary: $136k-$184k
- Posted: November 6, 2026
- Apply: https://jobsbylevel.com/go/97321f57-7b72-4f5f-a4be-eb7798ff2f38?utm_medium=ai-agent
- Free CV review for this job: https://jobsbylevel.com/cv-review?job=data-scientist-phased-array-antenna-system-validation-at-amazon-6b7114

## Description

Amazon LEO is an initiative to increase global broadband access through a constellation of 3,236 satellites in low Earth orbit (LEO). Its mission is to bring fast, affordable broadband to unserved and underserved communities around the world. Amazon Leo will help close the digital divide by delivering fast, affordable broadband to a wide range of customers, including consumers, businesses, government agencies, and other organizations operating in places without reliable connectivity. About this role We're looking for a Data Scientist to turn data from our satellite fleet into engineering decisions. Every satellite in orbit sends back a steady stream of telemetry. Every unit was also tested heavily on the ground before launch, and the ground segment watches the satellite every day while it operates. Your job is to connect these sources. You'll find out which in-orbit behaviors trace back to what we measured in the factory, which events repeat across the fleet, and which patterns point to weaknesses in the hardware design. Your findings will directly shape how we design, build, test, and operate the next generation of satellites. A typical problem starts small: a handful of satellites show a drifting temperature, an occasional link dropout, or a counter that creeps up faster than expected. You'll work out whether it's a real effect or noise, whether it's spreading, and what the affected units have in common. They might share a manufacturing lot, a configuration, an orbital environment, or a signature in their factory test history. From there you'll form a hypothesis about the physical cause and argue it in front of hardware, firmware, and reliability engineers who will push back hard. You'll also have to say plainly when the data rules your own idea out. Telemetry alone rarely settles the question, so your first stop is the ground test data we already have. Every unit in orbit has a detailed record from manufacturing and environmental testing, and the fleet as a whole is backed by an even larger population of units still on the ground. You'll dig through that history for the same behavior: did the affected units show early signs on the ground, did they sit near a test limit, does the effect appear across many units under certain conditions? Often the answer is already in data no one has looked at in this light. When it isn't, you'll design the ground experiments that can provide it. That means deciding which units to test and under what conditions, how many runs you need before the result means anything, and what outcome would confirm or refute the theory. You'll work with the engineers who run those tests, analyze the results, and close the question with a clear answer and a recommended action. Beyond individual investigations, you'll build the fleet-level view: baselines for healthy behavior, early warning indicators that catch emerging issues before they cause outages, and reliability estimates that tell us how the population is aging. You'll decide which recurring analyses should become automated monitoring and work with software engineers to make that happen. You'll be the person the team turns to when someone asks "is this normal?" about the fleet. The ideal candidate is curious about how hardware fails and comfortable with messy data from many sources. They can turn "we're seeing something odd on a few satellites" into a rigorous analysis and a clear recommendation. What you'll bring: - Master's degree or above in a quantitative field such as statistics, mathematics, data science, physics, electrical or aerospace engineering, or computer science, or PhD - 3/5+ years of hands-on experience in an applied or industry setting using Python and SQL to analyze large datasets such as time series, telemetry, sensor, or test data - Experience applying statistical methods (hypothesis testing, regression, time-series analysis, anomaly detection) to noisy, incomplete real-world data - Experience building visualizations and dashboards

The description is cut here. Read the full offer: https://jobsbylevel.com/jobs/data-scientist-phased-array-antenna-system-validation-at-amazon-6b7114

Source: https://jobsbylevel.com/jobs/data-scientist-phased-array-antenna-system-validation-at-amazon-6b7114

## Cite this page

Level. https://jobsbylevel.com/jobs/data-scientist-phased-array-antenna-system-validation-at-amazon-6b7114.

Get job alerts: https://jobsbylevel.com/newsletter