Sr. Principal Systems Engineer

We need to output HTML fragment with sections only when there is real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID etc. Remove boilerplate: relocation assistance, clearance required, travel etc? Those are metadata but maybe we can include in a short

if they are substantive? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include relocation assistance, clearance, travel as a short paragraph maybe under About the role? But we need to preserve all substantive information. The posting includes description about company, role, etc. We need to extract sections. We need to decide which sections have content. - About the role: we have description paragraph about Northrop Grumman, culture, etc. Also mention "Systems Engineering Roles at Rolling Meadows include, but are not limited to, Systems Engineering Design, Modeling & Simulation, Model Based Systems Engineering, Mission Modeling, Systems Integration, Systems Testing, Systems Validation, and more." Also "This position description does not represent a current opening but may be used to identify candidates..." etc. Also "This position will be full-time, on-site at our Rolling Meadows, IL location." Also "This position may be contingent upon funding/contract award, special access program, and acquiring and maintaining the necessary US Government security clearance per customers' requirements prior to start." Also "This position can be filled at the Systems Engineer or Principal Systems Engineer level." We can put that in About the role. - Responsibilities: Not explicitly listed. The posting does not have a separate responsibilities list. It mentions tasks like "design, develop, build, integrate, and test" but that's part of description. Could we create Responsibilities section with those? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". If we infer responsibilities from description, maybe we can include but must be specific content. The posting says: "Our products range from advanced sensing technologies to state-of-the-art targeting and tracking systems that are deployed in Electro-Optical Infrared (EOIR) and Radio Frequency Electronic Warfare (RFEW) systems. These systems are designed, developed, built, integrated, and tested by the capable folks at our company to protect the lives of US and Allied warfighters in present and future conflicts." That's more about what they do, not responsibilities of the role. There's no explicit bullet list of duties. Might be better to omit Responsibilities section. - Requirements: There's "Basic Qualifications" and "Preferred Qualifications". Those can go under Requirements or Qualifications. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. Probably we can have Requirements (basic qualifications) and Preferred Qualifications maybe under Qualifications or Skills. But we must not create thin sections. Let's think: We have basic qualifications (BS/MS/PhD + years experience, troubleshooting, collaborative environment, US Citizen, ability to obtain Secret clearance). That's substantive. We have preferred qualifications (integration/test experience, DOORS, VCRMs, specialty areas, MBSE, MATLAB etc, scripting languages, independent work, travel, active Secret/Top Secret clearance). That's also substantive. Could combine into Requirements section with two subparts? But we need to use

• for any list of duties/requirements/benefits. So we can make a Requirements section with two lists: Basic Qualifications and Preferred Qualifications as subheadings? But we cannot use headings other than

  for section headings. Could we embed or

  for subheadings? Probably okay to just have a single list mixing both? Might lose distinction. Better to have Requirements section with basic qualifications list, and then a Qualifications section for preferred qualifications? Or Skills section for technical skills. Let's map: - Requirements: Basic Qualifications (education/experience, citizenship, clearance). - Qualifications: Preferred Qualifications (integration/test experience, DOORS, VCRMs, specialty areas, MBSE, MATLAB etc, scripting languages, independent work, travel, active clearance). - Skills: maybe list of specific technical skills like MATLAB, C, C++, Java, Python, etc. But those are already in preferred qualifications. Could split. But we must avoid thin sections. If we split too much, each may be thin. Let's see content volume. Basic Qualifications list items: - BS degree in Electrical Engineering, Mechanical Engineering, or Related technical degree with 8+ years of related experience; OR MS degree ... with 6+ years; OR PhD ... with 4+ years. - Experience troubleshooting of hardware, software, and firmware issues - Demonstrated ability to work in a collaborative environment and with multiple stakeholders across various disciplines - Candidate must be a US Citizen - Ability to obtain and maintain a minimum of a Secret Clearance with additional customer specified clearance That's 5 items. Preferred Qualifications list items: - Experience in an integration and test environment for complex electronic systems evaluation - Experience performing Design Verification Tests, Environmental Qualification Testing, and Electromagnetic Interference (EMI) Qualification Testing - Working knowledge of DOORS and Verification Cross Reference Matrices (VCRMs) - Working knowledge of one or more of the following specialty areas: EOIR systems, sensors, optics, RFEW systems, DSP, antenna design, computational electromagnetics, RF test equipment - Experience with Model Based Systems Engineering (MBSE) concepts and tools (Cameo) - Has demonstrated experience applying basic systems‑engineering principles to develop and execute integration‑test plans - Knowledge of MATLAB, C, C++, Java, Python, or other scripting languages - Experience writing and executing test scripts - Ability and willingness to work independently with little oversight or direction - Ability and willingness to travel - Active Secret or Top Secret clearance That's about 11 items. We could combine both into a single Requirements section with two sub-lists maybe using

  headings? But we cannot use headings other than

  . Could use

  Basic Qualifications:

  then

  . That's acceptable as not a heading. The instruction only restricts using

  for section headings; using

  with bold is okay. Thus we can have one Requirements section containing both basic and preferred qualifications, maybe separated by paragraphs. Then we might have Skills section for specific technical skills like MATLAB, C, C++, Java, Python, etc. But those are already in preferred qualifications; splitting may cause duplication. Better to keep them within Requirements. Benefits: The posting mentions: "With our competitive pay and comprehensive benefits, we have the right opportunities to fit your life and launch your career today." Then later: "In addition, Northrop Grumman provides a variety of benefits including health insurance coverage, life and disability insurance, savings plan, Company paid holidays and paid time off (PTO) for vacation and/or personal business." Also mentions overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director. That's substantive benefits. So we can create Benefits section. Pay: There's "Primary Level Salary Range: $135,800.00 - $203,600.00" plus note about factors, overtime, shift differential, bonus, long term incentives. That's substantive. So we can create Pay section. Schedule: The posting mentions "This position will be full-time, on-site at our Rolling Meadows, IL location." Also maybe travel 10% of the time. That's schedule info. So we can create Schedule section with full-time, on-site, travel 10%. We also have relocation assistance, clearance required, travel etc. Those could be included in Schedule or maybe a short paragraph under About the role. But we already have travel in Schedule. Clearance required is part of Requirements (clearance). Relocation assistance maybe a short note under About the role or Benefits? Could be a short paragraph under Benefits? It says "Relocation assistance may be available". That's a benefit-ish. Could include in Benefits as a bullet. We must not repeat job title. No Job ID. We must remove boilerplate: EEO statement, application period, equal opportunity, etc. Also remove "The application period for the job is estimated to be 20 days..." etc. Also remove "Northrop Grumman is an Equal Opportunity Employer..." etc. Also remove "U.S. Citizenship is required for all positions with a government clearance..." maybe that's covered in Requirements (citizenship). But we can keep that as part of Requirements. We must preserve all substantive information. So we need to include the description about company, culture, etc. Also the note about position description not representing a current opening, etc. Also the note about contingent upon funding/contract award, special access program, acquiring clearance. Also the note about position can be filled at Systems Engineer or Principal Systems Engineer level. Now craft HTML. Structure:

  About the role

  ... description ...

  Maybe include relocation assistance line as a short sentence. Then

  Requirements

  Basic Qualifications:

  ...

  Preferred Qualifications:

  ...
  Then

  Benefits

  ...
  Then

  Pay

  ... salary range and bonus info ...

  Then

  Schedule

  ... full-time, on-site, travel 10% ...

  Check for any other substantive content: "Systems Engineering Roles at Rolling Meadows include, but are not limited to, Systems Engineering Design, Modeling & Simulation, Model Based Systems Engineering, Mission Modeling, Systems Integration, Systems Testing, Systems Validation, and more." That's about role; could be in About the role. Also "This position description does not represent a current opening but may be used to identify candidates with skills and experience for positions within Northrop Grumman that frequently become available. Candidates who express an interest may be considered for future positions at Northrop Grumman." That's also about role. Also "This position may be contingent upon funding/contract award, special access program, and acquiring and maintaining the necessary US Government security clearance per customers' requirements prior to start." That's about role/contingency. Also "This position can be filled at the Systems Engineer or Principal Systems Engineer level." That's about role. All good. Now ensure we don't include boilerplate: EEO, equal opportunity, pay transparency statement, application period, etc. Also remove "Relocation assistance may be available CLEARANCE REQUIRED FOR START: Yes CLEARANCE TYPE: Secret TRAVEL: Yes, 10% of the Time" - we have incorporated relocation assistance and travel elsewhere; clearance is in Requirements. We need to avoid duplication: travel appears in Schedule; we already have travel 10% there. Also we have willingness to travel in Preferred Qualifications; that's okay. Now craft the HTML. We need to output only HTML fragment, no or . Use

  ,

  ,

  • . Let's write. About the role paragraph: combine multiple sentences. We'll need to escape any HTML special characters? Not needed. Let's draft:

    About the role

    At Northrop Grumman, employees work on revolutionary systems that impact lives today and for generations, from advanced sensing technologies to state-of-the-art targeting and tracking systems deployed in Electro-Optical Infrared (EOIR) and Radio Frequency Electronic Warfare (RFEW) systems. These systems are designed, developed, built, integrated, and tested to protect US and Allied warfighters. The company culture values intellectual curiosity, cognitive diversity, and bringing your whole self to work, with a drive to do what others think is impossible. Systems Engineering roles at the Rolling Meadows site include Systems Engineering Design, Modeling & Simulation, Model Based Systems Engineering, Mission Modeling, Systems Integration, Systems Testing, Systems Validation, and more. This position