Jobs · Engineering · New Jersey

Manufacturing Engineer (Electrical/Systems)

KLA · Totowa, NJ · 1 mo ago
Engineering$96k–$163k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes Company Overview, Job Description/Preferred Qualifications, Travel Requirements, Technical Skills, Preferred Qualifications, Minimum Qualifications, Base Pay Range, Benefits description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse content. Company Overview: description of KLA. Could be "About the role"? Actually "Company Overview" is about company, not role. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly. We have: - Job Description/Preferred Qualifications: includes "Key Responsibilities:" list. So we can have Responsibilities section. - Also includes "Proven experience in:" list of duties. That's also responsibilities. - Also includes "Proven ability to manage multiple projects..." also responsibilities. - Travel Requirements: Up to 10% travel. That could be Schedule? Actually schedule maybe not. Travel could be part of Responsibilities? But we have a Schedule section only if posting states schedule (like work hours, shift). Not present. Travel could be part of Responsibilities or maybe a separate section? The allowed headings are limited; we could put travel under Responsibilities or maybe under Requirements? Probably Responsibilities. - Technical Skills: list of software etc. That's Skills section. - Preferred Qualifications: Bachelor's or Master's degree in Electrical Engineering. That's Qualifications. - Minimum Qualifications: Doctorate etc. That's also Qualifications (maybe Requirements). Could combine. - Base Pay Range: $96,000 - $163,200 Annually. That's Pay section. - Benefits: description of total rewards package. That's Benefits section. - About the role: maybe we can use Company Overview as About the role? Actually About the role could be a brief summary of the role. The posting doesn't have a explicit "About the role" but we have Job Description/Preferred Qualifications which includes responsibilities. Could treat Company Overview as About the role? Not exactly. But we need to include a section only when posting has real specific content. We could create an "About the role" section using the first paragraph(s) that describe the role? The posting starts with Company Overview (about KLA). Not role. There's no explicit role summary. However we could treat the first paragraph after Company Overview as "Job Description/Preferred Qualifications" which includes responsibilities. Might be okay to omit About the role if no specific content. But we need to decide. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we don't have a clear About the role summary, we should not include that heading. Thus we will include sections: Responsibilities, Requirements (maybe combine Minimum Qualifications and Preferred Qualifications?), Qualifications, Skills, Benefits, Pay. Possibly also Schedule? No schedule info. We need to decide how to split Requirements vs Qualifications. The instruction list includes both Requirements and Qualifications as separate headings. We could put "Requirements" for minimum qualifications (education/experience) and "Qualifications" for preferred qualifications. Or vice versa. Let's map: - Requirements: Minimum Qualifications (Doctorate etc). That's specific. - Qualifications: Preferred Qualifications (Bachelor's/Master's in EE). That's also specific. But also there is "Proven experience in:" list which is more responsibilities. So we keep that under Responsibilities. Skills: Technical Skills list. Benefits: total rewards package. Pay: Base Pay Range. We also have Travel Requirements: Up to 10% travel. Could be placed under Responsibilities (maybe as a bullet). Or we could create a Schedule section? Not appropriate. We'll add a bullet under Responsibilities: "Travel up to 10% to support customers worldwide." Now we need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning etc. So we need to strip those paragraphs at the end about EEO, accommodation, fraud warnings, privacy, etc. Also remove "Interns are eligible for some of the benefits listed." That's part of benefits? It's substantive? It's about benefits eligibility for interns. Might be considered substantive but it's still part of benefits description. However it's near the end after benefits list. It's not boilerplate; it's a detail about benefits. We'll keep it. We also need to remove duplicated lines. There's duplication: "Autodesk AutoCAD" appears twice in Technical Skills. We should keep only once? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we should deduplicate repeated items. So we need to list each unique item. Technical Skills list: Manufacturing Software: SAP ERP, Autodesk AutoCAD, SolidWorks, Catia, OrCAD, AutoCAD (duplicate), any harness design software, Cirris. Production Planning Tools: Advanced Planning and Scheduling (APS), MRP II, Kanban systems, Gantt charts. Data Analysis & Reporting: Microsoft Excel (Advanced), SQL (Intermediate), Power BI (Intermediate), VBA Macros. Regulatory Compliance: Knowledge or previous exposure to ISO 9001, Six Sigma (Green Belt), Lean Manufacturing principles, OSHA standards, EPA regulations. We need to format as a list under Skills heading. Could be subheadings? Not required; just a
  • for any list. We could flatten all items into a single list, but maybe better to keep categories as separate
      with headings? The instruction only says use
      • for any list of duties/requirements/benefits, and

        for prose. It doesn't forbid additional headings inside? But we should stick to the allowed headings. Could we include a

        describing categories then a list? Probably safer to just make a single list of all skills items, but we need to preserve the categorization? Might be considered summarizing away detail if we lose categories. However we could keep categories as part of the list items: e.g., "Manufacturing Software: SAP ERP, Autodesk AutoCAD, SolidWorks, Catia, OrCAD, any harness design software, Cirris". That's one item. Similarly for Production Planning Tools etc. That preserves detail. Thus we will create

        • each line as a category with its items. Now Responsibilities: we need to extract all responsibility statements. From posting: "Key Responsibilities: Skilled in troubleshooting, maintenance, and support for system-level challenges in a production environment. Conduct failure analysis reports and investigations.Work with suppliers to resolve component/yield/part problems in a timely manner and assist purchasing teams in driving supplier quality improvements and cost reductions efforts.Collaborate with team members to troubleshoot and resolve assembly issues efficiently.Proven experience in:Designing cables/harnesses. Experience with subcomponents and pricing.PCB board/electrical enclosures testing and debugging.Designing and developing fixtures to support productionBOM structuring for multidisciplinary products, submitting, and managing engineering change ordersProcedure writing to document assembly instructions production processes. Proven ability to manage multiple projects simultaneously, maintain project timelines and work independently." Also Travel Requirements: Up to 10% travel to support customers worldwide. We need to split into sensible bullet points. Ensure we preserve all info. Let's list responsibilities: - Skilled in troubleshooting, maintenance, and support for system-level challenges in a production environment. - Conduct failure analysis reports and investigations. - Work with suppliers to resolve component/yield/part problems in a timely manner and assist purchasing teams in driving supplier quality improvements and cost reductions efforts. - Collaborate with team members to troubleshoot and resolve assembly issues efficiently. - Designing cables/harnesses. - Experience with subcomponents and pricing. - PCB board/electrical enclosures testing and debugging. - Designing and developing fixtures to support production. - BOM structuring for multidisciplinary products, submitting, and managing engineering change orders. - Procedure writing to document assembly instructions production processes. - Proven ability to manage multiple projects simultaneously, maintain project timelines and work independently. - Travel up to 10% to support customers worldwide. We need to ensure no duplication. Some sentences are run together; we split. Now Requirements (Minimum Qualifications): "Minimum Qualifications Doctorate (Academic) Degree and 0 years related work experience; Master's Level Degree and related work experience of 3 years; Bachelor's Level Degree and related work experience of 5 years" We need to preserve that exactly. We could format as a list: - Doctorate (Academic) Degree and 0 years related work experience - Master's Level Degree and related work experience of 3 years - Bachelor's Level Degree and related work experience of 5 years Now Qualifications (Preferred Qualifications): "Preferred Qualifications: Bachelor's or Master's degree in Electrical Engineering." We can make a bullet: Bachelor's or Master's degree in Electrical Engineering. Now Skills: as described. Now Benefits: The paragraph after Base Pay Range: "KLA’s total rewards package for employees may also include participation in performance incentive programs and eligibility for additional benefits including but not limited to: medical, dental, vision, life, and other voluntary benefits, 401(K) including company matching, employee stock purchase program (ESPP), student debt assistance, tuition reimbursement program, development and career growth opportunities and programs, financial planning benefits, wellness benefits including an employee assistance program (EAP), paid time off and paid company holidays, and family care and bonding leave. Interns are eligible for some of the benefits listed." We need to preserve all that. Could be a list. We'll create a
          • each benefit item. List: - participation in performance incentive programs - medical benefits - dental benefits - vision benefits - life benefits - other voluntary benefits - 401(K) including company matching - employee stock purchase program (ESPP) - student debt assistance - tuition reimbursement program - development and career growth opportunities and programs - financial planning benefits - wellness benefits including an employee assistance program (EAP) - paid time off - paid company holidays - family care and bonding leave - Interns are eligible for some of the benefits listed. Now Pay: Base Pay Range: $96,000.00 - $163,200.00 Annually. We'll put in a

            . Now we need to ensure we don't include any boilerplate: The sections about EEO, accommodation, fraud warnings, privacy, etc. Must be removed. Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:

            Responsibilities

              ...

            Requirements

              ...

            Qualifications

              ...

            Skills

              ...

            Benefits

              ...

            Pay

            Base Pay Range: $96,000.00 - $163,200.00 Annually

            We should not include Schedule or About the role. Check for any other sections: maybe "Travel Requirements" could be its own section but not in allowed headings. We placed under Responsibilities. Now ensure we didn't miss any substantive info: The company overview paragraph about KLA is not included; is that substantive? It's about company, not role. The instruction says we can use About the role for section heading; but we don't have a role summary. The company overview is not about the role, but could be considered "About the role"? Not

Similar jobs