Radio Frequency Hardware Engineer I

We need to output HTML fragment with sections: About the role? The posting includes description about company and role. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We have: - About the role: The description of the role: "Our North American Semiconductor group is searching for an experienced Radio Frequency Hardware Engineer to develop and qualify new proprietary Radio Frequency (RF) data-acquisition hardware for high-speed voltage-current-impedance data acquisition and analysis for applications in semiconductor RF plasma generator and matching network applications." Also earlier paragraphs about company but not role specifics. We'll put that as About the role. - Responsibilities: The list under "Essential Job Functions" bullet points. Those are responsibilities. - Requirements: The "Skills/Experience Required" bullet list. - Qualifications: Might be overlapping with requirements; but we can treat "Skills/Experience Required" as Requirements. Qualifications maybe education? Could separate: Bachelor's degree etc. But we can combine. - Skills: maybe the same as requirements. But we need to avoid duplication. The instruction: prefer few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements (including skills/education), Benefits. Pay and Schedule not mentioned, so omit. - Benefits: The "Compensation Package" paragraph includes details: 401(k) match, dental, vision, life, disability, medical insurance, etc. That's benefits. We should not include EEO, accommodation, application instructions, etc. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include each bullet point exactly as given. Let's extract bullet points: Essential Job Functions: - Designs RF circuits, probes/sensors and systems for high-frequency (kHz to GHz) data acquisition of voltage, current, impedance signals used on RF generators and matches networks used for plasma etch or remote plasma processing equipment. - Conducts simulation, analysis, and modeling of RF circuits using Multiphysics, CAE or other types of simulators like Comsol, Cadence, Ansys, SPICE, etc. - Prototypes, tests, and validates RF hardware designs in laboratory environments. - Collaborates with PCB designers to ensure RF layout guidelines are followed for optimal performance. - Characterizes and optimizes RF components such as amplifiers, filters, spectrum analyzer ADC’s, and other power/ data acquisition components. - Generates documentation including schematics, PCB layout guidelines, test procedures, and design verification reports. Skills/Experience Required: - Bachelor’s degree in electrical engineering, or related field. - Master’s or PhD degree preferred. - Minimum of 5 years of experience in RF data acquisition or RF power control hardware design and development. - Proficiency in RF simulation and design tools such as Comsol, Cadence, Mentor, Ansys, SPICE, etc. - Hands-on experience with RF test equipment such as spectrum analyzers, network analyzers, signal generators, etc. - Familiarity with PCB layout techniques for RF and high-speed data acquisition circuits, Mentor Graphics or Cadence schematic capture and PCA-PCB layout experience preferable. - Strong analytical and problem-solving skills. Compensation Package paragraph: "HORIBA Instruments offers a competitive compensation package that includes a 401(k) plan with match; employee group dental, vision, life, and disability (short and long-term) paid for by the company; medical insurance, family dental and vision insurance, and supplemental life insurance available with reasonable employee contributions; employee assistance program; paid holidays, vacation, and sick time; flexible spending accounts; and educational reimbursement and commuter benefit programs." We need to preserve all details. Could turn into a list? It's a sentence with semicolons. Could keep as

  . But instruction: Use

  • for any list of duties/requirements/benefits. Benefits is a list; we could split into items. But we must preserve all info; we can convert each item separated by semicolon into
  • . That would be okay as it's still preserving. However we must not invent or summarize away detail. Splitting is fine as long as we keep each item verbatim. Let's split: - a 401(k) plan with match - employee group dental, vision, life, and disability (short and long-term) paid for by the company - medical insurance, family dental and vision insurance, and supplemental life insurance available with reasonable employee contributions - employee assistance program - paid holidays, vacation, and sick time - flexible spending accounts - educational reimbursement and commuter benefit programs Check that we didn't lose any nuance: The original: "HORIBA Instruments offers a competitive compensation package that includes a 401(k) plan with match; employee group dental, vision, life, and disability (short and long-term) paid for by the company; medical insurance, family dental and vision insurance, and supplemental life insurance available with reasonable employee contributions; employee assistance program; paid holidays, vacation, and sick time; flexible spending accounts; and educational reimbursement and commuter benefit programs." Our list matches. Now About the role: We need prose. Could be a paragraph summarizing the role description. The posting includes: "Our North American Semiconductor group is searching for an experienced Radio Frequency Hardware Engineer to develop and qualify new proprietary Radio Frequency (RF) data-acquisition hardware for high-speed voltage-current-impedance data acquisition and analysis for applications in semiconductor RF plasma generator and matching network applications." Also earlier paragraphs about company but not role specifics. We'll include that sentence as About the role. Could also include earlier description about HORIBA's focus? That's more company overview, not role. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can include role description. We'll put About the role as

    containing that sentence. Now Responsibilities: Use

    • for each bullet. Requirements: Use
      • for each bullet. Benefits: Use
        • for each item. We should not include Pay or Schedule sections. Now output HTML fragment only. Let's craft:

          About the role

          Our North American Semiconductor group is searching for an experienced Radio Frequency Hardware Engineer to develop and qualify new proprietary Radio Frequency (RF) data-acquisition hardware for high-speed voltage-current-impedance data acquisition and analysis for applications in semiconductor RF plasma generator and matching network applications.

          Responsibilities

          • Designs RF circuits, probes/sensors and systems for high-frequency (kHz to GHz) data acquisition of voltage, current, impedance signals used on RF generators and matches networks used for plasma etch or remote plasma processing equipment.
          • Conducts simulation, analysis, and modeling of RF circuits using Multiphysics, CAE or other types of simulators like Comsol, Cadence, Ansys, SPICE, etc.
          • Prototypes, tests, and validates RF hardware designs in laboratory environments.
          • Collaborates with PCB designers to ensure RF layout guidelines are followed for optimal performance.
          • Characterizes and optimizes RF components such as amplifiers, filters, spectrum analyzer ADC’s, and other power/ data acquisition components.
          • Generates documentation including schematics, PCB layout guidelines, test procedures, and design verification reports.

          Requirements

          • Bachelor’s degree in electrical engineering, or related field.
          • Master’s or PhD degree preferred.
          • Minimum of 5 years of experience in RF data acquisition or RF power control hardware design and development.
          • Proficiency in RF simulation and design tools such as Comsol, Cadence, Mentor, Ansys, SPICE, etc.
          • Hands-on experience with RF test equipment such as spectrum analyzers, network analyzers, signal generators, etc.
          • Familiarity with PCB layout techniques for RF and high-speed data acquisition circuits, Mentor Graphics or Cadence schematic capture and PCA-PCB layout experience preferable.
          • Strong analytical and problem-solving skills.

          Benefits

          • a 401(k) plan with match
          • employee group dental, vision, life, and disability (short and long-term) paid for by the company
          • medical insurance, family dental and vision insurance, and supplemental life insurance available with reasonable employee contributions
          • employee assistance program
          • paid holidays, vacation, and sick time
          • flexible spending accounts
          • educational reimbursement and commuter benefit programs
          Check that we didn't miss any info: The earlier paragraphs about HORIBA's motto, JOY and FUN, etc. Are those substantive? They are company culture but not role-specific. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Should we include that? It's about company culture, maybe considered substantive but not role-specific. However the instruction also says "Prefer a few substantive sections over many thin ones." Including a company overview section could be a section like "About the company". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could add a section like "About the company" but not in allowed headings? The instruction says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could add other headings if needed, but they gave examples. Safer to stick to those. The company overview might be considered "About the role"? Not exactly. But we could incorporate some of that into About the role paragraph if we want to preserve. However the About the role paragraph currently only includes the role search sentence. We could expand to include company description: "HORIBA has kept its sights keenly focused on this micro world and provides rewarding careers in Sales and Marketing, Research and Development, Production, and Operations. HORIBA Semiconductor's proprietary analysis technology is fully demonstrated in a wide range of fields - semiconductors, medicine, environment, science, and engine measurements. In high-tech industries like semiconductor manufacturing, HORIBA provides an extensive selection of process monitors for integration into manufacturing lines that aid the safe production of high-performance devices. The HORIBA Group of worldwide companies provides an extensive array of instruments and systems for applications ranging from automotive R&D, process and environmental monitoring, in-vitro medical diagnostics, semiconductor manufacturing and metrology, to a broad range of scientific R&D and QC measurements. Proven quality and trustworthy performance have established widespread confidence in the HORIBA Brand. Inspired by our unique motto, “JOY and FUN,” we focus on social responsibilities by building state-of-the-art products for scientific advancement; especially for protecting health, safety, and the environment. “HORIBARIANs,” the HORIBA employees all over the world, look forward to working with additional creative and entrepreneurial self-starters. To learn more about our unique culture and vision for our future, visit Our Future page." That's a lot of substantive info about the company. Should we include? The instruction says preserve ALL substantive information. So we should include it. Where? Could be part of About the role section (makes sense). Or we could add a separate section like "About the company". But the allowed headings list includes About the role, Responsibilities, etc. We could put company overview under About the role as well, making it longer. That would preserve all info. Thus About the role paragraph could be multiple paragraphs? We can use <