← К другим вакансиям
Amazon

RF Systems Scientist, Leo Antenna Team

AgileFluent referral
On-site • Redmond, United States • Senior • $136–184k / год
Зарплата
$136–184k / год
Опубликовано
18 мин назад
Описание

Description

Amazon Leo is Amazon’s low Earth orbit satellite constellation initiative designed to bring fast, affordable broadband connectivity to unserved and underserved communities around the world. We are building a next-generation satellite system from the ground up — designing everything from the spacecraft and payload to the ground infrastructure and customer terminals. This is a rare opportunity to join a team that is shaping the future of global connectivity at scale.

The Leo Antenna team is looking for an RF Systems Scientist who is excited to work at the intersection of radio frequency engineering, phased array antennas, large-scale data analysis, and hardware reliability. You will turn data from our customer terminal fleet into engineering decisions. Every terminal in the field reports a steady stream of telemetry: downlink and uplink signal quality, link state, antenna pointing, temperature, and reboots. Every terminal was also tested in the factory before it shipped, and the network sees every contact it makes with a satellite. Your job is to connect these sources. You'll find out which field behaviors trace back to the antenna hardware and which come from the installation, the sky around the terminal, the network, or a software release. You'll also look for patterns that point to weaknesses in the design. Your findings will shape how we design, build, test, and support the next generation of customer terminals.

A typical problem starts small. A few terminals spend far more time recovering their link than their neighbors, run a little hotter than the rest of the fleet, or reboot more often than they should. You'll work out whether it's a real effect or noise, whether it's spreading, and what the affected terminals have in common. They might share a hardware revision, a software version, a location, 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 antenna, RF, and software engineers who will push back hard. You'll also have to say plainly when the data rules your own idea out.

To find the cause, you'll pull in the rest of each terminal's history: its factory and thermal test results, its software and reboot record, and what the satellite measured on the other side of the link. Some questions can be answered from data we already collect. For the rest, you'll decide what new measurement or test would answer them, work with the teams who can run it, and report what the results show and what should happen next.

Beyond individual investigations, you'll build the fleet-level view. That means expected performance for a healthy terminal given where it is and what it sees, early warning signals for hardware that is starting to fail, and measures of how software releases and hardware revisions change the fleet. You'll decide which recurring analyses should become automate...

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis.

Хочешь прочитать весь текст вакансии?
Авторизуйся за пару секунд, чтобы получить полный доступ к описаниям и откликам.
Войти через Telegram