Manufacturing Test Engineer
Cornelis Networks · Chesterbrook, PA · 4 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate etc.
We need to parse the posting.
Key sections:
- About the role: description of company and role? The posting includes intro about Cornelis Networks, then "We are seeking an Engineering professional...". That could be "About the role". We'll put a paragraph summarizing that.
- Responsibilities: there is a "Key Responsibilities:" list with bullet points. We'll extract each bullet.
- Requirements: there is "Required Qualifications:" list. That could be Requirements.
- Qualifications: there is "Preferred Qualifications:" list. Could be Qualifications (or maybe separate Preferred). But we have only one Qualifications heading allowed? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading for required qualifications? Or we could split Required vs Preferred under Qualifications? But we have only one Qualifications heading. Could combine both required and preferred under Qualifications? Might be okay. However we also have Skills heading separate. Could put technical skills under Skills. The posting includes many skill requirements (Bash, Linux, Python, C/C++, etc). We could put those under Skills.
- Benefits: there is description of compensation package: equity, cash, incentives, health and retirement benefits, medical/dental/vision, disability, life insurance, dependent care FSA, accidental injury, pet insurance, generous paid holidays, 401(k) match, OTO, sick time, bonding leave, pregnancy disability leave. Also mention base salary determined by factors, performance-based incentives. That's benefits and pay.
- Pay: we have mention of base salary determined by skills, qualifications, experience, location relative to hiring range; performance-based incentives, annual bonus or sales incentives. That's pay info. Could separate Pay and Benefits.
- Schedule: not mentioned. No schedule info. So we should not include Schedule heading.
- Skills: we can list technical skills: Bash, Linux, Python, C/C++, experience with PLM systems, FPGA, programmable components, electronic troubleshooting, I2C, SPI, USB, Ethernet, PCIe, high speed signaling, measurement tools (volt meters, oscilloscopes, logic analyzers), PCB assembly processing and reworking methods for SMT, ability to read schematics, engineering drawings, CAD files. Also maybe experience with ICT development (preferred). We'll put under Skills.
- Qualifications: Required qualifications: Bachelor's degree in EE, CS, or related; advanced degree a plus; 3+ years experience in technology-based Manufacturing/Test Engineering; experience with Bash, Linux, Python, C/C++; experience working with PLM systems; history of setting up functional test stations; experience with FPGA's and other programmable components; strong electronic troubleshooting and analytical skills including familiarity with I2C, SPI, USB, Ethernet, PCIe, other high speed signaling; working experience with measurement tools; knowledge of PCB assembly processing and reworking methods for SMT; ability to read schematics, engineering drawings, CAD files.
Preferred qualifications: Experience with ICT development.
Location: This role is based on-site located in Wayne, PA. The ideal candidate must reside within a reasonable commuting distance. That's location info; could be part of About the role or maybe a separate section? Not in allowed headings; we could fold into About the role paragraph.
We must not include boilerplate like EEO, unsolicited resumes, etc.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics like "Contract Manufacturing – Responsible for the development of functional test processes and procedures to support the contract manufacturer." etc.
We must not create sections with filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
. Some are sub-bullets under Engineering Release Support; we can keep them as separate items.
Now Requirements: from "Required Qualifications:" list.
Extract each:
- Bachelor’s degree in electrical engineering, Computer Science, or related fields.
- Advanced degree a plus.
- 3+ years of experience in a technology-based Manufacturing/Test Engineering environment.
- Experience in Bash, Linux, Python, C/C++.
- Experience working with PLM systems – product structure, bills of material, AVL, and compliance attributes.
- History of setting up and working with functional test stations within a Manufacturing environment.
- Experience with FPGA’s and other programmable components.
- Strong electronic troubleshooting and analytical skills to include familiarity with I2C, SPI, USB, Ethernet, PCIe, and other high speed signaling protocols.
- Working experience with measurement tools such as volt meters, oscilloscopes, and logic analyzers.
- Knowledge of PCB assembly processing and reworking methods for SMT components.
- Ability to read schematics, Engineering drawings and CAD files.
Now Skills: we could list technical skills that are not already in Requirements? But many overlap. However we can still list them under Skills heading; but we must not duplicate content? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplicating is okay as long as we preserve. But better to avoid duplication? Not required. We could put under Skills the specific technical proficiencies: Bash, Linux, Python, C/C++, PLM systems, FPGA, programmable components, I2C, SPI, USB, Ethernet, PCIe, high speed signaling, measurement tools (volt meters, oscilloscopes, logic analyzers), PCB assembly processing and reworking for SMT, ability to read schematics, engineering drawings, CAD files, Linux basic system administration, Bash, Python, C/C++, VB, TeraTerm, Cygwin scripting tools, ICT development (preferred). However many are already in Requirements. Might be okay but could be seen as redundant. Perhaps better to put under Skills the "Preferred Qualifications" and any additional skills not captured in Requirements, like "Experience with ICT development" (preferred) and maybe "Linux basic system administration" (though that is in Responsibilities). But we can still include.
Given the instruction to prefer a few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But we have separate headings allowed. We could have Requirements for required qualifications, Qualifications for preferred qualifications, Skills for technical skills. That would be three sections.
But we already have Responsibilities, About the role, Benefits, Pay. That's many sections but okay if they have substantive content.
We must not create sections with filler. All have content.
Let's decide:
- About the role: company + role summary + location.
- Responsibilities: list.
- Requirements: required qualifications.
- Qualifications: preferred qualifications (ICT development).
- Skills: technical skills (maybe combine some from responsibilities and requirements but we can list distinct ones: Bash, Linux, Python, C/C++, PLM systems, FPGA, programmable components, I2C, SPI, USB, Ethernet, PCIe, high speed signaling, measurement tools, PCB assembly/rework, reading schematics/drawings/CAD, Linux basic system administration, scripting tools (VB, TeraTerm, Cygwin), ICT development (though that's preferred). Might be overlapping but okay.
- Benefits: list of benefits.
- Pay: base salary determination, performance-based incentives, annual bonus/sales incentives.
We need to ensure we don't include Schedule.
Now let's craft HTML.
We'll need to escape any special characters like & etc. Use plain text.
Let's write.
First, About the role paragraph:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate etc.
We need to parse the posting.
Key sections:
- About the role: description of company and role? The posting includes intro about Cornelis Networks, then "We are seeking an Engineering professional...". That could be "About the role". We'll put a paragraph summarizing that.
- Responsibilities: there is a "Key Responsibilities:" list with bullet points. We'll extract each bullet.
- Requirements: there is "Required Qualifications:" list. That could be Requirements.
- Qualifications: there is "Preferred Qualifications:" list. Could be Qualifications (or maybe separate Preferred). But we have only one Qualifications heading allowed? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading for required qualifications? Or we could split Required vs Preferred under Qualifications? But we have only one Qualifications heading. Could combine both required and preferred under Qualifications? Might be okay. However we also have Skills heading separate. Could put technical skills under Skills. The posting includes many skill requirements (Bash, Linux, Python, C/C++, etc). We could put those under Skills.
- Benefits: there is description of compensation package: equity, cash, incentives, health and retirement benefits, medical/dental/vision, disability, life insurance, dependent care FSA, accidental injury, pet insurance, generous paid holidays, 401(k) match, OTO, sick time, bonding leave, pregnancy disability leave. Also mention base salary determined by factors, performance-based incentives. That's benefits and pay.
- Pay: we have mention of base salary determined by skills, qualifications, experience, location relative to hiring range; performance-based incentives, annual bonus or sales incentives. That's pay info. Could separate Pay and Benefits.
- Schedule: not mentioned. No schedule info. So we should not include Schedule heading.
- Skills: we can list technical skills: Bash, Linux, Python, C/C++, experience with PLM systems, FPGA, programmable components, electronic troubleshooting, I2C, SPI, USB, Ethernet, PCIe, high speed signaling, measurement tools (volt meters, oscilloscopes, logic analyzers), PCB assembly processing and reworking methods for SMT, ability to read schematics, engineering drawings, CAD files. Also maybe experience with ICT development (preferred). We'll put under Skills.
- Qualifications: Required qualifications: Bachelor's degree in EE, CS, or related; advanced degree a plus; 3+ years experience in technology-based Manufacturing/Test Engineering; experience with Bash, Linux, Python, C/C++; experience working with PLM systems; history of setting up functional test stations; experience with FPGA's and other programmable components; strong electronic troubleshooting and analytical skills including familiarity with I2C, SPI, USB, Ethernet, PCIe, other high speed signaling; working experience with measurement tools; knowledge of PCB assembly processing and reworking methods for SMT; ability to read schematics, engineering drawings, CAD files.
Preferred qualifications: Experience with ICT development.
Location: This role is based on-site located in Wayne, PA. The ideal candidate must reside within a reasonable commuting distance. That's location info; could be part of About the role or maybe a separate section? Not in allowed headings; we could fold into About the role paragraph.
We must not include boilerplate like EEO, unsolicited resumes, etc.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics like "Contract Manufacturing – Responsible for the development of functional test processes and procedures to support the contract manufacturer." etc.
We must not create sections with filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... (company description and role summary)
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
... (base salary determination, performance-based incentives, annual bonus, sales incentives)
We need to ensure we don't repeat info unnecessarily. Let's extract details. About the role: combine company description and role summary. Company description: "Cornelis Networks delivers the world’s highest performance scale-out networking solutions for AI and HPC datacenters. Our differentiated architecture seamlessly integrates hardware, software and system level technologies to maximize the efficiency of GPU, CPU and accelerator-based compute clusters at any scale. Our solutions drive breakthroughs in AI & HPC workloads, empowering our customers to push the boundaries of innovation. Backed by top-tier venture capital and strategic investors, we are committed to innovation, performance and scalability - solving the world’s most demanding computational challenges with our next-generation networking solutions. We are a fast-growing, forward-thinking team of architects, engineers, and business professionals with a proven track record of building successful products and companies. As a global organization, our team spans multiple U.S. states and six countries, and we continue to expand with exceptional talent in onsite, hybrid, and fully remote roles. Cornelis Networks designs and manufacturers a portfolio of network interconnect switches deployed in High Performance Computing and Artificial Intelligence applications. The product lines could be categorized as low-medium volume, high complexity that utilizes contract manufacturing partners for its core manufacturing." Role summary: "We are seeking an Engineering professional with experience in Manufacturing Test Engineering that includes both hardware and software development. The ideal candidate will have a working knowledge of Manufacturing Test Engineering processes and procedures, including hardware test fixture development and software scripting to support functional test. The Manufacturing Test Engineer is responsible for supporting the technical functions within Manufacturing Operations. Supporting activities include but are not limited to, failure analysis on systems and assemblies, NPI process development as it relates to assembly and functional test, hands-on support for Engineering prototype needs, rework and repair of assemblies, etc." Location: "This role is based on-site located in Wayne, PA. The ideal candidate must reside within a reasonable commuting distance." We can incorporate location into About the role paragraph. Now Responsibilities: list from "Key Responsibilities:" bullet points. Let's extract each bullet: - Contract Manufacturing – Responsible for the development of functional test processes and procedures to support the contract manufacturer. - Test fixture design and deployment including creation of PCB test fixtures and assemblies. - Formal process documentation that includes fixture setup/diagrams & step by step instruction. - Provide test process training to the Contract Manufacturer’s technical groups and Cornelis Networks Manufacturing personnel. - Develops troubleshooting tools and techniques to analyze production test failures. - Implements and maintains all production test procedures in the material BOMs as “Reference Only” line items. - Engages in Production and RMA testing as a regular member of the Manufacturing Operations group. - Monitors and evaluates production test failures and RMA return failures for potential trends. - New Product Introduction – Acts as the liaison between Engineering and Manufacturing to ensure a smooth transition of products from prototype to full production. - Lead member of the Manufacturing NPI team. - Develops test strategies to support new designs. - Possess and demonstrates working knowledge of Bash, Python and C/C+ programming and script writing tools (VB, TeraTerm, Cygwin). - Possess and demonstrate a working knowledge of Linux basic system administration. - Engineering Release Support: - Provides ECO updates on the hardware and software platforms at the Contract Manufacturer and with Cornelis Networks Manufacturing. - Ensure test processes are fully functional after updates. - Ensure all contract manufacturing sites are always testing using the current production release versions. - Applies change controls for all test station S/W platforms. - Provides functional test and failure analysis on the Production and customer RMA assemblies. We need to keep each as separateCornelis Networks delivers the world’s highest performance scale-out networking solutions for AI and HPC datacenters. Its differentiated architecture integrates hardware, software, and system‑level technologies to maximize the efficiency of GPU, CPU, and accelerator‑based compute clusters at any