Sr. Communication Systems Engineer
for section headings, - for lists,
for prose.
We must not repeat job title as heading. No Job ID etc.
We must remove boilerplate: EEO, equal opportunity, legal, scam warning, navigation, cookie, etc. Also remove duplicated lines. Remove application instructions.
We need to preserve all substantive information.
We need to decide which sections to include.
We have content for:
- About the role: description of Amazon Leo initiative and role overview. Could be a paragraph.
- Responsibilities: bullet list of duties: leading integration, verification, testing; developing and testing advanced L1/L2/L3 concepts; developing simulation tools; building suite of system and network simulation services; develop requirements from system level to HW/SW level and define test cases; identify additional HW/SW needed; work closely with implementation teams; write scripts/code for functions; etc.
- Requirements: Basic Qualifications: Master's degree in CS/CE/EE or experience; 7+ years experience in wireless systems design and/or RF design implementation; experience in wireless system design and architecture, system integration, RF system analysis; 7+ years experience developing code in Matlab, C, C++, or Python, and experience with industry standard coding and regression practices.
- Qualifications: Preferred Qualifications: list of items.
- Skills: Could combine technical skills: experience with information theory, network coding, mobile mesh networks, modeling LEO satellite networks, simulation of RF standards, wireless communications system design with emphasis on L1/L2, system and link level simulation, capacity performance interference analysis, development of advanced physical layer and MAC layer techniques, design and understanding of advanced information theory and network coding concepts, design and development physical layer and some MAC layer techniques for high spectral efficiency, excellent analytical, problem solving, communication skills.
- Benefits: The posting mentions 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. Also sign-on payments and RSUs. So we can include Benefits section.
- Pay: The posting lists base salary range for specific locations: USA, CA, San Diego - 159,200.00 - 215,300.00 USD annually; USA, TX, Austin - same; USA, WA, Redmond - same. So we have pay info. Should we include Pay section? Yes, because posting states them. Provide maybe a
with the ranges.
- Schedule: Not mentioned. No schedule info. So we should not include Schedule section.
- Export Control Requirements: This is a requirement but maybe could be part of Requirements or a separate section like "Eligibility". But we only have predefined headings; we could incorporate into Requirements or Qualifications. Since it's a requirement (citizenship), we could add to Requirements as a bullet.
We must not invent sections like "Eligibility". So we can add a bullet under Requirements: "U.S. citizen or national, U.S. permanent resident (Green Card holder), or lawfully admitted as refugee or granted asylum (due to export control laws)."
We need to ensure we don't repeat boilerplate like "Amazon is an equal opportunity employer..." etc. Remove that.
Also remove Los Angeles County applicants text (that's location-specific legal). Remove that.
Also remove "If you have a disability..." etc.
Also remove "Learn more about our benefits at https://..." maybe we can keep benefits description but not the link? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is part of benefits info; but it's a URL. Should we keep it? It's not boilerplate; it's a link to benefits. Might be considered substantive. However, we might keep it as part of benefits description. But we need to decide: The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is not exactly those; it's a reference. I'd keep it.
But we need to avoid duplication: The benefits description already mentions comprehensive benefits; the link is extra. We'll keep it as a sentence.
Now, we need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Preferred Qualifications
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
...
We need to ensure we don't create empty sections.
Now, let's extract content precisely.
About the role: The description starts: "Description 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 underserved communities around the world. Come work at Amazon! The Role Be part of the team defining the overall communication system and architecture of Leo’s broadband wireless network. This is a unique opportunity to innovate and define groundbreaking wireless technology with few legacy constraints. The team develops and designs the communication system of Leo and analyzes its overall system level performance such as for overall throughput, latency, system availability, packet loss etc. This role in particular will be responsible for leading the effort in integration, verification and testing of the systems especially focused on MAC and higher layer testing. This role will also be responsible developing and testing advanced L1/L2/L3 concept to improve the performance and reliability of the LEO network. This role will also be part of a team and develop simulation tools with particular emphasis on modeling the physical layer aspects such as advanced receiver modeling and abstraction, interference cancellation techniques, FEC abstraction models etc."
We can combine into a paragraph.
Responsibilities: The bullet list from "In This Role You Will Work within a project team and take the responsibility for the Leo’s communication system design, system integration and verification. Work as a part of the team in building a suite of system and network simulation services in Matlab / C++ / Python Develop requirements from system level to HW/SW level and define test cases associated with the requirements. Identify additional HW and SW that are needed for the purposes of verification and guide the HW/SW development team in the development of these test solutions/tools// Work closely with implementation teams to simulate expected system level performance and provide quick feedback on potential improvements Write scripts / code for functions / features required for specific simulation, testing and verification of given RF system"
We need to split into sensible bullet points.
Let's list:
- Work within a project team and take responsibility for Leo’s communication system design, system integration, and verification.
- Work as part of the team building a suite of system and network simulation services in Matlab, C++, and Python.
- Develop requirements from system level to HW/SW level and define associated test cases.
- Identify additional HW and SW needed for verification and guide the HW/SW development team in developing these test solutions/tools.
- Work closely with implementation teams to simulate expected system-level performance and provide quick feedback on potential improvements.
- Write scripts/code for functions/features required for specific simulation, testing, and verification of given RF system.
Also earlier responsibilities: leading integration, verification, testing especially MAC and higher layer testing; developing and testing advanced L1/L2/L3 concepts; developing simulation tools with emphasis on physical layer modeling etc. Those could be part of responsibilities as well. Actually those were in the earlier paragraph. We can incorporate them.
Thus responsibilities bullets could include:
- Lead integration, verification, and testing of the communication system, focusing on MAC and higher layer testing.
- Develop and test advanced L1/L2/L3 concepts to improve LEO network performance and reliability.
- Develop simulation tools emphasizing physical layer modeling (advanced receiver modeling, abstraction, interference cancellation techniques, FEC abstraction models).
- Work within a project team and take responsibility for Leo’s communication system design, system integration, and verification.
- Work as part of the team building a suite of system and network simulation services in Matlab, C++, and Python.
- Develop requirements from system level to HW/SW level and define associated test cases.
- Identify additional HW and SW needed for verification and guide the HW/SW development team in developing these test solutions/tools.
- Work closely with implementation teams to simulate expected system-level performance and provide quick feedback on potential improvements.
- Write scripts/code for functions/features required for specific simulation, testing, and verification of given RF system.
We can combine some.
Now Requirements (Basic Qualifications):
- Master's degree in Computer Science, Computer Engineering, or Electrical Engineering, or experience working in electrical engineering field.
- 7+ years of experience in wireless systems design and/or RF design implementation.
- Experience in wireless system design and architecture, system integration, RF system analysis.
- 7+ years of experience developing code in Matlab, C, C++, or Python, and experience with industry standard coding and regression practices.
- U.S. citizen or national, U.S. permanent resident (Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum (due to export control laws).
We could combine some.
Now Preferred Qualifications:
- Experience with information theory and network coding.
- Experience with mobile mesh networks.
- Experience in modeling and performance analysis of LEO Satellite Networks.
- Experience with simulation of RF standards like (4G/5G), 802.11, DVB-S2 / DVB-C, or similar broadband wireless standards.
- Wireless Communications System design and development with emphasis on L1 and L2.
- System level and link level simulation of wireless networks.
- Capacity, performance and interference analysis of wireless networks.
- Development of advanced physical layer and MAC layer techniques for wireless networks.
- Design and understanding of advanced information theory and network coding concepts.
- Design and development physical layer and some MAC layer techniques for high spectral efficiency.
- Excellent analytical, problem solving, and communication skills.
Note some overlap with Skills. We could separate Skills as a distinct section summarizing technical skills.
But we have both Preferred Qualifications and Skills; we could merge them, but instructions say prefer few substantive sections over many thin ones. However we have distinct content for Preferred Qualifications and Skills; but they overlap. We could combine them into a single "Qualifications" section that includes both basic and preferred? But we already have Requirements (basic) and Qualifications (maybe preferred). The instruction list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should follow that: Requirements = basic qualifications; Qualifications = preferred qualifications; Skills = maybe technical skills (like programming languages, tools). However the posting already includes many technical skills in preferred qualifications. We could treat Skills as a separate section highlighting specific technical abilities: Matlab, C++, Python, simulation tools, etc. But we already have those in Requirements. Might be redundant.
Given the instruction to prefer few substantive sections, we could combine Preferred Qualifications and Skills into one section called "Qualifications". But the instruction says use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which to include. If we combine, we would still need to output both headings? The instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid omitting a heading if no substantive content. So we can omit sections that lack substantive content. We have content for Requirements (basic), Qualifications (preferred),
for prose. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO, equal opportunity, legal, scam warning, navigation, cookie, etc. Also remove duplicated lines. Remove application instructions. We need to preserve all substantive information. We need to decide which sections to include. We have content for: - About the role: description of Amazon Leo initiative and role overview. Could be a paragraph. - Responsibilities: bullet list of duties: leading integration, verification, testing; developing and testing advanced L1/L2/L3 concepts; developing simulation tools; building suite of system and network simulation services; develop requirements from system level to HW/SW level and define test cases; identify additional HW/SW needed; work closely with implementation teams; write scripts/code for functions; etc. - Requirements: Basic Qualifications: Master's degree in CS/CE/EE or experience; 7+ years experience in wireless systems design and/or RF design implementation; experience in wireless system design and architecture, system integration, RF system analysis; 7+ years experience developing code in Matlab, C, C++, or Python, and experience with industry standard coding and regression practices. - Qualifications: Preferred Qualifications: list of items. - Skills: Could combine technical skills: experience with information theory, network coding, mobile mesh networks, modeling LEO satellite networks, simulation of RF standards, wireless communications system design with emphasis on L1/L2, system and link level simulation, capacity performance interference analysis, development of advanced physical layer and MAC layer techniques, design and understanding of advanced information theory and network coding concepts, design and development physical layer and some MAC layer techniques for high spectral efficiency, excellent analytical, problem solving, communication skills. - Benefits: The posting mentions 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. Also sign-on payments and RSUs. So we can include Benefits section. - Pay: The posting lists base salary range for specific locations: USA, CA, San Diego - 159,200.00 - 215,300.00 USD annually; USA, TX, Austin - same; USA, WA, Redmond - same. So we have pay info. Should we include Pay section? Yes, because posting states them. Provide maybe a
with the ranges. - Schedule: Not mentioned. No schedule info. So we should not include Schedule section. - Export Control Requirements: This is a requirement but maybe could be part of Requirements or a separate section like "Eligibility". But we only have predefined headings; we could incorporate into Requirements or Qualifications. Since it's a requirement (citizenship), we could add to Requirements as a bullet. We must not invent sections like "Eligibility". So we can add a bullet under Requirements: "U.S. citizen or national, U.S. permanent resident (Green Card holder), or lawfully admitted as refugee or granted asylum (due to export control laws)." We need to ensure we don't repeat boilerplate like "Amazon is an equal opportunity employer..." etc. Remove that. Also remove Los Angeles County applicants text (that's location-specific legal). Remove that. Also remove "If you have a disability..." etc. Also remove "Learn more about our benefits at https://..." maybe we can keep benefits description but not the link? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is part of benefits info; but it's a URL. Should we keep it? It's not boilerplate; it's a link to benefits. Might be considered substantive. However, we might keep it as part of benefits description. But we need to decide: The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is not exactly those; it's a reference. I'd keep it. But we need to avoid duplication: The benefits description already mentions comprehensive benefits; the link is extra. We'll keep it as a sentence. Now, we need to output only HTML fragment, no /, no markdown fences. We'll structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Preferred Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
...
We need to ensure we don't create empty sections. Now, let's extract content precisely. About the role: The description starts: "Description 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 underserved communities around the world. Come work at Amazon! The Role Be part of the team defining the overall communication system and architecture of Leo’s broadband wireless network. This is a unique opportunity to innovate and define groundbreaking wireless technology with few legacy constraints. The team develops and designs the communication system of Leo and analyzes its overall system level performance such as for overall throughput, latency, system availability, packet loss etc. This role in particular will be responsible for leading the effort in integration, verification and testing of the systems especially focused on MAC and higher layer testing. This role will also be responsible developing and testing advanced L1/L2/L3 concept to improve the performance and reliability of the LEO network. This role will also be part of a team and develop simulation tools with particular emphasis on modeling the physical layer aspects such as advanced receiver modeling and abstraction, interference cancellation techniques, FEC abstraction models etc." We can combine into a paragraph. Responsibilities: The bullet list from "In This Role You Will Work within a project team and take the responsibility for the Leo’s communication system design, system integration and verification. Work as a part of the team in building a suite of system and network simulation services in Matlab / C++ / Python Develop requirements from system level to HW/SW level and define test cases associated with the requirements. Identify additional HW and SW that are needed for the purposes of verification and guide the HW/SW development team in the development of these test solutions/tools// Work closely with implementation teams to simulate expected system level performance and provide quick feedback on potential improvements Write scripts / code for functions / features required for specific simulation, testing and verification of given RF system" We need to split into sensible bullet points. Let's list: - Work within a project team and take responsibility for Leo’s communication system design, system integration, and verification. - Work as part of the team building a suite of system and network simulation services in Matlab, C++, and Python. - Develop requirements from system level to HW/SW level and define associated test cases. - Identify additional HW and SW needed for verification and guide the HW/SW development team in developing these test solutions/tools. - Work closely with implementation teams to simulate expected system-level performance and provide quick feedback on potential improvements. - Write scripts/code for functions/features required for specific simulation, testing, and verification of given RF system. Also earlier responsibilities: leading integration, verification, testing especially MAC and higher layer testing; developing and testing advanced L1/L2/L3 concepts; developing simulation tools with emphasis on physical layer modeling etc. Those could be part of responsibilities as well. Actually those were in the earlier paragraph. We can incorporate them. Thus responsibilities bullets could include: - Lead integration, verification, and testing of the communication system, focusing on MAC and higher layer testing. - Develop and test advanced L1/L2/L3 concepts to improve LEO network performance and reliability. - Develop simulation tools emphasizing physical layer modeling (advanced receiver modeling, abstraction, interference cancellation techniques, FEC abstraction models). - Work within a project team and take responsibility for Leo’s communication system design, system integration, and verification. - Work as part of the team building a suite of system and network simulation services in Matlab, C++, and Python. - Develop requirements from system level to HW/SW level and define associated test cases. - Identify additional HW and SW needed for verification and guide the HW/SW development team in developing these test solutions/tools. - Work closely with implementation teams to simulate expected system-level performance and provide quick feedback on potential improvements. - Write scripts/code for functions/features required for specific simulation, testing, and verification of given RF system. We can combine some. Now Requirements (Basic Qualifications): - Master's degree in Computer Science, Computer Engineering, or Electrical Engineering, or experience working in electrical engineering field. - 7+ years of experience in wireless systems design and/or RF design implementation. - Experience in wireless system design and architecture, system integration, RF system analysis. - 7+ years of experience developing code in Matlab, C, C++, or Python, and experience with industry standard coding and regression practices. - U.S. citizen or national, U.S. permanent resident (Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum (due to export control laws). We could combine some. Now Preferred Qualifications: - Experience with information theory and network coding. - Experience with mobile mesh networks. - Experience in modeling and performance analysis of LEO Satellite Networks. - Experience with simulation of RF standards like (4G/5G), 802.11, DVB-S2 / DVB-C, or similar broadband wireless standards. - Wireless Communications System design and development with emphasis on L1 and L2. - System level and link level simulation of wireless networks. - Capacity, performance and interference analysis of wireless networks. - Development of advanced physical layer and MAC layer techniques for wireless networks. - Design and understanding of advanced information theory and network coding concepts. - Design and development physical layer and some MAC layer techniques for high spectral efficiency. - Excellent analytical, problem solving, and communication skills. Note some overlap with Skills. We could separate Skills as a distinct section summarizing technical skills. But we have both Preferred Qualifications and Skills; we could merge them, but instructions say prefer few substantive sections over many thin ones. However we have distinct content for Preferred Qualifications and Skills; but they overlap. We could combine them into a single "Qualifications" section that includes both basic and preferred? But we already have Requirements (basic) and Qualifications (maybe preferred). The instruction list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should follow that: Requirements = basic qualifications; Qualifications = preferred qualifications; Skills = maybe technical skills (like programming languages, tools). However the posting already includes many technical skills in preferred qualifications. We could treat Skills as a separate section highlighting specific technical abilities: Matlab, C++, Python, simulation tools, etc. But we already have those in Requirements. Might be redundant. Given the instruction to prefer few substantive sections, we could combine Preferred Qualifications and Skills into one section called "Qualifications". But the instruction says use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which to include. If we combine, we would still need to output both headings? The instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid omitting a heading if no substantive content. So we can omit sections that lack substantive content. We have content for Requirements (basic), Qualifications (preferred),