PRODUCT DEVELOPMENT DESIGN ENGINEER
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for any list of duties/requirements/benefits, and
for prose.
- Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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.
- Output ONLY the HTML fragment — no /, no markdown code fences.
Now, analyze the provided job posting.
The posting starts with a company description: "At TE, you will unleash your potential working with people from diverse backgrounds and industries to create a safer, sustainable and more connected world." That's a general company intro.
Then "Job Overview" with a paragraph.
Then "Job Requirements" with a list of bullet points (duties). Actually the heading says "Job Requirements" but the content is responsibilities/duties. The user wants headings like "Responsibilities" or "Requirements". I need to map appropriately.
Then "What Your Background Should Look Like" which is qualifications/requirements.
Then "About Te Connectivity" which is company description.
Then "Compensation" with salary range.
Then "Benefits" with list.
Then "EOE, Including Disability/Vets" and "IMPORTANT NOTICE REGARDING RECRUITMENT FRAUD" which are boilerplate to remove.
I need to create sections only when there is real content.
Potential sections:
- About the role (or Job Overview) - there is a paragraph.
- Responsibilities (or Duties) - the list under "Job Requirements" (though heading says Job Requirements, but content is responsibilities). I'll use "Responsibilities".
- Requirements (or Qualifications) - the list under "What Your Background Should Look Like".
- Benefits - there is a list.
- Pay (or Compensation) - there is a salary range.
The company description "About Te Connectivity" could be included as "About the company" but the user didn't list that as a heading example. However, they said "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So "About the company" is not listed, but we could include it as a section if it's substantive. The posting has a paragraph about TE Connectivity. I think it's okay to include as "About the company" or "About TE Connectivity". But the user said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That's not exhaustive; they said "e.g." So we can add other relevant headings. However, they also said "Prefer a few substantive sections over many thin ones." The company description is a paragraph, could be included as a section.
But note: the first paragraph "At TE, you will unleash your potential..." is also company intro. Might combine with "About TE Connectivity". However, the posting has two company descriptions: one at top, one later. I'll combine into one "About the company" section.
Now, structure:
- About the role
with the Job Overview paragraph.
- Responsibilities
with the list from "Job Requirements" (the bullet points). Actually the bullet points are under "Job Requirements" but they are responsibilities. I'll use that list.
- Requirements
with the list from "What Your Background Should Look Like".
- About TE Connectivity
with the company description paragraph.
- Pay
with the compensation details (salary range).
- Benefits
with the benefits list.
Check for any schedule information? Not present. So no Schedule section.
Now, ensure we don't include boilerplate: EEO, fraud notice, etc. Remove.
Also, the "Compensation" section includes "Competitive base salary commensurate with experience: $140,000 – $150,000 (subject to change dependent on physical location) Posted salary ranges are made in good faith. TE Connectivity reserves the right to adjust ranges depending on the experience/qualification of the selected candidate as well as internal and external equity. Total Compensation = Base Salary + Incentive(s) + Benefits". That's substantive, so include.
Benefits: "A comprehensive benefits package including health insurance, 401(k), disability, life insurance, employee stock purchase plan, paid time off and voluntary benefits." That's a list, but it's a sentence. I'll convert to a list.
Now, write HTML.
Use for headings,
for prose,
- for lists.
For the responsibilities list: each bullet point is a duty. I'll wrap each in
- .
For requirements: each bullet point is a requirement.
For benefits: I'll split the sentence into list items.
Now, produce the HTML fragment.
Let's draft:
About the role
In this role, you will work on cutting-edge connectivity solutions for the automotive industry in an environment shaped by emerging technologies, dynamic projects, and continuous development. We are looking for individuals who are eager to learn, challenge existing boundaries, and transform technical ideas into innovative products. We value motivation, a willingness to learn, and a passion for technology just as much as existing technical expertise.
Responsibilities
- Monitor market trends, emerging technologies, and industry standards to identify innovation opportunities.
- Translate customer requirements and technology roadmaps into product and platform strategies.
- Collaborate with development engineering, customers, business development, product management, sales, manufacturing engineering, test laboratories, and prototype resources to lead the design and development of connectors, cable assemblies, components, and platform or custom solutions for next-generation automotive connectivity solutions.
- Partner with global Data Connectivity teams and support marketing, sales, and customers in technical discussions, meetings, and site visits.
- Define and evaluate new product concepts, materials, and design approaches that deliver technical and/or cost advantages.
- Create complex mechanical designs using parametric and non-parametric CAD tools.
- Perform and interpret mechanical simulations to optimize product performance, reliability, and durability.
- Build and validate prototypes using rapid prototyping methods and apply test results to iterative design improvements.
- Support launch teams through production release and troubleshoot design issues during startup.
- Contribute to technology roadmaps and identify future product and process innovations.
- Travel domestically and internationally as required.
Requirements
- Bachelor’s degree in Mechanical Engineering or a related engineering discipline; master’s degree preferred.
- 7-10 years of relevant mechanical design and product development experience, preferably in an automotive or industrial environment.
- Advanced CAD capability and experience creating complex mechanical designs; experience with PTC Creo and Ansys SpaceClaim is a plus.
- Experience with mechanical simulation tools, including structural, thermal, or multi-physics analysis in Ansys Mechanical, is a plus.
- Hands-on experience with connector crimp tooling, cable assembly equipment, rapid prototyping, and prototype development.
- Customer-focused communicator with strong technical presentation and stakeholder management skills.
- Structured, independent, and creative working style with the ability to collaborate effectively across international teams.
About TE Connectivity
TE Connectivity plc (NYSE: TEL) is a global industrial technology leader creating a safer, sustainable, productive, and connected future. As a trusted innovation partner, our broad range of connectivity and sensor solutions enable the distribution of power, signal and data to advance next-generation transportation, energy networks, automated factories, data centers enabling artificial intelligence, and more. Our more than 90,000 employees, including 10,000 engineers, work alongside customers in approximately 130 countries. In a world that is racing ahead, TE ensures that EVERY CONNECTION COUNTS. Learn more at www.te.com and on LinkedIn, Facebook, WeChat, Instagram and X (formerly Twitter).
Pay
Competitive base salary commensurate with experience: $140,000 – $150,000 (subject to change dependent on physical location). Posted salary ranges are made in good faith. TE Connectivity reserves the right to adjust ranges depending on the experience/qualification of the selected candidate as well as internal and external equity. Total Compensation = Base Salary + Incentive(s) + Benefits.
Benefits
- Health insurance
- 401(k)
- Disability insurance
- Life insurance
- Employee stock purchase plan
- Paid time off
- Voluntary benefits
Check for any missing info: The initial paragraph "At TE, you will unleash your potential..." is not included. Could be part of "About the role" or "About TE Connectivity". I'll include it in "About the role" maybe as a preamble. But the "About the role" already has the Job Overview paragraph. The first paragraph is more company mission. Could add as a separate paragraph before "About the role"? But the user said not to repeat job title as heading. The first paragraph is not a heading. I could include it as a before the first heading? But the output should be sections with headings. The user said "Output ONLY the HTML fragment". It could start with a
then headings. However, they said "use
for section headings". They didn't forbid a leading paragraph. But they said "include a section ONLY when the posting has real, specific content for it". The first paragraph is generic company mission. Might be okay to include as a
before sections. But to be safe, I'll incorporate it into "About the role" or "About TE Connectivity". I'll add it as a paragraph in "About TE Connectivity" maybe.
Actually, the "About TE Connectivity" section already has a detailed description. The first paragraph is a tagline. I'll include it as a separate paragraph before the headings? But the user might expect only sections. I think it's fine to have a leading
with that tagline. However, the instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So I can output a fragment that includes a
then headings. But they said "use
for section headings". They didn't say you can't have other elements. But they said "include a section ONLY when the posting has real, specific content for it". The tagline is not a section. I'll include it as a
before the first heading.
Alternatively, I could create a section "About the company" with that tagline and the
for prose. - Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. - Output ONLY the HTML fragment — no /, no markdown code fences. Now, analyze the provided job posting. The posting starts with a company description: "At TE, you will unleash your potential working with people from diverse backgrounds and industries to create a safer, sustainable and more connected world." That's a general company intro. Then "Job Overview" with a paragraph. Then "Job Requirements" with a list of bullet points (duties). Actually the heading says "Job Requirements" but the content is responsibilities/duties. The user wants headings like "Responsibilities" or "Requirements". I need to map appropriately. Then "What Your Background Should Look Like" which is qualifications/requirements. Then "About Te Connectivity" which is company description. Then "Compensation" with salary range. Then "Benefits" with list. Then "EOE, Including Disability/Vets" and "IMPORTANT NOTICE REGARDING RECRUITMENT FRAUD" which are boilerplate to remove. I need to create sections only when there is real content. Potential sections: - About the role (or Job Overview) - there is a paragraph. - Responsibilities (or Duties) - the list under "Job Requirements" (though heading says Job Requirements, but content is responsibilities). I'll use "Responsibilities". - Requirements (or Qualifications) - the list under "What Your Background Should Look Like". - Benefits - there is a list. - Pay (or Compensation) - there is a salary range. The company description "About Te Connectivity" could be included as "About the company" but the user didn't list that as a heading example. However, they said "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So "About the company" is not listed, but we could include it as a section if it's substantive. The posting has a paragraph about TE Connectivity. I think it's okay to include as "About the company" or "About TE Connectivity". But the user said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That's not exhaustive; they said "e.g." So we can add other relevant headings. However, they also said "Prefer a few substantive sections over many thin ones." The company description is a paragraph, could be included as a section.
But note: the first paragraph "At TE, you will unleash your potential..." is also company intro. Might combine with "About TE Connectivity". However, the posting has two company descriptions: one at top, one later. I'll combine into one "About the company" section.
Now, structure:
- About the role
with the Job Overview paragraph.
- Responsibilities
with the list from "Job Requirements" (the bullet points). Actually the bullet points are under "Job Requirements" but they are responsibilities. I'll use that list.
- Requirements
with the list from "What Your Background Should Look Like".
- About TE Connectivity
with the company description paragraph.
- Pay
with the compensation details (salary range).
- Benefits
with the benefits list.
Check for any schedule information? Not present. So no Schedule section.
Now, ensure we don't include boilerplate: EEO, fraud notice, etc. Remove.
Also, the "Compensation" section includes "Competitive base salary commensurate with experience: $140,000 – $150,000 (subject to change dependent on physical location) Posted salary ranges are made in good faith. TE Connectivity reserves the right to adjust ranges depending on the experience/qualification of the selected candidate as well as internal and external equity. Total Compensation = Base Salary + Incentive(s) + Benefits". That's substantive, so include.
Benefits: "A comprehensive benefits package including health insurance, 401(k), disability, life insurance, employee stock purchase plan, paid time off and voluntary benefits." That's a list, but it's a sentence. I'll convert to a list.
Now, write HTML.
Use for headings,
for prose,
- for lists. For the responsibilities list: each bullet point is a duty. I'll wrap each in
- .
For requirements: each bullet point is a requirement.
For benefits: I'll split the sentence into list items.
Now, produce the HTML fragment.
Let's draft:
About the role
In this role, you will work on cutting-edge connectivity solutions for the automotive industry in an environment shaped by emerging technologies, dynamic projects, and continuous development. We are looking for individuals who are eager to learn, challenge existing boundaries, and transform technical ideas into innovative products. We value motivation, a willingness to learn, and a passion for technology just as much as existing technical expertise.
Responsibilities
- Monitor market trends, emerging technologies, and industry standards to identify innovation opportunities.
- Translate customer requirements and technology roadmaps into product and platform strategies.
- Collaborate with development engineering, customers, business development, product management, sales, manufacturing engineering, test laboratories, and prototype resources to lead the design and development of connectors, cable assemblies, components, and platform or custom solutions for next-generation automotive connectivity solutions.
- Partner with global Data Connectivity teams and support marketing, sales, and customers in technical discussions, meetings, and site visits.
- Define and evaluate new product concepts, materials, and design approaches that deliver technical and/or cost advantages.
- Create complex mechanical designs using parametric and non-parametric CAD tools.
- Perform and interpret mechanical simulations to optimize product performance, reliability, and durability.
- Build and validate prototypes using rapid prototyping methods and apply test results to iterative design improvements.
- Support launch teams through production release and troubleshoot design issues during startup.
- Contribute to technology roadmaps and identify future product and process innovations.
- Travel domestically and internationally as required.
Requirements
- Bachelor’s degree in Mechanical Engineering or a related engineering discipline; master’s degree preferred.
- 7-10 years of relevant mechanical design and product development experience, preferably in an automotive or industrial environment.
- Advanced CAD capability and experience creating complex mechanical designs; experience with PTC Creo and Ansys SpaceClaim is a plus.
- Experience with mechanical simulation tools, including structural, thermal, or multi-physics analysis in Ansys Mechanical, is a plus.
- Hands-on experience with connector crimp tooling, cable assembly equipment, rapid prototyping, and prototype development.
- Customer-focused communicator with strong technical presentation and stakeholder management skills.
- Structured, independent, and creative working style with the ability to collaborate effectively across international teams.
About TE Connectivity
TE Connectivity plc (NYSE: TEL) is a global industrial technology leader creating a safer, sustainable, productive, and connected future. As a trusted innovation partner, our broad range of connectivity and sensor solutions enable the distribution of power, signal and data to advance next-generation transportation, energy networks, automated factories, data centers enabling artificial intelligence, and more. Our more than 90,000 employees, including 10,000 engineers, work alongside customers in approximately 130 countries. In a world that is racing ahead, TE ensures that EVERY CONNECTION COUNTS. Learn more at www.te.com and on LinkedIn, Facebook, WeChat, Instagram and X (formerly Twitter).
Pay
Competitive base salary commensurate with experience: $140,000 – $150,000 (subject to change dependent on physical location). Posted salary ranges are made in good faith. TE Connectivity reserves the right to adjust ranges depending on the experience/qualification of the selected candidate as well as internal and external equity. Total Compensation = Base Salary + Incentive(s) + Benefits.
Benefits
- Health insurance
- 401(k)
- Disability insurance
- Life insurance
- Employee stock purchase plan
- Paid time off
- Voluntary benefits
before the first heading? But the output should be sections with headings. The user said "Output ONLY the HTML fragment". It could start with a
then headings. However, they said "use
for section headings". They didn't forbid a leading paragraph. But they said "include a section ONLY when the posting has real, specific content for it". The first paragraph is generic company mission. Might be okay to include as a
before sections. But to be safe, I'll incorporate it into "About the role" or "About TE Connectivity". I'll add it as a paragraph in "About TE Connectivity" maybe. Actually, the "About TE Connectivity" section already has a detailed description. The first paragraph is a tagline. I'll include it as a separate paragraph before the headings? But the user might expect only sections. I think it's fine to have a leading
with that tagline. However, the instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So I can output a fragment that includes a
then headings. But they said "use
for section headings". They didn't say you can't have other elements. But they said "include a section ONLY when the posting has real, specific content for it". The tagline is not a section. I'll include it as a
before the first heading. Alternatively, I could create a section "About the company" with that tagline and the