Amazon.com Inc logo

Systems Engineer, Amazon LEO - Mission Operations

Amazon.com Inc

  • Redmond, WA
  • 22 days ago

    Highlights

    You will own the operational thread from problem discovery through validated closure: identifying systemic issues through incident trends, telemetry, operator feedback, recurring manual interventions, and cross-service failure modes, framing the underlying mission need, and translating it into concepts of operations, system requirements, interface expectations, and testable acceptance criteria. You should be able to decompose ambiguous operational problems across hardware, software, ground, and human elements; identify the assumptions and interfaces driving system risk; and drive multiple engineering teams toward a coherent resolution.

    Numbers & Facts

    LocationRedmond, WA
    IndustryRetail
    Company Size10,000 employees or more
    Year Founded1994
    Websitehttp://Amazon.com/militaryroles

    Description

    Amazon LEO is an initiative to launch a constellation of Low Earth Orbit satellites that will provide low-latency, high-speed broadband connectivity to unserved and underserved communities around the world.

    Key job responsibilities

    As a Systems Engineer within Amazon Leo Mission Operations, you will own the cross-system resolution of operational problems that determine whether multiple satellite constellations-including broadband and direct-to-device-can be operated safely, reliably, and at scale. You will own the operational thread from problem discovery through validated closure: identifying systemic issues through incident trends, telemetry, operator feedback, recurring manual interventions, and cross-service failure modes, framing the underlying mission need, and translating it into concepts of operations, system requirements, interface expectations, and testable acceptance criteria. You will conduct trade studies, requirements decomposition and traceability, interface definition, operational risk assessment, and cross-functional technical decisions. You will author CONOPS documents and operational requirements, define and maintain interface expectations between ground services, and establish clear owners, closure criteria, dependencies, and escalation paths for problems that span organizational boundaries. You will manage the operational risk register, define and track fleet health KPIs, and own the operational architecture roadmap that defines how operations scale across constellations with distinct mission profiles and growing fleet sizes. Your objective is not merely to represent operator requests, but to ensure that operational needs are incorporated into system architecture and resolved without transferring hidden cost, workload, or risk elsewhere in the mission.

    You will define verification strategies that demonstrate compliance with operational requirements and validation strategies that demonstrate mission utility under representative conditions. This includes nominal and off-nominal scenarios, degraded system states, failure injection, recovery behavior, realistic fleet volumes, and representative operator workload. Before a capability reaches the fleet, you will assess the complete operational-readiness package, including observability, procedures, training, support ownership, fallback behavior, and deployment or rollback criteria.

    The ideal candidate combines systems-level thinking with sufficient technical depth to interrogate architectures, requirements, interfaces, telemetry, test evidence, and failure behavior. You should be able to decompose ambiguous operational problems across hardware, software, ground, and human elements; identify the assumptions and interfaces driving system risk; and drive multiple engineering teams toward a coherent resolution. Success requires influence without direct authority, disciplined planning and prioritization, strong written and verbal communication, and a verification mindset that does not treat a capability as complete until it has been proven operable under realistic mission conditions.

    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.

    A day in the life

    You will identify systemic operational problems across the constellation by living in the operational data, triaging anomalies directly, and staying tightly coupled to operator experience. You will author operational requirements and drive cross-functional engineering teams to resolution. You will own operational verification and validation, ensuring solutions work under real fleet conditions. You will manage fleet health KPIs and the operational risk register, tracking what matters and driving accountability. You will define how the constellation is operated at scale and be responsible for the operational readiness of the LEO mission.

    About the team

    Amazon LEO Mission Operations team owns the infrastructure that manages and operates the constellation, providing a stable foundation for the networking team to run customer-facing connectivity service.

    About Company

    At Amazon, we don’t wait for the next big idea to present itself. We envision the shape of impossible things and then we boldly make them reality. So far, this mindset has helped us achieve some incredible things. Let’s build new systems, challenge the status quo, and design the world we want to live in. We believe the work you do here will be the best work of your life.

    Wherever you are in your career exploration, Amazon likely has an opportunity for you. Our research scientists and engineers shape the future of natural language understanding with Alexa. Fulfillment center associates around the globe send customer orders from our warehouses to doorsteps. Product managers set feature requirements, strategy, and marketing messages for brand new customer experiences. And as we grow, we’ll add jobs that haven’t been invented yet.

    It’s Always Day 1
    At Amazon, it’s always “Day 1.” Now, what does this mean and why does it matter? It means that our approach remains the same as it was on Amazon’s very first day – to make smart, fast decisions, stay nimble, invent, and stay focused on delighting our customers. In our 2016 shareholder letter, Amazon CEO Jeff Bezos shared his thoughts on how to keep up a Day 1 company mindset. “Staying in Day 1 requires you to experiment patiently, accept failures, plant seeds, protect saplings, and double down when you see customer delight,” he wrote. “A customer-obsessed culture best creates the conditions where all of that can happen.” You can read the full letter here

    Our Leadership Principles
    Our Leadership Principles help us keep a Day 1 mentality. They aren’t just a pretty inspirational wall hanging. Amazonians use them, every day, whether they’re discussing ideas for new projects, deciding on the best solution for a customer’s problem, or interviewing candidates. To read through our Leadership Principles from Customer Obsession to Bias for Action, visit https://www.amazon.jobs/principles

    Similar Jobs

    See more jobs