Principal Systems Engineer, Electronic Support Measures
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 as heading. Must not include Job ID etc. Remove boilerplate.
We need to parse the job description and extract content.
Let's identify sections:
- About the role: The initial paragraph: "Ready to make a difference? BAE Systems is looking for systems engineers to develop, build, and work on the world’s most advanced electromagnetic spectrum operations systems – detecting, identifying, locating, and countering threats for joint forces and international aircrew. We develop highly sophisticated digital Electronic Warfare (EW) systems and we are looking for motivated systems engineers to join cross-functional, multi-disciplinary teams developing and supporting next generation Electronic Support Measures (ESM) systems. Electronic Combat Solutions has technology, engineering and program teams that educate and mentor colleagues to deliver leading Electronic Warfare capabilities. We welcome all those who have big ideas, crave innovation, want to drive fielding velocity and have the passion to bring the warfighter home safe. With a 9/80 schedule, and every other Friday off, our flexible work environment provides you a chance to change the world without giving up your personal life. We put our customers first – exemplified by our mission: “We Protect Those Who Protect Us®.” Sound like a team you want to be a part of? Come build your career with BAE Systems."
That's about the role.
- Responsibilities: The bullet list after "In this Principal Systems Engineer supporting our Electronic Support Measures group you will make impacts in the following ways;" then list of responsibilities: Systems engineering activities such as developing and managing systems level requirements; Understanding operational systems concepts to inform system design, using system performance models, performing system design and implementation; Performing systems level integration and test to verify and validate aspects of system designs to ensure conformance with functional specifications and customer requirements.; Perform systems engineering activities across the development cycle (analysis/decomposition/derivation/allocation of requirements, system modeling & simulation, system design & development, system integration & test). Also maybe other responsibilities like work location etc but those are not responsibilities.
We can combine into a list.
- Requirements: Required Education, Experience, & Skills section. Contains: Possess an Active US Government security clearance (with ability to possess TS); Bachelor's Degree (or equivalent experience in a relevant field) with a minimum work experience of: 5+ Years with BS 3+ Years with MS 1+ Year with PHD; Experience with Electronic Support Measures (ESM), Radar Warning Receivers (RWR), or SIGINT systems architectures.; Experience in documenting and communicating - working within a team on design, development, analysis, test, results, reports, and presentations.; Experience with Surface and Airborne Radar and Missile System employment, capabilities, and processing.; Experience with systems engineering activities across the development cycle (analysis/decomposition/derivation/allocation of requirements, system modeling & simulation, system design & development, system integration & test).; Experience in one or more of: Performing systems engineering activities across the development cycle; Developing viable concept solutions, identifying and tracking technical risks, and leading technical teams.; Planning, conducting or contributing to trade studies.; FW and SW Algorithm development and analysis for detection, location, and identification of threats.; Digital Signal Processing (DSP).; Analog/digital receiver design, analysis, and integration.; RF System Design, Development, and Integration.
We need to preserve all substantive info. Could break into list items.
- Qualifications: Preferred Education, Experience, & Skills section. Contains: Bachelor's degree or higher in a related technical field; Electeical Engineering, Computer Science (typo: Electrical). Experience with system resource management.; Experience with Digital Signal Processing (DSP).; Experience with analog/digital receiver design, analysis, and integration.; Experience with advanced antenna technologies and ability to model antenna impacts on received and transmitted signals.; Model based systems engineering experience with tools such as MagicDraw.
We could treat as Qualifications.
- Skills: Might be overlapping; but we have both Required and Preferred. Could combine into Skills? But we have separate sections for Requirements and Qualifications. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map Required to Requirements, Preferred to Qualifications, and maybe Skills separate if there is a distinct skills list. There's not a separate skills beyond those. Could omit Skills if no distinct content. But we could put some overlapping skills under Skills? Better to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for Requirements and Qualifications. Skills maybe not distinct; we could omit.
- Benefits: There's a paragraph: "Employee Benefits: At BAE Systems, we support our employees in all aspects of their life, including their health and financial well-being. Regular employees scheduled to work 20+ hours per week are offered: health, dental, and vision insurance; health savings accounts; a 401(k) savings plan; disability coverage; and life and accident insurance. We also have an employee assistance program, a legal plan, and other perks including discounts on things like home, auto, and pet insurance. Our leave programs include paid time off, paid holidays, as well as other types of leave, including paid parental, military, bereavement, and any applicable federal and state sick leave. Employees may participate in the company recognition program to receive monetary or non-monetary recognition awards. Other incentives may be available based on position level and/or job specifics."
That's benefits.
- Pay: "Pay Information Full-Time Salary Range: $118095 - $200762 Please note: This range is based on our market pay structures. However, individual salaries are determined by a variety of factors including, but not limited to: business considerations, local market conditions, and internal equity, as well as candidate qualifications, such as skills, education, and experience."
That's pay.
- Schedule: "With a 9/80 schedule, and every other Friday off, our flexible work environment provides you a chance to change the world without giving up your personal life." Also later: "Because of the need for consistent, in-person collaboration and/or the requirement to perform all work onsite due to the nature of this particular role, it will be performed full-time on site. This means work will be conducted on location at a BAE Systems facility 100% of the time."
So schedule includes 9/80 schedule, every other Friday off, full-time on site. We'll include schedule section.
Now we need to output HTML fragment with headings and - for lists,
for prose.
We must not repeat job title as heading. Not include Job ID etc.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like location options (Nashua NH, Manchester NH, Burlington MA, or Lexington MA). That's part of responsibilities? Actually it's under work location. Could be part of Responsibilities or maybe a separate section? Not a defined heading; we could include under Responsibilities as a list item. Or maybe under About the role? Better to put under Responsibilities as a bullet: "Work location can be Nashua NH, Manchester NH, Burlington MA, or Lexington MA." Also the statement about full-time on site.
We need to ensure we don't lose any detail.
Let's structure:
About the role
Ready to make a difference? BAE Systems is looking for systems engineers to develop, build, and work on the world’s most advanced electromagnetic spectrum operations systems – detecting, identifying, locating, and countering threats for joint forces and international aircrew. We develop highly sophisticated digital Electronic Warfare (EW) systems and we are looking for motivated systems engineers to join cross-functional, multi-disciplinary teams developing and supporting next generation Electronic Support Measures (ESM) systems. Electronic Combat Solutions has technology, engineering and program teams that educate and mentor colleagues to deliver leading Electronic Warfare capabilities. We welcome all those who have big ideas, crave innovation, want to drive fielding velocity and have the passion to bring the warfighter home safe. With a 9/80 schedule, and every other Friday off, our flexible work environment provides you a chance to change the world without giving up your personal life. We put our customers first – exemplified by our mission: “We Protect Those Who Protect Us®.” Sound like a team you want to be a part of? Come build your career with BAE Systems.
But note schedule mentioned also in schedule section; we might duplicate. However we should not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid duplication. However schedule is mentioned in About the role; we also have a Schedule section. Could keep schedule details in Schedule section and maybe remove from About the role to avoid duplication. But the About the role paragraph includes schedule as part of flexible work environment; it's substantive. If we remove it, we lose that detail. We could keep it in About the role and also have Schedule section referencing same info; that would be duplication. Might be okay but better to avoid duplication by moving schedule details to Schedule section and adjust About the role to not mention schedule. However the About the role paragraph originally includes schedule; we could rephrase to omit schedule but still keep other content. But we must not invent or summarize away detail; removing schedule detail would be summarizing away detail. So we need to keep schedule detail somewhere. We could keep it in About the role and also have Schedule section that maybe just says "See above" but that would be summarizing. Better to keep schedule detail only in Schedule section and not in About the role, but then we lose that detail from About the role. However the instruction says preserve ALL substantive information; we can preserve it by putting it in Schedule section. The About the role section can still have other content; we just need to edit out the schedule sentence from About the role. Is that allowed? It's not inventing or summarizing away detail; we are moving detail to another section, still preserving it. That seems acceptable.
Thus we will remove the schedule sentence from About the role.
Now About the role paragraph without schedule: "Ready to make a difference? BAE Systems is looking for systems engineers to develop, build, and work on the world’s most advanced electromagnetic spectrum operations systems – detecting, identifying, locating, and countering threats for joint forces and international aircrew. We develop highly sophisticated digital Electronic Warfare (EW) systems and we are looking for motivated systems engineers to join cross-functional, multi-disciplinary teams developing and supporting next generation Electronic Support Measures (ESM) systems. Electronic Combat Solutions has technology, engineering and program teams that educate and mentor colleagues to deliver leading Electronic Warfare capabilities. We welcome all those who have big ideas, crave innovation, want to drive fielding velocity and have the passion to bring the warfighter home safe. We put our customers first – exemplified by our mission: “We Protect Those Who Protect Us®.” Sound like a team you want to be a part of? Come build your career with BAE Systems."
Now Responsibilities: We'll list bullet points.
Responsibilities list:
- Systems engineering activities such as developing and managing systems level requirements
- Understanding operational systems concepts to inform system design, using system performance models, performing system design and implementation
- Performing systems level integration and test to verify and validate aspects of system designs to ensure conformance with functional specifications and customer requirements
- Perform systems engineering activities across the development cycle (analysis/decomposition/derivation/allocation of requirements, system modeling & simulation, system design & development, system integration & test)
- Work location can be Nashua NH, Manchester NH, Burlington MA, or Lexington MA
- Because of the need for consistent, in-person collaboration and/or the requirement to perform all work onsite due to the nature of this particular role, it will be performed full-time on site. This means work will be conducted on location at a BAE Systems facility 100% of the time.
We could combine last two as separate bullets.
Now Requirements: list bullet points.
- Possess an Active US Government security clearance (with ability to possess TS)
- Bachelor's Degree (or equivalent experience in a relevant field) with a
- for lists,
for prose. We must not repeat job title as heading. Not include Job ID etc. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like location options (Nashua NH, Manchester NH, Burlington MA, or Lexington MA). That's part of responsibilities? Actually it's under work location. Could be part of Responsibilities or maybe a separate section? Not a defined heading; we could include under Responsibilities as a list item. Or maybe under About the role? Better to put under Responsibilities as a bullet: "Work location can be Nashua NH, Manchester NH, Burlington MA, or Lexington MA." Also the statement about full-time on site. We need to ensure we don't lose any detail. Let's structure:
About the role
Ready to make a difference? BAE Systems is looking for systems engineers to develop, build, and work on the world’s most advanced electromagnetic spectrum operations systems – detecting, identifying, locating, and countering threats for joint forces and international aircrew. We develop highly sophisticated digital Electronic Warfare (EW) systems and we are looking for motivated systems engineers to join cross-functional, multi-disciplinary teams developing and supporting next generation Electronic Support Measures (ESM) systems. Electronic Combat Solutions has technology, engineering and program teams that educate and mentor colleagues to deliver leading Electronic Warfare capabilities. We welcome all those who have big ideas, crave innovation, want to drive fielding velocity and have the passion to bring the warfighter home safe. With a 9/80 schedule, and every other Friday off, our flexible work environment provides you a chance to change the world without giving up your personal life. We put our customers first – exemplified by our mission: “We Protect Those Who Protect Us®.” Sound like a team you want to be a part of? Come build your career with BAE Systems.
But note schedule mentioned also in schedule section; we might duplicate. However we should not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid duplication. However schedule is mentioned in About the role; we also have a Schedule section. Could keep schedule details in Schedule section and maybe remove from About the role to avoid duplication. But the About the role paragraph includes schedule as part of flexible work environment; it's substantive. If we remove it, we lose that detail. We could keep it in About the role and also have Schedule section referencing same info; that would be duplication. Might be okay but better to avoid duplication by moving schedule details to Schedule section and adjust About the role to not mention schedule. However the About the role paragraph originally includes schedule; we could rephrase to omit schedule but still keep other content. But we must not invent or summarize away detail; removing schedule detail would be summarizing away detail. So we need to keep schedule detail somewhere. We could keep it in About the role and also have Schedule section that maybe just says "See above" but that would be summarizing. Better to keep schedule detail only in Schedule section and not in About the role, but then we lose that detail from About the role. However the instruction says preserve ALL substantive information; we can preserve it by putting it in Schedule section. The About the role section can still have other content; we just need to edit out the schedule sentence from About the role. Is that allowed? It's not inventing or summarizing away detail; we are moving detail to another section, still preserving it. That seems acceptable. Thus we will remove the schedule sentence from About the role. Now About the role paragraph without schedule: "Ready to make a difference? BAE Systems is looking for systems engineers to develop, build, and work on the world’s most advanced electromagnetic spectrum operations systems – detecting, identifying, locating, and countering threats for joint forces and international aircrew. We develop highly sophisticated digital Electronic Warfare (EW) systems and we are looking for motivated systems engineers to join cross-functional, multi-disciplinary teams developing and supporting next generation Electronic Support Measures (ESM) systems. Electronic Combat Solutions has technology, engineering and program teams that educate and mentor colleagues to deliver leading Electronic Warfare capabilities. We welcome all those who have big ideas, crave innovation, want to drive fielding velocity and have the passion to bring the warfighter home safe. We put our customers first – exemplified by our mission: “We Protect Those Who Protect Us®.” Sound like a team you want to be a part of? Come build your career with BAE Systems." Now Responsibilities: We'll list bullet points. Responsibilities list: - Systems engineering activities such as developing and managing systems level requirements - Understanding operational systems concepts to inform system design, using system performance models, performing system design and implementation - Performing systems level integration and test to verify and validate aspects of system designs to ensure conformance with functional specifications and customer requirements - Perform systems engineering activities across the development cycle (analysis/decomposition/derivation/allocation of requirements, system modeling & simulation, system design & development, system integration & test) - Work location can be Nashua NH, Manchester NH, Burlington MA, or Lexington MA - Because of the need for consistent, in-person collaboration and/or the requirement to perform all work onsite due to the nature of this particular role, it will be performed full-time on site. This means work will be conducted on location at a BAE Systems facility 100% of the time. We could combine last two as separate bullets. Now Requirements: list bullet points. - Possess an Active US Government security clearance (with ability to possess TS) - Bachelor's Degree (or equivalent experience in a relevant field) with a