Semiconductor Design Engineer

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 if posting has real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Must not create sections for Pay/Schedule/Benefits unless posting actually states them. The posting includes salary range: "US base salary range that Micron Technology, Inc. estimates it could pay for this full-time position is $173,607.10 - $246,000.00." Also mentions benefits: "Micron benefits are designed to help you stay well..." etc. So we can include Pay and Benefits sections. Schedule not mentioned, so omit. We need sections: About the role (vision statement maybe?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We must not invent or summarize away detail. Must preserve all substantive info. So we need to extract each piece. Let's parse the posting: First paragraph: "Our vision is to transform how the world uses information to enrich life for all. Micron Technology is a world leader in innovating memory and storage solutions that accelerate the transformation of information into intelligence, inspiring the world to learn, communicate and advance faster than ever." That's about the company vision. Could be "About the role" or maybe "About Micron". But we need section headings as per list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The "About the role" could contain the vision description? Usually "About the role" describes the position. The posting says: "Serve as the core technical individual contributor in design and validation of the on-chip controller and mixed signal circuitry in NAND Flash chips. Responsible for architecture development and product definition, system integration and full-chip and block-level validation planning and execution. Contribute to RTL design and implementation of the controller hardware, synthesis, APR and full timing closure as well as development of firmware code for NAND internal operations. Work closely with design teams both domestically and overseas on different projects." That's responsibilities. So we can put that under Responsibilities. The vision statement maybe could go under About the role? Or we could omit About the role if no specific content? But we have vision statement about company; maybe we can treat as About the role? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include About the role with a description of the role and maybe company vision. But we must not invent or summarize away detail. So we need to include the vision statement as is? It's not exactly about the role but it's part of the posting. We could include it under About the role as a brief intro. It's not repeating job title. It's okay. Next: "Employer will accept a Master’s degree in Electrical Engineering or related field." That's a requirement/qualification. Could be under Requirements or Qualifications. We'll decide. Then: "Position Requires Verilog language; Digital ASIC design methodology; Mixed-mode design and validation; Design or Verification CAD tools, including NCSim; Design Compiler, Formality, or PrimeTime; TCL, PERL, C, C++, or Python; and Non-volatile memory design (NAND)." That's skills/requirements. Then salary range. Then benefits paragraph. We need to preserve all substantive info, not invent or summarize away detail. So we need to include each bullet or list item as

• . For prose, use

  . We must not include boilerplate: EEO, equal opportunity, fraud alert, AI alert, etc. Also remove duplicated lines, application instructions like "For additional pay & benefits information, please refer to the requisition at Micron.com/careers." That's application instruction? It's a reference; maybe we should remove as it's not substantive? It's a pointer to external site; but it's not about the job. The instruction says remove application instructions. So we should remove that line. Also remove "For additional information regarding the Benefit programs available, please see the Benefits Guide posted on micron.com/careers/benefits." That's also a reference; maybe remove as it's not substantive? But it's about benefits; but it's a pointer. The instruction: remove application instructions. This is not exactly application instruction but a reference. Might be considered boilerplate. Safer to remove. Also remove EEO paragraph, fraud alert, AI alert, etc. Also remove "Micron Prohibits the use of child labor..." etc. Also remove "To learn about your right to work click here." etc. Also remove "Micron does not charge candidates any recruitment fees..." Also remove "For US Sites Only: To request assistance..." etc. Also remove "Micron is proud to be an equal opportunity workplace..." etc. Also remove "As a world leader in the semiconductor industry, Micron is dedicated to your personal wellbeing and professional growth." That's maybe part of benefits? It's a statement about benefits; we could keep as part of Benefits section? It's substantive about benefits. It says Micron benefits are designed to help you stay well... So we can keep that. We need to keep all substantive info: vision, responsibilities, requirement (Master's), skills list, salary range, benefits description (medical, dental, vision plans, income protection, paid family leave, paid time-off, paid holidays). Also maybe the statement about Micron being world leader etc. That's not directly benefits but could be part of About the role? Might be considered boilerplate? It's a generic statement about Micron's dedication; could be considered fluff but it's substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That statement is not exactly boilerplate but could be considered fluff. However it's part of the posting describing company culture; maybe we keep it under About the role or Benefits? It's about personal wellbeing and professional growth, which ties to benefits. I'd include it in Benefits section as part of description. We must not create sections with filler like "commensurate with experience". Not present. Thus sections: - About the role: include vision statement? Could also include short description of role? But we already have responsibilities. Maybe About the role can contain the vision statement and maybe a brief about Micron being world leader. Let's include: "Our vision is to transform how the world uses information to enrich life for all. Micron Technology is a world leader in innovating memory and storage solutions that accelerate the transformation of information into intelligence, inspiring the world to learn, communicate and advance faster than ever." That's two sentences. - Responsibilities: list of duties: "Serve as the core technical individual contributor in design and validation of the on-chip controller and mixed signal circuitry in NAND Flash chips. Responsible for architecture development and product definition, system integration and full-chip and block-level validation planning and execution. Contribute to RTL design and implementation of the controller hardware, synthesis, APR and full timing closure as well as development of firmware code for NAND internal operations. Work closely with design teams both domestically and overseas on different projects." We could break into

  • each sentence? The instruction: Use
    • for any list of duties/requirements/benefits. So we should convert each duty into list items. However the sentences are not explicitly a list but we can treat them as list items. We'll split by sentences. - Requirements: maybe the Master's degree requirement. Could be under Requirements. - Qualifications: maybe also the Master's degree? But we have both Requirements and Qualifications; we need to decide which to use. The posting only mentions "Employer will accept a Master’s degree in Electrical Engineering or related field." That's a qualification. Could be under Qualifications. We'll not duplicate. - Skills: list of required skills: Verilog language; Digital ASIC design methodology; Mixed-mode design and validation; Design or Verification CAD tools, including NCSim; Design Compiler, Formality, or PrimeTime; TCL, PERL, C, C++, or Python; and Non-volatile memory design (NAND). We'll make each as list item. - Benefits: include statements: "As a world leader in the semiconductor industry, Micron is dedicated to your personal wellbeing and professional growth. Micron benefits are designed to help you stay well, provide peace of mind and help you prepare for the future. We offer a choice of medical, dental and vision plans in all locations enabling team members to select the plans that best meet their family healthcare needs and budget. Micron also provides benefit programs that help protect your income if you are unable to work due to illness or injury, and paid family leave. Additionally, Micron benefits include a robust paid time-off program and paid holidays." We could break into list items: medical/dental/vision plans, income protection programs, paid family leave, paid time-off program, paid holidays. Also the statement about dedication to wellbeing and professional growth could be a

      preceding list. - Pay: include salary range: "The US base salary range that Micron Technology, Inc. estimates it could pay for this full-time position is $173,607.10 - $246,000.00." Could be a

      . We must not include Schedule. We must not include any boilerplate like "For additional pay & benefits information, please refer to the requisition at Micron.com/careers." Remove. We must not include "For additional information regarding the Benefit programs available, please see the Benefits Guide posted on micron.com/careers/benefits." Remove. We must not include EEO etc. Now produce HTML fragment: start with

      About the role

      then

      ... vision ...

      . Then

      Responsibilities

      • ... each duty.
      . Then

      Requirements

      maybe

      Employer will accept a Master’s degree in Electrical Engineering or related field.

      . Or we could put under Qualifications. Let's decide: Use Requirements for the degree, Qualifications maybe not needed. But we have both headings possible; we should only include sections with real specific content. If we put degree under Requirements, we have content. Qualifications we could omit if no other content. But we could also put degree under Qualifications and omit Requirements. Which is more appropriate? Usually Requirements are things like degree, experience; Qualifications are skills. But we have skills list separate. So we can put degree under Requirements, and skills under Skills. Qualifications maybe not needed. We'll omit Qualifications. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Check if any other content: maybe "Work closely with design teams both domestically and overseas on different projects." That's a duty. Now produce HTML. Be careful to not include any extra text outside HTML. Let's craft:

      About the role

      Our vision is to transform how the world uses information to enrich life for all. Micron Technology is a world leader in innovating memory and storage solutions that accelerate the transformation of information into intelligence, inspiring the world to learn, communicate and advance faster than ever.

      Responsibilities

      • Serve as the core technical individual contributor in design and validation of the on-chip controller and mixed signal circuitry in NAND Flash chips.
      • Responsible for architecture development and product definition, system integration and full-chip and block-level validation planning and execution.
      • Contribute to RTL design and implementation of the controller hardware, synthesis, APR and full timing closure as well as development of firmware code for NAND internal operations.
      • Work closely with design teams both domestically and overseas on different projects.

      Requirements