Co-op, Embedded Software Test Engineering: January - June 2027 (Onsite)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as 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 parse the posting. Key content: - Job Summary Co-op, Embedded Software Test Engineering: January - June 2027 (Onsite) - Position Dates: January 11, 2027 – June 30, 2027 - Job Title: Embedded Software Engineering Co-op - Department: Electronics COE - FLSA Status: Non-Exempt - About Insulet (description) - Position Overview (description) - Responsibilities (list) - Education And Experience Minimum Requirements: Currently enrolled in an undergraduate software or systems engineering program - Preferred Skills And Competencies: Knowledge of C, Familiar with statistical analysis, Good documentation skills, Strong attention to detail, Knowledge of Embedded systems is a plus - This position is not eligible for employer-based visa sponsorship. Candidates must have authorization to work in the U.S. without current or future sponsorship needs. - Additional Information Compensation & Benefits: For U.S.-based positions only, the annual base salary range for this role is $25.00 - $34.00 This position may also be eligible for incentive compensation. We offer a comprehensive benefits package, including: Medical insurance Holiday pay Sick time off And additional employee wellness programs - Application Details: (should be removed) - Additional paragraphs about Insulet (duplicate) - EEO statement (remove) - etc. We need to produce sections: maybe "About the role" (could combine About Insulet and Position Overview). "Responsibilities" (list). "Requirements" (Education And Experience Minimum Requirements). "Skills" (Preferred Skills And Competencies). "Benefits" (Compensation & Benefits includes benefits list). "Pay" (the salary range). Possibly "Schedule" not given (no schedule details). So we should not create Schedule section. We must not repeat job title as heading. We can include minor metadata like Position Dates, Department, FLSA Status in a short

  maybe under a heading? 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 Position Dates, Department, FLSA Status. We must not include application instructions, EEO, etc. We need to preserve all substantive information: that includes the description of Insulet, Position Overview, responsibilities list, education requirement, preferred skills, visa sponsorship note, compensation & benefits (salary range, benefits list, incentive compensation). Also maybe note that it's a co-op Jan-June 2027 onsite. That's substantive; we should include that maybe in a short paragraph. We must not create sections with filler. So we need to decide which sections to include: About the role (maybe combine About Insulet and Position Overview). Responsibilities (list). Requirements (education). Skills (preferred skills). Benefits (benefits list). Pay (salary range). Possibly also a short paragraph for metadata (position dates, department, FLSA status, visa note). Could be under a heading like "Position Details" but that's not in the allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list "Position Details". But we could fold minor metadata into a short

  under maybe "About the role" or just as a paragraph before sections. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can just have a

  with that metadata, not a heading. Thus output: maybe start with a

  containing: Position Dates: January 11, 2027 – June 30, 2027. Department: Electronics COE. FLSA Status: Non-Exempt. This position is not eligible for employer-based visa sponsorship; candidates must have authorization to work in the U.S. without current or future sponsorship needs. Then

  About the role

  with paragraphs: Insulet description and Position Overview. Then

  Responsibilities

  with
  • items. Then

    Requirements

    with

    Currently enrolled in an undergraduate software or systems engineering program. Then

    Skills

    with
    • list of preferred skills. Then

      Benefits

      with
      • list: Medical insurance, Holiday pay, Sick time off, Additional employee wellness programs. Then

        Pay

        with

        For U.S.-based positions only, the annual base salary range for this role is $25.00 - $34.00. This position may also be eligible for incentive compensation. We must not include Schedule. Check for duplication: The Insulet description appears twice; we should include only once. The Position Overview appears once; include. We must not include application details, EEO, etc. Check for any other substantive info: "The candidate will work with the software engineering group on new development projects and assisting with development, documentation, data analysis and testing." That's part of Position Overview. Already included. Now ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML fragment. We must not include or . Just the fragment. Let's craft:

        Position Dates: January 11, 2027 – June 30, 2027. Department: Electronics COE. FLSA Status: Non-Exempt. This position is not eligible for employer-based visa sponsorship; candidates must have authorization to work in the U.S. without current or future sponsorship needs.

        About the role

        Insulet Corporation is an innovative medical device company dedicated to making the lives of people with diabetes and other conditions easier through the use of its Omnipod® product platform. The Omnipod® system consists of a hand-held controller that communicates directly with a wearable on-body device to provide Insulin therapy. More than 150,000 users across the globe rely on Insulet’s Omnipod® Insulin Management System to bring simplicity and freedom to everyday life. Insulet Corporation is headquartered in a world class facility in Acton, MA.

        The candidate will work with the software engineering group on new development projects and assisting with development, documentation, data analysis and testing. The candidate will work with cross functional teams, including systems, software, and electrical engineers in supporting new product development. These functions and others help support Insulet’s ability to continue to improve the quality of life for more diabetes patients every day. The ideal candidate will have the desire to learn about and work with various different functional groups on programs ranging from software-only solutions to electrical problems, while learning about the medical device industry. Insulet focuses on professional development of co-op students. Each co-op has a manager who works with them to achieve desired learning outcomes based on the preferences of the co-op.

        Responsibilities

        • Work hands on with development boards and development software to aid in product development activities
        • Managing project documentation (creating requirements, design, protocols, reports, and design history file documentation) and drive team alignment and approvals
        • Assist/Lead Design Change Orders
        • Performs other duties as required

        Requirements

        Currently enrolled in an undergraduate software or systems engineering program

        Skills

        • Knowledge of C
        • Familiar with statistical analysis
        • Good documentation skills
        • Strong attention to detail
        • Knowledge of Embedded systems is a plus

        Benefits

        • Medical insurance
        • Holiday pay
        • Sick time off
        • Additional employee wellness programs

        Pay

        For U.S.-based positions only, the annual base salary range for this role is $25.00 - $34.00. This position may also be eligible for incentive compensation.

        Check if any other substantive info: "Actual pay depends on skills, experience, and education." That's kind of filler but it's substantive? It's a statement about actual pay depends on skills, experience, and education. Could be considered filler but it's not placeholder like "commensurate with experience". It's a statement that actual pay depends on skills, experience, and education. Might be considered generic but still substantive? The instruction: 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. The phrase "Actual pay depends on skills, experience, and education." is not exactly placeholder but it's generic. However we already have Pay section with salary range. Adding that sentence might be okay but could be considered filler. Safer to omit? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That sentence is substantive detail about pay determination. I'd include it maybe as another sentence in Pay paragraph. Thus Pay paragraph: "For U.S.-based positions only, the annual base salary range for this role is $25.00 - $34.00. This position may also be eligible for incentive compensation. Actual pay depends on skills, experience, and education." Now check for any other substantive info: "We offer a comprehensive benefits package, including: Medical insurance Holiday pay Sick time off And additional employee wellness programs" we captured. Also "This position may also be eligible for incentive compensation." we captured. Now ensure no duplicate content: we included Insulet description once, Position Overview once. Check for any other substantive info: "Insulet’s flagship innovation, the Omnipod 5 Automated Insulin Delivery System, integrates with a continuous glucose monitor to manage blood sugar with no multiple daily injections, zero fingersticks, and can be controlled by a compatible personal smartphone in the U.S. or by the Omnipod 5 Controller." That's in the later duplicate paragraph about Insulet. That is substantive info about Omnipod 5. Should we include? It appears in the later duplicate paragraph after the EEO statement. It's substantive about product details. Should we preserve? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that info somewhere, maybe in About the role section. We already have a generic description of Omnipod. Adding details about Omnipod 5 would be good. Thus we need to incorporate that paragraph: "Insulet’s flagship innovation, the Omnipod 5 Automated Insulin Delivery System, integrates with a continuous glucose monitor to manage blood sugar with no