Lifecycle Engineering Co-Op Full Time Intern Jan-June 2027

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. We have: - About This Role: description of role, lifecycle engineers, etc. That's content for "About the role". Should be

About the role

then

...

. - Assignment Details: full-time six-month internship, location, etc. Could be considered "Schedule" maybe? Actually schedule: full-time, six-month, Jan-June 2027, location. Could be "Schedule" section. Also "Pay" section: $25-30 per hour, estimated pay range $25-35. So we have pay info. - Responsibilities: list of bullet points. - Minimum Qualifications: list of qualifications. - Also there is a line "Familiar with lab test equipment..." etc. That's part of qualifications. - There's also "Values and prioritizes a supportive team environment..." etc. That's also qualifications. - Also "Strong working knowledge of MS office 365 tools..." etc. - Also "Ability to understand and modify different programming scripts..." etc. - Also "Familiarity with configuration and change control..." etc. Thus we can have sections: About the role, Responsibilities, Requirements (or Qualifications), Skills (maybe combine qualifications and skills?), Pay, Schedule. We need to decide which headings to use: The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can pick those that have content. We have content for About the role, Responsibilities, Minimum Qualifications (could be Requirements or Qualifications), Skills (maybe separate), Pay, Schedule. We should not repeat job title. No Job ID. We need to remove boilerplate: EEO, scam warning, etc. Also remove navigation, cookie, legal, duplicated lines. We need to preserve all substantive information. Let's extract substantive content. About This Role paragraph: "Join the team that supports released cardiac monitoring products after launch. Our Lifecycle Engineers ensure quality, reliability, compliance, manufacturability, and business continuity across the product lifecycle. The work connects electrical hardware, embedded firmware, manufacturing test systems, configuration control, verification, failure analysis, and technical documentation and the team focuses on supporting existing products through their lifecycle. As a Lifecycle Engineering Co-Op, you will support execution of changes to our electrical (PCBA design), embedded firmware, and manufacturing tooling software that keep our released medical device products safe, compliant, manufacturable, and reliable. You’ll work closely with our product development team of electrical, embedded firmware, and software engineers to resolve field and factory issues, manage obsolescence, improve yield, and maintain regulatory compliance." That's the about role. Responsibilities list: - Prototype and test electrical PCB components integrated with prototype product firmware and/or fixture software - Support software updates to manufacturing equipment & test systems (fixture software, functional test scripts, ICT/boundary scan integration) to drive improvements to yield, throughput, and reliability. - Support embedded software development and updates, ensuring compatibility with hardware and compliance with IEC 62304 and cybersecurity requirements. - Support execution of V&V (unit/integration/system), including test plans, protocols, automated regression suites, and reports compliant with IEC 62304 and internal SOPs. - Create and maintain engineering drawings, specifications, test methods, protocols, and reports to support design control, manufacturing transfer, and regulatory documentation - Work cross-functionally with engineering, quality, and regulatory groups to prepare or review product requirements, test methods, test protocols, and test reports. - Assist with failure analysis of production components, assemblies, and field returns - Contribute ideas that may support future product improvements or intellectual property - Perform lab equipment setup/maintenance as necessary Minimum Qualifications (list): - Pursuing a BS, MS, or PhD degree in Electrical or Computer Science Engineering or related fields - Basic understanding of PCBA design principles, embedded systems, embedded software development (C/C++), and hardware/software integration. - Familiar with lab test equipment and comfortable being hands-on in a lab environment (supporting fixture builds, following test protocols) - Detail-oriented with excellent troubleshooting and critical thinking skills - Strong written and verbal communication skills, and a positive attitude - Comfortable working with minimal supervision - Values and prioritizes a supportive team environment that enables open-minded and respectful discussion - Strong working knowledge of MS office 365 tools (Word, Excel, PowerPoint) - Ability to understand and modify different programming scripts such as Java, Python, JavaScript, C#, etc., used for writing automated test scripts and frameworks a plus - Familiarity with configuration and change control (Git, branching strategies, code reviews, CI; ECR/ECO, traceability) a plus Pay: "Full-time | January through June 2027 | Cypress, CA, (Orange County) | $25-30.00 per hour Housing assistance or a housing stipend is not provided. Candidates are responsible for arranging and funding their own housing during the assignment. Location: Orange County Actual compensation may vary depending on job-related factors including knowledge, skills, experience, and work location. Estimated Pay Range $25.00 - $35.00" Thus we have pay range $25-30 per hour, estimated range $25-35. We'll include both? Probably just mention the pay: $25-30 per hour, estimated range $25-35. We'll put in

. Schedule: "full-time, six-month Engineering Internship / Cooperative Education (Co-op) assignment for a current student. It offers internship-style learning, mentorship, and meaningful project work, but it is not a traditional summer internship. Candidates must be available for the full January through June 2027 assignment in San Francisco." Wait location contradictory: earlier says Cypress, CA (Orange County) then says San Francisco? Actually assignment details says "Candidates must be available for the full January through June 2027 assignment in San Francisco." Then later location says Orange County. Might be a mistake but we need to preserve all substantive info. We'll include both location mentions? Probably we should include location as part of schedule or maybe separate? There's no dedicated location heading; we could include location in Schedule section. We'll note location: Cypress, CA (Orange County) and also mention assignment in San Francisco? That seems contradictory; but we must preserve all info. We'll include both statements. Thus schedule: full-time, six-month, Jan-June 2027, location Cypress, CA (Orange County); assignment in San Francisco (maybe a mistake). We'll just include the location as given: Cypress, CA (Orange County). Also mention that candidates must be available for the full Jan-June 2027 assignment in San Francisco. We'll keep both. Benefits: No explicit benefits mentioned besides maybe mentorship, learning. Not specific benefits like health insurance etc. So we should not create Benefits section unless posting actually states them. It mentions "internship-style learning, mentorship, and meaningful project work". That's not typical benefits but could be considered. However instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state mentorship and learning, but not typical benefits. Might be okay to include Benefits? The phrase "internship-style learning, mentorship, and meaningful project work" is under Assignment Details. Could be considered benefits. But to be safe, we could omit Benefits section because it's not explicit like health, 401k, etc. The instruction says "Prefer a few substantive sections over many thin ones." So we might skip Benefits. Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Pay, Schedule. We need to decide whether to split qualifications and skills. The qualifications list includes both knowledge and skills. Could combine into Requirements. But we have also a separate "Skills" heading possible for things like MS Office, programming scripts, configuration control. However those are also in qualifications. To avoid thin sections, we could combine into one "Requirements" section that includes both qualifications and skills. But the instruction allows multiple headings; we should prefer few substantive sections. So maybe we just have About the role, Responsibilities, Requirements, Pay, Schedule. That's five sections. We need to embed lists using

• for any list of duties/requirements/benefits. So Responsibilities list as
  . Requirements list as
  . For About the role and Pay and Schedule we use

  . We must not repeat job title. No markdown. Let's craft HTML. First, About the role:

  About the role

  Join the team that supports released cardiac monitoring products after launch. Our Lifecycle Engineers ensure quality, reliability, compliance, manufacturability, and business continuity across the product lifecycle. The work connects electrical hardware, embedded firmware, manufacturing test systems, configuration control, verification, failure analysis, and technical documentation and the team focuses on supporting existing products through their lifecycle. As a Lifecycle Engineering Co-Op, you will support execution of changes to our electrical (PCBA design), embedded firmware, and manufacturing tooling software that keep our released medical device products safe, compliant, manufacturable, and reliable. You’ll work closely with our product development team of electrical, embedded firmware, and software engineers to resolve field and factory issues, manage obsolescence, improve yield, and maintain regulatory compliance.

  Second, Responsibilities:

  Responsibilities

  • Prototype and test electrical PCB components integrated with prototype product firmware and/or fixture software
  • Support software updates to manufacturing equipment & test systems (fixture software, functional test scripts, ICT/boundary scan integration) to drive improvements to yield, throughput, and reliability.
  • Support embedded software development and updates, ensuring compatibility with hardware and compliance with IEC 62304 and cybersecurity requirements.
  • Support execution of V&V (unit/integration/system), including test plans, protocols, automated regression suites, and reports compliant with IEC 62304 and internal SOPs.
  • Create and maintain engineering drawings, specifications, test methods, protocols, and reports to support design control, manufacturing transfer, and regulatory documentation
  • Work cross-functionally with engineering, quality, and regulatory groups to prepare or review product requirements, test methods, test protocols, and test reports.
  • Assist with failure analysis of production components, assemblies, and field returns
  • Contribute ideas that may support future product improvements or intellectual property
  • Perform lab equipment setup/maintenance as necessary
  Third, Requirements (or Qualifications). We'll use

  Requirements

  and list.

  Requirements

  • Pursuing a BS, MS, or PhD degree in Electrical or Computer Science Engineering or related fields
  • Basic understanding of PCBA design principles, embedded systems, embedded software development (C/C++), and hardware/software integration.
  • Familiar with lab test equipment and comfortable being hands-on in a lab environment (supporting fixture builds, following test protocols)
  • Detail-oriented with excellent troubleshooting and critical thinking skills
  • Strong written and verbal communication skills, and a positive attitude
  • Comfortable working with minimal supervision
  • Values and prioritizes a supportive team environment that enables open-minded and respectful discussion
  • Strong working knowledge of MS office 365 tools (Word, Excel, PowerPoint)
  • Ability to understand and modify different programming scripts such as Java, Python, JavaScript, C#, etc., used for writing automated test scripts and frameworks a plus
  • Familiarity with configuration and change control (Git, branching strategies, code reviews, CI; ECR/ECO, traceability