Software Development Engineer- Embedded, OTA Program Team, 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 not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the description. Key parts: - Intro: description of Amazon Leo, mission, role description. - Key job responsibilities: bullet list. - Export Control Requirement: mention citizenship requirement. - A day in the life: description. - About The Team: description. - Basic Qualifications: list. - Preferred Qualifications: list. - Amazon is an equal opportunity employer ... (boilerplate) remove. - If you have a disability ... (boilerplate) remove. - If the country/region you’re applying in isn’t listed ... (boilerplate) remove. - 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 ... 401(k) matching, paid time off, and parental leave. Learn more about our benefits at link. - USA, WA, Redmond - 143,700.00 - 194,400.00 USD annually - Company - Amazon Kuiper Manufacturing Enterprises LLC - Job ID: A10436400 (remove) We need sections: About the role (maybe intro), Responsibilities (key job responsibilities), Requirements (maybe basic qualifications?), Qualifications (maybe preferred?), Skills (maybe languages?), Benefits, Pay, Schedule. We need to decide what content fits each. We have: - About the role: could be the initial paragraph describing mission and role. - Responsibilities: bullet list under "Key job responsibilities". - Requirements: maybe "Basic Qualifications" (must-have). Could also include Export Control Requirement (citizenship) as requirement. - Qualifications: maybe "Preferred Qualifications". - Skills: maybe list of programming languages etc. Could be derived from Basic Qualifications: experience with C#, C++, Java, Perl; OOD; etc. - Benefits: health insurance, 401(k) matching, paid time off, parental leave, sign-on payments, RSUs. - Pay: salary range: $143,700 - $194,400 annually. - Schedule: not mentioned explicitly. No schedule info. So we should not include Schedule section. We must not create sections with placeholder text. So omit Schedule. We need to ensure we don't include boilerplate like EEO etc. We need to preserve all substantive info: include export control requirement, day in the life, about the team, etc. Where to put those? Could be part of About the role or separate sections? The instruction says: use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. If some content doesn't fit exactly, we could still put under About the role (like day in the life, about the team). Or we could create additional sections? Not allowed; only those headings. So we must fit all substantive info into those sections. Thus: - About the role: include mission description, role description, day in the life, about the team maybe. - Responsibilities: key job responsibilities bullet list. - Requirements: basic qualifications + export control requirement. - Qualifications: preferred qualifications. - Skills: maybe list of programming languages, OOD, etc. Could also include design/architecture experience. - Benefits: benefits list. - Pay: salary range. We must not repeat job title. We must not include Job ID etc. We must not include navigation/legal/EEO etc. We must not include duplicated lines. We must preserve all substantive info. Let's extract substantive info: Intro paragraph: "Amazon Leo is Amazon’s low Earth orbit satellite network. Our mission is to deliver fast, reliable internet connectivity to customers beyond the reach of existing networks. From individual households to schools, hospitals, businesses, and government agencies, Amazon Leo will serve people and organizations operating in locations without reliable connectivity. Join our dynamic team developing satellite technology that will revolutionize over-the-air update capabilities for satellite vehicles. In this critical role, you will design and implement robust software solutions that directly impact the proper functioning of satellite systems. Your expertise in problem solving and coding will be essential as you tackle complex challenges in a high-stakes environment where precision and reliability are paramount. This position offers the unique opportunity to work with sophisticated satellite technology while developing features that ensure seamless operation of these advanced systems. You'll collaborate with a technically strong team to solve challenging problems, implement innovative solutions, and maintain critical software infrastructure that powers our satellite fleet. This role provides significant growth potential for someone with the technical aptitude and drive to advance into a Principal Engineer position." That's about the role. Key job responsibilities (bullet list): - Design and develop software solutions for satellite vehicle systems, implementing best practices in code organization, clarity, and error handling while balancing short and long-term technical needs. - Contribute to technical architecture decisions and software development for satellite over-the-air update capabilities, ensuring high reliability, performance, and security in a mission-critical environment. - Collaborate with cross-functional teams to troubleshoot complex support issues, triage bugs, and implement solutions that maintain operational excellence of satellite systems. - Identify and resolve root causes of persistent problems in satellite software, making existing systems simpler while maintaining robust development practices. 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: "Your day begins with a team standup where you'll discuss ongoing projects and address any blockers. You'll spend time in design and implementation discussions for new satellite features, working collaboratively with your team to solve complex technical challenges. Throughout the day, you'll write and review code, triage critical bugs, and provide expert support for over-the-air update issues that require immediate attention. You'll balance proactive feature development with responsive troubleshooting, ensuring the satellite software vehicle maintains optimal performance." About The Team: "Our small, tight-knit team carries significant responsibility due to the criticality of the software we own. We take pride in our technical expertise, with each member being a subject matter expert in their core competency. When pressure mounts, we support each other to ensure mission success. Our team's work directly impacts the proper functioning of satellite vehicles, making our software development efforts crucial to mission success. We value technical excellence, collaborative problem-solving, and mutual support, creating an environment where talented engineers can thrive while working on technology that matters." 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 - 1+ years of software development engineer or related occupational experience - 1+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience - 1+ years of Object Oriented Design experience - Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field - Experience programming with at least one software programming language Preferred 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 Benefits/Pay: - Base salary range: $143,700 - $194,400 annually (USA, WA, Redmond) - Sign-on payments and restricted stock units (RSUs) - Comprehensive benefits: 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. We could also mention location: USA, WA, Redmond. Now we need to map to sections. About the role: include intro paragraph, day in the life, about the team maybe. Responsibilities: bullet list. Requirements: basic qualifications + export control requirement. Qualifications: preferred qualifications. Skills: maybe list of programming languages, OOD, design/architecture experience, etc. Could also include "experience programming with at least one software programming language". But that's already in basic qualifications. Might be redundant. Perhaps we can put skills as the specific technical skills: C#, C++, Java, Perl; OOD; design patterns; reliability and scaling; large-scale multi-tiered multi-threaded embedded/distributed systems; full SDLC; etc. But we need to avoid duplication. However we can still include them as skills, but ensure we don't lose info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all details. If we put some info in multiple sections, that's duplication but not losing info. However we should avoid duplication? Not explicitly prohibited, but better to avoid repeating same sentences. However we can restructure. We could put: - About the role: intro paragraph + day in the life + about the team. - Responsibilities: bullet list. - Requirements: basic qualifications list (including degree, years experience, OOD, programming language, etc.) plus export control requirement. - Qualifications: preferred qualifications list. - Skills: maybe list of specific technologies: C#, C++, Java, Perl; OOD; design patterns; reliability and scaling; large-scale multi-tiered multi-threaded embedded/distributed software applications; full SDLC; etc. But some of those are already in basic qualifications. To avoid duplication, we could treat Skills as a summary of technical skills not covered elsewhere, but we must preserve all info. If we omit some info from Skills that is already elsewhere, it's still preserved elsewhere. So it's okay to not repeat. So we can put Skills as maybe "C#, C++, Java, Perl; Object-Oriented Design; design patterns; reliability and scaling; large-scale multi-tiered multi-threaded embedded/distributed systems; full software development life cycle." That captures many details but not all like years of experience. Those are in Requirements. Thus we keep all info. Benefits: list benefits. Pay: salary range. Schedule: not present, omit. Now produce HTML. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include / or markdown. We'll output something like:

  About the role

  Amazon Leo is Amazon’s low Earth orbit satellite network. Our mission is to deliver fast, reliable internet connectivity to customers beyond the reach of existing networks. From individual households to schools, hospitals, businesses, and government agencies, Amazon Leo will serve people and organizations operating in locations without reliable connectivity. Join our dynamic team developing satellite technology that will revolutionize over-the-air update capabilities for satellite vehicles. In this critical role, you will design and implement robust software solutions that directly impact the proper functioning of satellite systems. Your expertise in problem solving and coding will be essential as you tackle complex challenges in a high-stakes environment where precision and reliability are paramount. This position offers the unique opportunity to work with sophisticated satellite technology while developing features that ensure seamless operation of these advanced systems. You'll collaborate with a technically strong team to solve challenging problems, implement innovative solutions, and maintain critical software infrastructure that powers our satellite fleet. This role provides significant growth potential for someone with the technical aptitude and drive to advance into a Principal Engineer position.

  Your day begins with a team standup where you'll discuss ongoing projects and address any blockers. You'll spend time in design and implementation discussions for new satellite features, working collaboratively with your team to solve complex technical challenges. Throughout the day