Assembly, Integration, and Test Intern (Winter 2027)
for section headings (e.g. 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. The posting includes:
- Company description (Astranis builds advanced satellites...). Could be "About the role"? Actually "About the role" is for role description. Could have "About the company" but not in list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those as needed.
We have:
- Role description: "Work on an interdisciplinary team to design, build, and test satellite hardware and software. Work with the Electrical, Mechanical, RF, Propulsion engineering teams to develop assembly and integration test plans and procedures based on concepts and designs. Learn to use various pieces of test equipment and instruments (thermal chambers, vibration tables, DAQs, oscilloscopes, etc.) to successfully execute test plans. Coordinate assembly, integration and environmental test efforts". That's responsibilities.
- Requirements: "Currently pursuing a four-year degree in Electrical Engineering, Mechanical Engineering (or equivalent technical degree) A passion for hardware development, including working in a fast-paced environment and hands-on design and development Ability to handle multiple tasks and prioritize Strong communication skills Familiarity with spacecraft systems and operation Must be onsite 5 days a week". That's requirements.
- Bonus: "Hands-on experience in designing, building, and testing Experience writing Python code to: Interface with test equipment, process large datasets, visualize data Experience in CAD Direct electrical or mechanical design experience Demonstrated ability to debug hardware and software problems under time pressure". That's qualifications/skills.
- Pay: "The base pay for this position is $29.00 per hour. Base Hourly Pay $29—$29 USD". So we have Pay.
- Schedule: Not explicitly given besides "Must be onsite 5 days a week". That's schedule info. Could be schedule section.
- Benefits: Not mentioned. No benefits listed. So we should not create Benefits section.
- About the role: Could be a brief overview: "Internships at Astranis typically last for twelve weeks, and are hourly roles designed for students who are currently enrolled at a four-year university. As an Intern, you will have an amazing opportunity to work on hard problems — we pride ourselves on giving everyone at Astranis a chance to do meaningful work on challenging projects, no matter their seniority. Many past interns have designed and tested hardware/software that is heading to space on our first satellite, and many of them are now full-time employees at Astranis. If you have already graduated from a four-year university, please apply to be an Associate Engineer." That's about the role/internship.
- Also company description at top: "Astranis builds advanced satellites for high orbits, expanding humanity’s reach into the solar system...". That could be part of About the role? Might be considered company overview. But we can include as part of About the role or maybe a separate section not in 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 suggests those as examples. Probably we should stick to those headings. The company description could go under About the role as context.
We must remove boilerplate: citizenship requirement, diversity statement, SMS terms, privacy policy, etc. Those are legal/EEO/equal-opportunity/scam-warning boilerplate. So we must drop those. Also remove duplicated lines.
Thus final HTML fragment will have sections: About the role, Responsibilities, Requirements, Qualifications (or Skills), Pay, Schedule. Possibly combine Qualifications and Skills? The bonus could be Skills. We'll treat Bonus as Skills.
We need to use - for any list of duties/requirements/benefits. For prose, use
. So for each section we can have a heading
then content.
We need to preserve all substantive information. Let's extract.
About the role content:
- Internships at Astranis typically last for twelve weeks, and are hourly roles designed for students who are currently enrolled at a four-year university.
- As an Intern, you will have an amazing opportunity to work on hard problems — we pride ourselves on giving everyone at Astranis a chance to do meaningful work on challenging projects, no matter their seniority.
- Many past interns have designed and tested hardware/software that is heading to space on our first satellite, and many of them are now full-time employees at Astranis.
- If you have already graduated from a four-year university, please apply to be an Associate Engineer.
We could combine into paragraphs.
Responsibilities content (list):
- Work on an interdisciplinary team to design, build, and test satellite hardware and software.
- Work with the Electrical, Mechanical, RF, Propulsion engineering teams to develop assembly and integration test plans and procedures based on concepts and designs.
- Learn to use various pieces of test equipment and instruments (thermal chambers, vibration tables, DAQs, oscilloscopes, etc.) to successfully execute test plans.
- Coordinate assembly, integration and environmental test efforts.
Requirements content (list):
- Currently pursuing a four-year degree in Electrical Engineering, Mechanical Engineering (or equivalent technical degree)
- A passion for hardware development, including working in a fast-paced environment and hands-on design and development
- Ability to handle multiple tasks and prioritize
- Strong communication skills
- Familiarity with spacecraft systems and operation
- Must be onsite 5 days a week
Skills/Bonus content (list):
- Hands-on experience in designing, building, and testing
- Experience writing Python code to: Interface with test equipment, process large datasets, visualize data
- Experience in CAD
- Direct electrical or mechanical design experience
- Demonstrated ability to debug hardware and software problems under time pressure
Pay: "$29.00 per hour". Could be a paragraph.
Schedule: "Must be onsite 5 days a week" (already in requirements). But schedule section could mention typical duration: twelve weeks, hourly role. Actually schedule: Internships typically last for twelve weeks, hourly role. Also must be onsite 5 days a week. So schedule section: "Internships typically last for twelve weeks, hourly role. Must be onsite 5 days a week."
We should avoid duplication: The onsite 5 days a week appears in requirements and schedule; we can keep it in both or deduplicate? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay if it's in original. But we could keep it in both sections; it's not duplicated lines exactly but same sentence appears twice. Might be considered duplicated lines? The original had "Must be onsite 5 days a week" under Requirements only. Not under schedule. So schedule we can mention duration and hourly nature, not repeat onsite. So schedule: "Internships typically last for twelve weeks, and are hourly roles designed for students who are currently enrolled at a four-year university." Actually that's from About the role. But schedule could be: "Internships typically last for twelve weeks, and are hourly roles." We'll keep that.
Now produce HTML.
We need to ensure we don't include any markdown fences. Just raw HTML.
Let's craft:
About the role
Internships at Astranis typically last for twelve weeks, and are hourly roles designed for students who are currently enrolled at a four-year university. As an Intern, you will have an amazing opportunity to work on hard problems — we pride ourselves on giving everyone at Astranis a chance to do meaningful work on challenging projects, no matter their seniority. Many past interns have designed and tested hardware/software that is heading to space on our first satellite, and many of them are now full-time employees at Astranis. If you have already graduated from a four-year university, please apply to be an Associate Engineer.
Responsibilities
- Work on an interdisciplinary team to design, build, and test satellite hardware and software.
- Work with the Electrical, Mechanical, RF, Propulsion engineering teams to develop assembly and integration test plans and procedures based on concepts and designs.
- Learn to use various pieces of test equipment and instruments (thermal chambers, vibration tables, DAQs, oscilloscopes, etc.) to successfully execute test plans.
- Coordinate assembly, integration and environmental test efforts.
Requirements
- Currently pursuing a four-year degree in Electrical Engineering, Mechanical Engineering (or equivalent technical degree)
- A passion for hardware development, including working in a fast-paced environment and hands-on design and development
- Ability to handle multiple tasks and prioritize
- Strong communication skills
- Familiarity with spacecraft systems and operation
- Must be onsite 5 days a week
Skills
- Hands-on experience in designing, building, and testing
- Experience writing Python code to: Interface with test equipment, process large datasets, visualize data
- Experience in CAD
- Direct electrical or mechanical design experience
- Demonstrated ability to debug hardware and software problems under time pressure
Pay
The base pay for this position is $29.00 per hour.
Schedule
Internships typically last for twelve weeks, and are hourly roles.
Check for any leftover boilerplate: we removed citizenship, diversity, SMS terms, privacy policy. Good.
We should ensure we didn't miss any substantive info: The description of Astranis building satellites etc. Could be considered "About the role" but we omitted. Is that substantive? It's company overview, not directly about role but maybe relevant. The instruction says preserve ALL substantive information. The company description is substantive. Should we include it? Could be placed under About the role as introductory paragraph. Let's add a paragraph before the internship description: "Astranis builds advanced satellites for high orbits, expanding humanity’s reach into the solar system. Today, Astranis satellites provide dedicated, secure networks to highly-sophisticated customers across the globe— large enterprises, sovereign governments, and the US military. With five satellites on orbit and many more set to launch soon, the company is servicing a backlog of more than $1 billion of commercial contracts. Astranis is the preferred satellite communications partner for buyers with stringent requirements for uptime, data security, network visibility, and customization. Astranis has raised over $750 million from some of the world’s best investors, from Andreessen Horowitz to Blackrock and Fidelity, and employs a team 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. The posting includes: - Company description (Astranis builds advanced satellites...). Could be "About the role"? Actually "About the role" is for role description. Could have "About the company" but not in list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those as needed. We have: - Role description: "Work on an interdisciplinary team to design, build, and test satellite hardware and software. Work with the Electrical, Mechanical, RF, Propulsion engineering teams to develop assembly and integration test plans and procedures based on concepts and designs. Learn to use various pieces of test equipment and instruments (thermal chambers, vibration tables, DAQs, oscilloscopes, etc.) to successfully execute test plans. Coordinate assembly, integration and environmental test efforts". That's responsibilities. - Requirements: "Currently pursuing a four-year degree in Electrical Engineering, Mechanical Engineering (or equivalent technical degree) A passion for hardware development, including working in a fast-paced environment and hands-on design and development Ability to handle multiple tasks and prioritize Strong communication skills Familiarity with spacecraft systems and operation Must be onsite 5 days a week". That's requirements. - Bonus: "Hands-on experience in designing, building, and testing Experience writing Python code to: Interface with test equipment, process large datasets, visualize data Experience in CAD Direct electrical or mechanical design experience Demonstrated ability to debug hardware and software problems under time pressure". That's qualifications/skills. - Pay: "The base pay for this position is $29.00 per hour. Base Hourly Pay $29—$29 USD". So we have Pay. - Schedule: Not explicitly given besides "Must be onsite 5 days a week". That's schedule info. Could be schedule section. - Benefits: Not mentioned. No benefits listed. So we should not create Benefits section. - About the role: Could be a brief overview: "Internships at Astranis typically last for twelve weeks, and are hourly roles designed for students who are currently enrolled at a four-year university. As an Intern, you will have an amazing opportunity to work on hard problems — we pride ourselves on giving everyone at Astranis a chance to do meaningful work on challenging projects, no matter their seniority. Many past interns have designed and tested hardware/software that is heading to space on our first satellite, and many of them are now full-time employees at Astranis. If you have already graduated from a four-year university, please apply to be an Associate Engineer." That's about the role/internship. - Also company description at top: "Astranis builds advanced satellites for high orbits, expanding humanity’s reach into the solar system...". That could be part of About the role? Might be considered company overview. But we can include as part of About the role or maybe a separate section not in 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 suggests those as examples. Probably we should stick to those headings. The company description could go under About the role as context.
We must remove boilerplate: citizenship requirement, diversity statement, SMS terms, privacy policy, etc. Those are legal/EEO/equal-opportunity/scam-warning boilerplate. So we must drop those. Also remove duplicated lines.
Thus final HTML fragment will have sections: About the role, Responsibilities, Requirements, Qualifications (or Skills), Pay, Schedule. Possibly combine Qualifications and Skills? The bonus could be Skills. We'll treat Bonus as Skills.
We need to use - for any list of duties/requirements/benefits. For prose, use
. So for each section we can have a heading
then content.
We need to preserve all substantive information. Let's extract.
About the role content:
- Internships at Astranis typically last for twelve weeks, and are hourly roles designed for students who are currently enrolled at a four-year university.
- As an Intern, you will have an amazing opportunity to work on hard problems — we pride ourselves on giving everyone at Astranis a chance to do meaningful work on challenging projects, no matter their seniority.
- Many past interns have designed and tested hardware/software that is heading to space on our first satellite, and many of them are now full-time employees at Astranis.
- If you have already graduated from a four-year university, please apply to be an Associate Engineer.
We could combine into paragraphs.
Responsibilities content (list):
- Work on an interdisciplinary team to design, build, and test satellite hardware and software.
- Work with the Electrical, Mechanical, RF, Propulsion engineering teams to develop assembly and integration test plans and procedures based on concepts and designs.
- Learn to use various pieces of test equipment and instruments (thermal chambers, vibration tables, DAQs, oscilloscopes, etc.) to successfully execute test plans.
- Coordinate assembly, integration and environmental test efforts.
Requirements content (list):
- Currently pursuing a four-year degree in Electrical Engineering, Mechanical Engineering (or equivalent technical degree)
- A passion for hardware development, including working in a fast-paced environment and hands-on design and development
- Ability to handle multiple tasks and prioritize
- Strong communication skills
- Familiarity with spacecraft systems and operation
- Must be onsite 5 days a week
Skills/Bonus content (list):
- Hands-on experience in designing, building, and testing
- Experience writing Python code to: Interface with test equipment, process large datasets, visualize data
- Experience in CAD
- Direct electrical or mechanical design experience
- Demonstrated ability to debug hardware and software problems under time pressure
Pay: "$29.00 per hour". Could be a paragraph.
Schedule: "Must be onsite 5 days a week" (already in requirements). But schedule section could mention typical duration: twelve weeks, hourly role. Actually schedule: Internships typically last for twelve weeks, hourly role. Also must be onsite 5 days a week. So schedule section: "Internships typically last for twelve weeks, hourly role. Must be onsite 5 days a week."
We should avoid duplication: The onsite 5 days a week appears in requirements and schedule; we can keep it in both or deduplicate? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay if it's in original. But we could keep it in both sections; it's not duplicated lines exactly but same sentence appears twice. Might be considered duplicated lines? The original had "Must be onsite 5 days a week" under Requirements only. Not under schedule. So schedule we can mention duration and hourly nature, not repeat onsite. So schedule: "Internships typically last for twelve weeks, and are hourly roles designed for students who are currently enrolled at a four-year university." Actually that's from About the role. But schedule could be: "Internships typically last for twelve weeks, and are hourly roles." We'll keep that.
Now produce HTML.
We need to ensure we don't include any markdown fences. Just raw HTML.
Let's craft:
About the role
Internships at Astranis typically last for twelve weeks, and are hourly roles designed for students who are currently enrolled at a four-year university. As an Intern, you will have an amazing opportunity to work on hard problems — we pride ourselves on giving everyone at Astranis a chance to do meaningful work on challenging projects, no matter their seniority. Many past interns have designed and tested hardware/software that is heading to space on our first satellite, and many of them are now full-time employees at Astranis. If you have already graduated from a four-year university, please apply to be an Associate Engineer.
Responsibilities
- Work on an interdisciplinary team to design, build, and test satellite hardware and software.
- Work with the Electrical, Mechanical, RF, Propulsion engineering teams to develop assembly and integration test plans and procedures based on concepts and designs.
- Learn to use various pieces of test equipment and instruments (thermal chambers, vibration tables, DAQs, oscilloscopes, etc.) to successfully execute test plans.
- Coordinate assembly, integration and environmental test efforts.
Requirements
- Currently pursuing a four-year degree in Electrical Engineering, Mechanical Engineering (or equivalent technical degree)
- A passion for hardware development, including working in a fast-paced environment and hands-on design and development
- Ability to handle multiple tasks and prioritize
- Strong communication skills
- Familiarity with spacecraft systems and operation
- Must be onsite 5 days a week
Skills
- Hands-on experience in designing, building, and testing
- Experience writing Python code to: Interface with test equipment, process large datasets, visualize data
- Experience in CAD
- Direct electrical or mechanical design experience
- Demonstrated ability to debug hardware and software problems under time pressure
Pay
The base pay for this position is $29.00 per hour.
Schedule
Internships typically last for twelve weeks, and are hourly roles.
Check for any leftover boilerplate: we removed citizenship, diversity, SMS terms, privacy policy. Good.
We should ensure we didn't miss any substantive info: The description of Astranis building satellites etc. Could be considered "About the role" but we omitted. Is that substantive? It's company overview, not directly about role but maybe relevant. The instruction says preserve ALL substantive information. The company description is substantive. Should we include it? Could be placed under About the role as introductory paragraph. Let's add a paragraph before the internship description: "Astranis builds advanced satellites for high orbits, expanding humanity’s reach into the solar system. Today, Astranis satellites provide dedicated, secure networks to highly-sophisticated customers across the globe— large enterprises, sovereign governments, and the US military. With five satellites on orbit and many more set to launch soon, the company is servicing a backlog of more than $1 billion of commercial contracts. Astranis is the preferred satellite communications partner for buyers with stringent requirements for uptime, data security, network visibility, and customization. Astranis has raised over $750 million from some of the world’s best investors, from Andreessen Horowitz to Blackrock and Fidelity, and employs a team of
. So for each section we can have a heading
then content.
We need to preserve all substantive information. Let's extract.
About the role content:
- Internships at Astranis typically last for twelve weeks, and are hourly roles designed for students who are currently enrolled at a four-year university.
- As an Intern, you will have an amazing opportunity to work on hard problems — we pride ourselves on giving everyone at Astranis a chance to do meaningful work on challenging projects, no matter their seniority.
- Many past interns have designed and tested hardware/software that is heading to space on our first satellite, and many of them are now full-time employees at Astranis.
- If you have already graduated from a four-year university, please apply to be an Associate Engineer.
We could combine into paragraphs.
Responsibilities content (list):
- Work on an interdisciplinary team to design, build, and test satellite hardware and software.
- Work with the Electrical, Mechanical, RF, Propulsion engineering teams to develop assembly and integration test plans and procedures based on concepts and designs.
- Learn to use various pieces of test equipment and instruments (thermal chambers, vibration tables, DAQs, oscilloscopes, etc.) to successfully execute test plans.
- Coordinate assembly, integration and environmental test efforts.
Requirements content (list):
- Currently pursuing a four-year degree in Electrical Engineering, Mechanical Engineering (or equivalent technical degree)
- A passion for hardware development, including working in a fast-paced environment and hands-on design and development
- Ability to handle multiple tasks and prioritize
- Strong communication skills
- Familiarity with spacecraft systems and operation
- Must be onsite 5 days a week
Skills/Bonus content (list):
- Hands-on experience in designing, building, and testing
- Experience writing Python code to: Interface with test equipment, process large datasets, visualize data
- Experience in CAD
- Direct electrical or mechanical design experience
- Demonstrated ability to debug hardware and software problems under time pressure
Pay: "$29.00 per hour". Could be a paragraph.
Schedule: "Must be onsite 5 days a week" (already in requirements). But schedule section could mention typical duration: twelve weeks, hourly role. Actually schedule: Internships typically last for twelve weeks, hourly role. Also must be onsite 5 days a week. So schedule section: "Internships typically last for twelve weeks, hourly role. Must be onsite 5 days a week."
We should avoid duplication: The onsite 5 days a week appears in requirements and schedule; we can keep it in both or deduplicate? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay if it's in original. But we could keep it in both sections; it's not duplicated lines exactly but same sentence appears twice. Might be considered duplicated lines? The original had "Must be onsite 5 days a week" under Requirements only. Not under schedule. So schedule we can mention duration and hourly nature, not repeat onsite. So schedule: "Internships typically last for twelve weeks, and are hourly roles designed for students who are currently enrolled at a four-year university." Actually that's from About the role. But schedule could be: "Internships typically last for twelve weeks, and are hourly roles." We'll keep that.
Now produce HTML.
We need to ensure we don't include any markdown fences. Just raw HTML.
Let's craft:
About the role
Internships at Astranis typically last for twelve weeks, and are hourly roles designed for students who are currently enrolled at a four-year university. As an Intern, you will have an amazing opportunity to work on hard problems — we pride ourselves on giving everyone at Astranis a chance to do meaningful work on challenging projects, no matter their seniority. Many past interns have designed and tested hardware/software that is heading to space on our first satellite, and many of them are now full-time employees at Astranis. If you have already graduated from a four-year university, please apply to be an Associate Engineer.
Responsibilities
- Work on an interdisciplinary team to design, build, and test satellite hardware and software.
- Work with the Electrical, Mechanical, RF, Propulsion engineering teams to develop assembly and integration test plans and procedures based on concepts and designs.
- Learn to use various pieces of test equipment and instruments (thermal chambers, vibration tables, DAQs, oscilloscopes, etc.) to successfully execute test plans.
- Coordinate assembly, integration and environmental test efforts.
Requirements
- Currently pursuing a four-year degree in Electrical Engineering, Mechanical Engineering (or equivalent technical degree)
- A passion for hardware development, including working in a fast-paced environment and hands-on design and development
- Ability to handle multiple tasks and prioritize
- Strong communication skills
- Familiarity with spacecraft systems and operation
- Must be onsite 5 days a week
Skills
- Hands-on experience in designing, building, and testing
- Experience writing Python code to: Interface with test equipment, process large datasets, visualize data
- Experience in CAD
- Direct electrical or mechanical design experience
- Demonstrated ability to debug hardware and software problems under time pressure
Pay
The base pay for this position is $29.00 per hour.
Schedule
Internships typically last for twelve weeks, and are hourly roles.
Check for any leftover boilerplate: we removed citizenship, diversity, SMS terms, privacy policy. Good. We should ensure we didn't miss any substantive info: The description of Astranis building satellites etc. Could be considered "About the role" but we omitted. Is that substantive? It's company overview, not directly about role but maybe relevant. The instruction says preserve ALL substantive information. The company description is substantive. Should we include it? Could be placed under About the role as introductory paragraph. Let's add a paragraph before the internship description: "Astranis builds advanced satellites for high orbits, expanding humanity’s reach into the solar system. Today, Astranis satellites provide dedicated, secure networks to highly-sophisticated customers across the globe— large enterprises, sovereign governments, and the US military. With five satellites on orbit and many more set to launch soon, the company is servicing a backlog of more than $1 billion of commercial contracts. Astranis is the preferred satellite communications partner for buyers with stringent requirements for uptime, data security, network visibility, and customization. Astranis has raised over $750 million from some of the world’s best investors, from Andreessen Horowitz to Blackrock and Fidelity, and employs a team of