Engineering Co-op - Summer 2027

We need to output HTML fragment with sections: About the role? The posting includes introductory paragraph about RoviSys employees, then "Responsibilities" heading? Actually the text includes "Responsibilities Co-op Position: College Student ..." So we need to parse. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Only include sections if posting has real specific content. We need to preserve all substantive info, not invent. We need to remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. There's none. We need to format duties/requirements/benefits as

• . Use

  for prose. We need to not repeat job title as heading (the page already shows it). No job title given explicitly; we can ignore. We must not put Job ID/requisition numbers as headings. We need to include sections only when posting has real specific content. Let's identify content: - Intro paragraph: "RoviSys employees work on exciting projects in a collaborative environment. Our engineers are intelligent, talented, enthusiastic teammates who use technology to provide innovative solutions for complex client challenges. Our innovative solutions make a difference in industry and society every day." This could be "About the role" or maybe "About the company". Use

  About the role

  with

  . - Responsibilities: The text after "Responsibilities Co-op Position: College Student RoviSys offers a broad opportunity to grow your career while working under the guidance of experienced Engineers and Developers with any of the following duties:" then list of duties bullet-like sentences. Then later "Below are the co-op paths we currently offer." Then sections for Systems, Information Systems, Industrial IT each with Success Factors, Technologies Used, Duties. Thus responsibilities include many items. We can combine all duties into a

  under Responsibilities. But we also have separate sections for each co-op path; maybe they could be under Responsibilities as sub-sections? However the instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can only have those headings. We cannot create custom headings like "Systems". So we need to fit content into those allowed headings. Thus we can have: - About the role (intro) - Responsibilities (list of duties) - Requirements (maybe qualifications) - Qualifications (maybe same as requirements? But we have "Qualifications" section in posting: "Full-time student status ..." So we can put that under Qualifications. - Skills? Not explicitly listed but maybe "Success Factors" could be considered skills. But we have to only include sections if posting has real specific content. The posting includes "Success Factors" for each path, which are like skills/knowledge. Could be placed under Skills. - Benefits: The posting includes "Compensation & Benefits Highlights" with Competitive Hourly Rate, Travel Perks, Grow With Us. So we can have Benefits section (maybe also Pay). Since Pay is mentioned (Competitive Hourly Rate: $25/hr). According to instruction, we should not create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation and benefits, so we can include Benefits (maybe also Pay). But we have both Pay and Benefits as possible headings. The posting includes both compensation and benefits; we could put Pay section for hourly rate, Benefits section for travel perks and training. However instruction says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section? But they said use headings e.g. Benefits, Pay, Schedule. We could include both if content exists. However to avoid thin sections, maybe combine into Benefits (including pay). But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation and benefits, so we could have a Benefits section that includes pay and perks. That's fine. We also have Schedule? Not mentioned. So no Schedule section. We also have Requirements? The posting includes "Qualifications" but not separate Requirements. Could treat Qualifications as Requirements. But we have both headings; we could put the qualifications under Requirements (or Qualifications). Since they have a "Qualifications" heading in the posting, we can use that heading. Thus sections: - About the role (intro) - Responsibilities (duties) - Qualifications (full-time student status, GPA, enrollment, etc.) - Skills (maybe Success Factors from each path) - Benefits (compensation & benefits highlights) We need to ensure we don't create empty sections. Now extract content. Intro paragraph: as above. Responsibilities: list of duties from the text. Let's extract duties: From after "Responsibilities Co-op Position: College Student RoviSys offers a broad opportunity to grow your career while working under the guidance of experienced Engineers and Developers with any of the following duties:" then list: - Design and develop automation systems - Design and develop electrical control systems that will interface with process lines, manufacturing equipment and sensors - Architect solutions using the appropriate technologies from database to AI to User Interface tools. - Provide our clients with real time, actionable information reports about their process - Develop quality code in accordance with established RoviSys and client standards - Work in team environment with engineers and designers from RoviSys, partners and clients - Travel to customer sites for planning meetings, commissioning and testing - Grow into position leading a team of engineers and technicians to provide automation and information solutions. Then later under each path there are more duties: Systems Duties: - Design and develop automation systems - Travel to client plants to assess and document existing systems and connected equipment - Use P&ID, Equipment Lists, I/O Lists and Process Descriptions to define control schemes for clients. - Network customer systems, Controllers, HMI PC's, Field mounted instruments and Process Skids to provide fully integrated control systems Information Systems Duties: - Design and implement industry software applications to aggregate manufacturing systems information and provide reports to support business decisions - Manually configure technical solutions and identify optimization opportunities by leveraging scripting and automation to increase process efficiency - Install and commission systems connected to the plant floor devices onsite and support operations personnel through effective use and maintenance of the deployed solutions - Scripting and light programming Industrial IT Duties: - Map and Design Network Architectures - Configure and Test Infrastructure components - Install and Commission equipment at customer sites, per design - Communicate with customer and project team to define needs and design/implement solutions We should combine all duties, avoiding duplication. Some duplicates: "Design and develop automation systems" appears twice. We should keep unique items. Let's list unique duties: 1. Design and develop automation systems 2. Design and develop electrical control systems that will interface with process lines, manufacturing equipment and sensors 3. Architect solutions using the appropriate technologies from database to AI to User Interface tools. 4. Provide our clients with real time, actionable information reports about their process 5. Develop quality code in accordance with established RoviSys and client standards 6. Work in team environment with engineers and designers from RoviSys, partners and clients 7. Travel to customer sites for planning meetings, commissioning and testing 8. Grow into position leading a team of engineers and technicians to provide automation and information solutions. 9. Travel to client plants to assess and document existing systems and connected equipment (similar to #7 but more specific; we can keep both or merge; but it's distinct: travel to client plants to assess/document existing systems) 10. Use P&ID, Equipment Lists, I/O Lists and Process Descriptions to define control schemes for clients. 11. Network customer systems, Controllers, HMI PC's, Field mounted instruments and Process Skids to provide fully integrated control systems 12. Design and implement industry software applications to aggregate manufacturing systems information and provide reports to support business decisions 13. Manually configure technical solutions and identify optimization opportunities by leveraging scripting and automation to increase process efficiency 14. Install and commission systems connected to the plant floor devices onsite and support operations personnel through effective use and maintenance of the deployed solutions 15. Scripting and light programming 16. Map and Design Network Architectures 17. Configure and Test Infrastructure components 18. Install and Commission equipment at customer sites, per design 19. Communicate with customer and project team to define needs and design/implement solutions We could also include "Grow into position leading a team..." already. Now Qualifications: from posting: - Full-time student status - Strong academic achievement, maintaining a GPA of 3.0 or above - Enrollment in a Bachelor's program in a Technical Field, related to Engineering, or Control Systems - Passionate about problem solving and developing solutions - Candidates must be authorized to work in the U.S. without RoviSys sponsorship Now Skills: Success Factors from each path: Systems Success Factors: Understanding of Process or Manufacturing Systems, Co-op Experience Electrical or Process Knowledge Information Systems Success Factors: Ability to understand Information System architectures Industrial IT Success Factors: Passion for networking Virtualization Cybersecurity in a manufacturing or office setting We could also include Technologies Used as skills? But they are under each path; maybe we can treat them as skills as well. However the instruction: Use

  • for any list of duties/requirements/benefits. So we can list skills as
    . We need to decide if we want a Skills section. The posting includes Success Factors which are like skills/knowledge. So we can include Skills section with those. Now Benefits: Compensation & Benefits Highlights: - Competitive Hourly Rate: $25/hr - Travel Perks: Travel incentives + per-diem packages for field assignments - Grow With Us: Ongoing training, certifications, and professional development support We can put these as
    under Benefits. Now we need to output HTML fragment only, no /, no markdown. We'll produce:

    About the role

    RoviSys employees work on exciting projects in a collaborative environment. Our engineers are intelligent, talented, enthusiastic teammates who use technology to provide innovative solutions for complex client challenges. Our innovative solutions make a difference in industry and society every day.

    Responsibilities

    • Design and develop automation systems
    • Design and develop electrical control systems that will interface with process lines, manufacturing equipment and sensors
    • Architect solutions using the appropriate technologies from database to AI to User Interface tools.
    • Provide our clients with real time, actionable information reports about their process
    • Develop quality code in accordance with established RoviSys and client standards
    • Work in team environment with engineers and designers from RoviSys, partners and clients
    • Travel to customer sites for planning meetings, commissioning and testing
    • Grow into position leading a team of engineers and technicians to provide automation and information solutions.
    • Travel to client plants to assess and document existing systems and connected equipment
    • Use P&ID, Equipment Lists, I/O Lists and Process Descriptions to define control schemes for clients.
    • Network customer systems, Controllers, HMI PC's, Field mounted instruments and Process Skids to provide fully integrated control systems
    • Design and implement industry software applications to aggregate manufacturing systems information and provide reports to support business decisions
    • Manually configure technical solutions and identify optimization opportunities by leveraging scripting and automation to increase process efficiency
    • Install and commission systems connected to the plant floor devices onsite and support operations personnel through effective use and maintenance of the deployed solutions
    • Scripting and light programming
    • Map and Design Network Architectures
    • Configure and Test Infrastructure components
    • Install and Commission equipment at customer sites, per design
    • Communicate with customer and project team to define needs and design/implement solutions