Heart Recovery Software R&D Co-Op

We need to output HTML fragment with sections: About the role? The posting includes a lot of intro about company, but we need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. We have: - About the role: Could be the program description, position summary, etc. The posting includes "Program Dates: January 11, 2027 – June 25, 2027", "Position Summary", "Key Responsibilities", "Minimum Requirements", "Required Skills Preferred Skills: The anticipated base pay range for this position is : $23.50/hr to $52.50/hr", "Additional Description For Pay Transparency", "Co-Ops/Interns are eligible to participate in Company sponsored employee medical benefits...", "Co-Ops and Interns are eligible for the following sick time benefits: up to 40 hours per calendar year; for employees who reside in the State of Washington, up to 56 hours per calendar year.", "Co-Ops and Interns are eligible to participate in the Company’s consolidated retirement plan (pension)." Thus we have content for: - About the role (maybe includes program dates, position summary) - Responsibilities (Key Responsibilities) - Requirements (Minimum Requirements) - Qualifications (maybe same as requirements? Could combine? But we need separate sections only if content exists. Could have Requirements and Qualifications separate if distinct. The posting has "Minimum Requirements" and also "Required Skills Preferred Skills". Might treat "Minimum Requirements" as Requirements, and "Required Skills Preferred Skills" as Skills? However they also mention "Preferred Skills". Could have a Skills section. - Benefits: The posting mentions medical benefits, sick time, retirement plan. So Benefits section. - Pay: The posting includes pay range. So Pay section. - Schedule: Not explicitly given aside from program dates (full time on site Jan 11 - June 25). That could be schedule. The posting says "Available full time on site: January 11, 2027 – June 25, 2027". That's schedule info. So we could have Schedule section. We need to avoid filler. Ensure we don't create sections with placeholder text. We need to output only HTML fragment, no /, no markdown fences. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We need to remove boilerplate: EEO statements, legal, etc. Also remove duplicated lines (the intro about J&J appears twice). Also remove navigation, cookie, etc. Also remove application instructions (like "Learn more at jnj.com", "Learn more at https://www.jnj.com/." maybe not needed? It's not application instruction but could be considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn more at jnj.com" might be considered navigation? It's a link to learn more about company. Might be considered boilerplate. Safer to remove it. Also "Learn more at https://www.jnj.com/." remove. Also remove "Job Function Career Programs Job Sub Function Non-LDP Intern/Co-Op Job Category Career Program All Job Posting Locations: Halethorpe, Maryland, United States of America". That's metadata; we can fold minor metadata into a short

  or drop it. Probably drop it. We need to keep substantive info: Program Dates, Position Summary, Key Responsibilities (list), Minimum Requirements (list), Required Skills Preferred Skills (list?), Pay range, Benefits (medical, sick time, retirement), Schedule (full time on site dates). Also maybe "Additional Description For Pay Transparency" is just repeating pay range; we can incorporate. We need to ensure we don't create sections with filler. So each section must have real content. Let's outline:

  About the role

  Program Dates: January 11, 2027 – June 25, 2027. Position Summary: Fueled by innovation at the intersection of biology and technology, we’re developing the next generation of smarter, less invasive, more personalized treatments. Abiomed Co-Ops are offered a unique opportunity to work in the forefront of medical device development. As a hands-on software engineering co-op, you'll be an integral part of our ECMO development team. You'll contribute to designing, testing, and implementing innovative solutions that support patients with critical heart and lung conditions. Join us in advancing the standard of care in ECMO technology.

  That's prose.

  Responsibilities

  • Assist in design and implementation of embedded software for a class II medical device
  • Construction and maintenance of software requirements
  • Design and implementation of software interfaces
  • Test case development, unit and integration testing
  • Participating in design reviews, code reviews and system integration activities
  • Collaborate on a multidisciplinary team

  Requirements

  • Available full time on site: January 11, 2027 – June 25, 2027
  • Currently enrolled at an accredited college/institution pursuing a Bachelor’s or master’s degree in computer science, computer engineering or related degree is required.
  • Currently in your third year of your undergraduate degree, or above, in school at the beginning of your co-op.
  • Have a minimum cumulative GPA of 3.0 on a 4.0 scale.
  • A passion for healthcare technology and making a positive impact in patients’ lives.
  • Experience (through coursework or projects) with at least one programming language (C, C++, Python, etc.).
  • Familiarity with embedded systems, electronics, or data acquisition is a plus.
  • Any experience with regulated industries, quality systems, or medical devices is a big asset (but not required).
  • Exposure to version control (e.g., Git) and issue tracking systems is preferred.
  • Willingness to learn, ask questions, and work as a reliable team player.
  • Excellent communication skills and attention to detail.
  • 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 requires future sponsorship for long term employment and do not meet the requirements for this program unless eligible for an alternative long-term status that does not require company sponsorship.
  But note: "Available full time on site: January 11, 2027 – June 25, 2027" could also go to Schedule section. However we can keep it in Requirements as it's a requirement. But we also need a Schedule section maybe. The instruction: Prefer a few substantive sections over many thin ones. Could combine schedule into Requirements or About the role. But we also have a Pay section and Benefits section. We could keep Schedule as separate if we have content. The schedule info is just the program dates; we already have them in About the role. So we could omit a separate Schedule section to avoid thin section. However the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule (full time on site dates). But we already included that in About the role. If we create a Schedule section, we would need to include that info. But we could also keep it in About the role and not have a separate Schedule section. That would be fewer sections. The instruction: Prefer a few substantive sections over many thin ones. So better to avoid a separate Schedule section if we can incorporate the schedule info elsewhere. However the schedule info is a requirement (availability). It's already in Requirements list as an item. So we can keep it there and not have a separate Schedule section. Thus we have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Now Skills: The posting includes "Required Skills Preferred Skills: The anticipated base pay range for this position is : $23.50/hr to $52.50/hr". Actually that line mixes skills and pay. Let's parse: After Minimum Requirements, there is: "Required Skills Preferred Skills: The anticipated base pay range for this position is : $23.50/hr to $52.50/hr Additional Description For Pay Transparency The expected pay range for this position is between $23.50 per hour and $52.50 per hour but will be based on candidate's program year, discipline, degree and/or experience. 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 the following sick time benefits: up to 40 hours per calendar year; for employees who reside in the State of Washington, up to 56 hours per calendar year. Co-Ops and Interns are eligible to participate in the Company’s consolidated retirement plan (pension). For additional general information on Company benefits, please go to: https://www.careers.jnj.com/employee-benefits" Thus there is a line "Required Skills Preferred Skills:" but no actual list of skills following that colon before the pay range. It seems the skills list is missing; maybe they intended to list skills but didn't. So we should not create a Skills section if there is no specific skill content. The line "Required Skills Preferred Skills:" is just a heading with no details. So we should not create a Skills section because it would be filler. Instead we can treat any skills mentioned elsewhere (like experience with programming language, familiarity with embedded systems, etc.) as part of Requirements. So we skip Skills section. Thus we have About the role, Responsibilities, Requirements, Benefits, Pay. Now Benefits: we have medical benefits, sick time, retirement plan. Also mention of link for additional info (we can drop link as it's navigation). So we need to list those. Pay: we have pay range and description. Now we need to ensure we don't include boilerplate like EEO statements, etc. Also remove duplicated lines (the intro about J&J appears twice). We already omitted. Now we need to output HTML fragment. Let's craft:

  About the role

  Program Dates: January 11, 2027 – June 25, 2027. Position Summary: Fueled by innovation at the intersection of biology and technology, we’re developing the next generation of smarter, less invasive, more personalized treatments. Abiomed Co-Ops are offered a unique opportunity to work in the forefront of medical device development. As a hands-on software engineering co-op, you'll be an integral part of our EC