Radiology Software Development Co-Op

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Content: - Intro paragraph: "The Operational Excellence Software Development Co-op position is intended to provide exposure to software development processes related to medical devices. The Co-op will participate in the development of operating systems and product images, assist with activities performed by the DevSecOps team such as pipeline development, test automation, and system administration, and contribute to platforms for medical device connectivity (Internet of Things (IoT)). This role also offers experience working with a variety of technologies and business challenges within a collaborative R&D environment." That's about the role. - "Your Tasks And Responsibilities" heading then list of responsibilities. List items: - Work as part of an agile product team to design, develop, build, secure, upgrade, enhance, and support the IoT platform and customer solutions utilizing the platform; - Conduct functional and non-functional testing activities; - Validate procedures and process changes in a timely manner; - Develop technical documentation to accurately represent application design and code, and to validate and verify solutions; - Identify opportunities to develop new and improved solutions, including researching software updates and third-party technologies for integration into medical devices; - Collaborate with Software Engineers on medical device software development programs and products, including application software, platform software, and operating system software; - Perform critical analysis of technical situations, identify problems, and work with cross-functional teams to develop and implement solutions; - Participate in continuous improvement initiatives supporting the Software Assurance Center of Excellence; - Support Operating Systems team members to ensure project requirements and deliverables are met; - Assist Team Leads with operating system and product image creation activities and timelines; - Collaborate with cross-functional teams across multiple geographies to communicate challenges, opportunities, solutions, and results related to medical device R&D activities. - "WHO YOU ARE" heading then required and preferred. Required: - Ability to work 40 hours per week; - Currently pursuing a bachelor's degree in Software Engineering, Computer Engineering, Computer Science, Information Technology, or a related engineering discipline; - Ability to work in-office in a hybrid environment. Preferred: list many items. We need to decide sections: About the role (intro). Responsibilities (list). Requirements (maybe required). Qualifications (maybe preferred? Or combine). Skills (maybe list of preferred technical skills). Benefits (maybe mention benefits). Pay (hourly rate). Schedule (maybe ability to work 40 hours per week? That's schedule). However schedule is about hours per week; we could put schedule section if present. The posting says "Ability to work 40 hours per week;" that's schedule expectation. Also "Ability to work in-office in a hybrid environment." That's location/hybrid. We need to include sections only if real specific content. Pay: "Employees can expect to be paid an hourly rate of approximately between $24.00 to $45.50. Additional compensation may include a bonus or commission (if relevant). Additional benefits may include health care, vision, dental, retirement, PTO, sick leave, etc. (if relevant). 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." Thus we have pay range and benefits mention. So we can have Pay section with the hourly rate. Benefits section with list of benefits (health care, vision, dental, retirement, PTO, sick leave). However note that benefits are described as "Additional benefits may include health care, vision, dental, retirement, PTO, sick leave, etc. (if relevant)." That's somewhat generic but still specific list. We'll include. Schedule: "Ability to work 40 hours per week;" and "Ability to work in-office in a hybrid environment." That's schedule/hybrid. We'll include Schedule section with those points. Now we need to avoid filler like "commensurate with experience". Not present. We must not repeat job title as heading. So we will not include heading "Operational Excellence Software Development Co-op". We'll start with sections. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the "YOUR APPLICATION" paragraph, the Equal Opportunity Employer statements, location, reference code, contact info, etc. Also remove "This posting will be available for application until at least March 19, 2027." That's application instruction? It's a date; maybe considered application instruction? It's not a duty; but it's about posting availability. Probably should remove as it's not substantive about role. Also remove "Be part of something bigger. Be you. Be Bayer." etc. Also remove "To all recruitment agencies: Bayer does not accept unsolicited third party resumes." etc. Also remove "Equal Opportunity Employer Statement: Notice for U.S. Visitors: ..." etc. Thus we keep only the core role description, responsibilities, who you are (required/preferred), pay, benefits, schedule. Now we need to decide which sections to output. Potential sections: - About the role (intro paragraph) - Responsibilities (list) - Requirements (required) - Qualifications (preferred? maybe combine with Skills) - Skills (list of technical skills from preferred) - Benefits (list) - Pay (hourly rate) - Schedule (40 hrs/week, hybrid) We must avoid thin sections. But we have enough content. We need to ensure we don't create sections with filler like "not specified". All have content. Now we need to format. Let's extract each piece. About the role paragraph: The first paragraph (maybe two sentences). We'll keep as

  . Responsibilities: list items as

  • each. Requirements: required items as
    • . Qualifications: maybe we treat preferred as Qualifications? Or we could have Skills section for technical skills and Qualifications for education/experience? But we already have degree in Requirements. Preferred includes familiarity with languages, frameworks, databases, Agile, IoT, tools, OS, interpersonal skills, MS Office, problem-solving, decision-making, communication, collaboration, troubleshooting, written communication. That's a mix of skills and qualifications. We could split: Skills section for technical skills (languages, frameworks, DB, Agile, IoT, tools, OS). Qualifications section for interpersonal skills, MS Office, problem-solving, etc. But the instruction says prefer few substantive sections over many thin ones. Might be better to have a single "Qualifications and Skills" section? But we need to follow rule: use headings for specific sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those that have real content. We could include Qualifications (preferred non-technical) and Skills (technical). That's two sections. But we must ensure not to create thin sections. Let's see content: Preferred technical: Familiarity with one or more of the following programming languages and frameworks: C++, Qt/QML, C#, .NET, Python, JavaScript, Node.js, Angular, and PowerShell; Familiarity with database technologies including SQL; Familiarity with Agile software development methodologies, including Scrum; Familiarity with IoT application platform development and management; Working knowledge of software development tools such as GitHub and JFrog; Working knowledge of Windows and Linux operating systems. That's a good list for Skills. Preferred non-technical/other: Excellent interpersonal skills with the ability to collaborate effectively in a team environment; Proficiency with Microsoft Office applications, including Word, Excel, and PowerPoint; Strong problem-solving, decision-making, communication, and collaboration skills; Ability to troubleshoot technical issues and make informed decisions based on available information; Strong written communication skills with the ability to create clear and concise documentation for diverse audiences, including testers, auditors, and peers. That's Qualifications. Thus we can have Skills and Qualifications sections. Now Benefits: list health care, vision, dental, retirement, PTO, sick leave. Pay: hourly rate approx between $24.00 to $45.50. Additional compensation may include a bonus or commission (if relevant). We'll include that. Schedule: Ability to work 40 hours per week; Ability to work in-office in a hybrid environment. Now we need to ensure we don't include any boilerplate like "if relevant". That's part of the content; we can keep it. Now produce HTML. Structure:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      • Ability to work 40 hours per week;
      • Currently pursuing a bachelor's degree in Software Engineering, Computer Engineering, Computer Science, Information Technology, or a related engineering discipline;
      • Ability to work in-office in a hybrid environment.

      Skills

      • Familiarity with one or more of the following programming languages and frameworks: C++, Qt/QML, C#, .NET, Python, JavaScript, Node.js, Angular, and PowerShell;
      • Familiarity with database technologies including SQL;
      • Familiarity with Agile software development methodologies, including Scrum;
      • Familiarity with IoT application platform development and management;
      • Working knowledge of software development tools such as GitHub and JFrog;
      • Working knowledge of Windows and Linux operating systems;

      Qualifications

      • Excellent interpersonal skills with the ability to collaborate effectively in a team environment;
      • Proficiency with Microsoft Office applications, including Word, Excel, and PowerPoint;
      • Strong problem-solving, decision-making, communication, and collaboration skills;
      • Ability to troubleshoot technical issues and make informed decisions based on available information;
      • Strong written communication skills with the ability to create clear and concise documentation for diverse audiences, including testers, auditors, and peers;

      Benefits

      • Health care
      • Vision
      • Dental
      • Retirement
      • PTO
      • Sick leave

      Pay

      Employees can expect to be paid an hourly rate of approximately between $24.00 to $45.50. Additional compensation may include a bonus or commission (if relevant).

      Schedule

      • Ability to work 40 hours per week;
      • Ability to work in-office in a hybrid environment.
      Check for duplication: The schedule items overlap with Requirements (Ability to work 40 hours per week; Ability to work in-office in a hybrid environment). Actually those were listed under Requirements. But we moved them to Schedule. However the requirement list originally included those two items. If we move them to Schedule, we should remove them from Requirements to avoid duplication. The instruction: preserve ALL substantive information; do not invent or summarize away detail. We can keep them in either section but not duplicate. Better to keep them under Requirements as they are required. But we also need a Schedule section if we have schedule info. However the schedule info is exactly those two items. We could keep them under Requirements and not have a separate Schedule section, because the schedule is covered. But the instruction says include a section ONLY when the posting has real, specific content for it. The posting