Jobs · Oregon

Electrical Engineer 2

Lam Research · Tualatin, OR · 3 wk ago
Full-time
We need to output HTML fragment with sections: h3 headings for sections that have content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections where posting has real specific content. The posting includes: "The group you’ll be a part of" (maybe About the role). Then "The impact you’ll make" (maybe Responsibilities). Then "What You’ll Do" (Responsibilities). Then "Minimum Qualifications" (Requirements/Qualifications). Then "Preferred Qualifications" (maybe Skills). Then "Our commitment" (maybe Benefits? Actually it's about EEO, but we must remove EEO boilerplate. The "Our commitment" is EEO statement; we should remove it. Then "Lam offers a variety of work location models..." That's about hybrid roles; could be considered Benefits? Not exactly benefits but maybe schedule? It's about work location models; could be considered Schedule? It's not pay or schedule specifics. It's about hybrid work models; could be considered Benefits? Might be considered "Benefits" but it's not typical benefits like health, 401k. The posting also includes "Our Perks And Benefits At Lam..." but no details given; it's just a heading with no specifics. So we should not create Benefits section because no specific content. Pay and Schedule not mentioned. So we include sections: About the role, Responsibilities, Requirements, Qualifications, Skills maybe. But we need to avoid duplication. The instructions: Use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We should include sections only when posting has real specific content. Let's map: - About the role: The group you’ll be a part of ... description. That's specific. - Responsibilities: The impact you’ll make + What You’ll Do (list of duties). That's specific. - Requirements: Minimum Qualifications (who we're looking for). That's specific. - Qualifications: Could be Preferred Qualifications? Might be considered Qualifications as well. But we have both Requirements and Qualifications; maybe we treat Minimum Qualifications as Requirements, and Preferred Qualifications as Qualifications or Skills. The instruction list includes both Requirements and Qualifications as separate possible headings. We could put Minimum Qualifications under Requirements, and Preferred Qualifications under Qualifications. Or we could combine them. But we need to avoid thin sections. Both have substantive content. - Skills: Could be derived from Preferred Qualifications (specific skills). But we already have Qualifications section for Preferred Qualifications. Might be redundant. Better to treat Minimum Qualifications as Requirements, Preferred Qualifications as Qualifications. Then we might not need Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications. We need to use
  • for any list of duties/requirements/benefits. So for Responsibilities we should list each duty as
  • . For Requirements we list each bullet as
  • . For Qualifications we list each bullet as
  • . For About the role we can use

    . We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate: EEO, equal opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. Also remove "Our commitment" (EEO). Remove "Our Perks And Benefits At Lam..." because it's just a heading with no details. Also remove "Lam offers a variety of work location models..." maybe it's not boilerplate but it's about hybrid roles; could be considered Benefits? But it's not specific benefits like health; it's about work location flexibility. Could be considered a benefit but it's not detailed; it's a description of work location models. The instruction says: include a section ONLY when the posting has real, specific content for it — 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. The work location models is specific content (describes On-site Flex and Virtual Flex). That could be considered a Benefit or maybe Schedule? It's about work location flexibility, not schedule. Could be considered a Benefit (work flexibility). However the Benefits section is only to be created if posting actually states them. It does state a benefit: hybrid work models. So we could include a Benefits section with that content. But we must not create Benefits unless posting actually states them. It does state them: "Lam offers a variety of work location models based on the needs of each role. Our hybrid roles combine the benefits of on-site collaboration with colleagues and the flexibility to work remotely and fall into two categories – On-site Flex and Virtual Flex. ‘On-site Flex’ you’ll work 3+ days per week on-site at a Lam or customer/supplier location, with the opportunity to work remotely for the balance of the week. ‘Virtual Flex’ you’ll work 1-2 days per week on-site at a Lam or customer/supplier location, and remotely the rest of the time." That's specific. So we should include a Benefits section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We must not include Skills unless we have specific skills content separate from qualifications. We could treat Preferred Qualifications as Qualifications. So we have Requirements (Minimum Qualifications) and Qualifications (Preferred Qualifications). Benefits as described. Now we need to extract the content precisely. Let's copy the relevant parts. About the role: "The group you’ll be a part of This position is part of Lam Research’s Global Products Group within the Wet Equipment Technology Systems organization. The WETs team develops advanced wet-processing equipment for semiconductor manufacturing. You will work in a collaborative New Product Development environment with Systems, Mechanical, Controls, Software, Process, Manufacturing, and Service Engineering teams to develop and deliver next-generation semiconductor equipment." We need to keep that as prose in

    . Responsibilities: includes "The impact you’ll make" paragraph and "What You’ll Do" list. The impact you’ll make: "As an Electrical Engineer II, you will contribute to the design, development, integration, and validation of electrical systems used in advanced semiconductor manufacturing equipment. You will work with experienced engineers to develop electrical hardware, machine controls, power distribution, and industrial automation solutions. You will apply electrical engineering fundamentals, participate in hands-on system integration and troubleshooting, and build your system-level engineering capabilities through involvement in the complete product development lifecycle." Then What You’ll Do list (many items). We need to preserve all items as

  • . Let's extract each bullet: - Design and develop electrical subsystems, control panels, cable assemblies, and electrical interfaces for semiconductor manufacturing equipment. - Create and maintain electrical schematics, wiring diagrams, cable drawings, bills of material, specifications, and related engineering documentation. - Support the integration of industrial controllers, distributed I/O, power supplies, sensors, actuators, motors, drives, and other electrical components. - Assist with the development and integration of industrial communication networks, including EtherCAT-based control systems. - Translate defined system and subsystem requirements into electrical designs with guidance from senior engineers. - Perform engineering calculations and analyses to support component selection, power distribution, load requirements, signal interfaces, and circuit protection. - Participate in electrical and cross-functional design reviews. - Collaborate with Systems, Mechanical, Controls, Software, Process, Manufacturing, and Service Engineering teams to resolve interface and integration issues. - Perform hands-on laboratory testing, equipment integration, design verification, and troubleshooting. - Use electrical test equipment such as digital multimeters, oscilloscopes, current probes, power analyzers, and protocol diagnostic tools. - Collect and analyze test data to evaluate design performance and support design improvements. - Assist with root-cause investigations using structured problem-solving methods such as 5-Why, fishbone analysis, and 8D. - Support prototype builds, system integration, manufacturing readiness, and product release activities. - Process engineering changes and maintain accurate product documentation throughout the development lifecycle. - Apply applicable electrical safety, regulatory, and internal design requirements under the guidance of senior engineers. - Incorporate design-for-safety, reliability, manufacturability, serviceability, and cost considerations into assigned work. - Communicate technical results through clear reports, presentations, and design-review materials. We need to keep each as
  • . Now Requirements (Minimum Qualifications): "Who we’re looking for Bachelor’s degree in Electrical Engineering or a related technical field with 2 or more years of relevant experience; or a master’s degree in Electrical Engineering or a related technical field with relevant internship, academic, or industry experience. Working knowledge of electrical engineering fundamentals, including analog circuits, digital circuits, control systems, signal interfaces, and electrical measurement techniques. Experience developing electrical schematics, wiring diagrams, or related engineering documentation. Familiarity with industrial electrical systems, machine controls, sensors, actuators, motors, or automation equipment. Ability to interpret electrical drawings, component specifications, and technical requirements. Hands-on experience using common electrical test and measurement equipment. Demonstrated analytical, troubleshooting, and problem-solving skills. Ability to work effectively in a multidisciplinary product development environment. Effective written, verbal, and technical presentation skills." We need to make each bullet as
  • . The first sentence is a bit long but we can keep as one
  • . Could split? It's one requirement: degree + experience. We'll keep as one. Now Qualifications (Preferred Qualifications): List: - Experience with industrial automation, programmable logic controllers, distributed I/O, motor controls, servo drives, or motion-control systems. - Familiarity with EtherCAT network architecture, EtherCAT devices, distributed I/O, or EtherCAT-based machine controls. - Experience with Beckhoff, TwinCAT, or a comparable industrial automation platform. - Experience with industrial communication protocols such as EtherCAT, Ethernet/IP, Profinet, Modbus, CAN, or serial communications. - Experience using electrical design tools such as Zuken E3, OrCAD, AutoCAD Electrical, PCAD, SPICE, or similar tools. - Internship or professional experience related to semiconductor equipment, industrial automation, robotics, manufacturing equipment, or other complex electromechanical products. - Familiarity with AC/DC power distribution, three-phase power, grounding and bonding, circuit protection, and electrical control panels. - Familiarity with electrical safety and equipment standards such as SEMI, UL, NFPA, IEC, or CE requirements. - Experience supporting system integration, prototype builds, design verification, qualification testing, or manufacturing release. - Familiarity with electromagnetic compatibility and electromagnetic interference design principles. - Basic programming, firmware, scripting, or software troubleshooting experience. We'll put each as
  • . Now Benefits: The hybrid work models description. We need to capture that as prose maybe

    . Could also list as

      but it's not a list; it's description. We'll use

      . Now we must ensure we don't include any boilerplate like "Our commitment", "Lam Research ("Lam" or the "Company") is an equal opportunity employer..." etc. Also remove "Our Perks And Benefits At Lam..." heading and following text (which is just a generic statement). Actually after "Our Perks And Benefits At Lam, our people make amazing things possible. That’s why we invest in you throughout the phases of your life with a comprehensive set of outstanding benefits." That's a generic statement with no specifics; we should drop it because it's filler. Then the hybrid work models follow. So we should keep only the hybrid work models description. Thus final HTML:

      About the role

      The group you’ll be a part of This position is part of Lam Research’s Global Products Group within the Wet Equipment Technology Systems organization. The WETs team develops advanced wet-processing equipment for semiconductor manufacturing. You will work in a collaborative New Product Development environment with Systems, Mechanical, Controls, Software, Process, Manufacturing, and Service Engineering teams to develop and deliver next-generation semiconductor equipment.

      Responsibilities

      • As an Electrical Engineer II, you will contribute to the design, development, integration, and validation of electrical systems used in advanced semiconductor manufacturing equipment. You will

Similar jobs

Electrical Engineer 2

OracleBurlington, MA· 3 wk ago
Engineering$74k–$148k/yrapply on eeho.fa.us2.oraclecloud.com

Electrical Engineer 2

CirrusDuluth, MN· 3 mo ago
Engineering$82k/yrapply on careers-cirrusaircraft.icims.com

Electrical Engineer 2

Universal Balancing (now part of Burke Porter, an Ascential Technologies Company)Utica, MI· 4 mo ago
Engineeringapply on recruiting.ultipro.com

Electrical Engineer 2

Burke Porter, an Ascential Technologies BrandShelby Township, MI· 2 mo ago
Engineeringapply on recruiting.ultipro.com

Electrical Engineer 2

Techtronic Industries - TTIAnderson, SC· 2 mo ago
Engineeringapply on tti.wd1.myworkdayjobs.com