Co-op - Software Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive info; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Content:
- Who We Are: description of Symbotic, AI-powered robotic tech platform, etc. Also includes "Timeframe{{:}} Spring (Jan-May 2027)". That's a timeframe. Should we include as a section? Possibly "Timeframe" could be a heading? Not in list of allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can only use those headings. So we need to map content to those sections.
We have "About The Opportunities" which describes software engineering function and intern opportunities. That could be "About the role". Also "What You’ll Do" is responsibilities. "What You’ll Need" is requirements/qualifications/skills. "Our Environment" includes travel, driver's license, credit card, etc. That could be maybe "Requirements" or "Qualifications". Also "About Symbotic" is company description, maybe part of "About the role". There's also compensation: "The base range for this position in the posted location is $32.00 - $44.00 however, base pay offered may vary depending on job-related knowledge, skills, and experience. The compensation package includes medical, dental, vision, disability, 401K, PTO and/or other benefits." That's pay and benefits. So we need Pay and Benefits sections.
Schedule: Not mentioned. No schedule info. So we should not create Schedule section.
We also have "Timeframe" (Spring Jan-May 2027). That's not schedule but maybe could be considered schedule? It's a timeframe of internship. Could be considered schedule? The instruction says only create Schedule section if posting actually states them. It does state timeframe, but not typical schedule like hours per week. However "Timeframe" could be considered schedule? Might be okay to include as Schedule? But they said "Schedule" heading for schedule info. The posting includes "Timeframe{{:}} Spring (Jan-May 2027)". That's a time period. Could be considered schedule. I'd include it under Schedule as it's specific. But we need to avoid filler like "varies". It's specific.
We also have "Symbotic offers transportation and housing benefits for students who meet our relocation requirements." That's a benefit.
Also "Interns and Co-ops are supported through mentorship, professional development, networking opportunities, and a robust calendar of events designed to help them build community and grow their careers." That's also benefits.
Thus Benefits section can include those.
Now we need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can combine some to avoid thin sections. For example, we could have About the role (company description + opportunity description). Responsibilities (What You’ll Do). Requirements (What You’ll Need). Skills maybe separate but could be part of Requirements. But we can keep Skills separate if we have specific skill list. The posting lists many skills: object-oriented programming in C#, Python, C++; experience with Linux, git, testing frameworks, CI/CD (Jenkins); enjoys learning new tech; experience with Vitis and Vivaldo is a plus; containerized development (Kubernetes, Docker) plus; experience with cross platform .NET core development plus; experience with MS SQL and SQL language plus. That's skills. Could be separate Skills section.
Qualifications: degree pursuing Computer Science or related discipline. That's qualification.
Requirements: maybe also include travel, driver's license, credit card, etc. Could be part of Requirements.
We need to avoid duplication.
Let's extract substantive content:
Who We Are: description of Symbotic (AI-powered robotic tech platform, intelligent software orchestrates advanced robots, high-density end-to-end system, reinventing warehouse automation, increased efficiency, speed, flexibility). Also "Timeframe{{:}} Spring (Jan-May 2027)". Also "At Symbotic, Early Career talent plays a meaningful role..." etc. That's about internship program.
About The Opportunities: description of Software Engineering function and intern opportunities: front-end, back-end, embedded, test automation.
What You’ll Do: list of responsibilities.
What You’ll Need: list of requirements/qualifications/skills.
Our Environment: travel up to 10%, driver's license, ability to drive/fly, owning credit card managing expenses.
About Symbotic: more company description.
Compensation: base range $32-$44, compensation package includes medical, dental, vision, disability, 401K, PTO and/or other benefits.
Also transportation and housing benefits for relocation.
Mentorship, professional development, networking, calendar of events.
EEO boilerplate to remove.
Now we need to output HTML fragment with headings
and content.
We must not include boilerplate like EEO, equal opportunity, etc.
We must not include navigation, cookie, legal, scam-warning, duplicated lines.
We must not repeat job title as heading (none given). No Job ID.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay (base range) and Benefits (medical etc, transportation/housing, mentorship). Schedule: we have Timeframe (Spring Jan-May 2027). That's a schedule? Could be considered schedule. We'll include Schedule section with that timeframe.
Now we need to decide which sections to include. We'll include:
- About the role (combining Who We Are, About The Opportunities, About Symbotic maybe)
- Responsibilities (What You’ll Do)
- Requirements (What You’ll Need - maybe split into Requirements and Skills)
- Qualifications (degree pursuing)
- Skills (technical skills list)
- Benefits (transportation/housing, mentorship/professional dev/networking/calendar, medical/dental/vision etc)
- Pay (base range)
- Schedule (Timeframe)
We need to avoid thin sections: each should have substantive content.
Let's extract content for each.
About the role: Should include description of Symbotic and the internship program. Combine:
"Symbotic is changing the way consumer goods move through the supply chain with its AI-powered robotic technology platform. Intelligent software orchestrates advanced robots in a high-density, end-to-end system, reinventing warehouse automation for increased efficiency, speed, and flexibility. At Symbotic, Early Career talent plays a meaningful role in helping us reimagine the future of supply chain automation. Through our Internship and Co-op programs, students have the opportunity to contribute to real projects, collaborate with experienced engineers and business leaders, and gain hands-on exposure to the technologies powering our end-to-end robotics and automation solutions. We are looking for curious, motivated students who are excited to solve complex problems, bring new perspectives to cross-functional teams, and see their work make an impact in a fast-moving, innovative environment. Along the way, Interns and Co-ops are supported through mentorship, professional development, networking opportunities, and a robust calendar of events designed to help them build community and grow their careers. Symbotic offers transportation and housing benefits for students who meet our relocation requirements."
But note that transportation/housing benefits and mentorship etc are benefits; maybe we should move those to Benefits section. However About the role can still include general description; we can keep mention of mentorship etc but maybe better to avoid duplication. We'll keep About the role focusing on company description and opportunity overview, not specific benefits.
Thus About the role: "Symbotic is changing the way consumer goods move through the supply chain with its AI-powered robotic technology platform. Intelligent software orchestrates advanced robots in a high-density, end-to-end system, reinventing warehouse automation for increased efficiency, speed, and flexibility. At Symbotic, Early Career talent plays a meaningful role in helping us reimagine the future of supply chain automation. Through our Internship and Co-op programs, students have the opportunity to contribute to real projects, collaborate with experienced engineers and business leaders, and gain hands-on exposure to the technologies powering our end-to-end robotics and automation solutions. We are looking for curious, motivated students who are excited to solve complex problems, bring new perspectives to cross-functional teams, and see their work make an impact in a fast-moving, innovative environment."
That seems good.
Responsibilities: list from "What You’ll Do". Let's extract each bullet:
- Play a hands-on role as part of an engineering team that works to design, develop, review and test new functionalities.
- Collaborate with others on an agile/scrum team to build features based on new business requirements.
- Evolve the current software architecture toward microservices using .NET Core, Kubernetes, RabbitMQ and Redis.
- Contribute to a distributed architecture built on .NET using multi-threaded and multi-processor concepts.
- Create visualizations to extract understanding of current state from logs.
- Develop high quality code and packages following software engineering best practices.
- Participate in customer facing calls, visits and workshops to educate and support customers on the integration requirements between Symbotic and customer systems.
- Work with our customer's technical resources to test Symbotic integrations with their systems.
We'll put each as
- inside
.
Requirements: maybe include "What You’ll Need" items that are mandatory (not plus). Let's parse:
What You’ll Need:
- Currently pursuing a degree in Computer Science or related discipline.
- Strong object-oriented programming skills in C#, Python and C++.
- Experience with Linux and its commands.
- Experience with source control (git), software testing frameworks, and CI/CD pipelines (Jenkins).
- Enjoys learning new technologies, skills, and techniques as well as teaching them to others.
- Experience with Vitis and Vivaldo is a plus.
- Containerized development (Kubernetes, Docker, etc.) is a plus.
- Experience with cross platform .NET core development is a plus.
- Experience with MS SQL and the SQL language is a plus.
Thus mandatory: degree pursuing, OOP skills in C#, Python, C++, Linux experience, experience with git, testing frameworks, CI/CD (Jenkins), enjoys learning/teaching. The plus items are optional; we could still list them under Skills maybe.
Thus Requirements section could contain the mandatory items.
Qualifications: maybe the degree pursuing is qualification; but we already have that in Requirements. Could separate: Qualifications: degree pursuing Computer Science or related discipline. Requirements: technical skills etc. But we need to avoid duplication.
Better: Qualifications: degree pursuing. Requirements: OOP skills, Linux, git, testing, CI/CD, enjoys learning/teaching. Skills: plus items (Vitis/Vivaldo, containerized dev, .NET core, MS SQL). Benefits: transportation/housing, mentorship/professional dev/networking/calendar, medical/dental/vision/disability/401K/PTO. Pay: base range $32-$44. Schedule: Timeframe Spring (Jan-May 2027).
We also have "Our Environment" with travel up to 10%, driver's license, ability to drive/fly, owning credit card managing expenses. That could be part of Requirements or maybe a separate section like "Requirements" includes those. Since we already
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive info; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - Who We Are: description of Symbotic, AI-powered robotic tech platform, etc. Also includes "Timeframe{{:}} Spring (Jan-May 2027)". That's a timeframe. Should we include as a section? Possibly "Timeframe" could be a heading? Not in list of allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can only use those headings. So we need to map content to those sections. We have "About The Opportunities" which describes software engineering function and intern opportunities. That could be "About the role". Also "What You’ll Do" is responsibilities. "What You’ll Need" is requirements/qualifications/skills. "Our Environment" includes travel, driver's license, credit card, etc. That could be maybe "Requirements" or "Qualifications". Also "About Symbotic" is company description, maybe part of "About the role". There's also compensation: "The base range for this position in the posted location is $32.00 - $44.00 however, base pay offered may vary depending on job-related knowledge, skills, and experience. The compensation package includes medical, dental, vision, disability, 401K, PTO and/or other benefits." That's pay and benefits. So we need Pay and Benefits sections. Schedule: Not mentioned. No schedule info. So we should not create Schedule section. We also have "Timeframe" (Spring Jan-May 2027). That's not schedule but maybe could be considered schedule? It's a timeframe of internship. Could be considered schedule? The instruction says only create Schedule section if posting actually states them. It does state timeframe, but not typical schedule like hours per week. However "Timeframe" could be considered schedule? Might be okay to include as Schedule? But they said "Schedule" heading for schedule info. The posting includes "Timeframe{{:}} Spring (Jan-May 2027)". That's a time period. Could be considered schedule. I'd include it under Schedule as it's specific. But we need to avoid filler like "varies". It's specific. We also have "Symbotic offers transportation and housing benefits for students who meet our relocation requirements." That's a benefit. Also "Interns and Co-ops are supported through mentorship, professional development, networking opportunities, and a robust calendar of events designed to help them build community and grow their careers." That's also benefits. Thus Benefits section can include those. Now we need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some to avoid thin sections. For example, we could have About the role (company description + opportunity description). Responsibilities (What You’ll Do). Requirements (What You’ll Need). Skills maybe separate but could be part of Requirements. But we can keep Skills separate if we have specific skill list. The posting lists many skills: object-oriented programming in C#, Python, C++; experience with Linux, git, testing frameworks, CI/CD (Jenkins); enjoys learning new tech; experience with Vitis and Vivaldo is a plus; containerized development (Kubernetes, Docker) plus; experience with cross platform .NET core development plus; experience with MS SQL and SQL language plus. That's skills. Could be separate Skills section. Qualifications: degree pursuing Computer Science or related discipline. That's qualification. Requirements: maybe also include travel, driver's license, credit card, etc. Could be part of Requirements. We need to avoid duplication. Let's extract substantive content: Who We Are: description of Symbotic (AI-powered robotic tech platform, intelligent software orchestrates advanced robots, high-density end-to-end system, reinventing warehouse automation, increased efficiency, speed, flexibility). Also "Timeframe{{:}} Spring (Jan-May 2027)". Also "At Symbotic, Early Career talent plays a meaningful role..." etc. That's about internship program. About The Opportunities: description of Software Engineering function and intern opportunities: front-end, back-end, embedded, test automation. What You’ll Do: list of responsibilities. What You’ll Need: list of requirements/qualifications/skills. Our Environment: travel up to 10%, driver's license, ability to drive/fly, owning credit card managing expenses. About Symbotic: more company description. Compensation: base range $32-$44, compensation package includes medical, dental, vision, disability, 401K, PTO and/or other benefits. Also transportation and housing benefits for relocation. Mentorship, professional development, networking, calendar of events. EEO boilerplate to remove. Now we need to output HTML fragment with headings
and content. We must not include boilerplate like EEO, equal opportunity, etc. We must not include navigation, cookie, legal, scam-warning, duplicated lines. We must not repeat job title as heading (none given). No Job ID. We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay (base range) and Benefits (medical etc, transportation/housing, mentorship). Schedule: we have Timeframe (Spring Jan-May 2027). That's a schedule? Could be considered schedule. We'll include Schedule section with that timeframe. Now we need to decide which sections to include. We'll include: - About the role (combining Who We Are, About The Opportunities, About Symbotic maybe) - Responsibilities (What You’ll Do) - Requirements (What You’ll Need - maybe split into Requirements and Skills) - Qualifications (degree pursuing) - Skills (technical skills list) - Benefits (transportation/housing, mentorship/professional dev/networking/calendar, medical/dental/vision etc) - Pay (base range) - Schedule (Timeframe) We need to avoid thin sections: each should have substantive content. Let's extract content for each. About the role: Should include description of Symbotic and the internship program. Combine: "Symbotic is changing the way consumer goods move through the supply chain with its AI-powered robotic technology platform. Intelligent software orchestrates advanced robots in a high-density, end-to-end system, reinventing warehouse automation for increased efficiency, speed, and flexibility. At Symbotic, Early Career talent plays a meaningful role in helping us reimagine the future of supply chain automation. Through our Internship and Co-op programs, students have the opportunity to contribute to real projects, collaborate with experienced engineers and business leaders, and gain hands-on exposure to the technologies powering our end-to-end robotics and automation solutions. We are looking for curious, motivated students who are excited to solve complex problems, bring new perspectives to cross-functional teams, and see their work make an impact in a fast-moving, innovative environment. Along the way, Interns and Co-ops are supported through mentorship, professional development, networking opportunities, and a robust calendar of events designed to help them build community and grow their careers. Symbotic offers transportation and housing benefits for students who meet our relocation requirements." But note that transportation/housing benefits and mentorship etc are benefits; maybe we should move those to Benefits section. However About the role can still include general description; we can keep mention of mentorship etc but maybe better to avoid duplication. We'll keep About the role focusing on company description and opportunity overview, not specific benefits. Thus About the role: "Symbotic is changing the way consumer goods move through the supply chain with its AI-powered robotic technology platform. Intelligent software orchestrates advanced robots in a high-density, end-to-end system, reinventing warehouse automation for increased efficiency, speed, and flexibility. At Symbotic, Early Career talent plays a meaningful role in helping us reimagine the future of supply chain automation. Through our Internship and Co-op programs, students have the opportunity to contribute to real projects, collaborate with experienced engineers and business leaders, and gain hands-on exposure to the technologies powering our end-to-end robotics and automation solutions. We are looking for curious, motivated students who are excited to solve complex problems, bring new perspectives to cross-functional teams, and see their work make an impact in a fast-moving, innovative environment." That seems good. Responsibilities: list from "What You’ll Do". Let's extract each bullet: - Play a hands-on role as part of an engineering team that works to design, develop, review and test new functionalities. - Collaborate with others on an agile/scrum team to build features based on new business requirements. - Evolve the current software architecture toward microservices using .NET Core, Kubernetes, RabbitMQ and Redis. - Contribute to a distributed architecture built on .NET using multi-threaded and multi-processor concepts. - Create visualizations to extract understanding of current state from logs. - Develop high quality code and packages following software engineering best practices. - Participate in customer facing calls, visits and workshops to educate and support customers on the integration requirements between Symbotic and customer systems. - Work with our customer's technical resources to test Symbotic integrations with their systems. We'll put each as
- .
Requirements: maybe include "What You’ll Need" items that are mandatory (not plus). Let's parse:
What You’ll Need:
- Currently pursuing a degree in Computer Science or related discipline.
- Strong object-oriented programming skills in C#, Python and C++.
- Experience with Linux and its commands.
- Experience with source control (git), software testing frameworks, and CI/CD pipelines (Jenkins).
- Enjoys learning new technologies, skills, and techniques as well as teaching them to others.
- Experience with Vitis and Vivaldo is a plus.
- Containerized development (Kubernetes, Docker, etc.) is a plus.
- Experience with cross platform .NET core development is a plus.
- Experience with MS SQL and the SQL language is a plus.
Thus mandatory: degree pursuing, OOP skills in C#, Python, C++, Linux experience, experience with git, testing frameworks, CI/CD (Jenkins), enjoys learning/teaching. The plus items are optional; we could still list them under Skills maybe.
Thus Requirements section could contain the mandatory items.
Qualifications: maybe the degree pursuing is qualification; but we already have that in Requirements. Could separate: Qualifications: degree pursuing Computer Science or related discipline. Requirements: technical skills etc. But we need to avoid duplication.
Better: Qualifications: degree pursuing. Requirements: OOP skills, Linux, git, testing, CI/CD, enjoys learning/teaching. Skills: plus items (Vitis/Vivaldo, containerized dev, .NET core, MS SQL). Benefits: transportation/housing, mentorship/professional dev/networking/calendar, medical/dental/vision/disability/401K/PTO. Pay: base range $32-$44. Schedule: Timeframe Spring (Jan-May 2027).
We also have "Our Environment" with travel up to 10%, driver's license, ability to drive/fly, owning credit card managing expenses. That could be part of Requirements or maybe a separate section like "Requirements" includes those. Since we already