Application Engineer (RF Test)

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: Overview, Learn more..., award-winning culture, etc? The overview includes company description; we need to keep substantive info? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the overview content? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. The "Overview" could be "About the role". The posting includes an overview paragraph about Keysight and role description. So we can put that under

About the role

with

paragraphs. Responsibilities: we have a list under "Responsibilities". Use

• . Qualifications: there is a "Qualifications" heading with Required and Preferred. We need to separate maybe Requirements vs Qualifications? The instruction lists possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. Typically "Requirements" could be required qualifications, "Qualifications" could be preferred? Or we could combine required and preferred under Qualifications. But we have both Required and Preferred sections. Could treat Required as "Requirements" and Preferred as "Qualifications" or "Skills". However we also have a separate "Skills" heading possible. The posting includes "Strong RF troubleshooting, analytical, and problem-solving skills." etc. Those are skills. Could put skills under Skills section. We need to avoid filler sections like Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay range: Utah pay range: MIN $78,520 - MAX $130,870. Also mentions benefits list. So we can include Benefits and Pay sections. Schedule? Not mentioned besides travel up to 25% domestically, occasional international. That's not a schedule; maybe we could put under Schedule? But schedule usually refers to work hours, shift etc. Not present. So we should not create Schedule section unless there is real specific content. The posting does not mention work schedule (e.g., full-time, hours). So omit Schedule. Benefits: list of benefits present. So include Benefits. Pay: include Pay. Now we need to ensure we don't include boilerplate like "Visa Sponsorship is unavailable for this position." That's substantive? It's a note about visa sponsorship. Could be considered relevant. Should we keep? It's not boilerplate; it's a specific condition. Might keep under Qualifications or Requirements? Could be a separate note but we don't have a heading for that. Could incorporate into Qualifications as a note. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Visa sponsorship is not exactly that; it's a condition. I'd keep it. Also "Careers Privacy Statement Keysight is an Equal Opportunity Employer..." that's boilerplate EEO; remove. Now we need to output only HTML fragment, no /, no markdown. Let's structure:

  About the role

  Overview text...

  Responsibilities

  • ...
  ...

  Requirements

  • Required qualifications list
  ...

  Qualifications

  Preferred experience...

  maybe also list.

  Skills

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  Utah pay range: MIN $78,520 - MAX $130,870. Note: For other locations, pay ranges will vary by region.

  We must not include Schedule. Now we need to extract the exact substantive content. Let's parse the posting. Overview section: "Overview Keysight is at the forefront of technology innovation, delivering breakthroughs and trusted insights in electronic design, simulation, prototyping, test, manufacturing, and optimization. Our ~15,000 employees create world-class solutions in communications, 5G, automotive, energy, quantum, aerospace, defense, and semiconductor markets for customers in over 100 countries. Learn more about what we do. Our award-winning culture embraces a bold vision of where technology can take us and a passion for tackling challenging problems with industry-first solutions. We believe that when people feel a sense of belonging, they can be more creative, innovative, and thrive at all points in their careers. Keysight Technologies is building on the trusted GPS/GNSS and Positioning, Navigation, and Timing (PNT) expertise acquired from Spirent to deliver advanced test solutions for U.S. government agencies, defense contractors, and industry partners. Our technologies help ensure the performance, reliability, and resilience of mission-critical navigation systems supporting aircraft, satellites, rockets, autonomous platforms, drones, and next-generation communications. As an Application Engineer, you'll be a trusted technical advisor, working directly with customers to deploy, support, and optimize industry-leading GPS/GNSS test solutions. You'll combine hands-on RF troubleshooting, technical problem solving, and customer engagement to help solve complex challenges while partnering closely with hardware and software engineering teams to improve our products and deliver an exceptional customer experience. This is an excellent opportunity for an engineer who enjoys working directly with customers, thrives on solving real-world technical problems, and wants to build expertise in cutting-edge navigation and RF technologies. Beyond customer support, you'll have opportunities to develop technical training, create application content, participate in user conferences, and grow your career within Keysight Technologies. This position is based in Pleasant Grove, Utah. Candidates with significant GPS/GNSS or Positioning, Navigation, and Timing (PNT) experience may also be considered for remote work if located near key aerospace and defense customer hubs, including Colorado Springs, Tewksbury, MA, Los Angeles/San Diego, Huntsville, Tucson, Dayton, or the Mid-Atlantic/Boston region." We need to keep all that but remove "Learn more about what we do." maybe it's a link; but it's part of overview. It's not boilerplate; it's a call to action. Might keep but it's vague. However it's not substantive detail; but it's part of the overview. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. "Learn more about what we do." is not substantive detail; it's a generic phrase. Could be considered boilerplate? It's not navigation/legal/EEO. Might be okay to keep but it's not adding value. I'd keep it as part of the overview paragraph. Now Responsibilities list: "Serve as the primary technical resource for customers after product deployment, providing timely support via phone, remote sessions, and onsite visits. Diagnose, replicate, troubleshoot, and resolve hardware, software, and system configuration issues involving GPS/GNSS and RF test solutions. Guide customers through system setup, test configuration, and best practices to ensure the successful deployment and operation of Keysight's GPS/GNSS test solutions. Support installation, system integration, upgrades, and onsite technical assistance for mission-critical customer environments. Collaborate with hardware and software engineering teams to troubleshoot complex technical issues, communicate product defects, and recommend product enhancements based on customer feedback. Act as the voice of the customer by identifying trends, documenting recurring issues, and providing technical insights that influence product quality, usability, and future development. Create customer-focused technical content, including application notes, knowledge articles, training materials, and instructional videos that improve the customer experience and reduce support requests. Deliver technical presentations, demonstrations, and hands-on training during customer visits, user conferences, and other technical events. Document and manage customer support cases using Salesforce and other support tools, maintaining accurate records of issues, resolutions, and customer communications. Build strong customer relationships through technical expertise, professionalism, and a commitment to delivering exceptional customer experience. Travel up to 25% domestically, with occasional international travel for training or business needs." We'll put each as
• . Now Requirements (Required qualifications): "Required Bachelor's degree in Electrical Engineering, Mechanical Engineering, Physics, or another related engineering discipline. Typically 2+ years of hands-on engineering experience, including internships or relevant industry experience. Hands-on experience with RF test and measurement equipment, including: Spectrum analyzers Signal generators Power meters Strong RF troubleshooting, analytical, and problem-solving skills. Experience troubleshooting hardware, software, and system configuration issues. Ability to communicate complex technical concepts clearly to customers and internal engineering teams. Strong interpersonal skills with a customer-focused mindset and a collaborative approach to problem solving. Willingness to travel up to 25% domestically, with occasional international travel. U.S. citizenship required due to federal customer requirements. Ability to obtain and maintain a U.S. security clearance. Ability to lift, carry, and move materials and equipment weighing up to 50 pounds, with or without reasonable accommodation. Equipment weighing more than 50 pounds is moved using team assistance or appropriate material-handling equipment. Ability to work onsite in Pleasant Grove, Utah is preferred. Candidates with significant GPS/GNSS or PNT experience who are located near key customer regions may also be considered for a remote work arrangement." We need to keep all that. Some lines are sub-bullets; we can flatten. Now Qualifications (Preferred): "Preferred Experience with GPS/GNSS, positioning, navigation, or timing (PNT) technologies. Experience supporting customers in technical, applications engineering, field engineering, or customer support role. Familiarity with defense, aerospace, government, or other regulated industries. Experience with Windows-based software installation, configuration, and troubleshooting. Basic scripting experience using Python or similar languages. Experience with MATLAB, LabVIEW, or other engineering software tools. Experience using Salesforce or similar CRM/support case management systems. Experience creating technical documentation, application notes, training materials, or delivering technical presentations" Now Skills: The posting includes many skill mentions within responsibilities and qualifications. But we could extract explicit skill statements: "Strong RF troubleshooting, analytical, and problem-solving skills." "Ability to communicate complex technical concepts clearly..." "Strong interpersonal skills..." etc. However those are already in qualifications. Might be redundant. But we could still create a Skills section summarizing skill-based items not captured elsewhere. However instruction: Prefer a few substantive sections over many thin ones. Could combine skills into Qualifications. But we have both Required and Preferred; maybe we treat Required as Requirements, Preferred as Qualifications, and Skills could be omitted or combined. However we need to decide if we include Skills heading. The posting does not have a separate "Skills" section; skills are embedded. If we create a Skills heading, we would need to extract skill-specific content; but that would be duplicative. Might be better to omit Skills section to avoid thin section. However the instruction says we can use Skills heading if there is real specific content. There is skill content, but it's already covered. Could still create a Skills section with those skill statements. But that would be repeating content already in Requirements/Qualifications, which might be considered duplication but not invented. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but might be redundant. However they said prefer a few substantive sections over many thin ones. So better to not create a Skills section if its content is already covered elsewhere. So we can omit Skills. Now Benefits: list: "Medical, dental and vision Health Savings Account Health Care and Dependent Care Flexible Spending Accounts Life, Accident, Disability insurance Business Travel Accident and Business Travel Health 401(k) Plan Flexible Time Off, Paid Holidays Paid Family Leave Discounts, Perks Tuition Reimbursement Adoption Assistance