Winter 2027 Supply Chain Analyst Co-op
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to include sections only when posting has real specific content. Let's parse.
Content:
- Intro about Anduril mission etc. Could be "About the role" or maybe "About the company". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present.
We have description: "The co-op position will support the Supply Chain group in strategic planning, long term supplier selection and negotiations. This position requires the ability to work with procurement, engineering, finance and legal teams and third parties such as suppliers. The position requires interest in industry dynamics, business negotiation and pricing, manufacturing processes, and risk mitigation."
That's more like responsibilities? Could be "Responsibilities".
Then "What You’ll Do" list: bullet points (Designing and implementing systems..., Analyzing..., Testing..., Documenting..., Liaising..., Ensuring compliance..., Providing training..., Perform financial research..., Effectively work with..., Understand trade-offs..., Improve supply chain performance..., Collaborate..., Present ideas..., Develop standards...). That's responsibilities.
Then "Required Qualifications": bullet list: Must be pursuing a bachelor’s or master’s degree..., Must be returning to school..., Must be a U.S. Person..., Ability to complete an in-person 16 to 24-week internship...
Then "Preferred Qualifications": list of technical skills.
Then "US Hourly Range $24—$40 USD". That's Pay.
Then "Benefits": description about salary range, equity grants, benefits.
Then there is no explicit Schedule section; maybe we can infer schedule from internship length? Not explicit schedule like full-time/part-time. The posting mentions "Ability to complete an in-person 16 to 24-week internship". That's duration, not schedule. No explicit schedule like "Full-time, 40 hrs/week". So we should not create Schedule section unless posting actually states them. So omit Schedule.
We also have "About the role" maybe we can include a short paragraph summarizing the role from intro. The intro about Anduril mission could be considered "About the role" or "About the company". The instruction says use heading for section headings (e.g. About the role, Responsibilities...). We need to include sections only when posting has real specific content. The intro about Anduril mission is generic company description, not specific to role. But we could still put under "About the role" a paragraph describing the role: "The co-op position will support the Supply Chain group..." That is specific. So we can put that as About the role.
Thus sections:
- About the role: paragraph(s) describing role.
- Responsibilities: list from "What You’ll Do".
- Requirements: maybe combine Required Qualifications? The instruction includes Requirements and Qualifications as separate headings. We have Required Qualifications and Preferred Qualifications. Could map Required Qualifications to "Requirements" and Preferred Qualifications to "Skills" or "Qualifications". But we have both Requirements and Qualifications headings. We need to decide.
We have Required Qualifications (must be pursuing degree, returning to school, US Person, ability to complete internship). Those are requirements. Then Preferred Qualifications (technical skills). Those could be Skills.
Thus:
- Requirements: list of required qualifications.
- Skills: list of preferred qualifications (technical skills).
- Qualifications: maybe we could combine? But we already used Requirements and Skills. The instruction gave examples; we can omit Qualifications if not needed. But we have both Required and Preferred; we could treat Required as Requirements, Preferred as Qualifications. However they also have Skills heading. Which is more appropriate? The preferred qualifications are technical skills, so Skills heading fits. Then we could omit Qualifications heading. Or we could treat Required as Requirements, Preferred as Qualifications, and not have Skills. But we have technical skills list; better to put under Skills.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
Check if we need to include Pay: yes we have US Hourly Range $24—$40 USD. So Pay section.
Benefits: we have description about salary range, equity grants, benefits. So Benefits section.
Now we need to format lists with - . For prose use
.
We must not repeat job title as heading. No Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out the scam warning, data privacy, etc. Also remove the "Explore Our Benefits" link etc. Keep only substantive info.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details: e.g., "US Hourly Range $24—$40 USD". Keep that exactly.
For Benefits: we have paragraph: "The salary range for this role is an estimate based on a wide range of compensation factors, inclusive of base salary only. Actual salary offer may vary based on (but not limited to) work experience, education and/or training, critical skills, and/or business considerations. Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package. Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next. For more information, Explore Our Benefits."
We need to keep that but remove the link "Explore Our Benefits" maybe as it's application instruction? It's a link for more info; could be considered boilerplate? It's not a legal/EEO but it's a call to action. Might be considered application instruction? The instruction says remove application instructions. This is a link to benefits; maybe it's okay to keep? It's not an instruction to apply. It's just a reference. Safer to keep the sentence but maybe drop the link text? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "For more information, Explore Our Benefits." is like a call to action; could be considered navigation. I'd remove that sentence entirely? But we need to preserve substantive information; the substantive part is about benefits description. The "For more information, Explore Our Benefits." is not substantive; it's a navigation. So we can drop that sentence.
Thus Benefits paragraph: "The salary range for this role is an estimate based on a wide range of compensation factors, inclusive of base salary only. Actual salary offer may vary based on (but not limited to) work experience, education and/or training, critical skills, and/or business considerations. Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package. Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next."
We need to keep the colon after "including:" then the sentence.
Now About the role: we can combine the introductory paragraph about Anduril mission? Might be considered company description not role-specific. But we can include a short paragraph: "Anduril Industries is a defense technology company with a mission to transform U.S. and allied military capabilities with advanced technology. By bringing the expertise, technology, and business model of the 21st century’s most innovative companies to the defense industry, Anduril is changing how military systems are designed, built and sold. Anduril’s family of systems is powered by Lattice OS, an AI-powered operating system that turns thousands of data streams into a realtime, 3D command and control center. As the world enters an era of strategic competition, Anduril is committed to bringing cutting-edge autonomy, AI, computer vision, sensor fusion, and networking technology to the military in months, not years." That's generic but maybe considered substantive about the company. The instruction says we should not repeat job title as heading, but we can include company description. It's not boilerplate; it's substantive about the role context. I'd keep it.
Then the specific role description: "The co-op position will support the Supply Chain group in strategic planning, long term supplier selection and negotiations. This position requires the ability to work with procurement, engineering, finance and legal teams and third parties such as suppliers. The position requires interest in industry dynamics, business negotiation and pricing, manufacturing processes, and risk mitigation."
We can combine into About the role section.
Now Responsibilities: list from "What You’ll Do". We need to preserve each bullet exactly.
List:
- Designing and implementing systems to meet business needs.
- Analyzing and understanding business requirements and processes
- Testing and troubleshooting new tools to be created that meets user requirements
- Documenting system functionality and maintaining user guides
- Liaising between business stakeholders and IT personnel
- Ensuring compliance with industry standards and security regulations.
- Providing training and support to system users.
- Perform financial research on suppliers, spend analysis and ad-hoc financial analysis for strategic deals
- Effectively work with identify industry/category optimal terms for sourcing on upcoming projects.
- Understand the trade-offs between cost, volume, and quality to close agreements that meet program criteria and secure long-term supply continuity
- Improve supply chain performance through cost and capacity scenario analysis, and supplier benchmarking
- Collaborate with cross-functional teams
- Present ideas, project details, and status to business leadership
- Develop standards, processes, and documentation as necessary to ensure continued success and transferability after project completion
Note some bullets have lowercase start; we keep as is.
Now Requirements: list from Required Qualifications:
- Must be pursuing a bachelor’s or master’s degree in Supply Chain Management, Business Analytics, Information Technology & Systems Architecture, Software Engineering, Computer Science, or a related field.
- Must be returning to school at the end of the internship to continue academic studies for at least one quarter or semester.
- Must be a U.S. Person due to required access to U.S. export-controlled information or facilities; U.S. clearance eligibility may be required depending on program.
- Ability to complete an in-person 16 to 24-week internship in one of our offices in winter 2027.
Now Skills: list from Preferred Qualifications:
- C++, Python, JavaScript (React & Angular), Microsoft Excel, Spark, PySpark, SQL (T-SQL Postgres), Enterprise Data Systems like Palantir Foundry a plus.
- Preferred but not limited to AWS, Azure, or GCP security ecosystem, containerization, and associated tooling.
- Connecting external APIs, and knowledge of data & visualization tools, such as Tableau.
We need to keep exactly as written.
Now Pay: section with "US Hourly Range $24—$40 USD". Note the dash is an em dash? We'll keep as given.
Now Benefits: paragraph as above.
Now we need to output only HTML fragment, no /, no markdown.
Thus:
About the role
...
Responsibilities
- ...
...
Requirements
...
Skills
...
Benefits
...
Pay
US Hourly Range $24—$40 USD
Make sure to not include extra whitespace? It's fine.
Check for any duplicated lines: we removed scam warning etc.
Check for any placeholders like "commensurate with experience": none.
Now
. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out the scam warning, data privacy, etc. Also remove the "Explore Our Benefits" link etc. Keep only substantive info. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details: e.g., "US Hourly Range $24—$40 USD". Keep that exactly. For Benefits: we have paragraph: "The salary range for this role is an estimate based on a wide range of compensation factors, inclusive of base salary only. Actual salary offer may vary based on (but not limited to) work experience, education and/or training, critical skills, and/or business considerations. Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package. Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next. For more information, Explore Our Benefits." We need to keep that but remove the link "Explore Our Benefits" maybe as it's application instruction? It's a link for more info; could be considered boilerplate? It's not a legal/EEO but it's a call to action. Might be considered application instruction? The instruction says remove application instructions. This is a link to benefits; maybe it's okay to keep? It's not an instruction to apply. It's just a reference. Safer to keep the sentence but maybe drop the link text? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "For more information, Explore Our Benefits." is like a call to action; could be considered navigation. I'd remove that sentence entirely? But we need to preserve substantive information; the substantive part is about benefits description. The "For more information, Explore Our Benefits." is not substantive; it's a navigation. So we can drop that sentence. Thus Benefits paragraph: "The salary range for this role is an estimate based on a wide range of compensation factors, inclusive of base salary only. Actual salary offer may vary based on (but not limited to) work experience, education and/or training, critical skills, and/or business considerations. Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package. Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next." We need to keep the colon after "including:" then the sentence. Now About the role: we can combine the introductory paragraph about Anduril mission? Might be considered company description not role-specific. But we can include a short paragraph: "Anduril Industries is a defense technology company with a mission to transform U.S. and allied military capabilities with advanced technology. By bringing the expertise, technology, and business model of the 21st century’s most innovative companies to the defense industry, Anduril is changing how military systems are designed, built and sold. Anduril’s family of systems is powered by Lattice OS, an AI-powered operating system that turns thousands of data streams into a realtime, 3D command and control center. As the world enters an era of strategic competition, Anduril is committed to bringing cutting-edge autonomy, AI, computer vision, sensor fusion, and networking technology to the military in months, not years." That's generic but maybe considered substantive about the company. The instruction says we should not repeat job title as heading, but we can include company description. It's not boilerplate; it's substantive about the role context. I'd keep it. Then the specific role description: "The co-op position will support the Supply Chain group in strategic planning, long term supplier selection and negotiations. This position requires the ability to work with procurement, engineering, finance and legal teams and third parties such as suppliers. The position requires interest in industry dynamics, business negotiation and pricing, manufacturing processes, and risk mitigation." We can combine into About the role section. Now Responsibilities: list from "What You’ll Do". We need to preserve each bullet exactly. List: - Designing and implementing systems to meet business needs. - Analyzing and understanding business requirements and processes - Testing and troubleshooting new tools to be created that meets user requirements - Documenting system functionality and maintaining user guides - Liaising between business stakeholders and IT personnel - Ensuring compliance with industry standards and security regulations. - Providing training and support to system users. - Perform financial research on suppliers, spend analysis and ad-hoc financial analysis for strategic deals - Effectively work with identify industry/category optimal terms for sourcing on upcoming projects. - Understand the trade-offs between cost, volume, and quality to close agreements that meet program criteria and secure long-term supply continuity - Improve supply chain performance through cost and capacity scenario analysis, and supplier benchmarking - Collaborate with cross-functional teams - Present ideas, project details, and status to business leadership - Develop standards, processes, and documentation as necessary to ensure continued success and transferability after project completion Note some bullets have lowercase start; we keep as is. Now Requirements: list from Required Qualifications: - Must be pursuing a bachelor’s or master’s degree in Supply Chain Management, Business Analytics, Information Technology & Systems Architecture, Software Engineering, Computer Science, or a related field. - Must be returning to school at the end of the internship to continue academic studies for at least one quarter or semester. - Must be a U.S. Person due to required access to U.S. export-controlled information or facilities; U.S. clearance eligibility may be required depending on program. - Ability to complete an in-person 16 to 24-week internship in one of our offices in winter 2027. Now Skills: list from Preferred Qualifications: - C++, Python, JavaScript (React & Angular), Microsoft Excel, Spark, PySpark, SQL (T-SQL Postgres), Enterprise Data Systems like Palantir Foundry a plus. - Preferred but not limited to AWS, Azure, or GCP security ecosystem, containerization, and associated tooling. - Connecting external APIs, and knowledge of data & visualization tools, such as Tableau. We need to keep exactly as written. Now Pay: section with "US Hourly Range $24—$40 USD". Note the dash is an em dash? We'll keep as given. Now Benefits: paragraph as above. Now we need to output only HTML fragment, no /, no markdown. Thus:
About the role
...
Responsibilities
- ... ...
Requirements
-
...
Skills
-
...
Benefits
...
Pay
US Hourly Range $24—$40 USD
Make sure to not include extra whitespace? It's fine. Check for any duplicated lines: we removed scam warning etc. Check for any placeholders like "commensurate with experience": none. Now