Firmware Test Engineer

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections with real content. No job title heading. No Job ID etc. Remove boilerplate: navigation, EEO, legal, etc. Also remove application instructions, etc. Keep substantive info. We need to parse the posting. Job Title: Firmware Test Engineer (already shown elsewhere, not heading). Job Description: We are seeking a hands-on Firmware Test Engineer to lead verification and validation activities for a Class III medical device program. You will be responsible for developing, executing, and maintaining firmware verification testing, ensuring requirements traceability, supporting regulatory submissions, and driving testing efforts during the final stages of product development. The ideal candidate will contribute as an individual contributor while growing their skills and responsibilities. That's prose about role. Could be "About the role" section. Responsibilities: list bullet points. Essential Skills: list bullet points. Additional Skills & Qualifications: list bullet points. Work Environment: includes location, onsite, 3-4 days per week, 10 days PTO, 10 paid holidays, high visibility, etc. Could be "Work Environment" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Work Environment" not in list; maybe we can incorporate into About the role or Benefits? But we should only use allowed headings. However we could treat "Work Environment" as part of "About the role" or maybe "Skills"? Not ideal. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning these are examples, not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we can also include other headings if they are appropriate? The examples suggest those are typical sections; but they didn't forbid others. However they say "Prefer a few substantive sections over many thin ones." So we could combine work environment into About the role or Benefits? But PTO and holidays are benefits. So we can put PTO and holidays under Benefits. Work environment location and hybrid could be under About the role or maybe a separate "Work Environment" not listed; but maybe we can put under About the role. Pay And Benefits: we have pay range and benefits list. So we need Pay and Benefits sections. They said include Pay and Benefits sections only if posting actually states them. Yes, they state pay range and benefits. So we need separate

Pay

and

Benefits

? Or combine? The examples list Pay and Benefits separate. We'll do separate. Schedule: they mention expected presence 3-4 days per week, hybrid position. That's schedule info. So we can have Schedule section. Requirements: maybe we can treat Essential Skills as Requirements? Or Qualifications? The posting has Essential Skills and Additional Skills & Qualifications. We could map Essential Skills to Requirements, Additional Skills & Qualifications to Qualifications. Or we could combine into Skills. But we have both Requirements and Qualifications headings allowed. Let's use Requirements for Essential Skills, Qualifications for Additional Skills & Qualifications. Skills: maybe we could also have a Skills section for technical skills like I2C, SPI, etc. But we already have those in Essential Skills. Could combine. We need to avoid duplication. Let's decide: - About the role: introductory paragraph (job description paragraph). - Responsibilities: bullet list from Responsibilities. - Requirements: bullet list from Essential Skills. - Qualifications: bullet list from Additional Skills & Qualifications. - Benefits: bullet list from benefits (medical, dental, vision, etc.) - Pay: paragraph with pay range. - Schedule: paragraph with hybrid, 3-4 days per week, location maybe. We must not repeat job title as heading. No Job ID. Remove boilerplate: navigation, EEO, equal opportunity, scam warning, etc. Also remove "About Actalent" and all that legal stuff. Also remove "Application Deadline". Also remove "Job Type & Location" maybe we incorporate location into Schedule or About the role. But we should not include "Job Type & Location" as heading. We'll incorporate location into Schedule or About the role. We must preserve all substantive information. So we need to keep location (Maple Grove, MN), hybrid, 3-4 days per week, contract position, etc. Also mention that it's a contract position. Also mention that it's high visibility role, etc. Also mention that it's a Class III medical device program. Also mention that it's a hands-on Firmware Test Engineer. Also mention that it's a critical product milestone. Also mention ability to help build verification organization, cross-functional exposure, influence process improvements. Also mention that it's a temporary role (contract). Also mention that benefits may be subject to change, eligibility requirements apply, etc. We need to keep that. We need to avoid repeating lines. Ensure we don't include boilerplate like "We are proud to be an Engineering News-Record (ENR) Top 500 Design Firm..." etc. Remove that. Also remove "If you would like to request a reasonable accommodation..." etc. Remove "San Francisco Fair Chance Ordinance..." etc. Remove "Massachusetts Lie Detector:" etc. Remove "Use of Artificial Intelligence (AI):" etc. Now craft HTML. We'll output:

About the role

We are seeking a hands-on Firmware Test Engineer to lead verification and validation activities for a Class III medical device program. You will be responsible for developing, executing, and maintaining firmware verification testing, ensuring requirements traceability, supporting regulatory submissions, and driving testing efforts during the final stages of product development. The ideal candidate will contribute as an individual contributor while growing their skills and responsibilities. This is a contract position located onsite in Maple Grove, MN with an expected presence of 3‑4 days per week (hybrid). The role offers high visibility during a critical product milestone, providing the opportunity to make a direct impact on a Class III life‑sustaining medical device and to help build a verification organization as the team expands, with strong cross‑functional exposure to Firmware, Systems, Quality, and Regulatory teams and the ability to influence process improvements and testing strategy.

Responsibilities

• Execute firmware verification and validation activities for a regulated medical device.
• Review, update, refine, and execute existing verification plans and test protocols.
• Author and maintain Verification Plans, Test Protocols, Test Reports, and Design History File (DHF) documentation.
• Establish and maintain requirements‑to‑test‑to‑results traceability.
• Perform manual firmware and system‑level testing.
• Conduct risk‑based testing aligned with medical device development standards.
• Participate in risk assessments and mitigation activities.
• Support FDA submission readiness and compliance activities.
• Investigate test failures and collaborate with engineering teams on root cause analysis.
• Support commercialization activities and future remediation efforts.
• Contribute to the development of scalable verification processes and future team expansion.

Requirements

• Experience performing firmware and embedded system testing.
• Strong understanding of verification and validation methodologies.
• Experience with requirements‑based testing.
• Experience with risk‑based testing.
• Ability to build and maintain requirements traceability matrices.
• Hands‑on testing experience with embedded devices and firmware‑controlled products.
• Knowledge of I2C and SPI communication protocols.
• Experience with hardware/software integration testing.
• Experience working within a regulated environment.
• Experience creating and maintaining DHF documentation, Verification Plans, Test Protocols, and Test Reports.
• Strong documentation and technical writing skills.

Qualifications

• Class II or Class III medical device experience.
• FDA submission support experience.
• Pump‑based medical device experience.
• Electromechanical device experience.
• Exposure to automation testing frameworks.
• Experience scaling verification processes or teams.

Benefits

• Medical, dental & vision
• Critical Illness, Accident, and Hospital
• 401(k) Retirement Plan – Pre‑tax and Roth post‑tax contributions available
• Life Insurance (Voluntary Life & AD&D for the employee and dependents)
• Short and long‑term disability
• Health Spending Account (HSA)
• Transportation benefits
• Employee Assistance Program
• Time Off/Leave (PTO, Vacation or Sick Leave)

Pay

The pay range for this position is $50.00 – $55.00 per hour. Individual compensation offered within this range will depend on qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job‑related factors.

Schedule

This is a hybrid position requiring onsite presence 3‑4 days per week in Maple Grove, MN. The role is a contract (temporary) position.

Check we didn't include any boilerplate. We kept location, contract, etc. We removed "Job Type & Location" heading. We kept "contract position" in About the role and Schedule. We kept "10 days of PTO and 10 paid holidays" – we included PTO in Benefits list but not explicit 10 days; we just listed "Time Off/Leave (PTO, Vacation or Sick Leave)". Might be okay but we lost the specific 10 days and 10 paid holidays. Should we preserve that? The instruction: Preserve ALL substantive information. So we need to include the specific 10 days PTO and 10 paid holidays. We can add a line in Benefits: "10 days of PTO and 10 paid holidays". Or incorporate into Time Off/Leave. Let's add a separate bullet: "10 days of PTO and 10 paid holidays". Also we have "Time Off/Leave (PTO, Vacation or Sick Leave)" maybe redundant. Better to combine: "Time Off/Leave: 10 days PTO and 10 paid holidays". Let's do that. Also we need to keep "This is a high visibility role during a critical product milestone, providing the opportunity to make a direct impact on a Class III life-sustaining medical device." Already in About the role. We kept "You will have the ability to help build a verification organization as the team expands and have strong cross-functional exposure to Firmware, Systems, Quality, and Regulatory teams." Included. We kept "The role offers the chance to influence process improvements and testing strategy." Included. We kept "If eligible, the benefits available for this temporary role may include the following:" we listed benefits. We kept "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms." Should we keep that? It's substantive but maybe considered boilerplate? It's about benefits eligibility. It's not legal boilerplate; it's about benefits. Might be considered substantive. However the instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly legal but it's about benefits eligibility. Might be okay to keep but could be considered boilerplate. I'd keep a brief note