Test Engineer

We need to output HTML fragment only, with headings

for sections: 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 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. The posting includes: - Job Description (intro paragraph) - Responsibilities (list) - Essential Skills (list) - Additional Skills & Qualifications (list) - Work Environment (paragraph) - #ACTmneng26 (maybe job ID) - minor metadata - Job Type & Location (Contract position based out of Eden Prairie, MN) - could be considered metadata; maybe put in a short

  . - Pay And Benefits (pay range and benefits list) - Workplace Type (Hybrid position) - Application Deadline (date) - maybe minor metadata; could be omitted or put in short

  . - About Actalent (boilerplate about company) - remove as boilerplate? It's not EEO but it's company description; maybe we keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Actalent is not exactly those; but it's generic company description. Might be considered boilerplate? Not sure. Usually we keep substantive info about role, not company fluff. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description may be considered substantive? It's not about the role. Might be considered boilerplate but not explicitly listed. Safer to keep? However they said "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is not that. But it's still generic. I'd lean to keep it as a short paragraph under maybe "About the company"? But we don't have a heading for that. We could include it as a

  after other sections, but not under a heading. The instruction says we can use

  for prose. So we could include a paragraph about Actalent as a

  without a heading. However they said "Prefer a few substantive sections over many thin ones." Might be okay to include as a paragraph. But we need to decide sections: About the role (intro paragraph), Responsibilities, Requirements (maybe combine Essential Skills and Additional Skills & Qualifications?), Qualifications (maybe same as Requirements?), Skills (maybe separate?), Benefits, Pay, Schedule. We have Pay and Benefits combined in posting. We could have a Pay section with pay range, and a Benefits section with list. Or combine into one Benefits section that includes pay? The instruction says use headings for those specific names if content exists. So we can have

  Pay

  with the pay range, and

  Benefits

  with list. Schedule: we have Workplace Type (Hybrid) and maybe schedule not given. No explicit schedule (like full-time, part-time). So we should not create Schedule section because no specific schedule content. We have Work Environment paragraph; could be under About the role or maybe a separate section like "Work Environment" but not in allowed headings. Allowed headings are only those listed. So we must fit content into those headings or as prose without heading. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples; we can use those headings. It doesn't say we cannot use other headings, but likely we should stick to those. So we can put Work Environment prose under About the role or as a

  without heading. We also have Job Type & Location (Contract position based out of Eden Prairie, MN). Could be a short

  without heading. Application Deadline: could be short

  without heading. We must not include filler like "commensurate with experience". Not present. Now we need to preserve all substantive information. Let's extract: Intro paragraph: "The Test Engineer acts as a technical subject matter expert for system testing, driving rigorous test practices, reliability validation, and continuous improvement throughout product development and deployment. This role collaborates closely with Systems, Software, Electrical, Mechanical, and Manufacturing teams to ensure products meet performance, reliability, and customer expectations. Success in this position is measured by product reliability, the quality and completeness of test coverage, effective defect prevention, and on-time execution of test programs." Responsibilities list (each bullet): - Serve as a technical subject matter expert for system-level testing across complex electro-mechanical, electrical, and embedded systems. - Develop, implement, and maintain comprehensive test plans and procedures to ensure robust test coverage for all product requirements. - Drive rigorous test methodologies and practices to validate product performance, reliability, and compliance with specifications. - Plan and execute reliability validation activities, including the use of accelerated testing methods to identify potential failure modes. - Collaborate closely with Systems, Software, Electrical, Mechanical, and Manufacturing teams to define test strategies and ensure testability of designs. - Lead test activities independently from planning through execution, analysis, and reporting, ensuring timely completion of test programs. - Use reliability tools such as DFMEA and FTA to identify, assess, and mitigate risks throughout the product lifecycle. - Analyze test results, identify defects and trends, and work with cross-functional teams to drive corrective actions and defect prevention. - Continuously improve test processes, tools, and methodologies to enhance efficiency, coverage, and product quality. - Ensure that test equipment and setups are appropriate, calibrated, and configured to accurately simulate real-world operating conditions. - Document test procedures, results, and findings clearly and thoroughly to support design validation, verification, and regulatory requirements. - Support deployment and manufacturing activities by providing test expertise, troubleshooting issues, and contributing to production test strategies. Essential Skills list: - Bachelor of Science in Engineering from an ABET accredited institution. - Minimum of 8 years of experience in test engineering, validation, or system verification roles. - Proven experience testing complex electro-mechanical, electrical, and embedded systems. - Demonstrated expertise in test engineering, including test planning and execution for system-level products. - Hands-on experience with test equipment used for validating electro-mechanical and electrical systems. - Experience applying reliability tools such as Design Failure Mode and Effects Analysis (DFMEA) and Fault Tree Analysis (FTA). - Experience using accelerated testing methods to evaluate product reliability and identify potential failure mechanisms. - Ability to lead test activities independently and drive execution from concept through completion. - Strong collaboration skills to work effectively with Systems, Software, Electrical, Mechanical, and Manufacturing teams. - Ability to interpret technical requirements and translate them into structured test plans and procedures. Additional Skills & Qualifications list: - Experience developing and maintaining structured test plans for complex systems. - Experience in system verification and validation for products that integrate mechanical, electrical, and embedded software components. - Proven ability to drive continuous improvement in test processes and methodologies. - Strong analytical and problem-solving skills for interpreting test data and identifying root causes of failures. - Clear and concise documentation skills for recording test procedures, results, and recommendations. Work Environment paragraph: "The Test Engineer works in a collaborative, cross-functional engineering environment, partnering closely with Systems, Software, Electrical, Mechanical, and Manufacturing teams throughout the product lifecycle. The role involves frequent interaction with laboratory and test facilities, including the setup and use of specialized test equipment for electro-mechanical, electrical, and embedded systems. Work typically combines desk-based activities such as test planning, analysis, and documentation with hands-on work in lab or test environments to execute test plans and validate product performance and reliability. The environment emphasizes rigorous engineering practices, structured verification and validation processes, and continuous improvement in test coverage and product quality." Job Type & Location: "This is a Contract position based out of Eden Prairie, MN." Pay And Benefits: includes pay range and benefits list. Pay range: "$48.00 - $64.00/hr." Benefits list (if eligible): 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). Workplace Type: "This is a hybrid position in Eden Prairie,MN." Application Deadline: "This position is anticipated to close on Sep 25, 2026." About Actalent: paragraph about company. We need to remove boilerplate like EEO etc. The About Actalent includes some EEO statements later; we should remove those. The About Actalent paragraph includes: "Actalent is a global leader in engineering and sciences services and talent solutions...." That's okay to keep? It's not EEO. Then later there is EEO statement: "The company is an equal opportunity employer..." and other statements about accommodation, San Francisco Fair Chance, Massachusetts Lie Detector, Use of AI. Those should be removed as boilerplate. So we keep only the first part about Actalent being a global leader etc., up to before the EEO statement. Let's extract: "Actalent is a global leader in engineering and sciences services and talent solutions. We help visionary companies advance their engineering and science initiatives through access to specialized experts who drive scale, innovation and speed to market. With a network of almost 20,000 consultants and 5,000 clients across the U.S., Canada, Asia and Europe, Actalent serves many of the Fortune 500. We are proud to be an Engineering News-Record (ENR) Top 500 Design Firm for our engineering design services and a ClearlyRated Best of Staffing® winner for both client and talent service." That seems substantive enough to keep as a paragraph. Now we need to output HTML fragment only. We'll structure:

  About the role

  Intro paragraph.

  Responsibilities

  • ...
  ...

  Requirements

  Maybe combine Essential Skills and Additional Skills & Qualifications into Requirements? Or we could have Requirements for Essential Skills, Qualifications for Additional Skills & Qualifications, Skills for something else? But we have both Essential Skills and Additional Skills & Qualifications; they are both skill/qualification lists. Could treat Essential Skills as Requirements, Additional Skills & Qualifications as Qualifications. Or we could have Skills section for both? Let's see allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for Requirements (essential skills), Qualifications (additional skills), Skills (maybe we could merge but we have both). To avoid thin sections, we could combine Essential Skills and Additional Skills & Qualifications into a single Skills section, but then we would lose distinction. However the instruction says prefer a few substantive sections over many thin ones. Having both Requirements and Qualifications might be thin if each list is short? They are moderate length. Could be okay. But we also have Skills heading; we could put something else there like maybe "Key Skills" but we don't have separate content. Might be better to use Requirements for Essential Skills, Qualifications for Additional Skills & Qualifications, and omit Skills heading (since no separate content). Or we could