Software Engineer 4

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Content: - Intro: "The group you’ll be a part of In the Global Products Group, we are dedicated to excellence in the design and engineering of Lam's etch and deposition products. We drive innovation to ensure our cutting-edge solutions are helping to solve the biggest challenges in the semiconductor industry." - "The impact you’ll make As a Software Engineer at Lam, you will be at the forefront of innovation by designing, developing, and troubleshooting, and debugging software programs. Your role is pivotal in developing software tools that support design, infrastructure, and technology platforms. Your expertise will determine hardware compatibility and influence design, ensuring seamless integration between software and hardware. In this role, you’ll make an impact across Lam’s entire product portfolio of equipment working within our centralized software engineering team, collaborating with some of the brightest minds in the industry." - "What You’ll Do Design, develop, troubleshoot, and debug software programs for enhancements and new products.Implement new customer requirements and features in our existing application.Maintain and enhance existing code base by investigating and resolving problem areas.Demonstrate, clearly communicate, and present solutions through clear documentation, flowcharts, and well-structured code.Collaborate with cross functional teams to design and develop software programs.Provide technical guidance and mentoring for more junior engineers.May visit customer site to provide support and have ability to travel (total is less than 10%)." - "Minimum Qualifications Who we’re looking for Bachelor’s degree in Computer Engineering, Electronics, Mechanical Engineering with 8+ years of experience; or Master’s degree with 6+ years’ experience; or a PhD with 3+ years’ experience; or equivalent experience.Knowledge of Object-Oriented Software (OOS), Object Oriented Design (OOD), or Object-Oriented Programming (OOP) implementation and design, including Design Patterns and Finite State Machines.Knowledge of multithreading, including preemptive thread scheduling.Knowledgeable with communication protocols such as Inter-Integrated Circuit (I2C), Service Provider Interface (SPI), Universal Asynchronous Receiver-Transmitter (UART)." - "Preferred Qualifications Prior semiconductor equipment experience.Experience in distributed embedded controls system desired.Software development skills in one or more general purpose programming languages: C++, C#." - "Our commitment We believe it is important for every person to feel valued, included, and empowered to achieve their full potential. By bringing unique individuals and viewpoints together, we achieve extraordinary results. Lam Research ("Lam" or the "Company") is an equal opportunity employer. Lam is committed to and reaffirms support of equal opportunity in employment and non-discrimination in employment policies, practices and procedures on the basis of race, religious creed, color, national origin, ancestry, physical disability, mental disability, medical condition, genetic information, marital status, sex (including pregnancy, childbirth and related medical conditions), gender, gender identity, gender expression, age, sexual orientation, or military and veteran status or any other category protected by applicable federal, state, or local laws. It is the Company's intention to comply with all applicable laws and regulations. Company policy prohibits unlawful discrimination against applicants or employees. 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." - "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." We need to remove boilerplate: EEO, equal opportunity, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions (none present). Also remove "Our commitment" EEO stuff. Also remove "Our Perks And Benefits" maybe we keep Benefits section if there is specific content. The Benefits paragraph is vague: "comprehensive set of outstanding benefits." No specifics. According to rule: never create Benefits section unless posting actually states them. It states "comprehensive set of outstanding benefits" but no specifics. That's vague; maybe we should not include Benefits because it's not specific. The rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Benefits statement is vague but not exactly placeholder; but it's not specific benefits. Likely we should omit Benefits section. Pay and Schedule: none given. So omit. We need sections: About the role (maybe "The group you’ll be a part of" and "The impact you’ll make") could be combined as About the role. Responsibilities: "What You’ll Do". Requirements: Minimum Qualifications. Qualifications: maybe Preferred Qualifications could be under Qualifications or Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (minimum qualifications) and Qualifications (preferred). Or Skills could be separate for technical skills. But we have knowledge of OOP, multithreading, communication protocols, etc. Those could be Skills. However we also have "Preferred Qualifications" includes semiconductor equipment experience, distributed embedded controls system, software development skills in C++, C#. That could be Skills or Qualifications. We need to decide structure: Probably:

About the role

with paragraphs describing group and impact.

Responsibilities

with

• items from What You’ll Do.

  Requirements

  with
  • items from Minimum Qualifications.

    Skills

    with
    • items from Knowledge of OOP/OOD/OOP, Design Patterns, Finite State Machines, multithreading, communication protocols (I2C, SPI, UART). Also maybe include preferred qualifications as skills? But we could also have a separate

      Qualifications

      for preferred qualifications. However the instruction says we can use Qualifications heading. Might be better to have Requirements (minimum) and Qualifications (preferred). Skills could be separate for technical competencies. But we have overlapping. Let's see typical job posting: Minimum Qualifications = Requirements. Preferred Qualifications = Qualifications. Skills could be separate but we could merge. Given we want few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But we need to follow headings list; we can choose which to include. We have substantive content for About the role, Responsibilities, Minimum Qualifications (Requirements), Preferred Qualifications (maybe Qualifications), and maybe Skills (technical knowledge). That's four sections. We need to avoid filler. All content is specific. Let's extract specifics. About the role: combine two paragraphs: Paragraph1: "In the Global Products Group, we are dedicated to excellence in the design and engineering of Lam's etch and deposition products. We drive innovation to ensure our cutting-edge solutions are helping to solve the biggest challenges in the semiconductor industry." Paragraph2: "As a Software Engineer at Lam, you will be at the forefront of innovation by designing, developing, and troubleshooting, and debugging software programs. Your role is pivotal in developing software tools that support design, infrastructure, and technology platforms. Your expertise will determine hardware compatibility and influence design, ensuring seamless integration between software and hardware. In this role, you’ll make an impact across Lam’s entire product portfolio of equipment working within our centralized software engineering team, collaborating with some of the brightest minds in the industry." We can combine into one

      or two

      . Use

      for prose. Responsibilities: list items: - Design, develop, troubleshoot, and debug software programs for enhancements and new products. - Implement new customer requirements and features in our existing application. - Maintain and enhance existing code base by investigating and resolving problem areas. - Demonstrate, clearly communicate, and present solutions through clear documentation, flowcharts, and well-structured code. - Collaborate with cross functional teams to design and develop software programs. - Provide technical guidance and mentoring for more junior engineers. - May visit customer site to provide support and have ability to travel (total is less than 10%). We need to ensure each as

    • . Requirements (Minimum Qualifications): - Bachelor’s degree in Computer Engineering, Electronics, Mechanical Engineering with 8+ years of experience; or Master’s degree with 6+ years’ experience; or a PhD with 3+ years’ experience; or equivalent experience. - Knowledge of Object-Oriented Software (OOS), Object Oriented Design (OOD), or Object-Oriented Programming (OOP) implementation and design, including Design Patterns and Finite State Machines. - Knowledge of multithreading, including preemptive thread scheduling. - Knowledgeable with communication protocols such as Inter-Integrated Circuit (I2C), Service Provider Interface (SPI), Universal Asynchronous Receiver-Transmitter (UART). We could split each as
    • . The first item is a compound; we can keep as one. Qualifications (Preferred Qualifications): - Prior semiconductor equipment experience. - Experience in distributed embedded controls system desired. - Software development skills in one or more general purpose programming languages: C++, C#. We could also include these as Skills, but we already have technical knowledge in Requirements. Might be better to have Skills section for programming languages and maybe other skills. However we already have knowledge of OOP etc. Could move those to Skills. But the instruction says we can use Skills heading. Let's think: The Minimum Qualifications includes knowledge of OOP, multithreading, communication protocols. Those are skills. The Preferred Qualifications includes semiconductor equipment experience, distributed embedded controls, C++, C#. Those are also skills/experience. We could have:

      Requirements

      (minimum qualifications)

      Skills

      (technical skills: OOP/OOD/OOP, Design Patterns, FSM, multithreading, I2C, SPI, UART, C++, C#)

      Preferred Qualifications

      (semiconductor equipment experience, distributed embedded controls) But that may be many sections. The instruction: "Prefer a few substantive sections over many thin ones." So we should aim for maybe 3 sections: About the role, Responsibilities, Requirements (including both minimum and preferred). Or we could combine Minimum and Preferred into Requirements with sub-bullets? But we need to preserve all info; we can list them all under Requirements with clear distinction maybe using separate

      notes. However the instruction says use

      • for any list of duties/requirements/benefits. So we can have a single
        for requirements that includes both minimum and preferred items. That's okay. Thus sections: - About the role (prose) - Responsibilities (list) - Requirements (list) (including minimum qualifications and preferred qualifications) We should not include Benefits, Pay, Schedule. We need to ensure we don't repeat job title as heading. Not needed. We need to output only HTML fragment. Let's craft. First, About the role: two paragraphs maybe combined into one

        with two sentences? Better to keep as two

        for readability. But we can also put both in one

        separated by space. It's fine. I'll do:

        About the role

        In the Global Products Group, we are dedicated to excellence in the design and engineering of Lam's etch and deposition products. We drive innovation to ensure our cutting-edge solutions are helping to solve the biggest challenges in the semiconductor industry.

        As a Software Engineer at Lam, you will