Engineer Principal – RF Software

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 must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the job description and extract content. Sections: - About the role: maybe the introductory paragraph: "Be a part of cutting-edge RF technology implementation! The Software and Ground Solutions group at BAE Systems Space & Mission Systems (SMS) is looking to expand our RF technologies team with a talented and energetic software engineer. The successful candidate will have a foundation in software engineering, modeling, and simulation, with experience in RF systems. As a key member of our cross-functional engineering team, the engineer will be responsible for designing, developing, and testing software applications that support RF systems. The Engineering, Science and Analysis (ESA) Strategic Capabilities Unit comprises the technical talent and organizational leadership that enables the successful delivery of high-impact discriminating technologies for our customers’ missions. Our collaborative, cross-functional teams are committed to innovation, integrity, continual learning and strong execution." That's about the role. - Responsibilities: list of duties: bullet points from "What You’ll Do" list. - Requirements: maybe Required Education, Experience, & Skills. - Qualifications: maybe Preferred Education, Experience, & Skills. - Skills: maybe separate? But we can combine. However we need to avoid thin sections. Could have Requirements (required) and Preferred Qualifications. - Benefits: Employee Benefits paragraph. - Pay: Pay Information. - Schedule: On-Site Work Environment (requires on-site five days each week). Also maybe Working Conditions? But schedule is about work schedule. The posting says: "Maintain a regular and predictable work schedule." and "On-Site Work Environment: This position requires regular in-person engagement by working on-site five days each normally scheduled week in the primary work location." So schedule section can include that. We should not include sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no markdown fences. Let's craft:

About the role

...

Responsibilities

• Convert Algorithm Description Documents (ADDs) into C++ software code for radar systems.
... etc. We need to include all bullet points from "What You’ll Do". Let's list them: - Convert Algorithm Description Documents (ADDs) into C++ software code for radar systems. - Develop and test software applications for radar tool chains and algorithms. - Collaborate with engineers and researchers to integrate radar systems with experimental data and analytical tools. - Analyze and optimize radar system performance, ensuring scalability and reliability. - Work with stakeholders to identify and prioritize project requirements, and develop solutions that meet business needs. - Participate in code reviews, ensuring adherence to coding standards and best practices. - Maintain a regular and predictable work schedule. - Establish and maintain effective working relationships within the department, the Strategic Business Units, Strategic Capabilities Units and the Company. - Interact appropriately with others in order to maintain a positive and productive work environment. - Perform other duties as necessary. We could keep "Maintain a regular and predictable work schedule." maybe also in Schedule section, but it's also a responsibility. We'll keep it there. Now Required Education, Experience, & Skills: - BS degree or higher in Engineering or a related technical field is required plus 6 or more years related experience. - Each higher-level degree, i.e., master’s degree or Ph.D., may substitute for two years of experience. - Related technical experience may be considered in lieu of education. - Degree must be from a university, college, or school which is accredited by an agency recognized by the US Secretary of Education, US Department of Education. - A current, active Secret clearance is required with the ability to obtain and maintain a Top Secret/SCI security clearance. - Experience in designing, developing, and testing software for RF processing or simulations using programming languages such as C, C++. - Containerization (Docker, Kubernetes, ContainerD). - Experience in developing test, simulation, or data processing applications in high-level languages such as Python, Ruby, or MATLAB. - Experience with object-oriented design. - Solid understanding of numerical methods, data structures, and algorithms. - Experience with some tactical mission domain. - Excellent problem-solving skills, with attention to detail and ability to work in a fast-paced environment. - Solid communication and collaboration skills, with ability to work effectively with cross-functional teams. We'll put these in
• . Preferred Education, Experience, & Skills: - Experience using Cameo or PlantUML for Design. - Experience designing/developing an SDR. - Experience designing/developing mission skills. - DevSecOps. - Understanding of high-speed network architectures. - Understanding of GPU use for algorithm implementation. - Testing frameworks (gtest, test-driven development, hardware-in-the-loop). - Understanding of Cyber Security Controls for integrity and cyber resiliency. - Knowledge in implementing secure communication protocols (IPSEC). - Experience implementing encryption. - A working knowledge of Agile lifecycles and activities in each phase. - Experience with formal software development practices including the use of software configuration management, coding standards, and style guides. We'll put in a section maybe "Preferred Qualifications". Could be heading "Qualifications". But we already have Requirements. Could use "Preferred Qualifications". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (required) and Qualifications (preferred). Or we could combine skills. But we have both required and preferred. We'll do Requirements for required, Qualifications for preferred. Skills: maybe we could extract specific skills from both lists? But we already have them in Requirements and Qualifications. To avoid thin sections, maybe we skip Skills section and keep Requirements and Qualifications. Benefits: paragraph about health, dental, vision, HSA, 401(k), disability, life and accident insurance, employee assistance program, legal plan, perks, leave programs, recognition program, other incentives. Pay: Pay Information: Full-Time Salary Range: $118095 - $200762 plus note. Schedule: On-Site Work Environment: five days each week on-site, travel and local commute may be required. Also Working Conditions: office, lab, production floor, cleanroom, outdoors, remote research environment, may occasionally work in production work centers where protective equipment required, may access other facilities in various weather conditions. That's more about work environment than schedule, but we can include in Schedule or maybe a separate section? The instruction says include Schedule only if posting actually states them. It does state schedule (regular and predictable work schedule, on-site five days). So we can include schedule details. Working Conditions could be part of Schedule or maybe we could add a section "Working Conditions" but not in allowed headings. We'll incorporate into Schedule section. Thus Schedule section:

  On‑site work environment: regular in‑person engagement five days each normally scheduled week in the primary work location. Travel and local commute between company campuses and other non‑company locations may be required. Work is performed in an office, laboratory, production floor, or cleanroom, outdoors or remote research environment; may occasionally work in production work centers where use of protective equipment and gear is required; may access other facilities in various weather conditions. Maintain a regular and predictable work schedule.

  Now we need to ensure we don't repeat job title. No mention. We must not include boilerplate like EEO, legal, scam warning, navigation, cookie, etc. The text includes "This position will be posted for at least 5 calendar days..." etc. That's boilerplate; we should remove. Also "About BAE Systems Space & Mission Systems" maybe considered company description; is that substantive? It's about the company, not the role. Might be considered boilerplate but could be considered part of "About the role"? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About BAE Systems Space & Mission Systems" is not exactly those but could be considered company overview. It's not strictly required to keep; but it's substantive info about the employer. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it if it's substantive. However the allowed headings do not include a generic "About the company". Could we put it under About the role? Might be okay to extend About the role paragraph to include that. But the About the role currently is about the team and mission. Adding company description may be okay. Alternatively we could create a section "About BAE Systems" but not in allowed headings. Better to incorporate into About the role. Thus About the role paragraph will include the initial description plus the company description. Let's craft About the role paragraph: "Be a part of cutting-edge RF technology implementation! The Software and Ground Solutions group at BAE Systems Space & Mission Systems (SMS) is looking to expand our RF technologies team with a talented and energetic software engineer. The successful candidate will have a foundation in software engineering, modeling, and simulation, with experience in RF systems. As a key member of our cross-functional engineering team, the engineer will be responsible for designing, developing, and testing software applications that support RF systems. The Engineering, Science and Analysis (ESA) Strategic Capabilities Unit comprises the technical talent and organizational leadership that enables the successful delivery of high-impact discriminating technologies for our customers’ missions. Our collaborative, cross-functional teams are committed to innovation, integrity, continual learning and strong execution. BAE Systems, Inc. is a defense, aerospace, and security company headquartered in Falls Church, Virginia, with more than 40,000 employees worldwide. We serve, supply, and protect those who protect us. As one of the most geographically diverse international defense companies, we deliver a full range of products and services spanning air, land, maritime, space, and cyber, including advanced electronics, intelligence solutions, and dedicated customer support. Our culture is performance-driven and values-led, built on curiosity, creativity, and collaboration. Purpose isn't a tagline here. It's what drives us. We're developing breakthrough technologies that defend national security and make a lasting impact on our communities and our planet. When you join BAE Systems, you're not just building a career. You're contributing to a mission that truly matters." That seems fine. Now Responsibilities list as above. Requirements list as required. Qualifications list as preferred. Benefits paragraph. Pay paragraph. Schedule paragraph. Now ensure we don't include any filler like "Please note:" etc. We can keep the note about pay determination as part of Pay section. Now produce HTML. Let's craft:

  About the role

  ...

  Responsibilities

  • Convert Algorithm Description Documents (ADDs) into C++ software code for radar systems.
  • Develop and test software applications for radar tool chains and algorithms.
  • Collaborate with engineers and researchers to integrate radar systems with experimental data and analytical tools.
  • Analyze and optimize radar system performance, ensuring scalability and reliability.
  • Work with stakeholders to identify and prioritize project requirements, and develop solutions that meet business needs.
  • Participate in code reviews, ensuring adherence to coding standards and best practices.
  • Maintain a regular and predictable work schedule.
  • Establish and maintain effective working relationships within the department, the Strategic Business Units, Strategic Capabilities Units and the Company.
  • Interact appropriately with others in order to maintain a positive and productive work environment.
  • Perform other duties as necessary.

  Requirements

  • BS degree or higher in Engineering or a related technical field is required plus 6 or more years related experience.
  • Each higher-level degree, i.e., master’s degree or Ph.D., may substitute for two years of experience.