Principal Failure Analysis Engineer (Semiconductor / Electronics)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title. No Job ID. Remove boilerplate, EEO, etc. Preserve all substantive info. We need to parse the posting. Company Description: we can include as "About the role"? Actually "About the role" maybe includes description of role and company. The posting includes Company Description and Job Description. We can combine into sections: About the role (company description + overview), Responsibilities (what you will do), Requirements (maybe education/experience), Qualifications (maybe ITAR, ISO), Skills (specific technical skills), Benefits (list of benefits), Pay (none), Schedule (none). We must not create Pay/Schedule unless present. There's no explicit pay or schedule. So omit those sections. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include details like: over 40 years experience, parent company Eurofins Scientific, etc. But we must avoid boilerplate like EEO, legal, etc. Also remove duplicated lines. We need to be careful to not include navigation, cookie, legal, EEO, equal-opportunity, scam-warning boilerplate. So we must cut out the equal opportunity employer statements at the end. Also remove "Check out our other opportunities:" etc. Also remove "We encourage you to apply even if your experience is not a 100% match..." maybe that's substantive? It's more of encouragement but could be considered boilerplate? It's not EEO but it's generic encouragement. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The encouragement to apply is not exactly application instructions? It says "We encourage you to apply even if your experience is not a 100% match..." That's somewhat encouraging but not exactly application instructions. Might be okay to keep? It's not a list. Might be considered fluff but not prohibited. However we should aim to preserve substantive information; that line is not substantive about the job. Could be considered filler. Safer to omit? The instruction says remove application instructions. That line is not exactly instructions but encouragement. I'd lean to keep it? Might be considered fluff. I'd omit to keep only substantive. We need to include sections only when posting has real specific content. So we need to decide which sections to include. Let's extract: Company Description: paragraphs about Eurofins EAG Laboratories, parent company, mission, industries served, instrumentation, people, etc. Job Description: description of lab in Irvine, CA, services, failure analysis staff, examples of investigations, role responsibilities: conducting technical discussions, designing/executing analytical plan, consulting, recommending next steps, senior member, leading teams, project management, job planning, multi-disciplinary problem solving, legal projects, etc. Qualifications: repeated block: Employees expected to comply with ISO 27001 and info security. Then ITAR requirement: US Person. Then Education And Experience: BSEE or MSEE required, Minimum 15+ yrs direct hands-on Failure Analysis lab experience (semiconductor and electronics industry), Experience and knowledge in following: Semiconductor, materials analysis, electronics manufacturing, design, etc. Experiences as technical lead, manager or mentor highly desired. Job Skills And Knowledge: Required Hands-on experience/expertise: list many items. Highly desired Hands-on experience/expertise: list many. Software: GDS layout, LabView. Working knowledge of: device physics, circuits/schematics, analog/digital circuits, IC design, DPA, Mil-Std, AEC, JEDEC, IPC, etc. Semiconductor fabrication/process, yield enhancement, Manufacturing, IC package assembly, NPI, Reliability/Qualification testing, Able to develop new methods or techniques, Excellent English communication skills (written and spoken), A strong work ethic with a commitment to accuracy, The ability to work to deadlines in a team-oriented environment are essential. Physical Requirements: list many. Additional Information: What It's Like To Work Here: Teamwork, Learning & Development, Diversity & Authenticity, Benefits & Perks To Foster Work/Life Balance: list with checkmarks: Medical, Dental and Vision Coverage, 401k Company Matching, Paid Time Off, Wellness Program, Education Assistance, …and more! We need to include Benefits section if present. Yes we have benefits list. We need to not include Pay or Schedule. We need to avoid duplication: The qualifications block appears twice? Actually there is "Qualifications" heading repeated: first "Qualifications Employees are expected to comply with ISO 27001 standard and company requirements for Information security." Then later "Qualifications This role is subject to the International Traffic in Arms Regulations (ITAR)..." Then later "Education And Experience:" etc. Then "Job Skills And Knowledge:" etc. Then "Physical Requirements:" etc. We'll combine into appropriate sections. We need to use

  for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping: - About the role: could include Company Description and maybe overview of role (Job Description first paragraph). Could be a prose

  . - Responsibilities: the duties: conducting technical discussions, designing/executing analytical plan, consulting, recommending next steps, senior member, leading teams, project management, job planning, multi-disciplinary problem solving, legal projects, etc. Also examples of investigations maybe part of responsibilities? Could be included. - Requirements: maybe education and experience (BSEE/MSEE, 15+ years, etc.) plus ITAR, ISO compliance. - Qualifications: maybe the technical skills and knowledge required (the long list). But we already have Skills section. The instruction says use headings for Skills as well. So we could put required hands-on experience/expertise under Skills, and highly desired under Skills as well? Or we could separate Required vs Desired? But we only have Skills heading. We'll put all skills under Skills. - Requirements could be education/experience and compliance. - Benefits: list of benefits. We must not repeat job title. We must not include boilerplate like EEO etc. We must preserve all substantive information: need to include details like "over 40 years experience", "parent company Eurofins Scientific", "multi-billion-dollar global leader", "over 950 labs in 60 countries", "65,000 employees", "portfolio of over 200,000 validated analytical methods", "curiosity fuels everything we do", etc. Also mention industries served: semiconductors, advanced electronics, pharmaceuticals, medical devices, energy systems, consumer products. Also mention techniques: analytical chemistry, microscopy, surface analysis, engineering sciences. Also mention that work influences safety, reliability, performance. Job Description: location Irvine, CA, test, engineering, reliability services to tech sectors, support clients from startup to Fortune 500, failure analysis staff succeed in challenging world, helping support clients research, develop, understand, refine technologies that shape consumer electronics, medical device, automotive, military, aerospace, manufacturing. Hands-on approach using leading-edge methods and tools. Examples of investigations: two bullet points. Then role responsibilities: conducting technical discussions, designing/executing analytical plan/method, consulting with value-added insight and result interpretation, recommending suitable next steps. As senior member, responsible working alongside peers and/or leading teams of engineers in the lab. Role includes aspects of project management, job planning, multi-disciplinary problem solving, legal projects and other complex client issues and requests. Dynamic role exposing to ever-changing samples, tools, techniques. Qualifications: Employees expected to comply with ISO 27001 standard and company requirements for Information security. ITAR: US Person definition. Education And Experience: BSEE or MSEE required, Minimum 15+ yrs direct hands-on Failure Analysis laboratory experience (semiconductor and electronics industry), Experience and knowledge in the following: Semiconductor, materials analysis, electronics manufacturing, design, etc. Experiences as a technical lead, manager or mentor are highly desired. Job Skills And Knowledge: Required Hands-on experience/expertise: list: Root cause failure analysis, Fault isolation techniques: OBIRCH, XIVA, emmi, IR Thermography, Electrical Test/Measurements: ATE datalog, Curve trace, Bench test (parametric analyzer, o-scopes, CV measurement, LCR meter, etc.), Microprobing/Picoprobing, X-ray (2D), SEM/EDS, Highly desired Hands-on experience/expertise: LVP/LTP, SDL/LADADBFIB, PFIB, X-ray (CT/3D), Scanning Acoustic Microscopy (C-SAM), Deprocessing (RIE, parallel lapping, PFIB, etc.), Chemical etching (decapsulation, HF, acids/bases, delineation, etc.), Plasma etching (RIE, ICP, CF4, etc.), Cross sectioning (metallurgical, ion mill, DB FIB, etc.), Nanoprobing, FinFET and advanced node technology, DPA (Destructive Physical Analysis), Software: GDS layout, LabView, Working knowledge of: Device physics, circuits/schematics, analog/digital circuits, IC design, DPA, Mil-Std, AEC, JEDEC, IPC, etc., Semiconductor fabrication/process, yield enhancement, Manufacturing, IC package assembly, NPI, Reliability/Qualification testing, Able to develop new methods or techniques, Excellent English communication skills (written and spoken), A strong work ethic with a commitment to accuracy, The ability to work to deadlines in a team-oriented environment are essential. Physical Requirements: list many. We need to decide whether to include Physical Requirements as a section. There's no heading for Physical Requirements in the allowed list. Could we put under Requirements? Possibly. But the instruction says use headings for those specific sections only. It didn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we could also add other headings? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but likely they expect only those. Safer to map Physical Requirements into Requirements or Qualifications? Probably Requirements includes education/experience and maybe physical requirements. But we have separate headings for Requirements and Qualifications. We could put physical requirements under Requirements as a list. But we must not invent sections; we can include a Requirements section that includes education/experience, ITAR, ISO, physical requirements. Skills section will contain the technical skills lists. Benefits section will contain the benefits list. We need to avoid duplication: The text repeats "Employees are expected to comply with ISO 27001 standard and company requirements for Information security." appears twice; we should include once. Also "We encourage you to apply even if your experience is not a 100% match..." we may omit as not substantive. Also "If you enjoy being immersed in technology, dreaming about the future, tackling challenges head-on, problem-solving through teamwork, flexing your technical abilities and taking pride in accomplishments, then join us to live this every day." That's motivational; could be considered fluff but maybe part of responsibilities? It's more about encouragement. Might be okay to keep in About the role? But it's not substantive detail about job. I'd omit. Also "If this role and the types of cases excite you, and you welcome daily challenges and are comfortable working in a fast-paced environment with a team-centric approach to solving problems, we encourage you to apply." That's application encouragement; omit. Also "We want