RF Validation Intern (Summer 2027)

We need to output HTML fragment with sections: About the role? The posting includes description of company, but we need to include sections only if real content. The job title is RF Validation Intern (Summer 2027). We should not repeat job title as heading. We can include sections like About the role (maybe description of internship), Responsibilities, Requirements, Qualifications (maybe same as Requirements), Skills, Benefits, Pay, Schedule. We need to include only sections with real specific content. Let's parse content: Company description: Astranis builds advanced satellites... This is about company, not role. Could be "About the role" or maybe "About the company". But we have to use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide which sections to include. We have: - Internship description: "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, and the candidate will help contribute to design validation and measurement automation of RF hardware for new and upcoming satellite designs." That's about the role. - Responsibilities: bullet list: "Measure and validate performance of; LNAs, power amplifiers, up/down converters, filters, oscillators, etc.Write automation code to automate and speed up the above measurementsDocument test plans, measurement methodologies, and data for review" That's responsibilities. - Requirements: list: "Currently enrolled in a Bachelor's Degree program in electrical engineering, computer engineering, applied physics, or related technical fieldPassion for hardware development, including working in a fast-paced environment and hands-on design and developmentDeep knowledge of basic RF concepts, such as transmission lines, S-parameters, RF building blocks (amps/mixers/attenuators)Experience with Python and object oriented programming conceptsExperience taking RF measurements with spectrum analyzers, signal generators, network analyzers, etc.Don't meet them all? Not a problem. Please apply even if you do not meet all these criteria." - Bonus: "Antennas and Electromagnetics propagation knowledge and backgroundExperience with Software Defined Radios (SDR)Experience automating RF measurements" - Pay: "The base pay for this position is $29.00 per hour. Base Hourly Pay $29—$29 USD" - Schedule: Not explicitly given besides internship length twelve weeks, hourly role. Could infer schedule: twelve weeks, hourly. Might be considered schedule info. The posting says "Internships at Astranis typically last for twelve weeks, and are hourly roles". That's schedule info. So we can include Schedule section with that. - Benefits: Not mentioned besides maybe none. No explicit benefits. So we should not include Benefits. - Qualifications: Could be same as Requirements; but we can combine Requirements and Qualifications? The instruction: Use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include both Requirements and Qualifications if distinct. But we have Requirements list; we could treat Bonus as Qualifications? Or Skills? The "Experience with Python..." etc are skills. Could make Skills section for technical skills: Python, OOP, RF measurement equipment, etc. But we already have Requirements covering those. To avoid duplication, we can follow typical pattern: Requirements (education, experience), Skills (technical). But we must not invent content. We have content for skills: Python, OOP, RF measurement equipment, etc. Also Bonus skills: Antennas, SDR, automating RF measurements. So we could have Skills section listing those. But we need to preserve all substantive information; not invent or summarize away detail. So we need to include all details from posting. We can split into sections but ensure we don't lose any info. Let's outline: - About the role: paragraph describing internship, opportunity, contribution. - Responsibilities: ul li list: Measure and validate performance of LNAs, power amplifiers, up/down converters, filters, oscillators, etc. Write automation code to automate and speed up the above measurements. Document test plans, measurement methodologies, and data for review. - Requirements: ul li list: Currently enrolled in a Bachelor's Degree program in electrical engineering, computer engineering, applied physics, or related technical field. Passion for hardware development, including working in a fast-paced environment and hands-on design and development. Deep knowledge of basic RF concepts, such as transmission lines, S-parameters, RF building blocks (amps/mixers/attenuators). Experience with Python and object oriented programming concepts. Experience taking RF measurements with spectrum analyzers, signal generators, network analyzers, etc. (Note: "Don't meet them all? Not a problem. Please apply even if you do not meet all these criteria." This is a note; we should preserve it as prose maybe in a p tag.) - Skills: Could list: Python and OOP, RF measurement equipment (spectrum analyzers, signal generators, network analyzers), RF concepts (transmission lines, S-parameters, RF building blocks), Bonus: Antennas and Electromagnetics propagation knowledge, Software Defined Radios (SDR), Experience automating RF measurements. But note that some of these overlap with Requirements. To avoid duplication, we could treat Requirements as education/experience, and Skills as technical skills. However the posting lumps them together. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we split, we must ensure we don't lose any info and not duplicate? Duplication is not prohibited but might be redundant. Safer to keep as Requirements section only, and maybe Skills not needed. But we need to include Pay and Schedule sections. We have Pay: base pay $29 per hour. Schedule: Internships typically last for twelve weeks, hourly roles. We could also include a short paragraph about company description? Not required heading; we could put in About the role? Actually About the role could include company context? But we already have About the role paragraph about internship. Could also include company description as part of About the role? Might be okay. We must not include boilerplate like citizenship requirement? That is substantive: "U.S. Citizenship, Lawful Permanent Residency, Or Refugee/Asylee Status Required (To comply with U.S. Government space technology export regulations, applicant must be a U.S. citizen, lawful permanent resident of the United States, or other protected individual as defined by 8 U.S.C. 1324b(a)(3))". That is a requirement; we should include it in Requirements or maybe a separate note. Also EEO statement: "Our mission and products are built for everyone, regardless of gender, race, creed, or background. We believe in a diverse and inclusive workplace, and we invite all people to join our team and bring their unique perspectives to make us stronger." That's EEO boilerplate; we should remove per instruction: remove EEO/equal-opportunity boilerplate. So drop that. Also SMS terms etc are boilerplate; remove. Thus we need to include citizenship requirement. Let's compile. Sections: - About the role: paragraph(s) describing internship, opportunity, contribution. - Responsibilities: ul li. - Requirements: ul li including education, passion, deep knowledge, experience with Python/OOP, experience taking RF measurements, citizenship requirement, plus note about not meeting all criteria. - Pay: p with base pay. - Schedule: p with duration twelve weeks, hourly. We could also include Skills? Not needed if we covered in Requirements. But we have Bonus skills: Antennas and Electromagnetics propagation knowledge, SDR, Experience automating RF measurements. Those are not in Requirements; they are bonus. We could add a "Bonus Qualifications" section but not in allowed headings. Could add under Requirements as separate bullet: "Bonus: Antennas and Electromagnetics propagation knowledge and background; Experience with Software Defined Radios (SDR); Experience automating RF measurements". That preserves info. Thus Requirements section will have bullets for required and bonus. Now ensure we don't include any heading with empty content. Let's craft HTML. We'll output:

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, and the candidate will help contribute to design validation and measurement automation of RF hardware for new and upcoming satellite designs.

Responsibilities

• Measure and validate performance of LNAs, power amplifiers, up/down converters, filters, oscillators, etc.
• Write automation code to automate and speed up the above measurements.
• Document test plans, measurement methodologies, and data for review.

Requirements

• Currently enrolled in a Bachelor's Degree program in electrical engineering, computer engineering, applied physics, or related technical field.
• Passion for hardware development, including working in a fast-paced environment and hands-on design and development.
• Deep knowledge of basic RF concepts, such as transmission lines, S-parameters, RF building blocks (amps/mixers/attenuators).
• Experience with Python and object‑oriented programming concepts.
• Experience taking RF measurements with spectrum analyzers, signal generators, network analyzers, etc.
• U.S. Citizenship, Lawful Permanent Residency, or Refugee/Asylee Status required (to comply with U.S. Government space technology export regulations).
• Bonus: Antennas and Electromagnetics propagation knowledge and background; Experience with Software Defined Radios (SDR); Experience automating RF measurements.

Don't meet them all? Not a problem. Please apply even if you do not meet all these criteria.

Pay

The base pay for this position is $29.00 per hour.

Schedule

Internships typically last for twelve weeks and are hourly roles.

Check we didn't repeat job title. No extra headings. All substantive info included: company description? Not included; but we included About the role paragraph which includes internship description. The initial company description about Astranis building satellites etc is not included. Is that substantive? It's about the company, not the role. The instruction: "Preserve ALL substantive information". Does that include company overview? It's part of the posting; it's substantive. Should we include it? Possibly under About the role? But About the role heading is for role description; we could add a short paragraph about company before role description. However the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid adding other headings not in list? It says use those for section headings; likely we should only use those headings. But we could include company info in a

under About the role or maybe a separate

before any heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs outside headings. But we should follow the pattern: include sections only when posting has real content. Could we have a leading paragraph about company before any heading? That would be outside a heading; not prohibited but maybe better to include under About the role as part of role description? The company description is not exactly about the role but could be considered "About the role" context. However the instruction says "About the role" heading for section headings (e.g. About the role...). So we could put company description in a

under About the role before the internship description. That would preserve it. Thus About the role section could have two paragraphs