Sr. Software Development Engineer, Leo Embedded System Team

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. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: EEO, accommodation link, etc. Also remove "Come work at Amazon!" maybe part of description but it's not boilerplate? It's part of description but could be considered fluff? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Come work at Amazon!" is not boilerplate but maybe considered marketing fluff; but we need to preserve all substantive information. It's not essential but maybe we can keep as part of About the role? The description includes "Project Leo is an initiative..." etc. We need to extract sections. Let's parse the posting: - Description: Project Leo ... mission ... Export Control Requirement: ... (citizenship requirement). That's a requirement. - Key job responsibilities: bullet list (Develop embedded software..., Write device drivers..., Develop security features..., Work closely...) - A day in the life: "Come work at Amazon! We need people who want to join an ambitious program..." This is more marketing; could be part of About the role. - About The Team: description of team functions, looking for outstanding software engineer. - Basic Qualifications: list (5+ years non-internship professional software dev experience; 5+ years programming with at least one software programming language experience; 5+ years leading design or architecture...; Experience as a mentor, tech lead or leading an engineering team) - Preferred Qualifications: list (5+ years of full software development life cycle..., Bachelor's degree in computer science or equivalent; Experience and technical knowledge of security engineering...) - Amazon is committed to diverse... EEO boilerplate (remove). - For individuals with disabilities... (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 https://amazon.jobs/en/benefits. - Then location salary ranges: USA, CA, SUNNYVALE - 193,300.00 - 261,500.00 USD annually; USA, TX, Austin - 168,100.00 - 227,400.00 USD annually; USA, WA, Redmond - 168,100.00 - 227,400.00 USD annually - Company - Amazon Kuiper Manufacturing Enterprises LLC Job ID: A10556822 (remove Job ID, maybe keep company? Not required as heading; could be minor metadata folded into short p.) We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role: could combine description of Project Leo, mission, export control requirement? Actually export control is a requirement (citizenship). About the role could be the overview: Project Leo initiative, mission, etc. Also "A day in the life" maybe. - Responsibilities: the bullet list under "Key job responsibilities". - Requirements: could include export control requirement (citizenship/permanent resident/refugee/asylum) and maybe basic qualifications? But basic qualifications are more like qualifications. The instruction: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have Basic Qualifications and Preferred Qualifications. Those could go under Qualifications (maybe split into Basic and Preferred). Or we could put Basic under Requirements and Preferred under Qualifications? But we have both Requirements and Qualifications sections. Usually Requirements = mandatory qualifications; Qualifications = preferred. We'll follow that. Thus: - Requirements: export control requirement (citizenship/permanent resident/refugee/asylum) + Basic Qualifications (5+ years non-internship professional software development experience, 5+ years programming with at least one software programming language experience, 5+ years leading design or architecture..., Experience as a mentor, tech lead or leading an engineering team). Also maybe "5+ years of programming with at least one software programming language experience" seems redundant with first? but keep. - Qualifications: Preferred Qualifications (5+ years of full software development life cycle..., Bachelor's degree in computer science or equivalent, Experience and technical knowledge of security engineering...). - Skills: maybe we can extract from responsibilities: Rust, C, C++, other modern languages; device drivers; I2C, SPI, CAN; security features; board bring-up; integration. Could list as skills. - Benefits: health insurance details, 401(k) matching, paid time off, parental leave. - Pay: salary ranges per location. - Schedule: not mentioned; we should not create Schedule section because no specific content. So omit. - About the role: overview of Project Leo, mission, maybe "Come work at Amazon!" and About The Team description. We must not repeat job title. Must not include Job ID. Must not include boilerplate like EEO, accommodation link, "Learn more about our benefits at ..." maybe we can keep benefits description but remove the link? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is not boilerplate but could be considered application instruction? It's a link to learn more; maybe we can keep benefits description but drop the link. Safer to keep benefits description without the link. Also "The base salary range for this position is listed below." is filler; we can keep the salary ranges but drop that sentence. Now produce HTML:

About the role

Project Leo is an initiative to increase global broadband access through a constellation of 3,236 satellites in low Earth orbit (LEO). Its mission is to bring fast, affordable broadband to unserved and underserved communities around the world. Project Leo will help close the digital divide by delivering fast, affordable broadband to a wide range of customers, including consumers, businesses, government agencies, and other organizations operating in places without reliable connectivity. The team tackles critical satellite functions including power management, hardware interfaces, command & telemetry, and autonomous control, seeking an outstanding software engineer to participate in all phases of software development from requirements through implementation and test to operations.

Maybe also include "Come work at Amazon! ..." but we can incorporate. Now Responsibilities:

Responsibilities

• Develop embedded software in Rust, C, C++, or other modern languages.
• Write device drivers and system applications for the various satellite systems and device interfaces like I2C, SPI, CAN, etc.
• Develop security features for satellite systems.
• Work closely with other software and hardware teams to support board bring-up and integration.

Requirements:

Requirements

• Must be a U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum (export control requirement).
• 5+ years of non‑internship professional software development experience.
• 5+ years of programming with at least one software programming language.
• 5+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems.
• Experience as a mentor, tech lead, or leading an engineering team.

Qualifications:

Qualifications

• 5+ years of full software development life cycle experience, including coding standards, code reviews, source control management, build processes, testing, and operations.
• Bachelor's degree in computer science or equivalent.
• Experience and technical knowledge of security engineering, system and network security, authentication and security protocols, cryptography, and application security.

Skills:

Skills

• Rust, C, C++, and other modern programming languages.
• Device driver development for I2C, SPI, CAN interfaces.
• Security feature implementation for satellite systems.
• Board bring‑up and hardware‑software integration.

Benefits:

Benefits

• Health insurance (medical, dental, vision, prescription, Basic Life & AD&D, 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 and restricted stock units (RSUs).

Pay:

Pay

• Sunnyvale, CA: $193,300 – $261,500 USD annually.
• Austin, TX: $168,100 – $227,400 USD annually.
• Redmond, WA: $168,100 – $227,400 USD annually.

We should not include Schedule section. Make sure no extra text. Output only HTML fragment. Check for any duplicated lines: none. Check for any boilerplate: we removed EEO, accommodation link, "Learn more about our benefits at", "The base salary range for this position is listed below.", "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." Actually we included sign-on payments and RSUs under Benefits; that's okay. The sentence about final compensation determined based on factors is filler; we omitted. Check for any mention of "Export Control Requirement": we included as requirement. Check for any mention of "Project Leo will help close the digital divide": we included in About the role. Check for any mention of "Come work at Amazon! We need people who want to join an ambitious program...": we omitted; maybe we should include some of that as part of About the role? It's not essential but could be considered fluff. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The "Come work at Amazon!" is marketing fluff but still part of posting. However it's not substantive detail about role; it's more of a call to action. Might be considered boilerplate? Not exactly. But we could include a short sentence: "We are looking for individuals who want to join an ambitious program pushing the state of the art in space‑based systems design." That is from "A day in the life". Actually the text: "Come work at Amazon! We need people who want to join an ambitious program that continues to push the state of the art in space-based systems design. Come help us solve the difficult and rewarding development challenges in building highly reliable, power efficient and low-cost satellite avionics!" That's substantive about the role's challenges. We could incorporate that into About the role or Responsibilities. Let's add a paragraph after the overview: "We are seeking engineers eager to join an ambitious program pushing the state of the art in space‑based systems design, tackling the challenges of building highly reliable, power‑efficient, low‑cost satellite avionics." That preserves detail. Now ensure we didn't miss any substantive info: The "About The Team" description: "Our team tackles many critical satellite functions including power management, hardware interfaces, command & telemetry, and autonomous control. We are looking for an outstanding software engineer to participate in all phases of software development from requirements through implementation and test to operations." We incorporated that. Now check for any