R&D Engineering Systems Co-op (May-Dec)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications and Preferred Qualifications?), Benefits, Pay, Schedule. Must only include sections if posting has real specific content. Let's parse. Content: - Additional Location(s): N/A (ignore) - Diversity - Innovation - Caring - Global Collaboration - Winning Spirit - High Performance (maybe part of boilerplate? It's not a section heading; it's a list of values. Could be considered part of About the role? But it's generic values; maybe we can include as a paragraph under About the role? The instruction: remove boilerplate, duplicated lines, EEO etc. This list might be considered boilerplate? It's values; but not specifically about the role. Might be okay to keep as part of About the role? However they said "Prefer a few substantive sections over many thin ones." Could include a short paragraph about company values under About the role. - About The Role: paragraph about collaboration, onsite work model, relocation assistance, no sponsorship, consider qualified applicants of all ages. - Then description of role: As an R&D Engineering Systems Co-op, you will join... etc. - Your Responsibilities Will Include: list bullet points. - Required Qualifications: list. - Preferred Qualifications: list. - Requisition ID: 635308 (metadata, drop or short p) - Minimum Salary: $ 60216 Maximum Salary: $ 75816 - Then compensation description: "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)." - For MA positions: It is unlawful to require or administer a lie detector test for employment. Violators are subject to criminal penalties and civil liability. - Boston Scientific Corporation has been and will continue to be an equal opportunity employer... (EEO boilerplate, remove) - Among other requirements, Boston Scientific maintains specific prohibited substance test requirements for safety-sensitive positions. This role is deemed safety-sensitive and, as such, candidates will be subject to a prohibited substance test as a requirement. The goal of the prohibited substance testing is to increase workplace safety in compliance with the applicable law. (This is specific content about prohibited substance test; we should keep.) We need sections: About the role, Responsibilities, Requirements (maybe combine Required and Preferred?), Benefits, Pay, Schedule. Do we have Benefits? The posting mentions "core and optional employee benefits offered by Boston Scientific (BSC) – see www.bscbenefitsconnect.com". That's a mention of benefits but not specific. It says "the value of core and optional employee benefits offered by Boston Scientific (BSC) – see www.bscbenefitsconnect.com—will vary based on actual location". That's not specific benefits; it's a reference. According to rule: never create Benefits section unless posting actually states them. It does mention benefits exist but not list them. Likely we should not create Benefits section because no specific benefits listed. So omit Benefits. Pay: we have salary range: Minimum Salary: $ 60216 Maximum Salary: $ 75816. Also compensation description includes variable etc. That's specific enough to create Pay section. We'll include the salary range and maybe note that compensation varies based on location etc. But we must not include filler like "commensurate with experience" if it's vague? The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). However the posting says "Compensation will be commensurate with demonstrable level of experience and training..." That's somewhat filler but it's actual statement. Might be okay to include as part of Pay section. But we should avoid just saying "commensurate with experience" alone. We can include the sentence as is. Schedule: The posting mentions onsite work model requiring employees to be in local office at least five days per week. Also co-op duration: May 17th or May 24th – December 17th, 2027. That's schedule info. So we can create Schedule section with those details. Now Requirements: We have Required Qualifications and Preferred Qualifications. Could combine into a Requirements section with subheadings? But we only allowed headings:

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have a Requirements section and inside maybe

• for required and preferred? Or we could have separate Qualifications and Skills sections. The list includes Required Qualifications and Preferred Qualifications. Could treat Required Qualifications as Requirements, Preferred Qualifications as Skills? Or we could have a Qualifications section containing both required and preferred. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which headings to use. We need to include sections only when posting has real specific content. We have both required and preferred qualifications; we could make a Qualifications section with two sub-lists: Required and Preferred. Or we could make Requirements for required, Skills for preferred. But preferred qualifications include communication skills, knowledge of system-level programming in C, Linux, Python, attention to detail. Those are skills. So we could have Requirements (required) and Skills (preferred). That seems appropriate. Thus sections: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. We must not repeat job title as heading. Not include Job ID/requisition numbers as headings; we can put them in a short

  maybe but we can drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can either drop or include a short p. Probably drop to keep minimal. Now we need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, required qualifications, preferred qualifications, etc. Also include the paragraph about onsite work model, relocation assistance, no sponsorship, consider qualified applicants of all ages. Also include the description of role (the paragraph starting "As an R&D Engineering Systems Co-op..."). Also include the prohibited substance test info. Also include the MA lie detector test law. Also include the EEO statement? That is boilerplate; we should remove. Also include the diversity - innovation - caring - global collaboration - winning spirit - high performance list. That's maybe values; could be considered part of About the role? It's not specific to role but it's company values. Might be considered boilerplate? Not sure. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The values list is not exactly those categories; it's more like corporate values. Might be okay to keep as a short paragraph under About the role. But we need to avoid filler. It's substantive? It's generic but still part of posting. I'd include it as a paragraph under About the role. Now we need to output only HTML fragment, no /, no markdown. Let's craft. Structure:

  About the role

  At Boston Scientific, we value collaboration and synergy. This role follows an onsite work model, requiring employees to be in our local office at least five 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. We will consider qualified applicants of all ages who are starting (or restarting) their careers.

  Additional note: Boston Scientific’s core values include Diversity, Innovation, Caring, Global Collaboration, Winning Spirit, and High Performance.

  But we need to preserve the line about "Additional Location(s): N/A" - we can drop as N/A. Now Responsibilities:

  Responsibilities

  • Help define and analyze system requirements, clinical workflows, and input/output processes using current systems engineering methods and technologies.
  • Solve system problems by analyzing situations and recommending corrective or alternative actions.
  • Document system architecture and design control elements through technical documents, reports and memos.
  • Collaborate in translating customer needs into technical requirements, partnering with field, marketing, service and other cross-functional teams.
  • Define, troubleshoot, and execute testing for system design and verification activities.
  • Assist with industry standards testing for safety and EMC in accordance with IEC 60601-1.
  • Support risk analysis activities for assigned projects.
  • Partner with cross-functional teams to deliver project objectives.
  Now Requirements (required qualifications):

  Requirements

  • Currently pursuing a bachelor’s or graduate-level degree in biomedical engineering, computer engineering, computer science or electrical engineering, with an expected graduate between Fall 2027 to Spring 2028.
  • Proficiency in programming using MATLAB.
  • Strong understanding of hardware/software systems.
  • Available to participate for the full duration of the co-op program from May 17th or May 24th – December 17th, 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.
  Now Skills (preferred qualifications):

  Skills

  • Strong written and verbal communication skills, including experience with documentation and report writing.
  • Knowledge of system-level programming in C, Linux, and Python.
  • High attention to detail with strong organizational and documentation skills.
  Now Pay:

  Pay

  The anticipated compensation for this role ranges from a minimum salary of $60,216 to a maximum salary of $75,816. 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 Boston Scientific, it is not typical for an individual to be hired near the bottom or top of the anticipated salary range. Compensation may also include variable components such as overtime, shift differential, annual bonus target, and long‑term incentives, subject to plan eligibility and other requirements.

  We need to preserve the exact numbers: $ 60216 and $ 75816 (with a space). We should keep as given: $ 60216 and $ 75816. Could format with commas for readability but must preserve info; adding commas is okay as it's still same value. Might be safer to keep exactly as in text: "$ 60216" and "$ 75816". We'll keep that. Now Schedule:

  Schedule