Specialist , Engineering Services

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings. We need to include sections only when posting has real specific content for it. So we need to decide content for each. We have content for: - About the role: company intro + job description paragraph. - Responsibilities: Essential Functions list. - Requirements: maybe the security clearance requirement? Also maybe "Ability to Obtain US Security Clearance." is a requirement. Could also include "Ability to work autonomously and with others to resolve technical issues" etc? Those are under Preferred Additional Skills? Actually those are under Preferred Additional Skills list: "Ability to work autonomously and with others to resolve technical issues" and "Proven and effective communications skills, interpersonal skills and customer focus are a must". Those are skills. - Qualifications: education/experience alternatives (Bachelor’s + 4 years, Graduate + 2 years, or 8 years no degree). - Skills: Preferred Additional Skills list (experience with test equipment, SMT, RF, etc.) - Benefits: list of benefits. - Pay: salary range. - Schedule: 9/80 schedule. Thus we have content for all sections. Now we need to output HTML fragment with

headings and appropriate

or

• . We must not include boilerplate like EEO, legal, etc. We must preserve all substantive info; do not invent or summarize away detail. We need to include the exact text as much as possible. Let's craft each section. About the role: Combine the introductory paragraph about L3Harris dedication and the Job Description paragraph. Should we include both? The instruction: Preserve ALL substantive information. So include both. Thus:

  L3Harris is dedicated to recruiting and developing high-performing talent who are passionate about what they do. Our employees are unified in a shared dedication to our customers’ mission and quest for professional growth. L3Harris provides an inclusive, engaging environment designed to empower employees and promote work-life success. Fundamental to our culture is an unwavering focus on values, dedication to our communities, and commitment to excellence in everything we do. L3Harris is the Trusted Disruptor in defense tech. With customers’ mission-critical needs always in mind, our employees deliver end-to-end technology solutions connecting the space, air, land, sea and cyber domains in the interest of national security.

  This role will contribute to the company’s success by being responsible for supporting the design, documentation, requirements management, integration, troubleshooting and/or testing analysis of electronic, mechanical and/or software devices, products and systems. They will work with development engineers to support and recommend resolutions and understand and apply applicable engineering processes. They may develop plans and schedules for short-term work activities. This candidate will interface with engineering teams and elevate significant problems to appropriate management. They may build customer intimacy through job assignments related system/product acceptance testing or hands-on user training.

  We could combine into one

  but it's okay to have multiple

  under same heading? The instruction: Use

  for prose. It doesn't forbid multiple

  . We'll output multiple

  under the heading. Responsibilities: Essential Functions list. We'll output

  • for each. List items exactly as in posting, preserving punctuation. Let's copy: - Executes complex projects or processes with general oversight. - Performs engineering tests, detailed experimental testing or operational test and fault isolation on systems and equipment. - Performs electrical or mechanical troubleshooting to determine problems in equipment. May work with complex machines or computer systems. - Perform subsystem and system level verification and validation testing. - Dismantles, adjusts, repairs, calibrates, aligns, assembles and operates equipment according to layout plans, blueprints, operating or repair manuals, rough sketches or drawings. - Uses test and diagnostic equipment to perform checkouts. - Identify, track and repair assigned hardware defects - Utilizes the L3Harris order entry system to order cables, attenuators, and other ancillary items. - Build cables, repairing radio and ancillary hardware. - Tracks radio and other development assets. - Ability to Obtain US Security Clearance. Note: some items start with capital verb, some lower case. Keep as is. Requirements: Ability to Obtain US Security Clearance? But that's already in Essential Functions. However we could still list it under Requirements as a requirement. But we might duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in the source? It appears in Essential Functions; we could still include it under Requirements but that would be duplication. Might be considered unnecessary but not prohibited. However better to avoid duplication; we could put the security clearance under Requirements and not repeat in Essential Functions? But Essential Functions includes it; we need to preserve that info somewhere. If we remove it from Essential Functions, we lose it. So we need to keep it somewhere. We could keep it in Essential Functions and not duplicate in Requirements. Then Requirements would be empty -> we shouldn't output heading. But we need to decide if there is any other requirement content besides that. The posting doesn't have a separate "Requirements" section besides Qualifications. So maybe we should not output a Requirements heading at all, because there is no distinct requirement content beyond what's covered in Qualifications and Essential Functions. However the instruction list includes Requirements as an example, but we only include if posting has real specific content for it. Since there is no separate Requirements section, we skip it. Thus we will not include Requirements heading. Qualifications: education/experience alternatives. We'll output

    containing the three alternatives. Text: "Bachelor’s Degree and minimum 4 years of prior relevant experience.Graduate Degree and a minimum of 2 years of prior related experience.In lieu of a degree, minimum of 8 years of prior related experience." Note there are no spaces after periods? In original: "Bachelor’s Degree and minimum 4 years of prior relevant experience.Graduate Degree and a minimum of 2 years of prior related experience.In lieu of a degree, minimum of 8 years of prior related experience." We'll preserve exactly. We could wrap in

    . Skills: Preferred Additional Skills list. List items: - Experience working with common test equipment such as oscilloscopes, logic analyzers, and voltmeters is required - Experience with assembly and repair methods for surface mount technology (0402 scale) - Basic understanding of Radio Frequency circuits and Software Defined Radio architectures - Experience with RF Communications systems (ASICs, PLLs, DACs, Amplifiers, and/or Power Supply circuitry preferred) - Experience with Configuration Management software (Agile preferred) - Experience writing failure analysis reports, test data summaries, or process documentation - Experience managing/maintaining calibration or electronics laboratory areas - Experience purchasing parts or equipment in support of engineering (P-Card responsibility preferred) - Working knowledge of IPC-610, IPC-620, and IPC-7711/7721 (certifications preferred) - Ability to work autonomously and with others to resolve technical issues - Proven and effective communications skills, interpersonal skills and customer focus are a must Note: some items have "is required" etc. Keep as is. Benefits: list: "health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, and company-paid holidays." Also note "The specific programs and options available to an employee may vary depending on date of hire, schedule type, and the applicability of collective bargaining agreements." That's also substantive; we should include that as prose after list. Thus we