Sr. Embedded Software Engineer, Leo Payload Radio
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Remove boilerplate: EEO, accommodation link, etc. Also remove duplicated lines (Export Control Requirement appears twice; we need to keep it once? It's substantive info about eligibility; we should preserve it. Probably include it in a paragraph. Also remove application instructions, navigation, cookie, legal, etc. Also remove "Learn more about our benefits at ..."? That's a link; maybe we keep benefits description but not the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link might be considered navigation? It's a link to benefits page; maybe we can keep benefits description but drop the link. However we need to preserve ALL substantive information; the link is not substantive? It's a reference; maybe we can keep the sentence but drop the URL? Safer to keep the sentence without the link? The instruction says remove boilerplate, duplicated lines, and application instructions. The link is not boilerplate; it's a reference to benefits. Could keep as plain text. But we might just keep the benefits description and omit the URL. However we need to preserve all substantive information; the URL is not substantive. So we can omit.
Pay and schedule: The posting includes base salary range for this position listed below. Also mentions sign-on payments and RSUs. Also location specifics: USA, CA, San Diego - 168,100.00 - 227,400.00 USD annually; USA, WA, Redmond - same. So we have pay info. Should we create a Pay section? Yes, because posting states them. Schedule not mentioned, so no Schedule section.
Benefits: they list comprehensive benefits. So we can create Benefits section.
We need to avoid filler like "commensurate with experience". Not present.
We need to ensure we don't create empty sections.
Let's extract content:
- 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? The description: "In this role, you will drive the design, development, and operation of a variety of key embedded security capabilities for each satellite throughout its lifetime – from launch to de-orbit. Develop software to payload Radio and Payload Mode Management. Own unique embedded software functions through design, implementation (in C, C++ or other), test, and integration in an embedded Linux system. Work closely with hardware teams to support board design, bring-up, and verification, as well as integration and test. Follow best practices in high reliability embedded software development to ensure high levels of satellite security and reliability. Work on the Satellite Communication Systems Payload."
We can turn each sentence into
- maybe.
- A day in the life: "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 prose; maybe we keep as
.
- About The Team: "Our team tackles many critical satellite functions including power management, hardware interfaces, command & telemetry, and autonomous control. We are looking for an software engineer to participate in all phases of software development from requirements through implementation and test to operations." That's prose.
- BASIC QUALIFICATIONS: list:
- 5+ years of non-internship professional software development experience
- 5+ years of programming with at least one software programming language experience
- 5+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- Experience as a mentor, tech lead or leading an engineering team
- PREFERRED QUALIFICATIONS:
- 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 in computer science or equivalent
- 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."
- Pay: "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." Then location specific ranges: "USA, CA, San Diego - 168,100.00 - 227,400.00 USD annually" and "USA, WA, Redmond - 168,100.00 - 227,400.00 USD annually". Also "Company - Amazon Kuiper Manufacturing Enterprises LLC". Job ID etc we drop.
We should not include "Your Amazon package will include sign-on payments and restricted stock units (RSUs)" maybe as part of Pay.
We should not include "Learn more about our benefits at ..." but we already omitted.
We should not include EEO etc.
We need to output only HTML fragment.
Structure: maybe sections: Export Control Requirement (maybe as a
under a heading? Could be part of About the role? But we need headings only for sections with real content. Could have heading "Export Control Requirement". However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not limited to those. We can use any appropriate heading. Probably better to use headings like "Responsibilities", "About the Team", "Basic Qualifications", "Preferred Qualifications", "Benefits", "Pay". Export Control Requirement could be a
under Responsibilities or a separate section "Eligibility". But not in examples; but we can still use
for any section heading. Let's make a section "Export Control Requirement". That's fine.
We need to avoid duplicate heading if no content.
Let's craft:
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.
Responsibilities
- Drive the design, development, and operation of a variety of key embedded security capabilities for each satellite throughout its lifetime – from launch to de-orbit.
- Develop software for payload Radio and Payload Mode Management.
- Own unique embedded software functions through design, implementation (in C, C++ or other), test, and integration in an embedded Linux system.
- Work closely with hardware teams to support board design, bring-up, and verification, as well as integration and test.
- Follow best practices in high reliability embedded software development to ensure high levels of satellite security and reliability.
- Work on the Satellite Communication Systems Payload.
A Day in the Life
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!
About the Team
Our team tackles many critical satellite functions including power management, hardware interfaces, command & telemetry, and autonomous control. We are looking for a software engineer to participate in all phases of software development from requirements through implementation and test to operations.
Basic Qualifications
- 5+ years of non-internship professional software development experience
- 5+ years of programming with at least one software programming language experience
- 5+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- Experience as a mentor, tech lead or leading an engineering team
Preferred Qualifications
- 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 in computer science or equivalent
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.
Pay
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.
- USA, CA, San Diego - $168,100.00 - $227,400.00 USD annually
- USA, WA, Redmond - $168,100.00 - $227,400.00 USD annually
We might also include company name? Not needed.
We must not include markdown fences. Just raw HTML.
Check for any boilerplate leftover: We removed EEO, accommodation link, etc. We kept Export Control Requirement only once. We removed duplicated line. Good.
Check for any placeholders like "not specified": none.
Check for any list that should be - . We used for responsibilities, qualifications, benefits? Benefits we used
with a list inside parentheses; that's okay. Could also make
but not required. The instruction: Use - for any list of duties/requirements/benefits. Benefits is a list; we could convert to
- . But the benefits sentence includes many items; maybe better to make a list. Let's do that.
Benefits: list 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.
We could break into multiple
- but the health insurance is a complex phrase; we can keep as one
- . That's fine.
Pay: we already used
- .
Check for any missing info: "Come work at Amazon!" etc included.
Check for "About The Team" we changed to "About the Team". Good.
Check for "A day in the life" we made heading "A Day in the Life". Good.
Check for "Key job responsibilities" we made heading "Responsibilities". Good.
Check for "Basic Qualifications" and "Preferred Qualifications". Good.
Check for "Export Control Requirement" we made heading.
Check for "Pay" heading.
We didn't include "Schedule" as not present.
We
for prose. Remove boilerplate: EEO, accommodation link, etc. Also remove duplicated lines (Export Control Requirement appears twice; we need to keep it once? It's substantive info about eligibility; we should preserve it. Probably include it in a paragraph. Also remove application instructions, navigation, cookie, legal, etc. Also remove "Learn more about our benefits at ..."? That's a link; maybe we keep benefits description but not the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link might be considered navigation? It's a link to benefits page; maybe we can keep benefits description but drop the link. However we need to preserve ALL substantive information; the link is not substantive? It's a reference; maybe we can keep the sentence but drop the URL? Safer to keep the sentence without the link? The instruction says remove boilerplate, duplicated lines, and application instructions. The link is not boilerplate; it's a reference to benefits. Could keep as plain text. But we might just keep the benefits description and omit the URL. However we need to preserve all substantive information; the URL is not substantive. So we can omit. Pay and schedule: The posting includes base salary range for this position listed below. Also mentions sign-on payments and RSUs. Also location specifics: USA, CA, San Diego - 168,100.00 - 227,400.00 USD annually; USA, WA, Redmond - same. So we have pay info. Should we create a Pay section? Yes, because posting states them. Schedule not mentioned, so no Schedule section. Benefits: they list comprehensive benefits. So we can create Benefits section. We need to avoid filler like "commensurate with experience". Not present. We need to ensure we don't create empty sections. Let's extract content: - 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? The description: "In this role, you will drive the design, development, and operation of a variety of key embedded security capabilities for each satellite throughout its lifetime – from launch to de-orbit. Develop software to payload Radio and Payload Mode Management. Own unique embedded software functions through design, implementation (in C, C++ or other), test, and integration in an embedded Linux system. Work closely with hardware teams to support board design, bring-up, and verification, as well as integration and test. Follow best practices in high reliability embedded software development to ensure high levels of satellite security and reliability. Work on the Satellite Communication Systems Payload." We can turn each sentence into
. - About The Team: "Our team tackles many critical satellite functions including power management, hardware interfaces, command & telemetry, and autonomous control. We are looking for an software engineer to participate in all phases of software development from requirements through implementation and test to operations." That's prose. - BASIC QUALIFICATIONS: list: - 5+ years of non-internship professional software development experience - 5+ years of programming with at least one software programming language experience - 5+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience - Experience as a mentor, tech lead or leading an engineering team - PREFERRED QUALIFICATIONS: - 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 in computer science or equivalent - 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." - Pay: "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." Then location specific ranges: "USA, CA, San Diego - 168,100.00 - 227,400.00 USD annually" and "USA, WA, Redmond - 168,100.00 - 227,400.00 USD annually". Also "Company - Amazon Kuiper Manufacturing Enterprises LLC". Job ID etc we drop. We should not include "Your Amazon package will include sign-on payments and restricted stock units (RSUs)" maybe as part of Pay. We should not include "Learn more about our benefits at ..." but we already omitted. We should not include EEO etc. We need to output only HTML fragment. Structure: maybe sections: Export Control Requirement (maybe as a
under a heading? Could be part of About the role? But we need headings only for sections with real content. Could have heading "Export Control Requirement". However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not limited to those. We can use any appropriate heading. Probably better to use headings like "Responsibilities", "About the Team", "Basic Qualifications", "Preferred Qualifications", "Benefits", "Pay". Export Control Requirement could be a
under Responsibilities or a separate section "Eligibility". But not in examples; but we can still use
for any section heading. Let's make a section "Export Control Requirement". That's fine.
We need to avoid duplicate heading if no content.
Let's craft:
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.
Responsibilities
- Drive the design, development, and operation of a variety of key embedded security capabilities for each satellite throughout its lifetime – from launch to de-orbit.
- Develop software for payload Radio and Payload Mode Management.
- Own unique embedded software functions through design, implementation (in C, C++ or other), test, and integration in an embedded Linux system.
- Work closely with hardware teams to support board design, bring-up, and verification, as well as integration and test.
- Follow best practices in high reliability embedded software development to ensure high levels of satellite security and reliability.
- Work on the Satellite Communication Systems Payload.
A Day in the Life
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!
About the Team
Our team tackles many critical satellite functions including power management, hardware interfaces, command & telemetry, and autonomous control. We are looking for a software engineer to participate in all phases of software development from requirements through implementation and test to operations.
Basic Qualifications
- 5+ years of non-internship professional software development experience
- 5+ years of programming with at least one software programming language experience
- 5+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- Experience as a mentor, tech lead or leading an engineering team
Preferred Qualifications
- 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 in computer science or equivalent
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.
Pay
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.
- USA, CA, San Diego - $168,100.00 - $227,400.00 USD annually
- USA, WA, Redmond - $168,100.00 - $227,400.00 USD annually
- . We used for responsibilities, qualifications, benefits? Benefits we used
with a list inside parentheses; that's okay. Could also make
- but not required. The instruction: Use
- for any list of duties/requirements/benefits. Benefits is a list; we could convert to
- . But the benefits sentence includes many items; maybe better to make a list. Let's do that. Benefits: list 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. We could break into multiple
- but the health insurance is a complex phrase; we can keep as one
- . That's fine.
Pay: we already used
- . Check for any missing info: "Come work at Amazon!" etc included. Check for "About The Team" we changed to "About the Team". Good. Check for "A day in the life" we made heading "A Day in the Life". Good. Check for "Key job responsibilities" we made heading "Responsibilities". Good. Check for "Basic Qualifications" and "Preferred Qualifications". Good. Check for "Export Control Requirement" we made heading. Check for "Pay" heading. We didn't include "Schedule" as not present. We
- for any list of duties/requirements/benefits. Benefits is a list; we could convert to