Senior Automated Test Engineer
- for any list of duties/requirements/benefits. So we can make a list.
- Who You Are (Basic Qualifications): list: Bachelor's degree in Computer Science, Engineering, or related technical field. Minimum of 5 years of engineering experience in automated test systems, software development, manufacturing test, or related fields. Experience with automated test equipment, including oscilloscopes, VNAs, TDRs, switching systems, data acquisition systems, or similar instrumentation. Proficiency in Python and experience developing software applications for test automation. Demonstrated experience in test system development, validation, troubleshooting, and deployment. Experience working with cross-functional and global teams. Ability to travel internationally and domestically up to 20%.
These are requirements/qualifications. We need to decide which heading to use: Requirements vs Qualifications. Usually Requirements = basic qualifications, Qualifications = preferred? The posting has "Who You Are (Basic Qualifications)" and "What Will Put You Ahead" (preferred). So we can map Basic Qualifications to Requirements (or Qualifications). And "What Will Put You Ahead" to Qualifications (or Skills). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we have both Requirements and Qualifications. We'll put basic qualifications under Requirements, and preferred qualifications under Qualifications. Skills maybe separate? Could also put technical skills under Skills. But we have proficiency in Python etc. Could be under Skills. However we already have them in Requirements. Might be okay to put them under Requirements. But we need to avoid duplication. Let's think: The posting includes both basic and preferred qualifications. We can put basic under Requirements, preferred under Qualifications. Skills maybe not needed separately if covered. But we could still have Skills heading for things like "Proficiency in Python, experience with test equipment, S-parameter analysis, etc." However that would duplicate. Better to follow the instruction: include a section ONLY when the posting has real, specific content for it. So we need to decide which sections have content.
We have content for About the role (first two paragraphs). Responsibilities (What You Will Do). Requirements (Basic Qualifications). Qualifications (What Will Put You Ahead). Skills? Could be derived from both but we already have them. Might be redundant. But we could still create Skills section listing technical skills: Python, test equipment, S-parameters, TDR, eye diagrams, BER, jitter, high-speed protocols, SPC, Gage R&R, process capability, statistical techniques. However that would be splitting content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we create a Skills section, we need to take content from somewhere else and not duplicate? Duplication is allowed? It says do NOT repeat the job title as a heading and do NOT put Job ID as headings — fold minor metadata into a short
or drop it. It doesn't forbid duplication of content across sections, but better to avoid redundancy. However we could keep the content under Requirements and Qualifications and not have Skills. Benefits: There's a section "Our Benefits" describing medical, dental, vision, etc. That's substantive. So we need Benefits section. Pay: There's a paragraph about compensation range: "Any compensation range provided for a role is an estimate determined by available market data. The actual amount may be higher or lower than the range provided considering each candidate's knowledge, skills, abilities, and geographic location. If you have questions, please speak to your recruiter about the flexibility and detail of our compensation philosophy." This is not a specific range; it's generic. The instruction says 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. Here they do not give a specific range; they just talk about compensation philosophy. This is arguably filler. So we should NOT include a Pay section. Schedule: There's mention of ability to travel up to 20% but not schedule like full-time, part-time, shift. No schedule details. So we should not include Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now we need to format. About the role: combine first two paragraphs (Your Job and Our Team) into prose
. Could be two
but we can combine. Responsibilities: list of duties from "What You Will Do". We'll make
- each sentence.
Requirements: list of basic qualifications.
Qualifications: list of preferred qualifications (What Will Put You Ahead).
Benefits: list of benefits from "Our Benefits". We'll make
- .
We must not include boilerplate like EEO, etc. Remove lines about Equal Opportunities, Military Ready, etc. Also remove "At Koch companies, we are entrepreneurs..." etc. Also remove "Our goal is for each employee..."? That's part of Benefits intro; we can keep the introductory sentence as
before list? The Benefits section includes a paragraph: "Our goal is for each employee, and their families, to live fulfilling and healthy lives. We provide essential resources and support to build and maintain physical, financial, and emotional strength - focusing on overall wellbeing so you can focus on what matters most. Our benefits plan includes - medical, dental, vision, flexible spending and health savings accounts, life insurance, ADD, disability, retirement, paid vacation/time off, educational assistance, and may also include infertility assistance, paid parental leave and adoption assistance." We can keep that as
then list. We must not include "Specific eligibility criteria is set by the applicable Summary Plan Description, policy or guideline and benefits may vary by geographic region. If you have questions on what benefits apply to you, please speak to your recruiter." That's somewhat boilerplate but still substantive? It's more about eligibility. Might be considered boilerplate but it's still info. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those but could be considered legal. Safer to omit that sentence. Also omit "Additionally, everyone has individual work and personal needs..." that's also fluff. We'll keep the core benefits description. Now produce HTML fragment. Let's craft:
About the role
The Senior Automated Test Engineer will lead the development, deployment, and continuous improvement of automated test solutions for high-speed interconnect products, cable assemblies, and production test systems. This role combines expertise in signal integrity, electrical validation, software development, and manufacturing test automation to ensure robust, scalable, and data-driven test platforms across global manufacturing locations. The successful candidate will work closely with Product Development, Signal Integrity, Manufacturing, Quality, Operations, and Customer Engineering teams to develop next-generation test solutions supporting high-speed connectivity technologies ranging from automotive networking to 224G/448G interconnect systems. This includes developing software applications, performing advanced electrical measurements, analyzing SI performance, and deploying production-ready automated test systems.
The Automated Test Engineering team is a global team that is responsible for designing and implementing production test strategies. This team of engineers is empowered to lead and drive teams through failure investigations and overcoming manufacturing barriers to ensure quality products are delivered while exceeding customer satisfaction.
Responsibilities
- Drive global standardization, deployment, and continuous improvement of automated test solutions to improve quality, yield, and operational efficiency.
- Partner with Product Development, Manufacturing, Quality, and Operations teams to define and implement scalable test solutions.
- Lead complex failure investigations, root cause analysis, and corrective actions to resolve manufacturing and product issues.
- Mentor engineers and technicians while providing technical leadership for automated test system development and deployment.
- Conduct software reviews, system verification and validation, and support release management activities.
- Develop and maintain technical documentation, specifications, validation reports, and work instructions.
- Support Molex TQM and Quality/Environmental Management Systems by following approved policies and procedures.
- Perform additional duties and special projects.
Requirements
- Bachelor's degree in Computer Science, Engineering, or related technical field.
- Minimum of 5 years of engineering experience in automated test systems, software development, manufacturing test, or related fields.
- Experience with automated test equipment, including oscilloscopes, VNAs, TDRs, switching systems, data acquisition systems, or similar instrumentation.
- Proficiency in Python and experience developing software applications for test automation.
- Demonstrated experience in test system development, validation, troubleshooting, and deployment.
- Experience working with cross-functional and global teams.
- Ability to travel internationally and domestically up to 20%.
Qualifications
- Master's degree in Engineering or Computer Science.
- 8+ years of experience in high-speed interconnects, signal integrity, automated test, or production validation.
- Knowledge of S-parameters, TDR analysis, eye diagrams, BER testing, jitter analysis, and high-speed communication protocols.
- Experience leading global engineering projects.
- Knowledge of SPC, Gage R&R, process capability analysis, and advanced statistical techniques.
Benefits
Our goal is for each employee, and their families, to live fulfilling and healthy lives. We provide essential resources and support to build and maintain physical, financial, and emotional
- .
We must not include boilerplate like EEO, etc. Remove lines about Equal Opportunities, Military Ready, etc. Also remove "At Koch companies, we are entrepreneurs..." etc. Also remove "Our goal is for each employee..."? That's part of Benefits intro; we can keep the introductory sentence as
- each sentence.
Requirements: list of basic qualifications.
Qualifications: list of preferred qualifications (What Will Put You Ahead).
Benefits: list of benefits from "Our Benefits". We'll make