Systems Automation Co-op
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. Let's parse posting: - Intro about J&J 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 can have "About the role" containing description of role and purpose". The posting includes "Job Description" and "Position Purpose". So we can put that under About the role. - Responsibilities: list of key responsibilities with bullet points. - Requirements: maybe "Education And Qualifications" includes required qualifications. Also "Candidate Eligibility Requirements". Could combine into Requirements. - Qualifications: maybe separate Required Qualifications and Preferred Qualifications. Could put under Qualifications. - Skills: maybe "Required Skills Preferred Skills" but they gave pay range. Actually they have "Required Skills Preferred Skills: The anticipated base pay range..." That's weird. There's also "Learning Opportunities" and "Expected Deliverables". Could treat as Skills? Or maybe "Skills" section for required/preferred skills. - Benefits: they mention benefits: medical benefits, sick time, retirement plan. Also link. - Pay: they give pay range $23.50/hr to $52.50/hr. - Schedule: they mention "Available to work full time for the applicable co-op term at the Raritan site." and "Be available to work 40 hours per week during the internship." So schedule info. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, legal, accommodation request, etc. Remove those. Also remove duplicated lines. We must preserve all substantive information. So we need to include details like: - Job Function Career Programs etc? Might be metadata but not substantive? Probably can drop minor metadata like Job Function, Job Sub Function, Job Category, All Job Posting Locations. Could fold into short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include location maybe in a paragraph. - The intro about J&J mission could be part of About the role. Let's craft sections:
About the role
At Johnson & Johnson, we believe health is everything... (mission statement). The Automation Co-op will support the Automation and Operational Technology (OT) team at the J&J Innovative Medicine Raritan manufacturing site. This position provides hands-on exposure to automation systems, process control technologies, industrial data platforms, and digital manufacturing solutions used to support pharmaceutical production. The co-op will work alongside Automation Engineers and Manufacturing teams to help improve automation reliability, enhance data visibility, and support projects involving manufacturing equipment, process control systems, and industrial integrations. Position Purpose: Build practical experience in manufacturing automation, industrial data systems, process controls, and operational technology while contributing to projects that improve manufacturing reliability, efficiency, and innovation.
That seems good.Responsibilities
- Automation Operations Support: Support day-to-day activities related to manufacturing automation systems i.e. Delta-V and OSI-Pi; assist with system monitoring, troubleshooting, and issue resolution; help maintain automation documentation and equipment inventories; participate in system upgrades and enhancement activities.
- Process Control & Equipment Integration: Support automation engineers during equipment onboarding and integration projects; assist with automation design reviews and technical assessments; participate in testing and commissioning activities for automation solutions; help document system configurations and operating procedures.
- Industrial Data & Connectivity: Support data collection, visualization, and reporting initiatives; assist with historian, OT network, and manufacturing data integration activities; help improve visibility of operational data through analytics and dashboards; participate in projects involving OT/IT connectivity and digital manufacturing technologies.
- Automation Compliance & Validation: Support qualification, testing, and validation activities for automation systems; assist with execution and documentation of test protocols; learn GMP requirements related to automation systems; participate in risk assessments, change controls, and quality-related activities.
- Continuous Improvement & Innovation: Analyze automation performance data to identify improvement opportunities; support initiatives focused on reliability, efficiency, and reduction of manual processes; participate in cross-functional projects involving Manufacturing, Quality, Engineering, and IT; present project outcomes and recommendations to stakeholders.
Requirements
Candidates must be authorized to work in the US without current or future sponsorship requirements; remain actively enrolled in their academic program throughout the internship; be available to work 40 hours per week during the internship; have a minimum GPA of 3.0 (the text says "Should have a minimum GPA of 3" presumably 3.0). Must be permanently authorized to work in the U.S., must not require sponsorship of an employment visa (e.g., H-1B or green card) at the time of application or in the future. Students currently on CPT, OPT, or STEM OPT usually require future sponsorship for long term employment and do not meet the requirements unless eligible for an alternative long-term status that does not require company sponsorship.
But we need to preserve all substantive info. The GPA line: "Should have a minimum GPA of 3". We'll keep as is.Qualifications
Required Qualifications
but we only allowed h3 headings. Could we usefor Required Qualifications and then
for list? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those specific headings allowed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can use other headings but they should be . Probably we should stick to those headings only. So we cannot add subheadings like Required Qualifications. We could embed required and preferred qualifications within the Qualifications section using etc.
Thus Qualifications
then ... list required and preferred.
Let's extract:
Required Qualifications:
- Currently enrolled in an accredited bachelor's or master's degree program in Computer Science, Information Systems, Computer Engineering, Electrical Engineering, Biomedical Engineering, Industrial Engineering, Chemical Engineering, or a related technical discipline.
- Available to work full time for the applicable co-op term at the Raritan site.
- Strong analytical, organizational, problem-solving, written communication, and verbal communication skills.
- Ability to work effectively both independently and in a collaborative, cross-functional team environment.
- Proficiency with standard Microsoft 365 applications, including Excel, Word, PowerPoint, Teams, and Outlook.
Preferred Qualifications:
- Coursework or project experience involving automation, controls, robotics, instrumentation, or process engineering.
- Knowledge of programming concepts and scripting languages.
- Familiarity with PLCs, SCADA, HMIs, industrial networking, or process control systems.
- Experience with data analytics tools such as Power BI, Python, or SQL.
- Interest in manufacturing technology, Industry 4.0, digital transformation, or operational technology.
Also Learning Opportunities and Expected Deliverables could be part of Qualifications or maybe Skills. But we have Skills section separate.
We could put Learning Opportunities and Expected Deliverables under Skills? Or maybe under Qualifications as additional info.
But we have a separate Skills section for required/preferred skills. The posting includes "Required Skills Preferred Skills: The anticipated base pay range..." That's weird; maybe they misplace. Actually there is a line: "Required Skills Preferred Skills: The anticipated base pay range for this position is : $23.50/hr to $52.50/hr". That seems to be a formatting error. The pay range is separate.
Thus Skills section could include required and preferred skills (like proficiency with MS Office, analytical skills, etc.) but we already put many in Qualifications. To avoid duplication, we could treat Qualifications as education/experience, and Skills as technical skills (like programming, PLC, SCADA, etc.). However the instruction says prefer few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section? But they asked to use those headings if content exists. We have content for Qualifications (education, enrollment, GPA, etc.) and also for Skills (technical skills). We'll keep both.
Thus:
Qualifications
Required: Currently enrolled in an accredited bachelor's or master's degree program in Computer Science, Information Systems, Computer Engineering, Electrical Engineering, Biomedical Engineering, Industrial Engineering, Chemical Engineering, or a related technical discipline. Available to work full time for the applicable co-op term at the Raritan site. Strong analytical, organizational, problem-solving, written communication, and verbal communication skills. Ability to work effectively both independently and in a collaborative, cross-functional team environment. Proficiency with standard Microsoft 365 applications, including Excel, Word, PowerPoint, Teams, and Outlook.
Preferred: Coursework or project experience involving automation, controls, robotics, instrumentation, or process engineering. Knowledge of programming concepts and scripting languages. Familiarity with PLCs, SCADA, HMIs, industrial networking, or process control systems. Experience with data analytics tools such as Power BI, Python, or SQL. Interest in manufacturing technology, Industry 4.0, digital transformation, or operational technology.
We could also include Learning Opportunities and Expected Deliverables maybe under Qualifications as additional info, but maybe better under Skills? Actually Learning Opportunities list what they will learn; that's more like benefits/experience. Could be under Benefits? But Benefits already covers medical, sick time, retirement. Learning Opportunities is about what they'll gain. Could be under Qualifications as "What you'll learn". But to avoid too many sections, we could add a paragraph under Qualifications about learning opportunities and expected deliverables.
Let's extract Learning Opportunities:
- Manufacturing Automation Systems
- Process Control Technologies
- Operational Technology (OT)
- Industrial Data Platforms and Historians
- Equipment Integration and Commissioning
- Validation and Qualification Activities
- GMP Manufacturing Operations
- OT/IT Convergence
- Digital Manufacturing Technologies
- Technical Communication and Project Management
Expected Deliverables:
- Complete a defined automation or digital manufacturing project with measurable outcomes.
- Maintain project documentation and provide regular status updates.
- Deliver a final presentation summarizing project objectives, results, lessons learned, and future recommendations.
We could put these under Qualifications as additional bullet points.
But we already have a lot. Maybe better to have a separate section for "Learning & Deliverables" but not in allowed headings. Could incorporate into Qualifications as extra paragraphs.
Given instruction to prefer few substantive sections, we could combine Qualifications and Skills into one section called Qualifications, and maybe another for Benefits, Pay, Schedule. But we need to follow the heading list if we have content. We have content for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. That's many sections but each substantive.
Let's decide to keep all eight headings if we have real content.
Now Benefits: medical benefits, sick time, retirement plan. Also maybe mention link.
We'll produce:
Benefits
Co‑ops/Interns are eligible to participate in Company‑sponsored employee medical benefits in accordance with the terms of the plan. Co‑ops and Interns are eligible for sick time benefits: up to 40 hours per calendar year (up to 56 hours per calendar year for employees who reside in
. Probably we should stick to those headings only. So we cannot add subheadings like Required Qualifications. We could embed required and preferred qualifications within the Qualifications section using etc.
Thus Qualifications
then ... list required and preferred.
Let's extract:
Required Qualifications:
- Currently enrolled in an accredited bachelor's or master's degree program in Computer Science, Information Systems, Computer Engineering, Electrical Engineering, Biomedical Engineering, Industrial Engineering, Chemical Engineering, or a related technical discipline.
- Available to work full time for the applicable co-op term at the Raritan site.
- Strong analytical, organizational, problem-solving, written communication, and verbal communication skills.
- Ability to work effectively both independently and in a collaborative, cross-functional team environment.
- Proficiency with standard Microsoft 365 applications, including Excel, Word, PowerPoint, Teams, and Outlook.
Preferred Qualifications:
- Coursework or project experience involving automation, controls, robotics, instrumentation, or process engineering.
- Knowledge of programming concepts and scripting languages.
- Familiarity with PLCs, SCADA, HMIs, industrial networking, or process control systems.
- Experience with data analytics tools such as Power BI, Python, or SQL.
- Interest in manufacturing technology, Industry 4.0, digital transformation, or operational technology.
Also Learning Opportunities and Expected Deliverables could be part of Qualifications or maybe Skills. But we have Skills section separate.
We could put Learning Opportunities and Expected Deliverables under Skills? Or maybe under Qualifications as additional info.
But we have a separate Skills section for required/preferred skills. The posting includes "Required Skills Preferred Skills: The anticipated base pay range..." That's weird; maybe they misplace. Actually there is a line: "Required Skills Preferred Skills: The anticipated base pay range for this position is : $23.50/hr to $52.50/hr". That seems to be a formatting error. The pay range is separate.
Thus Skills section could include required and preferred skills (like proficiency with MS Office, analytical skills, etc.) but we already put many in Qualifications. To avoid duplication, we could treat Qualifications as education/experience, and Skills as technical skills (like programming, PLC, SCADA, etc.). However the instruction says prefer few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section? But they asked to use those headings if content exists. We have content for Qualifications (education, enrollment, GPA, etc.) and also for Skills (technical skills). We'll keep both.
Thus:
Qualifications
Required: Currently enrolled in an accredited bachelor's or master's degree program in Computer Science, Information Systems, Computer Engineering, Electrical Engineering, Biomedical Engineering, Industrial Engineering, Chemical Engineering, or a related technical discipline. Available to work full time for the applicable co-op term at the Raritan site. Strong analytical, organizational, problem-solving, written communication, and verbal communication skills. Ability to work effectively both independently and in a collaborative, cross-functional team environment. Proficiency with standard Microsoft 365 applications, including Excel, Word, PowerPoint, Teams, and Outlook.
Preferred: Coursework or project experience involving automation, controls, robotics, instrumentation, or process engineering. Knowledge of programming concepts and scripting languages. Familiarity with PLCs, SCADA, HMIs, industrial networking, or process control systems. Experience with data analytics tools such as Power BI, Python, or SQL. Interest in manufacturing technology, Industry 4.0, digital transformation, or operational technology.
We could also include Learning Opportunities and Expected Deliverables maybe under Qualifications as additional info, but maybe better under Skills? Actually Learning Opportunities list what they will learn; that's more like benefits/experience. Could be under Benefits? But Benefits already covers medical, sick time, retirement. Learning Opportunities is about what they'll gain. Could be under Qualifications as "What you'll learn". But to avoid too many sections, we could add a paragraph under Qualifications about learning opportunities and expected deliverables.
Let's extract Learning Opportunities:
- Manufacturing Automation Systems
- Process Control Technologies
- Operational Technology (OT)
- Industrial Data Platforms and Historians
- Equipment Integration and Commissioning
- Validation and Qualification Activities
- GMP Manufacturing Operations
- OT/IT Convergence
- Digital Manufacturing Technologies
- Technical Communication and Project Management
Expected Deliverables:
- Complete a defined automation or digital manufacturing project with measurable outcomes.
- Maintain project documentation and provide regular status updates.
- Deliver a final presentation summarizing project objectives, results, lessons learned, and future recommendations.
We could put these under Qualifications as additional bullet points.
But we already have a lot. Maybe better to have a separate section for "Learning & Deliverables" but not in allowed headings. Could incorporate into Qualifications as extra paragraphs.
Given instruction to prefer few substantive sections, we could combine Qualifications and Skills into one section called Qualifications, and maybe another for Benefits, Pay, Schedule. But we need to follow the heading list if we have content. We have content for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. That's many sections but each substantive.
Let's decide to keep all eight headings if we have real content.
Now Benefits: medical benefits, sick time, retirement plan. Also maybe mention link.
We'll produce:
Benefits
Co‑ops/Interns are eligible to participate in Company‑sponsored employee medical benefits in accordance with the terms of the plan. Co‑ops and Interns are eligible for sick time benefits: up to 40 hours per calendar year (up to 56 hours per calendar year for employees who reside in
Qualifications
then... list required and preferred. Let's extract: Required Qualifications: - Currently enrolled in an accredited bachelor's or master's degree program in Computer Science, Information Systems, Computer Engineering, Electrical Engineering, Biomedical Engineering, Industrial Engineering, Chemical Engineering, or a related technical discipline. - Available to work full time for the applicable co-op term at the Raritan site. - Strong analytical, organizational, problem-solving, written communication, and verbal communication skills. - Ability to work effectively both independently and in a collaborative, cross-functional team environment. - Proficiency with standard Microsoft 365 applications, including Excel, Word, PowerPoint, Teams, and Outlook. Preferred Qualifications: - Coursework or project experience involving automation, controls, robotics, instrumentation, or process engineering. - Knowledge of programming concepts and scripting languages. - Familiarity with PLCs, SCADA, HMIs, industrial networking, or process control systems. - Experience with data analytics tools such as Power BI, Python, or SQL. - Interest in manufacturing technology, Industry 4.0, digital transformation, or operational technology. Also Learning Opportunities and Expected Deliverables could be part of Qualifications or maybe Skills. But we have Skills section separate. We could put Learning Opportunities and Expected Deliverables under Skills? Or maybe under Qualifications as additional info. But we have a separate Skills section for required/preferred skills. The posting includes "Required Skills Preferred Skills: The anticipated base pay range..." That's weird; maybe they misplace. Actually there is a line: "Required Skills Preferred Skills: The anticipated base pay range for this position is : $23.50/hr to $52.50/hr". That seems to be a formatting error. The pay range is separate. Thus Skills section could include required and preferred skills (like proficiency with MS Office, analytical skills, etc.) but we already put many in Qualifications. To avoid duplication, we could treat Qualifications as education/experience, and Skills as technical skills (like programming, PLC, SCADA, etc.). However the instruction says prefer few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section? But they asked to use those headings if content exists. We have content for Qualifications (education, enrollment, GPA, etc.) and also for Skills (technical skills). We'll keep both. Thus:
Qualifications
Required: Currently enrolled in an accredited bachelor's or master's degree program in Computer Science, Information Systems, Computer Engineering, Electrical Engineering, Biomedical Engineering, Industrial Engineering, Chemical Engineering, or a related technical discipline. Available to work full time for the applicable co-op term at the Raritan site. Strong analytical, organizational, problem-solving, written communication, and verbal communication skills. Ability to work effectively both independently and in a collaborative, cross-functional team environment. Proficiency with standard Microsoft 365 applications, including Excel, Word, PowerPoint, Teams, and Outlook.
Preferred: Coursework or project experience involving automation, controls, robotics, instrumentation, or process engineering. Knowledge of programming concepts and scripting languages. Familiarity with PLCs, SCADA, HMIs, industrial networking, or process control systems. Experience with data analytics tools such as Power BI, Python, or SQL. Interest in manufacturing technology, Industry 4.0, digital transformation, or operational technology.
We could also include Learning Opportunities and Expected Deliverables maybe under Qualifications as additional info, but maybe better under Skills? Actually Learning Opportunities list what they will learn; that's more like benefits/experience. Could be under Benefits? But Benefits already covers medical, sick time, retirement. Learning Opportunities is about what they'll gain. Could be under Qualifications as "What you'll learn". But to avoid too many sections, we could add a paragraph under Qualifications about learning opportunities and expected deliverables. Let's extract Learning Opportunities: - Manufacturing Automation Systems - Process Control Technologies - Operational Technology (OT) - Industrial Data Platforms and Historians - Equipment Integration and Commissioning - Validation and Qualification Activities - GMP Manufacturing Operations - OT/IT Convergence - Digital Manufacturing Technologies - Technical Communication and Project Management Expected Deliverables: - Complete a defined automation or digital manufacturing project with measurable outcomes. - Maintain project documentation and provide regular status updates. - Deliver a final presentation summarizing project objectives, results, lessons learned, and future recommendations. We could put these under Qualifications as additional bullet points. But we already have a lot. Maybe better to have a separate section for "Learning & Deliverables" but not in allowed headings. Could incorporate into Qualifications as extra paragraphs. Given instruction to prefer few substantive sections, we could combine Qualifications and Skills into one section called Qualifications, and maybe another for Benefits, Pay, Schedule. But we need to follow the heading list if we have content. We have content for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. That's many sections but each substantive. Let's decide to keep all eight headings if we have real content. Now Benefits: medical benefits, sick time, retirement plan. Also maybe mention link. We'll produce:Benefits
Co‑ops/Interns are eligible to participate in Company‑sponsored employee medical benefits in accordance with the terms of the plan. Co‑ops and Interns are eligible for sick time benefits: up to 40 hours per calendar year (up to 56 hours per calendar year for employees who reside in