Product Engineer

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. 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. Include a section ONLY when 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 posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Sections present: - What You'll Do (Responsibilities) - What You'll Bring (Qualifications/Requirements) - Why Engineers Are Interested in This Role (maybe Benefits? Actually it's more about role appeal) - Job Type & Location (maybe location) - Pay And Benefits (Pay and Benefits) - Workplace Type (Schedule? Actually it's onsite) - Application Deadline (maybe not needed? It's metadata; we can drop or put in short p) - About Actalent (company description) - maybe not needed? It's boilerplate? It's about company, but not required? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Actalent" is not exactly boilerplate but could be considered company description; but we need to preserve ALL substantive information. However, we might consider it as not essential to the job? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep substantive info about the role, not necessarily company description unless it's substantive. The "About Actalent" is generic company info; could be considered boilerplate? It's not about the job. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove company description. However, we might keep it as a short paragraph under maybe "About the company" but we don't have a heading for that. The allowed headings are limited to those list. We could put it under a

  without heading? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings; we could also have other headings? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections; we could also have other headings if needed, but they gave examples. Probably we should stick to those headings. So we need to map content to those sections. We have: - Responsibilities: "What You'll Do" content. - Requirements/Qualifications: "What You'll Bring" includes Required Qualifications and Preferred Qualifications. - Skills: maybe we can extract skills from responsibilities and qualifications? But we could also have a Skills section if we have specific skills list. The posting includes many skills: SolidWorks, DFMEA/PFMEA, load testing, etc. Could be placed under Skills. - Benefits: from Pay And Benefits section. - Pay: from Pay And Benefits section (pay range). - Schedule: from Workplace Type (fully onsite) and maybe travel 10-15% (that's schedule/travel). Also maybe "Application Deadline" not schedule. So we can have Schedule section with onsite and travel. - About the role: maybe we can have a brief summary? But we already have Responsibilities. Could combine About the role with Responsibilities? The instruction says prefer a few substantive sections over many thin ones. So we could have sections: Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Skills if we want to separate. But we need to avoid filler headings. If we create a Skills section, we need to ensure it has substantive content (list of skills). We can extract skills from responsibilities and qualifications. Let's list substantive content: Responsibilities (What You'll Do): - Lead Product Validation & Testing: Execute comprehensive product validation activities, including load testing, cycle testing, Factory Acceptance Testing (FAT), and performance verification. - Develop and execute test plans designed to validate product durability, reliability, and overall performance. - Analyze test results, identify failure modes, and implement corrective actions utilizing DFMEA and PFMEA methodologies. - Investigate product performance issues and drive engineering solutions based on data and testing outcomes. - Drive Product Development: Support major distribution-focused customers by executing engineering projects following concept approval. - Create and maintain engineering drawings, assemblies, and Bills of Material (BOMs) using SolidWorks. - Develop tolerance specifications, material requirements, coating specifications, and testing standards. - Apply Design for Manufacturability (DFM) principles to optimize product cost, performance, and production efficiency. - Collaborate with Suppliers & Manufacturing: Partner with domestic and international suppliers to clarify drawings, evaluate material substitutions, and improve product manufacturability. - Review supplier capabilities and recommend engineering improvements that reduce cost without sacrificing performance or quality. - Prepare scopes of work for third-party testing laboratories and evaluate test results for technical accuracy and validity. - Support supply chain initiatives through material evaluations, sourcing decisions, and supplier collaboration. - Own Engineering Projects: Independently manage projects from concept handoff through testing, validation, implementation, and launch. - Coordinate with manufacturing, supply chain, and external partners to ensure successful product deployment. - Spend time in testing environments, on the production floor, and at customer locations supporting installations and product evaluations. - Travel approximately 10-15% for customer visits, product testing, and implementation activities. Qualifications (What You'll Bring): Required: - Bachelor's degree in Mechanical Engineering or related engineering discipline. - 2-5 years of product engineering experience focused on design, testing, validation, and product development. - Strong proficiency in SolidWorks, including detailed drawings, assemblies, and BOM creation. - Strong mechanical engineering fundamentals with the ability to apply theory to real-world product challenges. - Experience performing and analyzing load testing, cycle testing, FATs, or similar validation activities. - Experience developing structured test procedures, validation plans, and engineering documentation. - Working knowledge of DFMEA, PFMEA, root cause analysis, and structured problem-solving methodologies. - Understanding of Design for Manufacturability (DFM) principles. - Ability to independently lead engineering projects with minimal oversight. - Hands-on approach to engineering, including direct involvement in testing, troubleshooting, and product trials. - Experience working with steel fabrication, structural products, or welded assemblies. - Ability to travel up to 15%. Preferred: - Experience supporting products within distribution, warehousing, material handling, or industrial equipment environments. - Background collaborating with overseas manufacturers and suppliers. - Experience evaluating materials, coatings, and manufacturing processes. - Familiarity with supplier development and cost-reduction initiatives. - Exposure to light manufacturing or supply-chain-driven product environments. Why Engineers Are Interested in This Role: - Own projects from design release through validation and implementation. - Balance CAD design, hands-on testing, manufacturing support, and supplier collaboration. - Work directly with customers and influence product performance in real-world applications. - Gain exposure to testing, reliability engineering, DFMEA/PFMEA, and product commercialization. - Join a role where engineering decisions directly impact product quality, cost, and customer success. Job Type & Location: - This is a Contract to Hire position based out of Elk Grove Village, IL. Pay And Benefits: - Pay range: $45.00 - $48.00/hr. - Individual compensation depends on many factors. - Benefits (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 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 fully onsite position in Elk Grove Village, IL. Application Deadline: - This position is anticipated to close on Sep 30, 2026. About Actalent: (company description) - maybe we can drop as boilerplate? It's not about the job. 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 could be considered company description. However, we might keep it as a short paragraph under maybe "About the company" but we don't have that heading. Could we include it as a

  without heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests we use those. It also says "Output ONLY the HTML fragment — no /, no markdown code fences." So we can include any HTML we want, but we should follow the rules. Probably safest to include only the sections we have substantive content for, using the allowed headings. We can omit About Actalent. We also need to remove duplicated lines. I don't see duplicates. Now we need to decide which sections to include. We have substantive content for: - Responsibilities (What You'll Do) - Requirements (What You'll Bring) - could split into Required and Preferred but we can combine. - Skills (maybe we can extract a list of skills: SolidWorks, DFMEA/PFMEA, load testing, cycle testing, FAT, test plan development, tolerance specs, material requirements, coating specs, DFM, supplier collaboration, project management, travel, etc.) - Benefits (from Pay And Benefits) - Pay (from Pay And Benefits) - Schedule (Workplace Type + travel) - Job Type & Location (maybe we can incorporate into Schedule or a separate section like "About the role"? But we have a heading "About the role" allowed. Could put job type and location there. We need to avoid filler headings. So we should only create sections where we have real specific content. Let's map: - About the role: Could include job type, location, maybe a brief summary of the role? But we already have Responsibilities. Could put job type and location there. - Responsibilities: as above. - Requirements: as above (maybe split into Required and Preferred but we can keep as list). - Skills: we could list specific skills: SolidWorks, DFMEA/PFMEA, load testing, cycle testing, FAT, test plan development, tolerance specification, material requirements, coating specifications, DFM, supplier evaluation, project management, travel, etc. But many of these are already in Responsibilities/Requirements. Creating a Skills section might be redundant but allowed if we have substantive content. However, the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Skills into Requirements or Responsibilities. Better to have Requirements include qualifications and skills. So we can have Requirements section that includes both required qualifications and skills. - Benefits: we have. - Pay: we have. - Schedule: we have (onsite, travel 10-15%). We could also have a section "Job Type & Location" but we could incorporate into About the role or Schedule. Since Schedule already includes onsite and travel, we could add location there. But location is not exactly schedule; it's location. However, we could put location in About the role. Let's decide sections: - About the role: includes job type (