Customer Engagement Applications Engineer

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes Company Overview, Job Description/Preferred Qualifications, Key Responsibilities, Qualifications, Preferred Skills, Minimum Qualifications, Base Pay Range, Primary Location, total rewards package (benefits). Also includes some other info like EEO etc which we must remove. We need to decide sections: About the role (maybe from Job Description/Preferred Qualifications). Responsibilities (Key Responsibilities). Requirements (maybe Minimum Qualifications? Or Qualifications?). Qualifications (maybe the Qualifications section). Skills (Preferred Skills). Benefits (total rewards package). Pay (Base Pay Range). Schedule (not mentioned, so omit). Also we might include About the role (Company Overview + Job Description). Must not repeat job title as heading. Must not include Job ID etc. We must preserve all substantive information. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create sections with placeholder. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

Company Overview ... Job Description/Preferred Qualifications ...

But we need to preserve all substantive info. Let's extract. Company Overview paragraph: "KLA is a global leader in diversified electronics for the semiconductor manufacturing ecosystem. Virtually every electronic device in the world is produced using our technologies. No laptop, smartphone, wearable device, voice-controlled gadget, flexible screen, VR device or smart car would have made it into your hands without us. KLA invents systems and solutions for the manufacturing of wafers and reticles, integrated circuits, packaging, printed circuit boards and flat panel displays. The innovative ideas and devices that are advancing humanity all begin with inspiration, research and development. KLA focuses more than average on innovation and we invest 15% of sales back into R&D. Our expert teams of physicists, engineers, data scientists and problem-solvers work together with the world’s leading technology providers to accelerate the delivery of tomorrow’s electronic devices. Life here is exciting and our teams thrive on tackling really hard problems. There is never a dull moment with us." Job Description/Preferred Qualifications: "Join KLA’s Electron Beam Division, a leader in advanced e-beam review and inspection tools for semiconductor manufacturing. Our mission is to serve as the “eyes” of KLA’s product line, delivering high-resolution defect data that helps customers identify and correct process issues quickly and accurately. As an Applications Engineer, you’ll work closely with customers and multi-functional teams to maintain and optimize eBeam tools, develop innovative applications, and drive improvements for next-generation products. This role combines technical expertise with customer engagement, ensuring our tools deliver maximum value in advanced semiconductor fabs." We can combine these into About the role. Responsibilities: list bullet points from "Key Responsibilities:" lines. Let's extract each bullet: - Support, maintain, and troubleshoot eBeam tools in customer environments - Diagnose tool issues, identify corrective actions, and ensure optimal tool performance - Work closely with service and engineering teams to resolve hardware/software issues - Develop applications and Best Known Methods (BKMs) to solve complex customer challenges and improve tool capability - Create use cases, scope new features, identify issues, and drive bug fixes - Maintain strategic customer relationships and assist sales teams with technical assessments - Develop and document training materials, and provide technical training - Collaborate with customers and internal teams to define requirements for future products We need

• for each. Qualifications: The section "Qualifications" includes bullet-like sentences: - MS or Ph.D. or equivalent experience in Physics, Chemistry, Engineering, Optics, Material Science, or related field - Experience in semiconductor fabrication or equivalent educational experience - Minimum 2 years of hands-on SEM review, SEM inspection, or TEM/FIB experience - Strong knowledge of semiconductor process flows and defect types - Understanding of electron optics and how electrons interact with a sample to produce SE, BSE, and VC signals - Experience in system-level troubleshooting, diagnostics, and reporting - Cleanroom experience and semiconductor device characterization - Familiarity with computer operating systems, networking, and analysis tools We can put these as
  • . Preferred Skills: list: - Strong customer focus and ability to build collaborative relationships - Motivation to innovate and proactively deliver exceptional customer outcomes - Proven technical leadership and problem-solving skills - Experience with Advanced Packaging, Wafer Level Packaging, or C4. - Excellent communication, teamwork, and project management skills - Ability to present technical content to diverse audiences - Data analysis tools (Excel, JMP, Minitab, Igor, Origin, ImageJ, etc.) - Programming (Matlab, LabVIEW, Python, etc.) Minimum Qualifications: "BS with 2+ years industry experience, MS with relevant experience". This could be part of Qualifications or Requirements. Since we already have Qualifications section, maybe we treat Minimum Qualifications as part of Requirements? But we have both Qualifications and Minimum Qualifications; we could combine them into Requirements or Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have both Requirements and Qualifications. We need to decide what goes where. Typically Requirements = minimum qualifications; Qualifications = preferred qualifications? But we already have Preferred Skills separate. The posting has "Qualifications" (list) and "Minimum Qualifications". We could map Minimum Qualifications to Requirements, and Qualifications to Qualifications (maybe preferred). However the Qualifications list seems like required qualifications (MS/PhD etc). Minimum Qualifications is a bit redundant: BS with 2+ years industry experience, MS with relevant experience. That seems like alternative path. We could include both under Requirements (maybe as bullet). But we must not duplicate. Let's think: The posting includes both "Qualifications" (which seems like required) and "Minimum Qualifications". To avoid duplication, we could treat the "Qualifications" as Requirements (since they are required) and the "Minimum Qualifications" as additional note maybe also under Requirements. But we need to preserve all substantive info; we can include both under Requirements as separate bullet points. Alternatively we could have Requirements section for Minimum Qualifications, and Qualifications section for the Qualifications list. That seems logical: Requirements = minimum needed; Qualifications = preferred or additional qualifications. However the Qualifications list includes MS/PhD etc which are more than minimum; but they are listed as Qualifications. So we can put them under Qualifications. Minimum Qualifications under Requirements. Thus:

    Requirements

    • BS with 2+ years industry experience
    • MS with relevant experience
    But we need to preserve the exact phrasing: "BS with 2+ years industry experience, MS with relevant experience". Could be one bullet: "BS with 2+ years industry experience, MS with relevant experience". We'll keep as one bullet. Now Qualifications section: the list above. Skills section: Preferred Skills. Benefits: total rewards package paragraph. Pay: Base Pay Range. Schedule: not present, omit. We must not include boilerplate like EEO, accommodation, fraud warnings, privacy, etc. We must not include headings with empty content. Now produce HTML. We need to ensure we use

    for each section heading. We'll output:

    About the role

    Company Overview ... Job Description/Preferred Qualifications ...

    But we need to ensure we preserve all substantive info from those two paragraphs. Let's combine them into a single paragraph or maybe two paragraphs. The instruction: use

    for prose. So we can have multiple

    elements. We'll put Company Overview in one

    , then Job Description/Preferred Qualifications in another

    . Now Responsibilities:

    Responsibilities

    ...
    Requirements:

    Requirements

    ...
    Qualifications:

    Qualifications

    ...
    Skills:

    Skills

    ...
    Benefits:

    Benefits

    ... total rewards package ...

    Pay:

    Pay

    Base Pay Range: $83,100.00 - $141,300.00 Annually

    We might also include Primary Location? Not a heading; maybe we can fold into About the role paragraph? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Primary location is minor metadata; we could include in About the role paragraph or maybe a separate

    under About the role. But we already have About the role with two paragraphs; we could add a third paragraph for location. However location is not part of About the role but it's okay to include as a short paragraph. But we must not invent sections. We can add a

    under About the role for location. Or we could add a separate

    Location? Not in allowed headings. So we fold into About the role. Thus About the role will have three

    : Company Overview, Job Description/Preferred Qualifications, Primary Location. Let's extract Primary Location: "Primary Location: USA-OR-Hillsboro-Beaverton-KLA". We'll keep that. Now Benefits paragraph: The total rewards package description: "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. We'll put in a

    . Now ensure we don't include any boilerplate like "Our pay ranges are determined by role, level, and location..." etc. That's part of Pay section? Actually that is after Base Pay Range. It's substantive? It explains how pay determined. Might be considered part of Pay section. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that explanation as part of Pay section. However we must not create a Pay section with filler like "commensurate with experience". This is substantive. So we should include that paragraph after the base pay range. Thus Pay section will have:

    Base Pay Range: $83,100.00 - $141,300.00 Annually

    Our pay ranges are determined by role, level, and location. The range displayed reflects the pay for this position in the primary location identified in this posting. Actual pay depends on several factors, including state minimum pay wage rates, location, job-related skills, experience, and relevant education level or training. We are committed to complying with all applicable federal and state minimum wage requirements where applicable. If applicable, your recruiter can share more about the specific pay range for your preferred location during the hiring process.

    We must not include the EEO etc. Now check for any other substantive info: There's also a line about "KLA is proud to be an Equal Opportunity Employer..." which is boilerplate EEO, must remove. Also accommodation request line, fraud warning, privacy statement - remove. Now ensure we didn't miss any substantive info: The "Preferred Skills" list includes "Experience with Advanced Packaging, Wafer Level Packaging, or C4." Good. Now check if any other sections like "Schedule" not present. Now produce final HTML. We