Software Intern - Summer 2027
Antares · Los Angeles, CA · 1 mo ago
On-siteInformation TechnologyVolunteer
We need to output HTML fragment with sections: About Us, About The Summer Internship Program, About The Role, Roles and Responsibilities, Basic Qualifications, Preferred Skills & Experience, Location, Culture. Possibly also Pay/Schedule/Benefits if present. The posting mentions relocation and housing stipend (benefit). Also mentions schedule: interns work onsite five days per week, and cohort dates. So we have schedule info (cohort dates) and location. Also mention relocation and housing stipend as benefit. So we can include Benefits section with that. Pay not mentioned. So we omit Pay.
We must not repeat job title as heading. Use for section headings. Use
for section headings. 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: EEO, ITAR, etc. Also remove duplicated lines. Also remove navigation/cookie/legal. Also remove "Equal Opportunity" and "ITAR Requirements". Also remove "About Us" maybe keep as section? It's substantive. We'll keep About Us.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
We need to include sections only when posting has real specific content.
Let's extract content:
About Us: paragraph about mission, team, funding, etc.
About The Summer Internship Program: description of internships, cohorts dates, onsite five days per week, relocation and housing stipend.
About The Role: description of Software Intern role.
Roles and Responsibilities: list bullet points.
Basic Qualifications: list bullet points? It's two items: 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. Could be list.
Preferred Skills & Experience: list bullet points.
Location: paragraph about Torrance facility.
Culture: list of five cultural values with descriptions.
Benefits: relocation and housing stipend (maybe also mention stipend as part of offer package). Could be Benefits section.
Schedule: cohort dates and five days per week onsite. Could be Schedule section.
We must not create Pay section.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must output only HTML fragment.
Let's craft.
Structure:
About Us
...
About the Summer Internship Program
...
Maybe include schedule as separate Schedule
with list of cohort dates and onsite requirement. But we could embed schedule in About The Summer Internship Program. However instruction: prefer few substantive sections over many thin ones. Could combine schedule and benefits into About The Summer Internship Program. But we also have Benefits separate maybe.
We need to decide: The posting includes schedule specifics (cohort dates, five days per week). That's substantive. Could be its own Schedule section. Benefits: relocation and housing stipend. Could be Benefits section.
Let's create sections: About Us, About the Summer Internship Program, About the Role, Roles and Responsibilities, Basic Qualifications, Preferred Skills & Experience, Location, Culture, Benefits, Schedule.
Check if any section would be empty or filler: all have content.
Now extract precise text.
About Us: "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."
We'll keep that as paragraph.
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."
We could split schedule and benefits later, but we can keep all here and then create separate sections for schedule and benefits to avoid duplication. But we must not duplicate content. If we create separate sections, we need to extract those specifics.
Better: Keep About the Summer Internship Program as general description, then create Schedule section with cohort dates and onsite requirement, Benefits section with relocation and housing stipend. Ensure we don't repeat same sentences.
Let's extract schedule specifics: "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."
Benefits: "Interns will receive a relocation and housing stipend as part of their offer package."
Now About the Summer Internship Program paragraph without those specifics: "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."
That seems fine.
About The Role: "As a Software Intern, you will work on the infrastructure and tooling that enables Antares teams to deploy, monitor, and operate internal applications and compute workloads. You will own substantive projects spanning cloud deployment tooling, systems automation, observability, data project infrastructure, and cluster operations. You will work across both cloud and on-premises infrastructure, improving how applications and data projects are deployed and monitored while helping make internal compute resources more reliable, recoverable, and efficient. This role is well suited for someone who enjoys building practical tools, automating manual processes, and improving the systems other technical teams rely on."
Roles and Responsibilities: list bullet points:
- Improve cloud deployment tooling for shared internal applications
- Automate integrations between internal and external systems
- Create Grafana dashboards and alerts to improve visibility into internal systems
- Build standardized templates for Python data projects that improve deployment, monitoring, and dependency management
- Document quality processes so they can be consistently used by non-software developers
- Migrate cluster infrastructure to the latest versions of Rocky Linux and Warewulf
- Build storage tooling to improve recovery and performance
- Analyze and optimize cloud costs for internal job pipelines
- Create dashboards that provide visibility into cluster usage
- Build tooling to help teams better understand and optimize their use of shared compute resources
Basic Qualifications: list:
- 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: list:
- 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
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: list of five cultural values with descriptions. The text:
"Think in Systems - Energy and Defense are complex ecosystems with numerous stakeholders with competing priorities, conflicting policies, perverse incentives, and emergent and path-dependent properties. First principles thinking alone is insufficient. Think probabilistically and then take action. “If you want to be certain, then you are apt to be obsolete.” Over-optimizing the components often degrades the system"
"Obsess over the End User - The customer and end user are often not the same. We will never build globally competitive commercial products if we lose sight of our end users and their entire interaction with the product life cycle"
"Be Unconstrained by Convention - Our only limits are the laws of physics. Many, even experts, will say what we are working on is impossible. They said the same about SpaceX reusing rockets. Generationally impactful companies, by definition, must accomplish the seemingly impossible. If it were easy, it would have already been done. Never shy away from a solution because it has never been tried before, and never choose to do something because that's “how it's always been done”"
"Go Where the Work Is - Never miss a chance to meet a customer, user, or stakeholder face to face, even if that means hopping on a plane. If you can’t make it, find a teammate who can channel your intentions and go in your place. Deep work can be done from anywhere, but we believe teams are built in person, and aim to maximize our time together"
"Operate in the Grey - Embrace nuance in pursuit of truth. Question every fundamental assumption"
We'll format each as - with the value bold? Not required. Just put as list items.
Benefits: "Interns will receive a relocation and housing stipend as part of their offer package."
Schedule: list cohort dates and onsite requirement.
We could present as
- Cohort #1: Monday, May 17 – Friday, August 13
- Cohort #2: Monday, June 14 – Friday, September 10
- All internships are onsite five days per week at the Torrance headquarters; remote
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, ITAR, etc. Also remove duplicated lines. Also remove navigation/cookie/legal. Also remove "Equal Opportunity" and "ITAR Requirements". Also remove "About Us" maybe keep as section? It's substantive. We'll keep About Us. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. We need to include sections only when posting has real specific content. Let's extract content: About Us: paragraph about mission, team, funding, etc. About The Summer Internship Program: description of internships, cohorts dates, onsite five days per week, relocation and housing stipend. About The Role: description of Software Intern role. Roles and Responsibilities: list bullet points. Basic Qualifications: list bullet points? It's two items: 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. Could be list. Preferred Skills & Experience: list bullet points. Location: paragraph about Torrance facility. Culture: list of five cultural values with descriptions. Benefits: relocation and housing stipend (maybe also mention stipend as part of offer package). Could be Benefits section. Schedule: cohort dates and five days per week onsite. Could be Schedule section. We must not create Pay section. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must output only HTML fragment. Let's craft. Structure:
About Us
...
About the Summer Internship Program
...
Maybe include schedule as separateSchedule
with list of cohort dates and onsite requirement. But we could embed schedule in About The Summer Internship Program. However instruction: prefer few substantive sections over many thin ones. Could combine schedule and benefits into About The Summer Internship Program. But we also have Benefits separate maybe. We need to decide: The posting includes schedule specifics (cohort dates, five days per week). That's substantive. Could be its own Schedule section. Benefits: relocation and housing stipend. Could be Benefits section. Let's create sections: About Us, About the Summer Internship Program, About the Role, Roles and Responsibilities, Basic Qualifications, Preferred Skills & Experience, Location, Culture, Benefits, Schedule. Check if any section would be empty or filler: all have content. Now extract precise text. About Us: "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." We'll keep that as paragraph. 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." We could split schedule and benefits later, but we can keep all here and then create separate sections for schedule and benefits to avoid duplication. But we must not duplicate content. If we create separate sections, we need to extract those specifics. Better: Keep About the Summer Internship Program as general description, then create Schedule section with cohort dates and onsite requirement, Benefits section with relocation and housing stipend. Ensure we don't repeat same sentences. Let's extract schedule specifics: "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." Benefits: "Interns will receive a relocation and housing stipend as part of their offer package." Now About the Summer Internship Program paragraph without those specifics: "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." That seems fine. About The Role: "As a Software Intern, you will work on the infrastructure and tooling that enables Antares teams to deploy, monitor, and operate internal applications and compute workloads. You will own substantive projects spanning cloud deployment tooling, systems automation, observability, data project infrastructure, and cluster operations. You will work across both cloud and on-premises infrastructure, improving how applications and data projects are deployed and monitored while helping make internal compute resources more reliable, recoverable, and efficient. This role is well suited for someone who enjoys building practical tools, automating manual processes, and improving the systems other technical teams rely on." Roles and Responsibilities: list bullet points: - Improve cloud deployment tooling for shared internal applications - Automate integrations between internal and external systems - Create Grafana dashboards and alerts to improve visibility into internal systems - Build standardized templates for Python data projects that improve deployment, monitoring, and dependency management - Document quality processes so they can be consistently used by non-software developers - Migrate cluster infrastructure to the latest versions of Rocky Linux and Warewulf - Build storage tooling to improve recovery and performance - Analyze and optimize cloud costs for internal job pipelines - Create dashboards that provide visibility into cluster usage - Build tooling to help teams better understand and optimize their use of shared compute resources Basic Qualifications: list: - 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: list: - 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 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: list of five cultural values with descriptions. The text: "Think in Systems - Energy and Defense are complex ecosystems with numerous stakeholders with competing priorities, conflicting policies, perverse incentives, and emergent and path-dependent properties. First principles thinking alone is insufficient. Think probabilistically and then take action. “If you want to be certain, then you are apt to be obsolete.” Over-optimizing the components often degrades the system" "Obsess over the End User - The customer and end user are often not the same. We will never build globally competitive commercial products if we lose sight of our end users and their entire interaction with the product life cycle" "Be Unconstrained by Convention - Our only limits are the laws of physics. Many, even experts, will say what we are working on is impossible. They said the same about SpaceX reusing rockets. Generationally impactful companies, by definition, must accomplish the seemingly impossible. If it were easy, it would have already been done. Never shy away from a solution because it has never been tried before, and never choose to do something because that's “how it's always been done”" "Go Where the Work Is - Never miss a chance to meet a customer, user, or stakeholder face to face, even if that means hopping on a plane. If you can’t make it, find a teammate who can channel your intentions and go in your place. Deep work can be done from anywhere, but we believe teams are built in person, and aim to maximize our time together" "Operate in the Grey - Embrace nuance in pursuit of truth. Question every fundamental assumption" We'll format each as- Cohort #1: Monday, May 17 – Friday, August 13
- Cohort #2: Monday, June 14 – Friday, September 10
- All internships are onsite five days per week at the Torrance headquarters; remote