Product Supply Co-Op

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. First, job title: Product Supply Co-Op (not used as heading). Then description: "This position offers a hands-on co-op experience within Bayer’s Pittsburgh Product Supply organization, a dynamic medical device manufacturing environment. The role provides students with practical experience supporting operational excellence, continuous improvement, and product supply activities while working alongside professionals across multiple disciplines. Through meaningful assignments and project work, the successful candidate will have the opportunity to explore and contribute to Engineering, Quality, Supply Chain, and Manufacturing Operations. This position offers exposure to medical device production processes, problem-solving, data analysis, process improvement, and cross-functional collaboration in a highly regulated industry. Student contributions will support business objectives while providing valuable insight into the end-to-end Product Supply organization and potential career paths within Bayer Product Supply. This is a local, onsite position. Candidates will spend time at Bayer’s Pittsburgh-area locations, with specific reporting locations varying based on assigned projects: 1 Bayer Drive, Indianola, PA 15051625 Alpha Drive, Pittsburgh, PA 15238150 Victory Road, Saxonburg, PA 16056" We can treat that as "About the role" section (prose). Could also include location details there. Next: "YOUR TASKS AND RESPONSIBILITIES" list bullet points. We'll put under

Responsibilities

with

• each bullet. Next: "KEY WORKING RELATIONSHIPS" maybe could be part of Responsibilities or separate? Not a required heading; but we could include under Responsibilities as part of prose? The instruction: Use headings only for those categories if content exists. Could we treat "Key working relationships" as part of Responsibilities? Probably better to include under Responsibilities as a bullet list? But it's a list of relationships; could be a separate section like "Working Relationships" but not in allowed headings. So we incorporate into Responsibilities prose or as a bullet under Responsibilities. Next: "WHO YOU ARE" includes Required and Preferred. This maps to Requirements, Qualifications, Skills. We need to decide. We have Required: Currently pursuing a bachelor’s or master’s degree in Engineering, Supply Chain, Operations Management, Quality, Business, or a related field; Demonstrated interest in manufacturing operations, medical devices, engineering, quality, supply chain, or continuous improvement; Strong analytical, problem-solving, and organizational skills; Ability to analyze data, identify trends, and support improvement opportunities; Ability to work effectively both independently and as part of a cross-functional team; Strong verbal and written communication skills; Proficiency with Microsoft Office applications, including Excel, PowerPoint, and Word; Ability to work onsite and travel between Bayer’s Pittsburgh-area locations, as required. Preferred: Previous internship, co-op, project, laboratory, manufacturing, or operational experience; Exposure to Lean, Six Sigma, process improvement, quality systems, or regulated manufacturing environments; Familiarity with production planning, procurement, data analysis, or project coordination. We need to split into sections: Requirements (maybe required), Qualifications (maybe education?), Skills (maybe technical skills). But we must not invent sections without content. We can create sections: Requirements (required), Qualifications (maybe degree?), Skills (maybe proficiency). However we need to ensure we don't create thin sections. Better approach: Use "Requirements" for required items, "Qualifications" for preferred items? Or "Skills" for technical skills like MS Office, analytical, communication. Let's think. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose any of those that have content. We have content for: - About the role: yes. - Responsibilities: yes. - Requirements: we have required items. - Qualifications: we have preferred items (could be qualifications). Or we could treat required as Qualifications and preferred as Skills? But we need to avoid duplication. We could do:

  Requirements

  with required list.

  Preferred Qualifications

  but heading must be exactly from list? The list includes "Qualifications". Not "Preferred Qualifications". But we could still use

  Qualifications

  and put both required and preferred? Might be mixing. Better: Use

  Requirements

  for required,

  Skills

  for technical skills (MS Office, analytical, problem-solving, communication). Then

  Qualifications

  for preferred items (experience, Lean Six Sigma, familiarity). However we need to ensure not to create thin sections. Let's extract: Required items list: - Currently pursuing a bachelor’s or master’s degree in Engineering, Supply Chain, Operations Management, Quality, Business, or a related field; - Demonstrated interest in manufacturing operations, medical devices, engineering, quality, supply chain, or continuous improvement; - Strong analytical, problem-solving, and organizational skills; - Ability to analyze data, identify trends, and support improvement opportunities; - Ability to work effectively both independently and as part of a cross-functional team; - Strong verbal and written communication skills; - Proficiency with Microsoft Office applications, including Excel, PowerPoint, and Word; - Ability to work onsite and travel between Bayer’s Pittsburgh-area locations, as required. Preferred items: - Previous internship, co-op, project, laboratory, manufacturing, or operational experience; - Exposure to Lean, Six Sigma, process improvement, quality systems, or regulated manufacturing environments; - Familiarity with production planning, procurement, data analysis, or project coordination. We could also note salary and benefits. Salary: "Employees can expect to be paid a salary of approximately between $20.75 to $47.75. Additional compensation may include a bonus or commission (if relevant)." Benefits: "Additional benefits include health care, vision, dental, retirement, PTO, sick leave, etc.." Also note: "This salary (or salary range) is merely an estimate and may vary based on an applicant’s location, market data/ranges, an applicant’s skills and prior relevant experience, certain degrees and certifications, and other relevant factors." This is boilerplate but still substantive? It's a disclaimer about salary variability. Might be considered boilerplate but it's about salary. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This salary disclaimer might be considered legal boilerplate? It's not EEO but it's a disclaimer about salary. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The salary disclaimer is substantive about salary variability. I'd keep it as part of Pay section. Also: "This position will be posted until 11.01.2026" - that's a date; could be considered metadata but not a heading. Could be placed in a short paragraph under About the role or separate? Probably include in About the role as a note. Also: "YOUR APPLICATION" etc is application instructions, should be removed. Also: "Bayer offers a wide variety of competitive compensation and benefits programs..." is boilerplate encouraging to apply; remove. Also: "To all recruitment agencies: Bayer does not accept unsolicited third party resumes." is boilerplate; remove. Also: "Bayer is an Equal Opportunity Employer/Disabled/Veterans..." etc is EEO boilerplate; remove. Also: "Equal Opportunity Employer Statement: Notice for U.S. Visitors: ..." remove. Also: "Location: United States : Pennsylvania : Pittsburgh Division: Pharmaceuticals Reference Code: 881472 Contact Us Email: hrop_usa@bayer.com" - metadata; could be placed in a short paragraph maybe under About the role? But it's minor metadata; we can fold into a short

  or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph with location and reference code maybe. Thus final HTML:

  About the role

  This position offers a hands-on co-op experience within Bayer’s Pittsburgh Product Supply organization, a dynamic medical device manufacturing environment. The role provides students with practical experience supporting operational excellence, continuous improvement, and product supply activities while working alongside professionals across multiple disciplines. Through meaningful assignments and project work, the successful candidate will have the opportunity to explore and contribute to Engineering, Quality, Supply Chain, and Manufacturing Operations. This position offers exposure to medical device production processes, problem-solving, data analysis, process improvement, and cross-functional collaboration in a highly regulated industry. Student contributions will support business objectives while providing valuable insight into the end-to-end Product Supply organization and potential career paths within Bayer Product Supply. This is a local, onsite position. Candidates will spend time at Bayer’s Pittsburgh-area locations, with specific reporting locations varying based on assigned projects: 1 Bayer Drive, Indianola, PA 15051; 625 Alpha Drive, Pittsburgh, PA 15238; 150 Victory Road, Saxonburg, PA 16056. The position will be posted until 11.01.2026.

  Responsibilities

  • Actively contribute within Engineering, Quality, Supply Chain, and Manufacturing Operations while developing an understanding of the end-to-end Product Supply organization
  • Support critical projects across Production, Engineering, Quality, and Supply Chain functions
  • Analyze operational data and performance metrics to identify opportunities to improve safety, quality, delivery, and cost
  • Partner with cross-functional teams to drive continuous improvement initiatives and implement sustainable process enhancements
  • Support day-to-day operational business processes, including production planning, procurement, performance tracking, problem-solving activities, and project coordination
  • Participate in root-cause investigations and corrective-action implementation to improve product quality and manufacturing reliability
  • Assist with the development and maintenance of standard operating procedures, visual work instructions, and operational documentation, while identifying and suggesting potential improvements
  • Lead or support process-improvement projects focused on increasing productivity, reducing waste, improving compliance, and enhancing customer service
  • Collaborate with production teams to identify and implement solutions that improve operational efficiency and manufacturing performance
  • Prepare and present project updates, analyses, and recommendations to site leadership and functional teams
  • Complete additional tasks that arise throughout the assignment
  • Key working relationships include: Quality Engineers; Production Engineers; Project Engineers; Production Management; Production Associates; Supply Chain Teams

  Requirements

  • Currently pursuing a bachelor’s or master’s degree in Engineering, Supply Chain, Operations Management, Quality, Business, or a related field
  • Demonstrated interest in manufacturing operations, medical devices, engineering, quality, supply chain, or continuous improvement
  • Strong analytical, problem-solving, and organizational skills
  • Ability to analyze data, identify trends, and support improvement opportunities
  • Ability to work effectively both independently and as part of a cross-functional team
  • Strong verbal and written communication skills
  • Proficiency with Microsoft Office applications, including Excel, PowerPoint, and Word
  • Ability to work onsite and travel between Bayer’s Pittsburgh-area locations, as required

  Qualifications

  • Previous internship, co-op, project, laboratory, manufacturing, or operational experience
  • Exposure to Lean, Six Sigma, process improvement, quality systems, or regulated manufacturing environments
  • Familiarity with production planning, procurement, data analysis, or project coordination