Harnessing Engineer , Satellite Hardware
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment.
Let's craft.
First, maybe a short paragraph for metadata? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a
with location and job ID? But they said drop minor metadata. Probably we can drop Job ID. Location maybe part of Pay? The Pay line includes location. We'll keep that in Pay.
Now content:
About the role: The first paragraph(s) up to "Export Control Requirement:"? Actually Export Control is a requirement, not about role. So 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. In the Harnessing Engineer role, you will be responsible for conceptualizing, designing, procuring, testing, and support integration for the wiring harnesses across the entire satellite. Robust harness systems are crucial to maintaining reliable electrical system functionality. You will have direct impact on the success of creating a constellation of communication satellites that will be capable of reaching and providing broadband internet to the most remote areas of the world."
That's prose.
Responsibilities: list items from "Key job responsibilities" and maybe "A day in the life". Let's extract each sentence as bullet.
Key job responsibilities list:
- Harnessing design for satellite system requiring interfacing across mechanical, electrical and payload design owners, trading various configurations to identify best overall solution for reliability, manufacturability, test, integration, and cost.
- Support make vs buy decisions, design reviews, and implement manufacturing and integration plans optimized for high rate production.
- Engage various component suppliers and Harnessing manufacturing vendors for component & assembly level qualification.
- Design/develop specifications and produce/procure power/data harnesses which meets electrical design requirements including current rating, targeted power loss, shielding, grounding and EMI/EMC.
- Perform/oversee harness qualification and acceptance tests for launch environments and operation through mission life, including test fixture fabrication for prototype evaluations, and deliver all development and flight hardware per vehicle schedules
- Create 3D CAD routings, 2D manufacturing drawings, schematics, and assembly installation drawings.
"A day in the life" paragraph: "As a Harness Engineer, you will be working closely with all hardware sub-system and support teams on a daily basis. You will play an integral part of gathering requirements for harness development as well as providing critical input for successful integration of avionics hardware."
We could add as bullets or prose. Since it's prose, we could put as
under Responsibilities. But instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can keep the list as
- and then add a
for the day in the life.
Requirements: Basic Qualifications and Export Control Requirement.
Basic Qualifications: "2+ years of hardware design and validation of components, subsystems and systems experience" and "Bachelor's degree in mechanical engineering, electrical engineering, material science, physics or equivalent". Also Export Control: "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."
We can make a list.
Qualifications: Preferred Qualifications: "Knowledge of engineering practices and patterns for the full software/hardware/networks development life cycle, including coding standards, code reviews, source control management, build processes, testing, certification, and livesite operations" and "Experience with hardware/software integration and real-time systems".
Skills: Not present; we can omit.
Benefits: Paragraph: "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. Learn more about our benefits at https://amazon.jobs/en/benefits." Also mention sign-on payments and RSUs? That is compensation; maybe include in Pay.
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, WA, REDMOND - 96,600.00 - 160,000.00 USD annually"
We need to preserve all substantive info. So include that paragraph.
We should not include the link to benefits? It's part of benefits; we can keep as prose.
We should not include the accommodation link etc.
Now construct HTML.
We'll start with
About the role
then ...
Then Responsibilities
then - ... etc
then A day in the life ...
Then Requirements
then - ... etc
Then Qualifications
then - ... etc
Then Benefits
then ... benefits paragraph ...
Then Pay
then ... pay paragraph ...
We should not include Schedule.
Check for any duplicated lines: we have not duplicated.
Check for any boilerplate removed: we removed EEO, accommodation link, etc.
Check for any minor metadata like Job ID: we omitted.
Now ensure we preserve all substantive info: Did we miss anything? The description also includes "Amazon Leo is Amazon's low Earth orbit satellite network." included. Good.
"Harnessing Engineer role, you will be responsible for conceptualizing, designing, procuring, testing, and support integration for the wiring harnesses across the entire satellite." included.
"Robust harness systems are crucial to maintaining reliable electrical system functionality." included.
"You will have direct impact on the success of creating a constellation of communication satellites that will be capable of reaching and providing broadband internet to the most remote areas of the world." included.
"Export Control Requirement:" included as requirement.
"Key job responsibilities" list included.
"A day in the life" paragraph included.
"About The Team" paragraph: we omitted? It's about team collaboration etc. That is substantive info about team. Should we include? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The About The Team section has content: "On the Harnessing Team, each member has the freedom to explore new ideas and explore their feasibility. Collaboration is critical to success and is always a high priority both within the team, as well as when working with other teams. While you are an individual contributor, it is still expected that each member takes ownership when needed. No job/task is beneath any member." That's substantive. Should we create a section? We have sections defined: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the Team" in the list. But we could incorporate that content into About the role or Responsibilities? The instruction says use those headings 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)." It seems they expect us to use those headings only. So we should map content to those headings. The About the Team content could go under About the role or Responsibilities? Probably under About the role as it's about the team. We'll add a paragraph after the initial About the role prose.
Thus About the role will have two paragraphs: mission/role and team description.
Now check if we missed any other substantive: "If you have a disability and need a workplace accommodation..." removed as boilerplate. "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." removed.
Now ensure we didn't include any filler like "commensurate with experience". Not present.
Now produce HTML.
Let's craft.
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. In the Harnessing Engineer role, you will be responsible for conceptualizing, designing, procuring, testing, and support integration for the wiring harnesses across the entire satellite. Robust harness systems are crucial to maintaining reliable electrical system functionality. You will have direct impact on the success of creating a constellation of communication satellites that will be capable of reaching and providing broadband internet to the most remote areas of the world.
On the Harnessing Team, each member has the freedom to explore new ideas and explore their feasibility. Collaboration is critical to success and is always a high priority both within the team, as well as when working with other teams. While you are an individual contributor, it is still expected that each member takes ownership when needed. No job/task is beneath any member.
Responsibilities:
- Harnessing design for satellite system requiring interfacing across mechanical, electrical and payload design owners, trading various configurations to identify best overall solution for reliability, manufacturability, test, integration, and cost.
- Support make vs buy decisions, design reviews, and implement manufacturing and integration plans optimized for high rate production
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment. Let's craft. First, maybe a short paragraph for metadata? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a
with location and job ID? But they said drop minor metadata. Probably we can drop Job ID. Location maybe part of Pay? The Pay line includes location. We'll keep that in Pay. Now content: About the role: The first paragraph(s) up to "Export Control Requirement:"? Actually Export Control is a requirement, not about role. So 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. In the Harnessing Engineer role, you will be responsible for conceptualizing, designing, procuring, testing, and support integration for the wiring harnesses across the entire satellite. Robust harness systems are crucial to maintaining reliable electrical system functionality. You will have direct impact on the success of creating a constellation of communication satellites that will be capable of reaching and providing broadband internet to the most remote areas of the world." That's prose. Responsibilities: list items from "Key job responsibilities" and maybe "A day in the life". Let's extract each sentence as bullet. Key job responsibilities list: - Harnessing design for satellite system requiring interfacing across mechanical, electrical and payload design owners, trading various configurations to identify best overall solution for reliability, manufacturability, test, integration, and cost. - Support make vs buy decisions, design reviews, and implement manufacturing and integration plans optimized for high rate production. - Engage various component suppliers and Harnessing manufacturing vendors for component & assembly level qualification. - Design/develop specifications and produce/procure power/data harnesses which meets electrical design requirements including current rating, targeted power loss, shielding, grounding and EMI/EMC. - Perform/oversee harness qualification and acceptance tests for launch environments and operation through mission life, including test fixture fabrication for prototype evaluations, and deliver all development and flight hardware per vehicle schedules - Create 3D CAD routings, 2D manufacturing drawings, schematics, and assembly installation drawings. "A day in the life" paragraph: "As a Harness Engineer, you will be working closely with all hardware sub-system and support teams on a daily basis. You will play an integral part of gathering requirements for harness development as well as providing critical input for successful integration of avionics hardware." We could add as bullets or prose. Since it's prose, we could put as
under Responsibilities. But instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can keep the list as
- and then add a
for the day in the life. Requirements: Basic Qualifications and Export Control Requirement. Basic Qualifications: "2+ years of hardware design and validation of components, subsystems and systems experience" and "Bachelor's degree in mechanical engineering, electrical engineering, material science, physics or equivalent". Also Export Control: "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." We can make a list. Qualifications: Preferred Qualifications: "Knowledge of engineering practices and patterns for the full software/hardware/networks development life cycle, including coding standards, code reviews, source control management, build processes, testing, certification, and livesite operations" and "Experience with hardware/software integration and real-time systems". Skills: Not present; we can omit. Benefits: Paragraph: "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. Learn more about our benefits at https://amazon.jobs/en/benefits." Also mention sign-on payments and RSUs? That is compensation; maybe include in Pay. 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, WA, REDMOND - 96,600.00 - 160,000.00 USD annually" We need to preserve all substantive info. So include that paragraph. We should not include the link to benefits? It's part of benefits; we can keep as prose. We should not include the accommodation link etc. Now construct HTML. We'll start with
About the role
then...
ThenResponsibilities
then- ... etc
A day in the life ...
ThenRequirements
then- ... etc
Qualifications
then- ... etc
Benefits
then... benefits paragraph ...
ThenPay
then... pay paragraph ...
We should not include Schedule. Check for any duplicated lines: we have not duplicated. Check for any boilerplate removed: we removed EEO, accommodation link, etc. Check for any minor metadata like Job ID: we omitted. Now ensure we preserve all substantive info: Did we miss anything? The description also includes "Amazon Leo is Amazon's low Earth orbit satellite network." included. Good. "Harnessing Engineer role, you will be responsible for conceptualizing, designing, procuring, testing, and support integration for the wiring harnesses across the entire satellite." included. "Robust harness systems are crucial to maintaining reliable electrical system functionality." included. "You will have direct impact on the success of creating a constellation of communication satellites that will be capable of reaching and providing broadband internet to the most remote areas of the world." included. "Export Control Requirement:" included as requirement. "Key job responsibilities" list included. "A day in the life" paragraph included. "About The Team" paragraph: we omitted? It's about team collaboration etc. That is substantive info about team. Should we include? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The About The Team section has content: "On the Harnessing Team, each member has the freedom to explore new ideas and explore their feasibility. Collaboration is critical to success and is always a high priority both within the team, as well as when working with other teams. While you are an individual contributor, it is still expected that each member takes ownership when needed. No job/task is beneath any member." That's substantive. Should we create a section? We have sections defined: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the Team" in the list. But we could incorporate that content into About the role or Responsibilities? The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect us to use those headings only. So we should map content to those headings. The About the Team content could go under About the role or Responsibilities? Probably under About the role as it's about the team. We'll add a paragraph after the initial About the role prose. Thus About the role will have two paragraphs: mission/role and team description. Now check if we missed any other substantive: "If you have a disability and need a workplace accommodation..." removed as boilerplate. "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." removed. Now ensure we didn't include any filler like "commensurate with experience". Not present. Now produce HTML. Let's craft. 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. In the Harnessing Engineer role, you will be responsible for conceptualizing, designing, procuring, testing, and support integration for the wiring harnesses across the entire satellite. Robust harness systems are crucial to maintaining reliable electrical system functionality. You will have direct impact on the success of creating a constellation of communication satellites that will be capable of reaching and providing broadband internet to the most remote areas of the world.
On the Harnessing Team, each member has the freedom to explore new ideas and explore their feasibility. Collaboration is critical to success and is always a high priority both within the team, as well as when working with other teams. While you are an individual contributor, it is still expected that each member takes ownership when needed. No job/task is beneath any member.
Responsibilities:- Harnessing design for satellite system requiring interfacing across mechanical, electrical and payload design owners, trading various configurations to identify best overall solution for reliability, manufacturability, test, integration, and cost.
- Support make vs buy decisions, design reviews, and implement manufacturing and integration plans optimized for high rate production
- and then add a