Engineering Co-op - Summer 2027
About the role
maybe for introductory paragraph. ThenResponsibilities
for duties list. ThenQualifications
. ThenSkills
? Not explicit; maybe we can include skills from technologies used? But the instruction: include a section only when posting has real, specific content for it. Skills could be derived from "Technologies Used" etc. But we might treat those as part of responsibilities or qualifications. Safer to not create Skills if not explicitly listed. The posting does not have a separate Skills section. So omit. Benefits: we have Travel Perks and Grow With Us (training, certifications). So we can create Benefits section with those items. Pay: Competitive Hourly Rate: $24-$25/hr. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We must not repeat job title as heading. No Job ID. We need to use- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to format content. Let's extract: About the role: The first 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." That's prose. Responsibilities: The section 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 after that: "Below are the co-op paths we currently offer." Then subpaths with details. Those also contain duties. We could incorporate them under Responsibilities as sub-items or separate? Probably include them as part of responsibilities as they are duties for each path. We need to preserve all substantive information. So we should include the details for each path. Let's extract each path: Systems: Success Factors: Understanding of Process or Manufacturing Systems Co-op Experience Electrical or Process Knowledge Technologies Used: DCS, PLCs, Rockwell, Siemens, Emerson, Schneider, Inductive, Aveva 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: Success Factors: Ability to understand Information System architectures Technologies Used: Relational Databases and Historians (MS SQL Server, Oracle, OSIsoft, etc.) Python, VBA/VBscript/C# syntax, Linux shell scription (Bash,make), PowerShell scripting 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: Success Factors: Passion for networking Virtualization Cybersecurity in a manufacturing or office setting Technologies Used: Virtualization, Networking Cybersecurity, Windows, Wireless 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 include these as part of responsibilities. Could group under each path as subheadings? But we only allowed headings for sections; we could still use
- and maybe include nested lists? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We could have a top-level list for responsibilities, and within each item we could have sublist for each path? Might be okay.
But to keep simple, we could flatten all duties into a single list, preserving all items. That would include duplicates (Design and develop automation systems appears twice). We should preserve all substantive information; duplicates okay but we could keep both. However we might want to avoid duplication but not required. I'd keep as given.
Let's compile responsibilities list:
From initial 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.
From Systems path duties:
- Design and develop automation systems (duplicate)
- 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
From 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
From 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 could also include Success Factors and Technologies Used as part of responsibilities? They are more like qualifications/skills. But they are under each path. Might be better to treat them as qualifications or skills. However we have Qualifications section separate. The posting also has a Qualifications section: "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"
We could also include the Success Factors and Technologies Used as part of Qualifications or Skills. But to avoid missing info, we could include them under Qualifications as additional items. However the instruction: Use
- for any list of duties/requirements/benefits. Qualifications is a list of requirements. So we can add those items there.
Thus Qualifications list:
- 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
- Understanding of Process or Manufacturing Systems Co-op Experience Electrical or Process Knowledge (Systems Success Factors)
- Ability to understand Information System architectures (Information Systems Success Factors)
- Passion for networking Virtualization Cybersecurity in a manufacturing or office setting (Industrial IT Success Factors)
- Technologies Used: DCS, PLCs, Rockwell, Siemens, Emerson, Schneider, Inductive, Aveva (Systems)
- Technologies Used: Relational Databases and Historians (MS SQL Server, Oracle, OSIsoft, etc.) Python, VBA/VBscript/C# syntax, Linux shell scription (Bash,make), PowerShell scripting (Information Systems)
- Technologies Used: Virtualization, Networking Cybersecurity, Windows, Wireless (Industrial IT)
But that seems a bit messy. Perhaps better to keep Qualifications as the explicit list, and treat Success Factors and Technologies Used as part of Responsibilities or Skills. Since we don't have Skills section, we could incorporate them into Responsibilities as bullet points under each path. That would preserve info.
Thus we can structure Responsibilities as:
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.
- Systems path:
- Success Factors: Understanding of Process or Manufacturing Systems Co-op Experience Electrical or Process Knowledge
- Technologies Used: DCS, PLCs, Rockwell, Siemens, Emerson, Schneider, Inductive, Aveva
- 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 path:
- Success Factors: Ability to understand Information System architectures
- Technologies Used: Relational Databases and Historians (MS SQL Server, Oracle, OSIsoft, etc.) Python, VBA/VBscript/C# syntax, Linux shell scription (Bash,make), PowerShell scripting
- 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 path:
- for any list of duties/requirements/benefits. Qualifications is a list of requirements. So we can add those items there.
Thus Qualifications list:
- 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
- Understanding of Process or Manufacturing Systems Co-op Experience Electrical or Process Knowledge (Systems Success Factors)
- Ability to understand Information System architectures (Information Systems Success Factors)
- Passion for networking Virtualization Cybersecurity in a manufacturing or office setting (Industrial IT Success Factors)
- Technologies Used: DCS, PLCs, Rockwell, Siemens, Emerson, Schneider, Inductive, Aveva (Systems)
- Technologies Used: Relational Databases and Historians (MS SQL Server, Oracle, OSIsoft, etc.) Python, VBA/VBscript/C# syntax, Linux shell scription (Bash,make), PowerShell scripting (Information Systems)
- Technologies Used: Virtualization, Networking Cybersecurity, Windows, Wireless (Industrial IT)
But that seems a bit messy. Perhaps better to keep Qualifications as the explicit list, and treat Success Factors and Technologies Used as part of Responsibilities or Skills. Since we don't have Skills section, we could incorporate them into Responsibilities as bullet points under each path. That would preserve info.
Thus we can structure Responsibilities as:
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We could have a top-level list for responsibilities, and within each item we could have sublist for each path? Might be okay.
But to keep simple, we could flatten all duties into a single list, preserving all items. That would include duplicates (Design and develop automation systems appears twice). We should preserve all substantive information; duplicates okay but we could keep both. However we might want to avoid duplication but not required. I'd keep as given.
Let's compile responsibilities list:
From initial 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.
From Systems path duties:
- Design and develop automation systems (duplicate)
- 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
From 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
From 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 could also include Success Factors and Technologies Used as part of responsibilities? They are more like qualifications/skills. But they are under each path. Might be better to treat them as qualifications or skills. However we have Qualifications section separate. The posting also has a Qualifications section: "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"
We could also include the Success Factors and Technologies Used as part of Qualifications or Skills. But to avoid missing info, we could include them under Qualifications as additional items. However the instruction: Use
- and maybe include nested lists? The instruction: Use