Product Development Engineer

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. No job title heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Preserve all substantive info. We need to parse the posting. Key info: - Company: Aptiv - Job Title: Product Development Engineer (but we don't output heading) - Location: Remote (Melbourne, FL mentioned) - Department: Engineering PCG - Reports To: Product Manager - Job Type: Full Time - Summary: At Aptiv, we inspire... seeking a high-caliber, innovative Product Development Engineer to take responsibility for full lifecycle of new product design and development (NPD), from initial concept through production launch. You will create CAD models, conduct FEA/testing, select materials, collaborate with cross-functional teams to ensure products meet design, cost, regulatory requirements. Operating within core values of Accountability, Collaboration, Empowerment (ACE), you will work directly with engineering teams, PCG, Core Engineering to drive innovation, sustainability, manufacturability while impacting business strategy and company goals. - Leadership & Core Responsibilities: includes bullet points (but they are paragraphs). We need to extract responsibilities. List of responsibilities: - Engineering Design & Development - Product Design & Lifecycle Management: Perform product design and development of new products to meet customer-funded programs and NPI projects in accordance with site capabilities, engineering standards, systems, procedures, and policies. - Technical Documentation & Modeling: Specify designs, document materials, components, and performance specifications; create detailed drawings, procedures, test specifications, and BOMs using CAD (SolidWorks) and PDM/ERP systems. - Feasibility & Engineering Support: Perform research to determine product design/development feasibility (FAE), initiate and process ECOs, and follow designs through production by soliciting feedback from process engineering. - Cross-Functional Collaboration & Process Management - Proposal & Customer Technical Support: Review and provide technical content for proposal/quote responses (specification reviews, design concept drawings, performance limits) to applications and sales teams. - Cross-Functional NPI Integration: Actively participate across PCG on NPI projects, Contract Review, Process Specifications, Design Release, MRBs, RMAs, CARs, and standard processes including DFM, DFMEA, and PFMEA. - Position Requirements Education & Technical Qualifications - Education: Bachelor's Degree in Engineering. - Experience: 3+ years of progressive experience in product design, development, or R&D (experience in connector design or electronics industry is a plus). - Industry Domain: Knowledge of injection molding, stamping, and machined part design techniques to meet cost and manufacturability targets. - Regulatory & Standards Compliance: General understanding of drawings, Mil-Specs, Industry standards, and customer requirements. - Certifications & Competencies - Technical Proficiency: Proficiency in CAD design (SolidWorks preferred), GD&T, and Drafting. - Systems Proficiency: Experience in ERP workflow processes (BOM development, ECO, routing), PDM systems, Google Enterprise, ADP, and Salesforce. - Core Competencies: Creative and analytical problem solver; excellent organization, communication, and presentation skills to act as a direct technical liaison with internal and external functions. - Compensation, Benefits & Legal - Total Rewards & Compensation - Incentive Compensation: Eligible for incentive compensation/bonus structure. - Benefits & Perks: Employees receive a comprehensive benefits package featuring health coverage, 401(k) with company match, paid time off, and career development resources. - EEO Statement (remove) - Connected etc (remove) - Common questions (remove) - Also note: "Benefits 401(k) with company match incentive compensation/bonus" appears earlier. - Pay: The posting does not list pay. So we should NOT include Pay section because no specific pay info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated (health coverage, 401(k) with company match, paid time off, career development resources). So we can include Benefits section. - Schedule: Not mentioned (full-time is mentioned but schedule not specific). We could include Schedule? The posting says Full Time but not schedule details like hours. Probably we should not create Schedule section unless explicit schedule info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Full Time but not schedule details like "Monday-Friday 9-5". Might be considered schedule? Safer to omit Schedule. - About the role: Could be a section summarizing the role. We have summary paragraph. Could put that under About the role. - Responsibilities: we have responsibilities list. - Requirements: we have education, experience, industry domain, regulatory. - Qualifications: maybe combine with Requirements? But we can have Qualifications for certifications & competencies. - Skills: could list technical proficiencies: CAD (SolidWorks), GD&T, Drafting, ERP workflow, PDM, Google Enterprise, ADP, Salesforce, FEA/testing, material selection, injection molding, stamping, machined part design, etc. - Benefits: health coverage, 401(k) with company match, paid time off, career development resources. We must not repeat job title as heading. Use

for each section heading. We need to output only HTML fragment, no /, no markdown. We must preserve all substantive information; do not invent or summarize away detail. So we need to include details like specific systems, etc. We need to use

• for any list of duties/requirements/benefits. So for responsibilities, requirements, qualifications, skills, benefits we should use lists. We need to use

  for prose. We need to avoid filler like "commensurate with experience". Not present. We need to remove duplicated lines. Let's craft sections:

  About the role

  At Aptiv, we inspire the world’s most innovative teams by doing the right thing, the right way. We are seeking a high‑caliber, innovative Product Development Engineer to take responsibility for the full lifecycle of new product design and development (NPD), from initial concept through production launch. In this role you will create CAD models, conduct FEA/testing, select materials, and collaborate with cross‑functional teams to ensure products meet design, cost, and regulatory requirements. Operating within our core values of Accountability, Collaboration, and Empowerment (ACE), you will work directly with engineering teams, PCG, and Core Engineering to drive innovation, sustainability, and manufacturability while directly impacting business strategy and company goals.

  Responsibilities

  • Product Design & Lifecycle Management: Perform product design and development of new products to meet customer‑funded programs and NPI projects in accordance with site capabilities, engineering standards, systems, procedures, and policies.
  • Technical Documentation & Modeling: Specify designs, document materials, components, and performance specifications; create detailed drawings, procedures, test specifications, and BOMs using CAD (SolidWorks) and PDM/ERP systems.
  • Feasibility & Engineering Support: Perform research to determine product design/development feasibility (FAE), initiate and process ECOs, and follow designs through production by soliciting feedback from process engineering.
  • Proposal & Customer Technical Support: Review and provide technical content for proposal/quote responses (specification reviews, design concept drawings, performance limits) to applications and sales teams.
  • Cross‑Functional NPI Integration: Actively participate across PCG on NPI projects, Contract Review, Process Specifications, Design Release, MRBs, RMAs, CARs, and standard processes including DFM, DFMEA, and PFMEA.

  Requirements

  • Education: Bachelor's Degree in Engineering.
  • Experience: 3+ years of progressive experience in product design, development, or R&D (experience in connector design or electronics industry is a plus).
  • Industry Domain: Knowledge of injection molding, stamping, and machined part design techniques to meet cost and manufacturability targets.
  • Regulatory & Standards Compliance: General understanding of drawings, Mil‑Specs, industry standards, and customer requirements.

  Qualifications

  • Technical Proficiency: Proficiency in CAD design (SolidWorks preferred), GD&T, and drafting.
  • Systems Proficiency: Experience in ERP workflow processes (BOM development, ECO, routing), PDM systems, Google Enterprise, ADP, and Salesforce.
  • Core Competencies: Creative and analytical problem solver; excellent organization, communication, and presentation skills to act as a direct technical liaison with internal and external functions.

  Skills

  • CAD modeling (SolidWorks)
  • GD&T and drafting
  • FEA and testing
  • Material selection for thermoplastics
  • Injection molding design
  • Stamping and machined part design
  • ERP workflow (BOM development, ECO, routing)
  • PDM systems
  • Google Enterprise, ADP, Salesforce
  • DFM, DFMEA, PFMEA
  • Technical documentation and BOM creation
  • Cross‑functional collaboration

  Benefits

  • Health coverage
  • 401(k) with company match
  • Paid time off
  • Career development resources
  • Eligible for incentive compensation/bonus structure
  We should not include Pay or Schedule sections. Check for any duplicated content: we have incentive compensation also in Benefits; it's okay. We need to ensure we didn't include any boilerplate like EEO, legal, etc. We removed. Check for any mention of location: Remote (Melbourne, FL). Should we include location? Could be part of About the role? The instruction: 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. Location is minor metadata; we could include a short

  somewhere. Perhaps add a

  after About the role: "Location: Remote (Melbourne, FL)." But we need to preserve all substantive information. Location is substantive. So we should include it. Where? Could add a

  under About the role or a separate

  About the role

  then a

  that includes summary and location. Or we could add a separate

  Location

  but that's not a prescribed heading; we should use only the prescribed headings? 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 but we can use those headings. It didn't forbid other headings, but better to stick to those. We can fold location into About the role paragraph. Thus modify About the role paragraph to include location. Let's rewrite About the role:

  At Aptiv, we inspire the world’s most innovative teams by doing the right thing, the right way. We are seeking a high‑caliber, innovative Product Development Engineer to take responsibility for the full lifecycle of new product design and development (NPD), from initial concept through production launch. In this role you will create CAD models, conduct FEA/testing, select materials, and collaborate with cross‑functional teams to ensure products meet design, cost, and regulatory requirements. Operating within