Electronic Warfare, Systems Engineering Lead

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 as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove application instructions. Must not include placeholder sections like Pay/Schedule/Benefits unless posting actually states them. The posting includes Job Schedule: 9/80- employees work 9 out of 14 days, totaling 80 hours worked- and have every other Friday off. So schedule is present. Pay: salary range given: $127,500-$236,500 (with note). So Pay section can be included. Benefits: they list benefits: health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, company-paid holidays. So Benefits section can be included. We need sections: About the role? The posting includes a description about L3Harris mission etc. Could be "About the role" or "Job Description". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have: - About the role: maybe the introductory paragraph about L3Harris dedication etc. But we should not repeat job title. Could include "About the role" with description of role and mission. - Responsibilities: list of essential functions (the bullet list). Those are duties. - Requirements: maybe the qualifications (education/experience) and clearance etc. - Qualifications: maybe separate? Actually they have "Qualifications:" heading in posting. Could treat that as Qualifications section. But we also have Requirements maybe overlapping. The instruction says we can have both Requirements and Qualifications sections if content exists. We need to decide what goes where. The posting has "Qualifications:" with bullet points: Bachelor’s Degree and minimum 9 years... etc. Also "Preferred Additional Skills:" list. Thus we can have: - Qualifications: the mandatory qualifications (degree/experience, clearance, travel %). - Skills: the preferred additional skills list. - Responsibilities: essential functions list. - About the role: maybe the paragraph describing L3Harris and the role purpose. - Pay: salary range. - Benefits: benefits list. - Schedule: job schedule description. We must not include boilerplate like EEO, legal, etc. Also remove duplicated lines. We need to preserve all substantive information. So we need to include all details from the posting that are not boilerplate. Let's extract substantive content: Intro paragraph: "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." That's about company, could be About the role. Job Title line: we ignore. Job Code etc ignore. Job Location: Clifton, NJ - maybe we could include location in About the role? But instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Location is minor metadata; we could include in a short paragraph maybe under About the role or separate? Probably we can include location in a short

after About the role heading? But they said "fold minor metadata into a short

or drop it." So we could include location in a short paragraph after About the role heading, maybe as part of About the role content. Job Schedule: we have schedule description. Job Description paragraph: "L3Harris provides the knowledge, technology, and techniques needed for mission success against threats across air, land and sea domains. We have and continue to deliver high-performing EW, ESM, ELINT, and Radar systems that meet/exceed the performance, cost, schedule needs of our military customers. And, best of all, we’re looking to grow our team! We are seeking a Systems Engineer with radar expertise and strong customer engagement skills to support advanced radar system development and strategic growth initiatives. The selected candidate will contribute to system requirements, architecture, performance analysis, integration, and test activities while also supporting customer interactions, technical presentations, and business development efforts. The ideal candidate has experience in radar or sensor systems engineering and is comfortable working directly with customers to understand mission needs, shape technical solutions, and support capture and proposal activities. This role requires strong communication skills and the ability to operate effectively in a cross-functional environment. If you believe you fit the bill, we’d love to meet you and talk about your future at L3Harris!" That's substantive; could be part of About the role or Responsibilities? It's more about role description. We'll put under About the role. Essential Functions list: each line starts with a verb. We'll put under Responsibilities as

• . Qualifications: list: - Bachelor’s Degree and minimum 9 years of prior relevant experience. - Graduate Degree and a minimum of 7 years of prior related experience. - In lieu of a degree, minimum of 13 years of prior related experience. - 9 years of experience in systems engineering for radar, RF, or sensor systems - Ability to obtain secret clearance - 10%-20% travel We need to preserve all. We'll put under Qualifications as
  • . Preferred Additional Skills list: - 9 years of experience radar principles and system performance analysis - 9 years of experience with requirements development and verification - Customer-facing, business development, or stakeholder engagement experience - Strong communication and teamwork skills - Master’s degree in a relevant technical field. - Experience with airborne, maritime, ground-based, or multi-mission radar systems. - Familiarity with MBSE methods and tools. - Experience with tools such as DOORS, Cameo, MATLAB, Simulink, or Python. - Experience supporting proposals, customer demos, technical roadmaps, and strategic growth initiatives. - Knowledge of RF systems, antennas, EW environments, or advanced sensing concepts. We'll put under Skills as
    • . Pay: salary range: "$127,500-$236,500. This is not a guarantee of compensation or salary, as final offer amount may vary based on factors including but not limited to experience and geographic location." We'll put under Pay as

      . 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." We'll include that note. Schedule: "Job Schedule: 9/80- employees work 9 out of 14 days, totaling 80 hours worked- and have every other Friday off". We'll put under Schedule as

      . We must not include boilerplate: EEO, legal, E-Verify, etc. Also remove duplicated lines. Now produce HTML fragment with headings

      for each section we include. Order: About the role, Responsibilities, Requirements? Actually we have Qualifications and Skills separate. The instruction list includes Requirements, Qualifications, Skills. We have Qualifications (mandatory) and Skills (preferred). We could treat Requirements as maybe the qualifications? But we already have Qualifications. To be safe, we can include Requirements section for the mandatory qualifications (maybe same as Qualifications). But we cannot duplicate content. Better to follow instruction: we can have Requirements and Qualifications both if content distinct. But we have only one set of qualifications. Could split: Requirements = education/experience/clearance/travel; Qualifications = maybe the "Preferred Additional Skills"? But they already have Skills heading. Hmm. The instruction list: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. We should include sections only when posting has real specific content. So we need to decide which headings map to our content. We have: - About the role: yes. - Responsibilities: yes (essential functions). - Requirements: could be the mandatory qualifications (education/experience, clearance, travel). We'll label that as Requirements. - Qualifications: maybe the "Preferred Additional Skills"? But they are skills, not qualifications. However Qualifications could be the degree/experience etc. But we already used that for Requirements. To avoid duplication, we could treat Qualifications as the preferred additional skills (though they are skills). But we also have Skills heading. Could combine: Qualifications = preferred additional skills, Skills = maybe something else? Not needed. Better: Use Requirements for mandatory qualifications, Qualifications for preferred additional skills, Skills maybe omitted or we could put technical skills under Skills. But the preferred list includes both experience and skills. Could split: Qualifications = preferred additional skills (including Master's degree, experience with systems, familiarity with MBSE, tools, etc). Skills = maybe the soft skills like strong communication and teamwork skills, customer-facing experience? But that's messy. Given the instruction says "Prefer a few substantive sections over many thin ones." So we should not over-section. Perhaps we combine Requirements and Qualifications into one section called Qualifications (or Requirements). But we need to follow heading examples; we can choose either. Let's pick "Qualifications" for mandatory qualifications (degree/experience/clearance/travel). And "Skills" for preferred additional skills. That seems logical: Qualifications = baseline qualifications; Skills = preferred skills. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We will not include Requirements heading. Now ensure we don't include any placeholder text like "commensurate with experience". Not present. Now produce HTML. We need to wrap content in appropriate tags. Example:

      About the role

      L3Harris is dedicated to recruiting and developing high-performing talent ... 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. The position is located in Clifton, NJ.

      We need to include the job description paragraph as well. Could combine. Let's craft About the role paragraph: combine the introductory company description and the job description paragraph. We'll include location as a short sentence. Now Responsibilities:
      • each essential function. Essential Functions list lines: - Support the development and management of system requirements, architectures, and interface definitions for radar systems and related subsystems. - Perform system-level analysis, trade studies, and performance assessments for radar solutions in support of customer and program needs. - Partner with engineering, program management, and business development teams to align technical solutions with customer requirements and strategic growth objectives. - Engage directly with customers to understand mission needs, communicate technical capabilities, and support solution development. - Support capture, proposal, and business development activities, including technical presentations, white papers, requirements analysis, and customer briefings. - Assist in defining and communicating radar system concepts, operational use cases, and differentiated technical approaches. - Support integration, verification, validation, and test planning for radar systems. - Collaborate across multidisciplinary teams including systems, software, RF, antenna, hardware, and test engineering. - Participate in technical and program reviews and help drive resolution of technical issues and customer concerns. - Build and maintain strong customer relationships while serving as a trusted technical interface between internal teams and external