Software Engineer

We need to output HTML fragment with sections: About the role? Actually we need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. We need to extract content from posting. Let's parse the posting: - Who We Are: description of Symbotic. - Timeframe: Summer (May-Aug 2027) - About Symbotic internship description. - About The Opportunities: description of Software Engineering function and intern opportunities (list of roles). - What You’ll Do: list of duties. - What You’ll Need: list of requirements/qualifications/skills. - Our Environment: travel, driver's license, credit card. - About Symbotic: more company description. - Compensation: base range $32.00 - $44.00, compensation package includes medical, dental, vision, disability, 401K, PTO and/or other benefits. - Also mention transportation and housing benefits for students who meet relocation requirements. We need sections: About the role (maybe summary of role), Responsibilities (What You’ll Do), Requirements (What You’ll Need), Qualifications (maybe overlapping), Skills (maybe specific tech), Benefits (transportation/housing, medical etc), Pay (base range), Schedule (maybe timeframe? Actually schedule could be internship schedule: Summer (May-Aug 2027) maybe considered schedule). We need to include only sections with real specific content. Let's decide: - About the role: we can use the introductory paragraph about intern role: "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..." That's about the role. Could be used. - Responsibilities: "What You’ll Do" list. - Requirements: "What You’ll Need" list (including degree, OOP skills, Linux, git, etc). Also maybe "Our Environment" travel etc could be part of Requirements? But we can keep separate. - Qualifications: maybe overlapping with Requirements; but we can separate: degree, etc. However we need to avoid duplication. Could combine Requirements and Qualifications? But we need to follow instruction: use headings only when posting has real specific content for it. We can have both if content distinct. Let's see: "What You’ll Need" includes both qualifications and skills. Could split: Qualifications: degree, etc. Skills: programming languages, tools, etc. Benefits: transportation/housing, medical etc. Pay: base range. Schedule: Timeframe (Summer May-Aug 2027). Also maybe "Our Environment" could be part of Requirements or Benefits? It's about travel, driver's license, credit card. Could be considered part of Requirements (eligibility). But we already have Requirements; we could add those points there. We must not repeat job title as heading. No Job ID. We must not include boilerplate like EEO etc. Remove that. We must not include application instructions. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Let's extract details precisely. From posting: Who We Are: "With its A.I.-powered robotic technology platform, Symbotic is changing the way consumer goods move through the supply chain. Intelligent software orchestrates advanced robots in a high-density, end-to-end system – reinventing warehouse automation for increased efficiency, speed and flexibility." Timeframe: "Summer (May-Aug 2027)" About Internship: "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." About The Opportunities: "Symbotic’s Software Engineering function is a diverse community of skilled engineers who are building innovative technology across the stack. Intern opportunities in our Software function include:" Then bullet list: - Front-end engineers develop and enhance desktop, mobile, and web applications, optimizing performance and usability for end-users. - Back-end engineers develop high quality code and packages following software engineering best practices in areas such as tasking, cognitive tools, fleet orchestration, case handling, and storage and retrieval. - Embedded engineers design, implement, and validate Hardware-in-the-Loop (HIL) test frameworks to ensure reliability and robustness of embedded systems. - Test Automation engineers triage complex onsite issues and build automated pipelines to validate new products and packaging at scale. What You’ll Do: - 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. 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. Our Environment: - Up to 10% of travel may be required. - Employees must have a valid driver’s license and the ability to drive and/or fly to client and other customer locations. - The employee is responsible for owning a credit card and managing expenses personally to be reimbursed on a bi-weekly basis. About Symbotic (company description): - Symbotic is an automation technology leader reimagining the supply chain with its end-to-end, AI-powered robotic and software platform. - Symbotic reinvents the warehouse as a strategic asset for the world’s largest retail, wholesale, and food & beverage companies. - Applying next-gen technology, high-density storage and machine learning to solve today's complex distribution challenges, Symbotic enables companies to move goods with unmatched speed, agility, accuracy and efficiency. - As the backbone of commerce the Symbotic platform transforms the flow of goods and the economics of supply chain for its customers. - For more information, visit www.symbotic.com. - We are a community of innovators, collaborators and pioneers who embrace our differences, because we know unique perspectives make us stronger and smarter. - Every perspective matters. - We depend on the collective voices of our employees, customers and community to help guide us as we build a better place to work – for you and the world. - That’s why we’re proud to be an equal opportunity employer. (We will remove EEO boilerplate) - We do not discriminate based on ... (remove) 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. Also transportation and housing benefits mentioned earlier. Now we need to map to sections. Potential sections:

About the role

: Could contain the paragraph about intern role (Early Career talent...). Also maybe include Who We Are? But "About the role" likely about the position. We'll use the paragraph(s) describing the internship opportunity.

Responsibilities

: Use "What You’ll Do" list.

Requirements

: Use "What You’ll Need" list (including degree, OOP, Linux, git, etc). Also maybe include "Our Environment" travel etc? Could be part of Requirements but we could also add a separate section for "Work Environment" but not in allowed headings. Since allowed headings are limited, we could incorporate travel etc into Requirements as additional bullet points.

Qualifications

: Could be degree etc but we already used Requirements. To avoid duplication, maybe we treat Requirements as the hard requirements, and Qualifications as preferred/pluses. Let's see: The posting has "Experience with Vitis and Vivaldo is a plus." etc. Those are pluses. So we can put those under Qualifications (or Skills). But we also have Skills heading allowed. Let's decide: - Requirements: degree, OOP skills, Linux, git, testing frameworks, CI/CD (Jenkins), enjoys learning/teaching. - Qualifications: pluses (Vitis/Vivaldo, containerized development, cross-platform .NET core, MS SQL). Could also include degree? But we already have degree in Requirements. Might be okay to duplicate? Better not duplicate. We'll keep degree in Requirements. - Skills: maybe list specific technologies: C#, Python, C++, .NET Core, Kubernetes, RabbitMQ, Redis, multi-threaded/multi-processor, .NET, etc. But many of those appear in Responsibilities. Could also list them under Skills. However we need to avoid duplication but we can still mention them if they are substantive. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all details. If we put them in multiple sections, that's duplication but not invented. It's okay to repeat? Might be considered redundant but not prohibited. However better to organize logically without repeating same bullet points. We can distribute details across sections without repeating exact same sentences. Let's think: Responsibilities already mention using .NET Core, Kubernetes, RabbitMQ, Redis, multi-threaded/multi-processor concepts, .NET, etc. So we could keep those there. Skills could list programming languages: C#, Python, C++, etc. Also mention experience with Linux, git, testing frameworks, CI/CD, etc. But those are also in Requirements. Might be okay to have overlapping but we need to avoid unnecessary duplication. Perhaps better to have: - About the role: introductory paragraph. - Responsibilities: What You’ll Do list. - Requirements: What You’ll Need list (degree, OOP, Linux, git, testing frameworks, CI/CD, enjoys learning/teaching). - Qualifications: pluses (Vitis/Vivaldo, containerized development, cross-platform .NET core, MS SQL). - Benefits: transportation and housing benefits for relocation; compensation package includes medical, dental, vision, disability, 401K, PTO and/or other benefits. - Pay: base range $32.00 - $44.00. - Schedule: Timeframe Summer (May-Aug 2027). We also have "Our Environment" travel etc. Could be part of Requirements (as additional bullet). Let's add those under Requirements as bullet points: Up to 10% travel may be required; valid driver’s license; ability to drive/fly; own credit card manage expenses reimbursed bi-weekly. Now we need to ensure we don't include boilerplate like EEO etc.