Principal Applications 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 that have real specific content. We need to parse the posting. Content: - Intro paragraph about Qorvo (company description). Could be "About the role"? Actually "About the role" is typical heading for description of role. The posting includes description of duties and responsibilities. We'll treat that as "Responsibilities". Also there is "DUTIES:" section. - There's "Hybrid: Four days in the office with one day optional may work home." appears twice (in duties and requirements). That's schedule info. So we can include a Schedule section. - Minimum Requirements: Bachelor's degree + 10 years experience, plus 5 years experience specifics (list). That's requirements/qualifications. We'll put under "Requirements" or "Qualifications". Probably "Requirements". Also "This position is not eligible for visa sponsorship by the Company." That's a note; could be part of Requirements or a separate note. We'll include in Requirements. - "MAKE A DIFFERENCE AT QORVO" paragraph about company culture; could be "About the role" or "About Qorvo". But we have no "About the role" heading requirement; we can use "About the role" for a brief description of the role? Actually the intro about Qorvo is more about company; but we could put under "About the role" maybe not. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We have duties/responsibilities content. So we will have

Responsibilities

with

• items. We have requirements/qualifications content. So

  Requirements

  with
  • . We have schedule info: Hybrid: Four days in the office with one day optional may work home. So

    Schedule

    with

    . We might also have "About the role" maybe not needed because we already have responsibilities. But we could include a short paragraph about the role summarizing the intro? However the instruction: "Prefer a few substantive sections over many thin ones." So we can skip About the role if not needed. The company description could be considered "About the role"? Not exactly. But we could include a brief About the role paragraph summarizing the role: "As the Principal Applications Engineer, be the technical liaison..." That's actually part of duties. So we can incorporate that into Responsibilities. Thus sections: Responsibilities, Requirements, Schedule. Check if any Benefits, Pay info: none. So we omit those. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from duties, requirements, schedule, visa note. We need to format duties as list items. Let's extract duties bullet points: From "DUTIES:" paragraph: - As the Principal Applications Engineer, be the technical liaison between US development teams (Application Engineers, RF Design Engineers) and our organization’s application engineers abroad who are working in direct contact with end customers and technical partners. - Coordinate the activities at both locations to maximize efficiency and shorten time-to-market of our organization’s Radio Frequency (RF) solutions. - This includes working with a number of RF technologies, components, systems, products, and solutions. - Additionally, will act as technical leader driving the voice of the customer: ensure customer critical features and specifications are accounted for in the solutions developed by US design teams. - Highlight customer change requests and new feature requests early enough to US technical teams in order to maintain the relevance of the products in development. - Publish internal documentation detailing new customers’ standards and new architecture choices. - Drive changes in measurement methods to keep them aligned to the latest evolutions of RF communication standards. - Moreover, responsibilities include mentoring and training junior Application Engineers, and Field Application Engineers on new products and new features. - Standardize and document characterization techniques for measurement at the system level. Also there is "Hybrid: Four days in the office with one day optional may work home." (schedule) appears also in duties paragraph but we will treat as schedule. Now requirements: "MINIMUM REQUIREMENTS: Bachelor’s degree in Electrical Engineering or Electronic Engineering and 10 years of experience in the semiconductor, radio communication, or related fields. Also, 5 years of experience stated herein to involve: (1) RF equipment including, signal generators, network analyzers, spectrum analyzers, oscilloscopes, to perform testing and debugging of product evaluation boards and customer reference design boards; (2) RF circuit design, filter design, impedance matching, and PCB board schematic and layout tools; and (3) WiFi IEEE802.11 wireless communication standards and Digital Pre-distortion; (4) platform attachment, validate performance included RF, Throughput, Power consumption. Create design support package and training to support field applications engineers. Support package included datasheet, device revision guide, schematic, layout guide, hardware training guide, and design validation testing performance report; (5) Tier-1 customer support: Design review, RF tuning, internal/external chipset features training, issues debug and root-cause analysis, performance (RF/Throughput/power consumption) improvement, regulatory certification, and mass production yield improvement; (6) perform QDART, QSPR, QRCT, QMINE (find the industry related tools); and (7) WiFi board data file (BDF) tuning on TPC/DPD parameters during RF tuning. Hybrid: Four days in the office with one day optional may work home. This position is not eligible for visa sponsorship by the Company." We need to break into list items preserving details. Could be long but we need to keep all info. We'll create

    • for each major bullet. We need to parse the requirements into logical items: - Bachelor’s degree in Electrical Engineering or Electronic Engineering and 10 years of experience in the semiconductor, radio communication, or related fields. - 5 years of experience involving: 1. RF equipment including signal generators, network analyzers, spectrum analyzers, oscilloscopes, to perform testing and debugging of product evaluation boards and customer reference design boards. 2. RF circuit design, filter design, impedance matching, and PCB board schematic and layout tools. 3. WiFi IEEE802.11 wireless communication standards and Digital Pre-distortion. 4. Platform attachment, validate performance included RF, Throughput, Power consumption. Create design support package and training to support field applications engineers. Support package included datasheet, device revision guide, schematic, layout guide, hardware training guide, and design validation testing performance report. 5. Tier-1 customer support: Design review, RF tuning, internal/external chipset features training, issues debug and root-cause analysis, performance (RF/Throughput/power consumption) improvement, regulatory certification, and mass production yield improvement. 6. Perform QDART, QSPR, QRCT, QMINE (find the industry related tools). 7. WiFi board data file (BDF) tuning on TPC/DPD parameters during RF tuning. - Hybrid: Four days in the office with one day optional may work home. - This position is not eligible for visa sponsorship by the Company. We'll output as list items; maybe combine the 5 years experience as a parent item with sublist? But spec says use
      • for any list of duties/requirements/benefits. It didn't forbid nested lists, but we can keep flat list items; each requirement as a separate
      • . Could embed the subpoints as separate
      • as well. We'll produce:

        Responsibilities

        • As the Principal Applications Engineer, be the technical liaison between US development teams (Application Engineers, RF Design Engineers) and the organization’s application engineers abroad who work directly with end customers and technical partners.
        • Coordinate activities at both locations to maximize efficiency and shorten time-to-market of the organization’s Radio Frequency (RF) solutions.
        • Work with a variety of RF technologies, components, systems, products, and solutions.
        • Act as technical leader driving the voice of the customer: ensure customer critical features and specifications are accounted for in solutions developed by US design teams.
        • Highlight customer change requests and new feature requests early to US technical teams to maintain product relevance.
        • Publish internal documentation detailing new customers’ standards and new architecture choices.
        • Drive changes in measurement methods to keep them aligned with the latest evolutions of RF communication standards.
        • Mentor and train junior Application Engineers and Field Application Engineers on new products and new features.
        • Standardize and document characterization techniques for system‑level measurement.

        Requirements

        • Bachelor’s degree in Electrical Engineering or Electronic Engineering and 10 years of experience in the semiconductor, radio communication, or related fields.
        • Five years of specific experience involving:
          • RF equipment including signal generators, network analyzers, spectrum analyzers, oscilloscopes, to perform testing and debugging of product evaluation boards and customer reference design boards.
          • RF circuit design, filter design, impedance matching, and PCB board schematic and layout tools.
          • WiFi IEEE 802.11 wireless communication standards and Digital Pre‑distortion.
          • Platform attachment, validate performance including RF, throughput, power consumption; create design support package and training for field applications engineers (datasheet, device revision guide, schematic, layout guide, hardware training guide, design validation testing performance report).
          • Tier‑1 customer support: design review, RF tuning, internal/external chipset features training, issue debug and root‑cause analysis, performance (RF/throughput/power consumption) improvement, regulatory certification, and mass production yield improvement.
          • Perform QDART, QSPR, QRCT, QMINE (industry‑related tools).
          • WiFi board data file (BDF) tuning on TPC/DPD parameters during RF tuning.
        • Hybrid work schedule: four days in the office with one day optional to work from home.
        • This position is not eligible for visa sponsorship by the Company.

        Schedule

        Hybrid: Four days in the office with one day optional may work home.

        But we have schedule duplicated; we already included schedule in Requirements as a bullet; but we could still have a separate Schedule section. However to avoid duplication, we could keep schedule only in Requirements and not repeat. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we put schedule only in Requirements, we still preserve it. Having a separate Schedule section would duplicate the same info, which might be considered duplication but not prohibited? It says remove duplicated lines. So we should avoid duplicating the same sentence. So we should not repeat schedule info. We'll keep schedule only in Requirements (or as a separate section but not duplicate). Since we already have schedule bullet in Requirements, we can omit separate Schedule section. Thus final sections: Responsibilities, Requirements. We need to ensure we didn't miss any other substantive info like "MAKE A DIFFERENCE AT QORVO" paragraph about company culture. That is substantive but not a specific section heading; we could incorporate into Responsibilities or maybe an "About the role" section. The instruction says we can use About the role heading. We could create an About the role section with that paragraph. That would be substantive and not duplicated. Let's consider: The paragraph after requirements: "MAKE A DIFFERENCE AT QORVO We are Qorvo. We do more than create innovative RF and Power solutions for the mobile, defense and infrastructure markets – we are a place to innovate and shape the future of wireless communications. It starts with our employees. As a unified global team, we bring a commitment to excellence, growth and