Supply Chain Engineering Intern - Summer 2027

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. We need to parse the posting. Key info: - About Us (maybe not needed as heading? Could be "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. We have: - About The Summer Internship Program (description). Could map to "About the role". That's appropriate. - About The Team (Supply Chain Engineering Intern description). Could also be part of role description. Might combine. - Roles and Responsibilities: list bullet points. - Basic Qualifications: list. - Preferred Skills & Experience: list. - Location: maybe not a heading; could be included in a paragraph. - Culture: maybe not needed; but could be part of "About the role"? Probably not needed as separate heading unless we have content. The instruction: include a section ONLY when posting has real, specific content for it. Culture is present but not one of the listed headings; we could ignore because not in list. We could still include if we think it's relevant but they gave examples; not required to stick strictly to those headings but they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should map content to those. We have no explicit Pay or Schedule info. There's mention of cohorts dates and onsite five days per week. That's schedule info: we have schedule (cohort dates, onsite 5 days/week). So we can include a Schedule section. Benefits: mention relocation and housing stipend. That's a benefit. So we can include Benefits. Pay: not mentioned; do not include. Qualifications: we have Basic Qualifications and Preferred Skills & Experience. Could combine into Qualifications and Skills sections. The instruction: separate Qualifications and Skills headings. So we can put Basic Qualifications under Qualifications, and Preferred Skills & Experience under Skills. Responsibilities: we have Roles and Responsibilities list. About the role: we have About The Summer Internship Program and About The Team (maybe combine). We'll put that in About the role. Location: maybe not a heading; we can include in a paragraph after About the role or as part of it. But we could also include as a short p. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, ITAR, Equal Opportunity, etc. Also remove navigation, cookie, legal, duplicated lines. We must preserve all substantive information. Let's extract substantive content: About Us: mission statement etc. Might be considered substantive but not directly about role. Could be included in About the role? Probably not needed; but it's about company. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep About Us info. Where to put? Could be a paragraph before About the role heading? There's no heading for About Us; we could just include as a

before the first heading. That's acceptable. Similarly, Culture values: substantive; we could include as a

after About the role or as its own section? Not in list but we could still include as a

. The instruction: use

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. those). Likely they expect only those headings; but we can still include paragraphs for other info. We must not include filler like "commensurate with experience". Not present. Now produce HTML. Structure:

About Us paragraph(s)

About the role

Combine About The Summer Internship Program and About The Team.

Responsibilities

• ...

Qualifications

• Basic Qualifications items

Skills

• Preferred Skills & Experience items

Benefits

• Relocation and housing stipend

Schedule

• Cohort #1 Monday, May 17 – Friday, August 13
• Cohort #2 Monday, June 14 – Friday, September 10
• All internship roles are based at our Torrance headquarters and require interns to work onsite five days per week.
• We will not be considering candidates for remote or hybrid arrangements.

Maybe also include Location paragraph after Schedule or before. We could add a

Location: Torrance, CA ...

after Schedule. We must not include any markdown fences. Let's craft the About Us paragraph: "At Antares, our long-term mission is to make clean energy abundant from Earth to the Asteroid Belt. We’re fueled by the belief that advanced nuclear energy can strengthen our military, solve the climate crisis, elevate global living standards, and expand humanity's presence in outer space. To achieve our mission, we’re building mass-producible, inherently safe, deployable microreactors that can be used terrestrially, underwater, and in space. The Antares team hails from SpaceX, the White House, the Pentagon, the Department of Energy, MIT, Rigetti Computing, General Atomics, Relativity Space, Ursa Major, and National Laboratories like Idaho, Oak Ridge, Los Alamos, and Savannah River. Antares has raised over $600M in venture capital from top-tier investors and has hundreds of million-dollars on contract with the military services, NASA, and the Department of Energy." Now About the role paragraph: combine About The Summer Internship Program and About The Team. About The Summer Internship Program: "Internships at Antares are anything but ordinary. You'll work alongside our team as we design, build, and test fission microreactors built to deliver reliable energy for critical missions on Earth, in space, and underwater. Our interns contribute to real work from day one. Depending on your role, you may touch hardware, write and test software, support manufacturing and operations, or help build the systems that allow Antares to move quickly as we scale. You'll work alongside engineers, operators, and other experts solving challenging problems—and you'll leave your internship with hands-on experience that's difficult to find anywhere else. We work hard, move quickly, and take pride in what we're building. If you're excited to learn by doing and want to contribute to the next generation of nuclear energy, we'd love to have you join us next summer. We will be running two separate cohorts to accommodate students on both semester and quarter schedules: Cohort #1 Monday, May 17 – Friday, August 13 Cohort #2 Monday, June 14 – Friday, September 10 All internship roles are based at our Torrance headquarters and require interns to work onsite five days per week. We will not be considering candidates for remote or hybrid arrangements. Interns will receive a relocation and housing stipend as part of their offer package." About The Team: "As a Supply Chain Engineering Intern, you will work alongside Antares’ Supply Chain and Engineering teams to help source the components and materials needed to build our reactor systems. You will contribute to hands-on sourcing, supplier development, and technical procurement work, gaining exposure to both the engineering requirements behind what we build, and the supply chain required to make it possible. This role is well suited for someone who is interested in the intersection of engineering and supply chain and wants hands-on experience working through technical sourcing and supplier challenges." We can combine them but avoid duplication of cohort info (already in Schedule). Might still keep in About the role but we could omit duplicate. However we need to preserve all substantive information; we can keep it but it's okay if duplicated? The instruction: remove duplicated lines. So we should avoid duplicating the cohort info in About the role if we already have Schedule section. So we can omit that part from About the role paragraph. Also the relocation stipend is benefit; we can omit from About the role. Thus About the role paragraph: combine the descriptive parts without the cohort/dates/location/stipend. Let's craft: "Internships at Antares are anything but ordinary. You'll work alongside our team as we design, build, and test fission microreactors built to deliver reliable energy for critical missions on Earth, in space, and underwater. Our interns contribute to real work from day one. Depending on your role, you may touch hardware, write and test software, support manufacturing and operations, or help build the systems that allow Antares to move quickly as we scale. You'll work alongside engineers, operators, and other experts solving challenging problems—and you'll leave your internship with hands-on experience that's difficult to find anywhere else. We work hard, move quickly, and take pride in what we're building. If you're excited to learn by doing and want to contribute to the next generation of nuclear energy, we'd love to have you join us next summer. As a Supply Chain Engineering Intern, you will work alongside Antares’ Supply Chain and Engineering teams to help source the components and materials needed to build our reactor systems. You will contribute to hands-on sourcing, supplier development, and technical procurement work, gaining exposure to both the engineering requirements behind what we build, and the supply chain required to make it possible. This role is well suited for someone who is interested in the intersection of engineering and supply chain and wants hands-on experience working through technical sourcing and supplier challenges." Now Responsibilities list: - Support sourcing activities for technical components and materials - Work with Supply Chain and Engineering teams on technical procurement activities - Support supplier development efforts - Help translate engineering needs into sourcing and procurement activities - Contribute to hands-on supply chain projects supporting Antares’ engineering work Basic Qualifications: - Enrolled in at least a bachelor’s degree program, and going into your Junior or Senior year of studies - Must have prior internship experience, or significant (>1yr) project team, laboratory, or research experience Preferred Skills & Experience: - GPA of 3.5 or above - Experience in a University club or organization, leadership role preferred - Strong interpersonal and technical communication skills (examples: leading a student project team, presenting research at conferences, etc.) - Strong analytical and problem-solving skills with attention to detail - Ability to work cross-departmentally with different groups and teams - Ability to work effectively in a dynamic environment with changing needs and requirements - Ability to work independently and in a team, take initiative, and communicate effectively Benefits: - Relocation and housing stipend Schedule: - Cohort #1 Monday, May 17 – Friday, August 13 - Cohort #2 Monday, June 14 – Friday, September 10 - All internship roles are based at our Torrance headquarters and require interns to work onsite five days per week. - We will not be considering candidates for remote or hybrid arrangements. Location paragraph: maybe after Schedule. Location: "We are located in Torrance, CA in a 322,000 square foot, brand new facility featuring large open spaces for team collaboration, R&D, and production, as well as easy access to the 405, 105, and 110 freeways. Our facility is in the heart of Los Angeles' vibrant emerging tech ecosystem alongside many other high growth startups and enterprises." Culture paragraph: maybe after Location. Culture: list values? Could be a paragraph summarizing: "At Antares, we like to specifically tie each role to our founding document’s set of values–here are the top five cultural values we think you should believe at your core to