Embedded Software Engineer, Amazon Leo

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 must remove boilerplate: EEO, accommodation, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove Job ID etc. We need to preserve all substantive information. Let's parse the description. First paragraph: Description Amazon Leo is a low Earth orbit satellite broadband network... As an Embedded Software Engineer, you will be a part of the team participating in the definition and implementation of the Amazon Leo’s satellite communication software stack. In this role, you will develop embedded software modules and test frameworks for the Leo satellite constellation. You will be responsible for the design, implementation, deployment and operations of a 3GPP 5G NTN and Open RAN based networking and management stack functions for the satellite payloads. You will work closely with software, test and validation, reliability, RF hardware, and custom silicon development teams to optimize low-latency high-reliability payload connectivity solution. 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: bullet list. Basic Qualifications: bullet list. Preferred Qualifications: bullet list. Then Amazon is an equal opportunity employer... (remove). Then accommodation etc (remove). Then If the country/region you’re applying in isn’t listed... (remove). Then 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. 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. Then location salary ranges: USA, TX, Austin - 143,700.00 - 194,400.00 USD annually; USA, WA, Redmond - 143,700.00 - 194,400.00 USD annually. Company - Amazon Kuiper Manufacturing Enterprises LLC Job ID: A10552156 (remove). We need sections: About the role (maybe from description paragraph). Responsibilities (Key job responsibilities). Requirements (maybe Basic Qualifications). Qualifications (Preferred Qualifications). Skills (maybe combine languages, etc). Benefits (benefits description). Pay (salary ranges). Schedule (maybe not present; no schedule info, so omit). Also Export Control Requirement could be part of Requirements or a separate note; but we can include as part of Requirements (maybe as a note). The instruction: include a section ONLY when posting has real specific content. So we need to decide which sections to include. We have content for About the role (first paragraph). Responsibilities (list). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills (maybe we can extract from responsibilities: programming languages, Linux, RTOS, etc). Benefits (benefits description). Pay (salary ranges). Schedule: none -> omit. We must not repeat job title as heading. Use

for each section heading. We need to use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate like EEO, accommodation, etc. We need to ensure we don't include placeholder text like "commensurate with experience". Not present. We need to avoid duplicating lines. Let's extract content. About the role: The description paragraph(s) before Export Control Requirement? The first paragraph(s) describing mission and role. Let's capture: "Amazon Leo is a low Earth orbit satellite broadband network. Its mission is to deliver fast, reliable internet to customers and communities around the world, and we’ve designed the system with the capacity, flexibility, and performance to serve a wide range of customers, from individual households to schools, hospitals, businesses, government agencies, and other organizations operating in locations without reliable connectivity. As an Embedded Software Engineer, you will be a part of the team participating in the definition and implementation of the Amazon Leo’s satellite communication software stack. In this role, you will develop embedded software modules and test frameworks for the Leo satellite constellation. You will be responsible for the design, implementation, deployment and operations of a 3GPP 5G NTN and Open RAN based networking and management stack functions for the satellite payloads. You will work closely with software, test and validation, reliability, RF hardware, and custom silicon development teams to optimize low-latency high-reliability payload connectivity solution." That's substantive. 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." We could include that under Requirements or a separate note. Since it's a requirement, we can put under Requirements as a bullet or paragraph. Key job responsibilities: list: - Develop embedded software for satellites and ground systems related to the operation, validation, and management of a 3GPP 5G networking stack. - Participate in all phases of SDLC including requirements gathering, design, code, test, and code/test coverage. - Developing embedded software modules in assembly, C, C++, Rust or other languages operating against 3GPP 5G/ O-RAN defined protocols and interfaces - Have experience with real-time embedded software development and robust design practices - Have expertise with Linux and RTOS - Review schematics, logic analyzer, wireless signal and protocol analysis, and embedded software (bare-metal) troubleshooting techniques. Note: Some bullet points start with verb forms; we keep as is. Basic Qualifications: - 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 languages such as C/C++, Python, Java or Perl - Experience working with Linux operating systems - Experience with embedded software Preferred Qualifications: - Bachelor's degree in computer science or equivalent - 5+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience - Bachelor's degree or equivalent in Computer Science (duplicate? Actually first is Bachelor's degree in computer science or equivalent; second is Bachelor's degree or equivalent in Computer Science. Might be duplicate; we need to preserve all substantive information but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say to deduplicate. However later: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines: we should remove duplicated lines. So we need to deduplicate identical lines. The two lines are similar but not identical: one says "Bachelor's degree in computer science or equivalent", the other "Bachelor's degree or equivalent in Computer Science". They are essentially same meaning but wording differs. Are they considered duplicated lines? Probably yes, they convey same info. We should keep only one. We'll keep one. - Experience with version control systems and CI/CD pipeline implementation - Experience in wireless system design and architecture, system integration, and RF system analysis - Experience writing low level drivers, or experience in computer architecture - Experience developing PHY/MAC layer HW/SW targeting SoCs, FPGAs, and general-purpose processors Benefits: "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." Also mention sign-on payments and RSUs: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's part of compensation/benefits. Could be under Benefits or Pay. We'll include under Benefits maybe. Pay: Salary ranges: "USA, TX, Austin - 143,700.00 - 194,400.00 USD annually" and "USA, WA, Redmond - 143,700.00 - 194,400.00 USD annually". Also mention base salary range and final compensation determined based on factors. We'll include that. Schedule: none. Now we need to output HTML fragment with headings

  and content. We must not include or . Just the fragment. We'll structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...
  Maybe also include Export Control Requirement as a bullet under Requirements.

  Qualifications

  • ...
  ...

  Skills

  We could list programming languages, Linux, RTOS, etc. But we already have those in Responsibilities/Requirements. However we need to include a Skills section only if posting has real specific content for it. The posting does mention languages, Linux, RTOS, etc. Could be considered skills. But we might avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can combine Skills into Responsibilities or Requirements. But we need to follow the rule: Use sections only when posting has real specific content for it. The posting does have content that could be considered skills (experience with languages, Linux, RTOS, etc). However we already have those in Requirements and Responsibilities. If we create a Skills section, we would be duplicating content. Better to not create a Skills section to avoid duplication and keep sections few. Thus we will omit Skills. Benefits:

  Benefits

  or

  ? Benefits is a list; we can use

  • for each benefit item. But the description is a sentence with parentheses. We could break into items: 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, parental leave, sign-on payments, RSUs. That's a lot. We'll keep as a

    maybe. The rule: Use

    • for any list of duties/requirements/benefits. So we should make a list. We'll extract each distinct benefit: - Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, option for Supplemental life plans) - EAP (Employee Assistance Program) - Mental Health Support - Medical Advice Line - Flexible Spending Accounts - Adoption and Surrogacy Reimbursement coverage - 401(k) matching - Paid time off - Parental leave - Sign-on payments - Restricted stock units (RSUs) We could combine some. We'll keep as list. Pay:

      Pay

      Base salary range: USA, TX, Austin - $143,700.00 - $194,400.00