Software Development Manager, Software Defined Network Control Plane
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content.
We have:
- Description: about Amazon Leo mission, export control requirement.
- Key job responsibilities: "Responsibilities" heading then bullet list.
- "A day in the life": prose.
- "About The Team": prose.
- Basic Qualifications: list of qualifications.
- Preferred Qualifications: list.
- Export Control Requirement: statement about citizenship.
- Salary ranges: base salary range listed for locations.
- Benefits: mention of comprehensive benefits including health insurance etc.
- Also mention sign-on payments and RSUs.
- Also mention "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, and parental leave."
Thus we have content for:
- About the role (maybe description + export control requirement + about the team? Actually "About the role" could be description of role and mission. We'll include description paragraph(s).
- Responsibilities: bullet list.
- Requirements: maybe combine Basic Qualifications and Preferred Qualifications? The instruction says use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to actually include based on content. We have content for Responsibilities, Qualifications (basic and preferred), Benefits, Pay (salary range). Possibly Skills? Not explicit separate skills list; qualifications cover skills. Could combine Requirements and Qualifications? But we need to follow instruction: Use headings only when posting has real, specific content for it. So we can include sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Requirements? The basic qualifications could be considered Requirements. But we have both Basic and Preferred Qualifications; we could put them under Qualifications (with subheadings? Not allowed to add extra headings beyond those listed? We could still use
for Qualifications and then within that we can have
or
. Could separate Basic and Preferred as separate with headings? Not allowed to add extra headings beyond the allowed list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. We can include subheadings using or but better to keep within Qualifications section we can have two lists: Basic Qualifications and Preferred Qualifications as inside or as
? Might be okay to use to denote subheadings. Safer: keep as with bold text.
We also have Export Control Requirement: must be US citizen etc. That's a requirement; could be included under Requirements or Qualifications. We'll include under Requirements maybe.
We have Schedule? Not mentioned. No schedule info. So we should not include Schedule section.
We have Skills? Not explicit separate list; qualifications cover skills. Could omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to ensure we don't repeat job title. Not include Job ID.
We need to preserve all substantive information: description, export control, responsibilities bullet list, day in the life, about the team, basic qualifications, preferred qualifications, benefits, pay ranges, sign-on payments and RSUs.
We must remove boilerplate: EEO statements, Los Angeles County specifics, accommodation link, etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (maybe keep benefits description but not the link). Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "Los Angeles County applicants: ..." etc. Also remove "Criminal history may have a direct..." etc. Also remove "Pursuant to the Los Angeles County Fair Chance Ordinance..." etc. Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc.
Also remove "Export Control Requirement:"? Actually that is substantive; keep.
Also remove "Key job responsibilities Responsibilities" duplication? We'll keep responsibilities.
Also remove "A day in the life" heading? It's prose; we can keep as paragraph under About the role or Responsibilities? Probably under About the role.
Also remove "About The Team" heading; we can keep as paragraph under About the role.
Also remove "Basic Qualifications" and "Preferred Qualifications" headings; we can keep as lists under Qualifications.
Also remove "Preferred Qualifications" heading.
Also remove "Basic Qualifications" heading.
Also remove "Experience partnering with product or program management teams" etc.
Also remove "Amazon is an equal opportunity employer..." etc.
Also remove "Los Angeles County applicants: ..." etc.
Also remove "Our inclusive culture empowers Amazonians..." etc.
Also remove "If you have a disability..." etc.
Also remove "If the country/region you’re applying in isn’t listed..." etc.
Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (but we can keep benefits description).
Also 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." Keep that as part of Pay section.
Also remove "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." Keep as benefits.
Also remove "USA, CA, Sunnyvale - 212,700.00 - 287,700.00 USD annually USA, WA, Redmond - 184,900.00 - 250,200.00 USD annually" Keep as pay.
Also remove "Company - Amazon Kuiper Manufacturing Enterprises LLC Job ID: A10544023" maybe drop Job ID but keep company? Could be minor metadata; we can fold into a short
or drop. Probably drop.
Now construct HTML.
We'll start with
About the role
then containing description, export control requirement, day in the life, about the team.
We need to preserve all substantive info: description: "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."
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."
Day in the life: "This is an opportunity to make history by owning a key network component for the space age of networking. You assist in designing, building and operating a massive satellite constellation and terrestrial network. We interact with the satellite ground control services, the customer engagement systems and monitoring services to constantly fine-tune our network and deliver a high quality service to our customers. You will be responsible to build the best network for our customers."
About The Team: "The SDN Control Plane team is building the brain driving the Leo Network. Innovation is in our DNA and we tackle the problems presented by a dynamic network at global scale. It is our responsibility to ensure that the network works and our customer has a one-of-a-kind experience using our service. Our team will design, implement and operate the control plane that provides a high throughput telecom service comprised of Low Earth Orbit satellites, customer terminals, gateways, Cloud services and terrestrial network infrastructure that connects into public and private networks."
We can combine these into paragraphs.
Now Responsibilities:
Responsibilities
then - items.
List from "For this role, you will:" bullet points:
- Be the Single threaded owner for all Agent and device network health
- Drive operational improvements to achieve 99.99+ network availability
- Implement highly-available software that will drive networking control plane operation on physical and remote nodes
- Define and automate processes used for software development, implementation, testing, and maintenance
- Manage network software network nodes written in C and Rust
Also maybe earlier bullet: "Key job responsibilities Responsibilities Have you wanted an opportunity to develop the core wireless and networking for an advanced global telecom service spanning both space and terrestrial networks? Have you wondered what it takes to run software across multiple devices all working to enable end to end network access? Amazon Leo's SDN Agent team is responsible for managing all the device network plans. This service works in coordination with high throughput telecom service using a system of LEO satellites, customer terminals, gateways, cloud services, and terrestrial network infrastructure that connect into public and private networks." That's more description; but we already covered role. Could include as part of responsibilities? Might be redundant. We'll keep the explicit bullet list.
Now Requirements:
Requirements
then maybe include Export Control Requirement? Already in About the role. Could also include basic qualifications? But we have Qualifications section. Perhaps Requirements could be minimal: maybe we can include "Export Control Requirement" as a requirement. But we already placed it in About the role. Could move it to Requirements. However we need to preserve all substantive info; duplication is okay? Better to avoid duplication. Let's put Export Control Requirement under Requirements.
Thus Requirements section: 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: Qualifications
then we need to list Basic Qualifications and Preferred Qualifications. We'll use Basic Qualifications: then list items. Then Preferred Qualifications: then list items.
Basic Qualifications items from posting:
- 3+ years of
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - Description: about Amazon Leo mission, export control requirement. - Key job responsibilities: "Responsibilities" heading then bullet list. - "A day in the life": prose. - "About The Team": prose. - Basic Qualifications: list of qualifications. - Preferred Qualifications: list. - Export Control Requirement: statement about citizenship. - Salary ranges: base salary range listed for locations. - Benefits: mention of comprehensive benefits including health insurance etc. - Also mention sign-on payments and RSUs. - Also mention "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, and parental leave." Thus we have content for: - About the role (maybe description + export control requirement + about the team? Actually "About the role" could be description of role and mission. We'll include description paragraph(s). - Responsibilities: bullet list. - Requirements: maybe combine Basic Qualifications and Preferred Qualifications? The instruction says use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to actually include based on content. We have content for Responsibilities, Qualifications (basic and preferred), Benefits, Pay (salary range). Possibly Skills? Not explicit separate skills list; qualifications cover skills. Could combine Requirements and Qualifications? But we need to follow instruction: Use headings only when posting has real, specific content for it. So we can include sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Requirements? The basic qualifications could be considered Requirements. But we have both Basic and Preferred Qualifications; we could put them under Qualifications (with subheadings? Not allowed to add extra headings beyond those listed? We could still use
for Qualifications and then within that we can have
or
- . Could separate Basic and Preferred as separate
- items.
List from "For this role, you will:" bullet points:
- Be the Single threaded owner for all Agent and device network health
- Drive operational improvements to achieve 99.99+ network availability
- Implement highly-available software that will drive networking control plane operation on physical and remote nodes
- Define and automate processes used for software development, implementation, testing, and maintenance
- Manage network software network nodes written in C and Rust
Also maybe earlier bullet: "Key job responsibilities Responsibilities Have you wanted an opportunity to develop the core wireless and networking for an advanced global telecom service spanning both space and terrestrial networks? Have you wondered what it takes to run software across multiple devices all working to enable end to end network access? Amazon Leo's SDN Agent team is responsible for managing all the device network plans. This service works in coordination with high throughput telecom service using a system of LEO satellites, customer terminals, gateways, cloud services, and terrestrial network infrastructure that connect into public and private networks." That's more description; but we already covered role. Could include as part of responsibilities? Might be redundant. We'll keep the explicit bullet list.
Now Requirements:
Requirements
then maybe include Export Control Requirement? Already in About the role. Could also include basic qualifications? But we have Qualifications section. Perhaps Requirements could be minimal: maybe we can include "Export Control Requirement" as a requirement. But we already placed it in About the role. Could move it to Requirements. However we need to preserve all substantive info; duplication is okay? Better to avoid duplication. Let's put Export Control Requirement under Requirements. Thus Requirements section: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:Qualifications
then we need to list Basic Qualifications and Preferred Qualifications. We'll use Basic Qualifications: then- list items. Then Preferred Qualifications: then
- list items.
Basic Qualifications items from posting:
- 3+ years of
- with headings? Not allowed to add extra headings beyond the allowed list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. We can include subheadings using or but better to keep within Qualifications section we can have two lists: Basic Qualifications and Preferred Qualifications as inside or as
? Might be okay to use to denote subheadings. Safer: keep as with bold text.
We also have Export Control Requirement: must be US citizen etc. That's a requirement; could be included under Requirements or Qualifications. We'll include under Requirements maybe.
We have Schedule? Not mentioned. No schedule info. So we should not include Schedule section.
We have Skills? Not explicit separate list; qualifications cover skills. Could omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to ensure we don't repeat job title. Not include Job ID.
We need to preserve all substantive information: description, export control, responsibilities bullet list, day in the life, about the team, basic qualifications, preferred qualifications, benefits, pay ranges, sign-on payments and RSUs.
We must remove boilerplate: EEO statements, Los Angeles County specifics, accommodation link, etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (maybe keep benefits description but not the link). Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "Los Angeles County applicants: ..." etc. Also remove "Criminal history may have a direct..." etc. Also remove "Pursuant to the Los Angeles County Fair Chance Ordinance..." etc. Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc.
Also remove "Export Control Requirement:"? Actually that is substantive; keep.
Also remove "Key job responsibilities Responsibilities" duplication? We'll keep responsibilities.
Also remove "A day in the life" heading? It's prose; we can keep as paragraph under About the role or Responsibilities? Probably under About the role.
Also remove "About The Team" heading; we can keep as paragraph under About the role.
Also remove "Basic Qualifications" and "Preferred Qualifications" headings; we can keep as lists under Qualifications.
Also remove "Preferred Qualifications" heading.
Also remove "Basic Qualifications" heading.
Also remove "Experience partnering with product or program management teams" etc.
Also remove "Amazon is an equal opportunity employer..." etc.
Also remove "Los Angeles County applicants: ..." etc.
Also remove "Our inclusive culture empowers Amazonians..." etc.
Also remove "If you have a disability..." etc.
Also remove "If the country/region you’re applying in isn’t listed..." etc.
Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (but we can keep benefits description).
Also 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." Keep that as part of Pay section.
Also remove "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." Keep as benefits.
Also remove "USA, CA, Sunnyvale - 212,700.00 - 287,700.00 USD annually USA, WA, Redmond - 184,900.00 - 250,200.00 USD annually" Keep as pay.
Also remove "Company - Amazon Kuiper Manufacturing Enterprises LLC Job ID: A10544023" maybe drop Job ID but keep company? Could be minor metadata; we can fold into a short
or drop. Probably drop.
Now construct HTML.
We'll start with
About the role
then containing description, export control requirement, day in the life, about the team.
We need to preserve all substantive info: description: "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."
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."
Day in the life: "This is an opportunity to make history by owning a key network component for the space age of networking. You assist in designing, building and operating a massive satellite constellation and terrestrial network. We interact with the satellite ground control services, the customer engagement systems and monitoring services to constantly fine-tune our network and deliver a high quality service to our customers. You will be responsible to build the best network for our customers."
About The Team: "The SDN Control Plane team is building the brain driving the Leo Network. Innovation is in our DNA and we tackle the problems presented by a dynamic network at global scale. It is our responsibility to ensure that the network works and our customer has a one-of-a-kind experience using our service. Our team will design, implement and operate the control plane that provides a high throughput telecom service comprised of Low Earth Orbit satellites, customer terminals, gateways, Cloud services and terrestrial network infrastructure that connects into public and private networks."
We can combine these into paragraphs.
Now Responsibilities:
Responsibilities
then
but better to keep within Qualifications section we can have two lists: Basic Qualifications and Preferred Qualifications as inside or as with bold text.
We also have Export Control Requirement: must be US citizen etc. That's a requirement; could be included under Requirements or Qualifications. We'll include under Requirements maybe.
We have Schedule? Not mentioned. No schedule info. So we should not include Schedule section.
We have Skills? Not explicit separate list; qualifications cover skills. Could omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to ensure we don't repeat job title. Not include Job ID.
We need to preserve all substantive information: description, export control, responsibilities bullet list, day in the life, about the team, basic qualifications, preferred qualifications, benefits, pay ranges, sign-on payments and RSUs.
We must remove boilerplate: EEO statements, Los Angeles County specifics, accommodation link, etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (maybe keep benefits description but not the link). Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "Los Angeles County applicants: ..." etc. Also remove "Criminal history may have a direct..." etc. Also remove "Pursuant to the Los Angeles County Fair Chance Ordinance..." etc. Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc.
Also remove "Export Control Requirement:"? Actually that is substantive; keep.
Also remove "Key job responsibilities Responsibilities" duplication? We'll keep responsibilities.
Also remove "A day in the life" heading? It's prose; we can keep as paragraph under About the role or Responsibilities? Probably under About the role.
Also remove "About The Team" heading; we can keep as paragraph under About the role.
Also remove "Basic Qualifications" and "Preferred Qualifications" headings; we can keep as lists under Qualifications.
Also remove "Preferred Qualifications" heading.
Also remove "Basic Qualifications" heading.
Also remove "Experience partnering with product or program management teams" etc.
Also remove "Amazon is an equal opportunity employer..." etc.
Also remove "Los Angeles County applicants: ..." etc.
Also remove "Our inclusive culture empowers Amazonians..." etc.
Also remove "If you have a disability..." etc.
Also remove "If the country/region you’re applying in isn’t listed..." etc.
Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (but we can keep benefits description).
Also 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." Keep that as part of Pay section.
Also remove "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." Keep as benefits.
Also remove "USA, CA, Sunnyvale - 212,700.00 - 287,700.00 USD annually USA, WA, Redmond - 184,900.00 - 250,200.00 USD annually" Keep as pay.
Also remove "Company - Amazon Kuiper Manufacturing Enterprises LLC Job ID: A10544023" maybe drop Job ID but keep company? Could be minor metadata; we can fold into a short or drop. Probably drop.
Now construct HTML.
We'll start with containing description, export control requirement, day in the life, about the team.
We need to preserve all substantive info: description: "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."
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."
Day in the life: "This is an opportunity to make history by owning a key network component for the space age of networking. You assist in designing, building and operating a massive satellite constellation and terrestrial network. We interact with the satellite ground control services, the customer engagement systems and monitoring services to constantly fine-tune our network and deliver a high quality service to our customers. You will be responsible to build the best network for our customers."
About The Team: "The SDN Control Plane team is building the brain driving the Leo Network. Innovation is in our DNA and we tackle the problems presented by a dynamic network at global scale. It is our responsibility to ensure that the network works and our customer has a one-of-a-kind experience using our service. Our team will design, implement and operate the control plane that provides a high throughput telecom service comprised of Low Earth Orbit satellites, customer terminals, gateways, Cloud services and terrestrial network infrastructure that connects into public and private networks."
We can combine these into paragraphs.
Now Responsibilities: ? Might be okay to use to denote subheadings. Safer: keep as
About the role
then Responsibilities
then