Software Development Engineer Co-op (Jan- Aug)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications and Preferred Qualifications?), Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. First, remove boilerplate: Additional Location(s): N/A, Diversity - Innovation..., etc. Also remove EEO, equal-opportunity, scam-warning, etc. Also remove application instructions (none). Also remove duplicated lines. We need to preserve substantive info. Let's extract sections: - About Role: The paragraph starting "About Role" then description: "We will consider qualified applicants of all ages who are starting (or restarting) their careers. At Boston Scientific, we value collaboration and synergy. This role follows a hybrid work model, requiring employees to be in our local office at least four days per week. Relocation assistance may be available to those who meet the eligibility criteria. Boston Scientific will not offer sponsorship or take over sponsorship of an employment VISA for this position at this time. As a Software Development Engineer Co-op, you will join a highly effective development team working in an Agile environment alongside cross-functional partners. You will contribute to the development of a wide range of software applications and components, including user interfaces, algorithms and back-end data handling, using C++ in a Linux operating system environment. In this role, you will have the opportunity to apply your problem-solving skills to meaningful engineering work, expand your professional network, grow your technical capabilities through hands-on experience and mentorship, and gain exposure to life at a Fortune 500 medical device company. The U.S. Waltham-based division is a small, dynamic and fast-growing part of the Boston Scientific Electrophysiology group, with a highly talented team developing and testing the leading-edge Opal Mapping System. This system centers around a real-time virtual model of the human heart. As physicians probe the heart with a catheter, the system generates an accurate anatomical model of the chamber, leveraging high-performance rendering and advanced algorithms to provide instant, meaningful feedback." That's the About Role content. - Responsibilities: "Your Responsibilities Will Include Design, develop and unit test software applications using C++ in a Linux environment.Participate in Agile scrum teams to coordinate development of new features and resolve technical issues.Collaborate with cross-functional teams, including software development and testing, across all phases of the development lifecycle.Contribute to user interface, algorithm development, and back-end data handling components.Apply problem-solving skills to deliver high-quality, reliable software solutions.Engage in continuous learning and development through mentorship and hands-on experience." We need to split into list items. - Required Qualifications: list: "Currently pursuing a bachelor’s or graduate level degree majoring in Computer Science or Biomedical Engineering and Electrical Engineering, with an expected graduation date in fall/winter 2027 or spring 2030.Proficiency skills in programming using C, C++, or Rust.Strong understanding of object-oriented programming principles.Available to participate for the full duration of the co-op program from Jan. 11th- Aug. 6 or Aug. 13th, 2027. Eligible to work in the U.S. without company sponsorship, now or in the future, for employment-based work authorization.Have reliable transportation to and from 309 Waverley Oaks Road, Waltham, MA 02452. Boston Scientific does not provide transportation or transportation support to and from its locations." We need to split into list items. - Preferred Qualifications: list: "Strong written and verbal communication skills, including experience with documentation and report writing.Knowledge of systems-level programming, Linux, and QT.High attention to detail with strong organizational and documentation skillsDemonstrated ability to learn complex software and quickly adapt to new tools and technologies.Ability to work independently and collaboratively as part of a team." - Pay: The posting includes "Minimum Salary: $ 44616 Maximum Salary: $ 75816 The anticipated compensation listed above and the value of core and optional employee benefits offered by Boston Scientific (BSC) – see www.bscbenefitsconnect.com—will vary based on actual location of the position and other pertinent factors considered in determining actual compensation for the role. Compensation will be commensurate with demonstrable level of experience and training, pertinent education including licensure and certifications, among other relevant business or organizational needs. At BSC, it is not typical for an individual to be hired near the bottom or top of the anticipated salary range listed above. Compensation for non-exempt (hourly), non-sales roles may also include variable compensation from time to time (e.g., any overtime and shift differential) and annual bonus target (subject to plan eligibility and other requirements). Compensation for exempt, non-sales roles may also include variable compensation, i.e., annual bonus target and long-term incentives (subject to plan eligibility and other requirements)." We need to include Pay section only if posting has real specific content. It does have salary range. However we must avoid filler like "commensurate with experience". The rule: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The posting includes "Compensation will be commensurate with demonstrable level of experience and training..." That's filler? It's basically saying commensurate with experience. Might be considered filler. But we also have concrete numbers: Minimum Salary: $44616 Maximum Salary: $75816. That's specific. So we can include Pay section with those numbers and maybe note that compensation varies based on location etc. But we must avoid filler like "commensurate with experience". We could include the salary range and maybe a brief note that compensation varies based on location and other factors, but that is somewhat filler. However the rule says never emit a heading followed by filler/placeholder text. If we include a sentence that is filler, that might violate. Safer to include only the concrete salary numbers and maybe a short phrase like "The anticipated compensation range is $44,616 – $75,816." Avoid filler. We could also mention that compensation may include variable compensation and bonuses, but that might be considered filler? It's still specific info. Probably okay. - Schedule: The posting mentions hybrid work model requiring employees to be in local office at least four days per week. That's schedule info. Also maybe mention full duration of co-op program dates (Jan 11th - Aug 6 or Aug 13, 2027). That's schedule. So we can include Schedule section with those details. - Benefits: The posting mentions "Relocation assistance may be available to those who meet the eligibility criteria." Also mentions core and optional employee benefits via link. But no specific benefits listed. The rule: never create Benefits section unless posting actually states them. It does mention relocation assistance, and mentions core and optional employee benefits but not specifics. Might be considered not specific enough. However "Relocation assistance may be available" is a specific benefit. Could include Benefits section with that. But we need to avoid filler like "varies". It's okay. We also have "Access to the latest tools, information and training" earlier in the boilerplate but that's generic. Might be considered filler. We'll ignore. Thus sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Pay, Schedule, Benefits (maybe). Skills? Not explicitly listed; we could combine Required and Preferred as Skills? But we have separate sections for Required Qualifications and Preferred Qualifications. The instruction says use headings like Skills, Benefits, Pay, Schedule. It didn't require Required Qualifications heading; but we can still use it? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use Requirements or Qualifications. We'll use "Requirements" for required qualifications, and maybe "Preferred Qualifications" as a subsection? But we could combine into Requirements and Preferred under same heading? Better to follow examples: they gave Requirements, Qualifications as possible headings. We could have "Requirements" for required, and "Preferred Qualifications" as separate heading? Might be okay. But to keep few sections, we could have "Requirements" covering both required and preferred? But they'd be mixed. I'd produce separate headings: "Required Qualifications" and "Preferred Qualifications". Both are allowed as they are in the list (Qualifications). The example includes Qualifications. So we can use "Required Qualifications" and "Preferred Qualifications". That's fine. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

About the role

...

Responsibilities

• Design, develop and unit test software applications using C++ in a Linux environment.
• Participate in Agile scrum teams to coordinate development of new features and resolve technical issues.
• Collaborate with cross-functional teams, including software development and testing, across all phases of the development lifecycle.
• Contribute to user interface, algorithm development, and back-end data handling components.
• Apply problem-solving skills to deliver high-quality, reliable software solutions.
• Engage in continuous learning and development through mentorship and hands-on experience.

Required Qualifications

• Currently pursuing a bachelor’s or graduate level degree majoring in Computer Science or Biomedical Engineering and Electrical Engineering, with an expected graduation date in fall/winter 2027 or spring 2030.
• Proficiency in programming using C, C++, or Rust.
• Strong understanding of object-oriented programming principles.
• Available to participate for the full duration of the co-op program from Jan. 11th – Aug. 6 or Aug. 13th, 2027.
• Eligible to work in the U.S. without company sponsorship, now or in the future, for employment-based work authorization.
• Have reliable transportation to and from 309 Waverley Oaks Road, Waltham, MA 02452. (Boston Scientific does not provide transportation or transportation support to and from its locations.)

Preferred Qualifications

• Strong written and verbal communication skills, including experience with documentation and report writing.
• Knowledge of systems-level programming, Linux, and QT.
• High attention to detail with strong organizational and documentation skills.
• Demonstrated ability to learn complex software and quickly adapt to new tools and technologies.
• Ability to work independently and collaboratively as part of a team.

Pay

The anticipated compensation range is $44,616 – $75,816.

Schedule

• Hybrid work model: required to be in the local office at least four days per week.
• Co‑op duration: January 11 – August 6 or August 13, 2027 (full duration).

Benefits

• Relocation assistance may be available to eligible candidates.

We need to ensure we didn't include filler like "commensurate with experience". We avoided that. Check for any leftover boilerplate: We removed diversity statement, EEO, etc. Check for duplicate lines: none. Check for any mention of "Minimum Salary: $ 44616 Maximum Salary: $ 75816". We turned into range. Check for any mention of "Relocation assistance may be available to those who meet the eligibility criteria." We captured. Check for any mention of "Boston Scientific does not provide transportation or transportation support to and from its locations." We included in parentheses. Check