Software Development Engineer, Amazon Leo Ground Systems Engineering

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Content: - Description: Amazon Leo initiative... looking for a Software Development Engineer... - Export Control Requirement: must be US citizen etc. - Key job responsibilities: list bullet points. - A day in the life: prose. - About The Team: prose. - Basic Qualifications: list. - Preferred Qualifications: list. - Benefits: mention comprehensive benefits list. - Pay: base salary range listed: USA, WA, Redmond - 143,700.00 - 194,400.00 USD annually. Also mention sign-on payments and RSUs. - Schedule: not mentioned. - Skills: maybe from Preferred Qualifications: experience with distributed systems, hardware/software troubleshooting, building data pipelines on AWS with Python, etc. We need to avoid boilerplate: EEO, equal opportunity, accommodations, etc. Also remove duplicated lines. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive info. We need to not repeat job title as heading. We need to not put Job ID as heading. We need to include sections only when posting has real specific content. Thus sections likely: About the role (maybe from description?), Responsibilities, Requirements (maybe Basic Qualifications?), Qualifications (maybe Preferred Qualifications?), Skills (maybe from Preferred?), Benefits, Pay. Schedule: none -> omit. We need to decide mapping. "About the role": could be the initial description paragraph: "Amazon Leo is an initiative... We are looking for a Software Development Engineer to help us build this service from the ground up." plus maybe Export Control Requirement? That is a requirement but could be in Requirements. "Responsibilities": the bullet list under "Key job responsibilities" plus maybe "A day in the life" could be part of responsibilities or separate but we can incorporate. "Requirements": Basic Qualifications. "Qualifications": Preferred Qualifications. "Skills": maybe combine relevant skills from Preferred Qualifications: experience with distributed systems, hardware/software troubleshooting, building data pipelines or services on AWS with Python, etc. "Benefits": the paragraph about comprehensive benefits. "Pay": the base salary range plus sign-on payments and RSUs. We must not include filler like "commensurate with experience". Not present. We need to ensure we don't include duplicated lines. Let's extract content. Description paragraph: "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 under-served communities around the world. We are looking for a Software Development Engineer to help us build this service from the ground up." 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 (list): - Design, develop, deploy, and support software that keeps a globally deployed fleet of ground terminals healthy and available. - Build and scale data pipelines and monitoring that enable condition monitoring, predictive maintenance, and automated remediation. - Develop automation for the integration, test, calibration, and release of ground systems software. - Own the full software development lifecycle, including design, testing, deployment, mission integration, and operational support. A day in the life: "In this role as a Software Development Engineer, you will design, implement, optimize, and operate systems critical to the uptime and performance of Leo ground terminals. Your contributions will have a direct impact on customers around the world." About The Team: "The Leo Ground Systems Engineering team is responsible for the development, deployment, and long-term performance optimization of the Leo satellite Gateway and Telemetry, Tracking, and Command (TT&C) terminals located around the world. These terminals include full-motion parabolic antennas, radio frequency spectrum monitoring, terminal monitoring and control, and fault management systems. These software-driven distributed systems form the communications backbone for the Leo constellation and must provide the world-class reliability, uptime, and performance our customers expect from Amazon." Basic Qualifications (list): - 3+ years of non-internship professional software development experience - 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience - Experience programming with at least one software programming language Preferred Qualifications (list): - 3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience - Bachelor's degree in computer science or equivalent - Experience with distributed systems and a mix of hardware/software troubleshooting - Experience building data pipelines or services on AWS (e.g., DynamoDB, record streaming, data lakes) with Python Benefits paragraph: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." plus base salary range. Pay section: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. USA, WA, Redmond - 143,700.00 - 194,400.00 USD annually" We need to include that. Schedule: none. Now produce HTML. We need to use

  for each section heading. We need to use

  • for any list of duties/requirements/benefits. For Benefits, we have a paragraph describing benefits; could be a list but it's a paragraph. We'll use

    . For Pay, we have prose plus maybe list? We'll use

    . We need to avoid duplication: The Export Control Requirement could be part of Requirements (Basic Qualifications) or a separate Requirement? It's a eligibility requirement. We'll include it under Requirements as a list item maybe. But we have Basic Qualifications list; we could add Export Control as an item. Better: Under Requirements section, include both Basic Qualifications and Export Control Requirement as list items. But we must not invent headings; we have Requirements heading. We need to preserve all substantive info. Thus: maybe not needed; just headings and content. We'll output:

    About the role

    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 under-served communities around the world. We are looking for a Software Development Engineer to help us build this service from the ground up.

    Responsibilities

    • Design, develop, deploy, and support software that keeps a globally deployed fleet of ground terminals healthy and available.
    • Build and scale data pipelines and monitoring that enable condition monitoring, predictive maintenance, and automated remediation.
    • Develop automation for the integration, test, calibration, and release of ground systems software.
    • Own the full software development lifecycle, including design, testing, deployment, mission integration, and operational support.
    • In this role as a Software Development Engineer, you will design, implement, optimize, and operate systems critical to the uptime and performance of Leo ground terminals. Your contributions will have a direct impact on customers around the world.
    But note: The day in the life is prose; we could keep as

    but we included as list item; maybe better to keep as

    after list. However rule: Use

    • for any list of duties/requirements/benefits, and

      for prose. So day in the life is prose, not a duty list. So we should separate. Thus:

      Responsibilities

      • Design, develop, deploy, and support software that keeps a globally deployed fleet of ground terminals healthy and available.
      • Build and scale data pipelines and monitoring that enable condition monitoring, predictive maintenance, and automated remediation.
      • Develop automation for the integration, test, calibration, and release of ground systems software.
      • Own the full software development lifecycle, including design, testing, deployment, mission integration, and operational support.

      In this role as a Software Development Engineer, you will design, implement, optimize, and operate systems critical to the uptime and performance of Leo ground terminals. Your contributions will have a direct impact on customers around the world.

      Now About The Team could be part of About the role? But we already have About the role section; we could add team description there as prose. Or we could make a separate section "About the team" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should incorporate team description into About the role. Thus About the role paragraph can include both the initiative description and team description. Let's combine: About the role: Amazon Leo initiative... We are looking for a Software Development Engineer... The Leo Ground Systems Engineering team is responsible for... We'll put as

      . Now Requirements section: include Basic Qualifications and Export Control Requirement. We'll make list.

      Requirements

      • 3+ years of non-internship professional software development experience
      • 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience
      • Experience programming with at least one software programming language
      • 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.
      Now Qualifications section: Preferred Qualifications.

      Qualifications

      • 3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
      • Bachelor's degree in computer science or equivalent
      • Experience with distributed systems and a mix of hardware/software troubleshooting
      • Experience building data pipelines or services on AWS (e.g., DynamoDB, record streaming, data lakes) with Python
      Now Skills section: Could extract from Preferred Qualifications: experience with distributed systems, hardware/software troubleshooting, building data pipelines on AWS with Python, etc. But we already listed them; maybe we can create a Skills section summarizing those. However we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we create a Skills section that repeats content from Qualifications, that's duplication but still preserving detail; but we might be duplicating. Better to avoid duplication; we could omit Skills section if its content is already covered elsewhere. But we need to decide if we should include Skills section. The posting does not have a explicit "Skills" heading; but we could create one if we have specific skill info not already captured. However the Preferred Qualifications already list skills. If we create Skills section, we would be repeating. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we omit Skills section to avoid thin duplication. Thus we will not include Skills section. Benefits section: we have paragraph.

      Benef