Test Engineer (Avionics Test Lab)
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to drop the EEO statement, ITAR? Actually ITAR is a requirement, not boilerplate; we should keep it. The EEO statement is boilerplate; remove. Also the "Learn more about the ITAR here." link maybe we can keep mention but not the link? Probably keep the requirement text but drop the link. Also "SpaceX is an Equal Opportunity Employer..." remove.
Also "Applicants wishing to view a copy of SpaceX’s Affirmative Action Plan..." remove.
Also "Your actual level and base salary will be determined on a case-by-case basis..." keep as part of compensation.
We need to ensure we don't include placeholders like "commensurate with experience" etc. Not present.
We need to output only HTML fragment.
Let's extract content:
About the role: The paragraph: "SpaceX was founded under the belief that a future where humanity is out exploring the stars is fundamentally more exciting than one where we are not. Today SpaceX is actively developing the technologies to make this possible, with the ultimate goal of enabling human life on Mars. TEST ENGINEER (AVIONICS TEST LAB) The Avionics Test Lab performs critical environmental stress and functional screening of all electronic hardware prior to vehicle integration including flight computers, power conversion units, analog and digital circuit boards, FPGAs, communication system units, and more. As a Test Engineer, you will own the success of both flight hardware through testing and any associated test processes to drive safe, high-quality, and efficient delivery to SpaceX vehicles."
We should not repeat the job title as heading, but we can keep the text that includes the title? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't say we must remove the title from the prose. It's okay to keep it in the paragraph. However we might want to keep the description after title. We'll keep the paragraph as is.
Responsibilities: list items:
- Own flight hardware through thermal, vibration, and other screening procedures and serve as primary contact for any associated issues or stoppages
- Ensure all avionics flight hardware meets SpaceX and customer requirements at the conclusion of testing process
- Write automation software in Python to interact with flight hardware, test equipment, instrumentation, and production documentation
- Troubleshoot test software and modify codebase to adjust test bounds, implement fixes, and incorporate updates as needed
- Collaborate with mechanical/electrical design, quality, and production teams solve high-complexity testing challenges
- Drive continuous improvement efforts to increase throughput and reduce cost to meet launch target
Note: there is a missing "and" before solve? Actually original: "Collaborate with mechanical/electrical design, quality, and production teams solve high-complexity testing challenges". We'll keep as is.
Requirements (Basic Qualifications + Additional Requirements + ITAR):
Basic Qualifications:
- Bachelor’s degree in engineering, computer science, or physics
- 1+ years of experience in a hardware and/or software testing environment
- 1+ years of experience in any of the following languages: Python, C#, C++, JavaScript, Visual Basic, MATLAB, and/or LabVIEW
Additional Requirements:
- Standing, lifting, and carrying equipment up to 25 lbs. unassisted
- Must be available to work extended hours and weekends as needed
ITAR Requirements:
- To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C.1157, or (iv) Asylee under 8 U.S.C.1158, or be eligible to obtain the required authorizations from the U.S. Department of State.
We could combine into a single Requirements section with sub-lists? But we just need a list; we can combine all items into one
. However we might want to keep logical grouping but not required. We'll just list all.
Skills (Preferred Skills And Experience):
- Knowledge of and experience with avionics hardware including flight computers, gas sensors, controllers, antennas, transmitters, receivers, and PCBAs
- Experience developing object-oriented software and automated test software
- Experience with environmental testing such as thermal, vibration, shock, and thermal vacuum
- Understanding of electrical schematics and electronics manufacturing to analyze and improve test coverage
- Proven track record solving complex problems with minimal supervision and on a tight schedule
- Excellent communication skills both written and verbal
Compensation And Benefits: We need Pay and Benefits sections? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could have separate Pay and Benefits headings, but we should only include if posting actually states them. The posting includes Pay Range and benefits description. So we can have Pay
with pay range info, and Benefits
with benefits list. Or combine into Compensation And Benefits heading. The instruction says we can use Benefits, Pay as headings. It says "Prefer a few substantive sections over many thin ones." So maybe combine into one section "Compensation And Benefits". But they gave examples including Benefits, Pay. It's up to us. I'd combine to avoid thin sections. However we need to preserve all substantive information; we can still include both under one heading with paragraphs and lists.
Let's do Compensation And Benefits
then
Pay Range: Level 1: $105,000.00 - $140,000.00 Level 2: $120,000.00 - $170,000.00 Your actual level and base salary will be determined on a case-by-case basis and may vary based on the following considerations: job-related knowledge and skills, education, and experience. Base salary is just one part of your total rewards package at SpaceX. You may also be eligible for long-term incentives, in the form of company stock or long-term cash awards, as well as potential discretionary bonuses and the ability to purchase additional stock at a discount through an Employee Stock Purchase Plan.
then - ... benefits list
.
Benefits list: comprehensive medical, vision, and dental coverage, access to a 401(k) retirement plan, short and long-term disability insurance, life insurance, paid parental leave, various other discounts and perks, 3 weeks of paid vacation, 10 or more paid holidays per year, paid sick leave pursuant to Company policy which satisfies or exceeds the accrual, carryover, and use requirements of the law.
We'll output as - ... each benefit as separate li? Could combine but better separate.
Let's craft.
Make sure no extra text outside HTML.
Let's produce:
About the role
SpaceX was founded under the belief that a future where humanity is out exploring the stars is fundamentally more exciting than one where we are not. Today SpaceX is actively developing the technologies to make this possible, with the ultimate goal of enabling human life on Mars. TEST ENGINEER (AVIONICS TEST LAB) The Avionics Test Lab performs critical environmental stress and functional screening of all electronic hardware prior to vehicle integration including flight computers, power conversion units, analog and digital circuit boards, FPGAs, communication system units, and more. As a Test Engineer, you will own the success of both flight hardware through testing and any associated test processes to drive safe, high-quality, and efficient delivery to SpaceX vehicles.
Responsibilities
- Own flight hardware through thermal, vibration, and other screening procedures and serve as primary contact for any associated issues or stoppages
- Ensure all avionics flight hardware meets SpaceX and customer requirements at the conclusion of testing process
- Write automation software in Python to interact with flight hardware, test equipment, instrumentation, and production documentation
- Troubleshoot test software and modify codebase to adjust test bounds, implement fixes, and incorporate updates as needed
- Collaborate with mechanical/electrical design, quality, and production teams solve high-complexity testing challenges
- Drive continuous improvement efforts to increase throughput and reduce cost to meet launch target
Requirements
- Bachelor’s degree in engineering, computer science, or physics
- 1+ years of experience in a hardware and/or software testing environment
- 1+ years of experience in any of the following languages: Python, C#, C++, JavaScript, Visual Basic, MATLAB, and/or LabVIEW
- Standing, lifting, and carrying equipment up to 25 lbs. unassisted
- Must be available to work extended hours and weekends as needed
- To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C.1157, or (iv) Asylee under 8 U.S.C.1158, or be eligible to obtain the required authorizations from the U.S. Department of State.
Skills
- Knowledge of and experience with avionics hardware including flight computers, gas sensors, controllers, antennas, transmitters, receivers, and PCBAs
- Experience developing object-oriented software and automated test software
- Experience with environmental testing such as thermal, vibration, shock, and thermal vacuum
- Understanding of electrical schematics and electronics manufacturing to analyze and improve test coverage
- Proven track record solving complex problems with minimal supervision and on a tight schedule
- Excellent communication skills both written and verbal
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to drop the EEO statement, ITAR? Actually ITAR is a requirement, not boilerplate; we should keep it. The EEO statement is boilerplate; remove. Also the "Learn more about the ITAR here." link maybe we can keep mention but not the link? Probably keep the requirement text but drop the link. Also "SpaceX is an Equal Opportunity Employer..." remove. Also "Applicants wishing to view a copy of SpaceX’s Affirmative Action Plan..." remove. Also "Your actual level and base salary will be determined on a case-by-case basis..." keep as part of compensation. We need to ensure we don't include placeholders like "commensurate with experience" etc. Not present. We need to output only HTML fragment. Let's extract content: About the role: The paragraph: "SpaceX was founded under the belief that a future where humanity is out exploring the stars is fundamentally more exciting than one where we are not. Today SpaceX is actively developing the technologies to make this possible, with the ultimate goal of enabling human life on Mars. TEST ENGINEER (AVIONICS TEST LAB) The Avionics Test Lab performs critical environmental stress and functional screening of all electronic hardware prior to vehicle integration including flight computers, power conversion units, analog and digital circuit boards, FPGAs, communication system units, and more. As a Test Engineer, you will own the success of both flight hardware through testing and any associated test processes to drive safe, high-quality, and efficient delivery to SpaceX vehicles." We should not repeat the job title as heading, but we can keep the text that includes the title? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't say we must remove the title from the prose. It's okay to keep it in the paragraph. However we might want to keep the description after title. We'll keep the paragraph as is. Responsibilities: list items: - Own flight hardware through thermal, vibration, and other screening procedures and serve as primary contact for any associated issues or stoppages - Ensure all avionics flight hardware meets SpaceX and customer requirements at the conclusion of testing process - Write automation software in Python to interact with flight hardware, test equipment, instrumentation, and production documentation - Troubleshoot test software and modify codebase to adjust test bounds, implement fixes, and incorporate updates as needed - Collaborate with mechanical/electrical design, quality, and production teams solve high-complexity testing challenges - Drive continuous improvement efforts to increase throughput and reduce cost to meet launch target Note: there is a missing "and" before solve? Actually original: "Collaborate with mechanical/electrical design, quality, and production teams solve high-complexity testing challenges". We'll keep as is. Requirements (Basic Qualifications + Additional Requirements + ITAR): Basic Qualifications: - Bachelor’s degree in engineering, computer science, or physics - 1+ years of experience in a hardware and/or software testing environment - 1+ years of experience in any of the following languages: Python, C#, C++, JavaScript, Visual Basic, MATLAB, and/or LabVIEW Additional Requirements: - Standing, lifting, and carrying equipment up to 25 lbs. unassisted - Must be available to work extended hours and weekends as needed ITAR Requirements: - To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C.1157, or (iv) Asylee under 8 U.S.C.1158, or be eligible to obtain the required authorizations from the U.S. Department of State. We could combine into a single Requirements section with sub-lists? But we just need a list; we can combine all items into one
- . However we might want to keep logical grouping but not required. We'll just list all.
Skills (Preferred Skills And Experience):
- Knowledge of and experience with avionics hardware including flight computers, gas sensors, controllers, antennas, transmitters, receivers, and PCBAs
- Experience developing object-oriented software and automated test software
- Experience with environmental testing such as thermal, vibration, shock, and thermal vacuum
- Understanding of electrical schematics and electronics manufacturing to analyze and improve test coverage
- Proven track record solving complex problems with minimal supervision and on a tight schedule
- Excellent communication skills both written and verbal
Compensation And Benefits: We need Pay and Benefits sections? The instruction: "Use
- ... benefits list
- ... each benefit as separate li? Could combine but better separate.
Let's craft.
Make sure no extra text outside HTML.
Let's produce:
About the role
SpaceX was founded under the belief that a future where humanity is out exploring the stars is fundamentally more exciting than one where we are not. Today SpaceX is actively developing the technologies to make this possible, with the ultimate goal of enabling human life on Mars. TEST ENGINEER (AVIONICS TEST LAB) The Avionics Test Lab performs critical environmental stress and functional screening of all electronic hardware prior to vehicle integration including flight computers, power conversion units, analog and digital circuit boards, FPGAs, communication system units, and more. As a Test Engineer, you will own the success of both flight hardware through testing and any associated test processes to drive safe, high-quality, and efficient delivery to SpaceX vehicles.
Responsibilities
- Own flight hardware through thermal, vibration, and other screening procedures and serve as primary contact for any associated issues or stoppages
- Ensure all avionics flight hardware meets SpaceX and customer requirements at the conclusion of testing process
- Write automation software in Python to interact with flight hardware, test equipment, instrumentation, and production documentation
- Troubleshoot test software and modify codebase to adjust test bounds, implement fixes, and incorporate updates as needed
- Collaborate with mechanical/electrical design, quality, and production teams solve high-complexity testing challenges
- Drive continuous improvement efforts to increase throughput and reduce cost to meet launch target
Requirements
- Bachelor’s degree in engineering, computer science, or physics
- 1+ years of experience in a hardware and/or software testing environment
- 1+ years of experience in any of the following languages: Python, C#, C++, JavaScript, Visual Basic, MATLAB, and/or LabVIEW
- Standing, lifting, and carrying equipment up to 25 lbs. unassisted
- Must be available to work extended hours and weekends as needed
- To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C.1157, or (iv) Asylee under 8 U.S.C.1158, or be eligible to obtain the required authorizations from the U.S. Department of State.
Skills
- Knowledge of and experience with avionics hardware including flight computers, gas sensors, controllers, antennas, transmitters, receivers, and PCBAs
- Experience developing object-oriented software and automated test software
- Experience with environmental testing such as thermal, vibration, shock, and thermal vacuum
- Understanding of electrical schematics and electronics manufacturing to analyze and improve test coverage
- Proven track record solving complex problems with minimal supervision and on a tight schedule
- Excellent communication skills both written and verbal
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could have separate Pay and Benefits headings, but we should only include if posting actually states them. The posting includes Pay Range and benefits description. So we can have Pay
with pay range info, and Benefits
with benefits list. Or combine into Compensation And Benefits heading. The instruction says we can use Benefits, Pay as headings. It says "Prefer a few substantive sections over many thin ones." So maybe combine into one section "Compensation And Benefits". But they gave examples including Benefits, Pay. It's up to us. I'd combine to avoid thin sections. However we need to preserve all substantive information; we can still include both under one heading with paragraphs and lists.
Let's do Compensation And Benefits
then
Pay Range: Level 1: $105,000.00 - $140,000.00 Level 2: $120,000.00 - $170,000.00 Your actual level and base salary will be determined on a case-by-case basis and may vary based on the following considerations: job-related knowledge and skills, education, and experience. Base salary is just one part of your total rewards package at SpaceX. You may also be eligible for long-term incentives, in the form of company stock or long-term cash awards, as well as potential discretionary bonuses and the ability to purchase additional stock at a discount through an Employee Stock Purchase Plan.
then