Consulting Chief Engineer - Battle Management

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, remove boilerplate: relocation assistance, clearance required, travel etc? Those are metadata; we can fold minor metadata into a short

or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short paragraph with relocation assistance, clearance, travel maybe. But we must preserve all substantive information. So we need to keep details about role, responsibilities, qualifications, etc. We need to decide which sections to include. We have: - About the role: description paragraph about Northrop Grumman, Aeronautics Systems – R&AD, description of team, location, role summary. That's substantive. - Responsibilities: list of primary responsibilities (bulleted). Should be

• . - Requirements: Basic Qualifications (list). Could be under Requirements. - Qualifications: Preferred Qualifications (list). Could be under Qualifications. - Skills: maybe we can extract skills from responsibilities/qualifications? Not explicit separate skills section. Could combine into Requirements or Qualifications. But we need to include a Skills section only if posting has real specific content for it. There's no explicit "Skills" heading; but we could infer skills like "systems engineering principles, tools, and techniques", "project management planning and presentation skills", "organizational and written communication skills". Might be considered skills. However instruction: "Prefer a few substantive sections over many thin ones." Might be better to not create a Skills section unless clearly present. The posting does not have a dedicated Skills section; we could omit. - Benefits: posting mentions benefits: health insurance, life and disability insurance, savings plan, company paid holidays, paid time off (PTO). Also mentions overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director. That's substantive. So we can include Benefits section. - Pay: posting includes Primary Level Salary Range: $183,200.00 - $318,100.00. Also mentions that salary range is guideline, factors, etc. So we have pay info. Include Pay section. - Schedule: posting mentions travel up to 15% (or earlier says travel: Yes, 25% of the Time). Actually there is travel line: "TRAVEL: Yes, 25% of the Time". Also later "Ability to travel up to 15%". There's inconsistency. But we have travel info. Schedule maybe not explicit; but we could treat travel as schedule? Not exactly. There's no mention of work schedule (e.g., full-time, shift). So we may not include Schedule section unless we have real content. The posting does not give schedule details. So we omit Schedule. We also need to include a short paragraph for metadata like relocation assistance, clearance required, travel. Could be placed at top as a

  . We must not repeat job title as heading (the page already shows it). So we don't add heading for job title. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to remove EEO statement, application period, etc. Also remove "U.S. Citizenship is required..." maybe considered EEO? It's related to clearance; but it's still a requirement? It says "U.S. Citizenship is required for all positions with a government clearance and certain other restricted positions." That's a requirement; we could keep it under Requirements or Qualifications. But it's more of a condition. Might keep as part of Requirements. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics: relocation assistance may be available, clearance required for start: Yes, clearance type: Secret, travel: Yes, 25% of the Time. Also later ability to travel up to 15% (contradiction). We need to keep both? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include both statements as they appear, maybe combine? But we should not duplicate lines. There's duplication? The travel appears twice: once in metadata "TRAVEL: Yes, 25% of the Time." and later in Preferred Qualifications? Actually it's in Basic Qualifications? No, it's in the "Preferred Qualifications"? Actually it's in the "Basic Qualifications"? Let's scroll: After Basic Qualifications list, there is "Ability to travel up to 15%". That's separate. So we have two travel statements: one says 25% of the Time, another says up to 15%. Both are substantive; we should keep both. Could combine into a sentence: "Travel required: up to 25% of the time (with ability to travel up to 15% noted)." But that would be summarizing; maybe better to keep both as separate bullet points? But we are not supposed to create list unless it's a list of duties/requirements/benefits. Travel is not a duty; it's metadata. Could include in a short paragraph: "Relocation assistance may be available. Clearance required for start: Yes (Secret). Travel: Yes, 25% of the time. Ability to travel up to 15%." That preserves both. Now we need to ensure we don't include boilerplate like "Northrop Grumman is an Equal Opportunity Employer..." etc. Remove that. Also remove "The application period for the job is estimated to be 20 days..." etc. Also remove "For our complete EEO and pay transparency statement, please visit..." etc. Also remove "U.S. Citizenship is required for all positions with a government clearance and certain other restricted positions." This is not EEO but it's a requirement; we might keep it under Requirements. Now we need to format. We'll start with a short paragraph for metadata. Then

  About the role

  followed by

  containing the description paragraphs (maybe multiple paragraphs). We need to preserve all substantive info; we can combine into one

  or multiple

  . Use

  for prose. Then

  Responsibilities

  followed by
  • for each responsibility. Then

    Requirements

    for Basic Qualifications (list). Could be
    • . Then

      Qualifications

      for Preferred Qualifications (list). Then

      Benefits

      for benefits list. Then

      Pay

      for salary range and related info. We need to avoid creating sections with filler. Ensure each section has real content. Now extract content. Metadata paragraph: "Relocation assistance may be available. Clearance required for start: Yes (Secret). Travel: Yes, 25% of the time. Ability to travel up to 15%." Now About the role: The description includes multiple paragraphs. Let's capture: "At Northrop Grumman, our employees have incredible opportunities to work on revolutionary systems that impact people's lives around the world today, and for generations to come. Our pioneering and inventive spirit has enabled us to be at the forefront of many technological advancements in our nation's history - from the first flight across the Atlantic Ocean, to stealth bombers, to landing on the moon. We look for people who have bold new ideas, courage and a pioneering spirit to join forces to invent the future, and have fun along the way. Our culture thrives on intellectual curiosity, cognitive diversity and bringing your whole self to work — and we have an insatiable drive to do what others think is impossible. Our employees are not only part of history, they're making history. Northrop Grumman’s Aeronautics Systems – Research & Advanced Design (R&AD) transforms breakthrough ideas into mission-ready capabilities through intelligent anticipation. We’re the front-end design engine, defining what comes next. From developing cutting-edge next-generation future aircraft to trailblazing collaborative autonomous platforms, we push the boundaries of technology and forge industry-leading partnerships that set new standards for what’s possible. Our team owns the full lifecycle of advanced concept creation, from visionary early-stage designs and rapid prototyping to high-impact demonstrations and solving the toughest technical challenges in survivability, autonomy, and battle management. We seek curious, adaptable people who thrive on turning intuition into breakthrough solutions. If you’re driven to invent the future, build what’s next, and shape the landscape of national security, this is where you belong. R&AD has an opening for a Consulting Chief Engineer to join our Battle Management Operating Unit (OU) located in Redondo Beach, CA; El Segundo, CA; or Melbourne, FL. In this role, the successful candidate will lead a multi-disciplinary engineering team executing research & development projects within the Battle Management OU. This team conceives, develops, demonstrates, and transitions cutting-edge technologies in the Advanced Autonomy, Joint All-Domain Command & Control (JADC2), and Battle Management Architecture, Systems, and Technologies (BAST) domains. Activities within the OU span the spectrum from applied research through operational demonstrations, including such industry leading capabilities such as the Talon IQ Next-Generation Autonomous Testbed Ecosystem." We need to keep all that. Could be multiple

      tags. Now Responsibilities: list bullet points from "Primary Responsibilities Will Include But Are Not Limited To" then each line: - Serve as the technical authority for the OU, providing technical direction and leadership to internally funded and contracted activities - Serve as the focal point for definition and control of technical requirements, and ensure technical coordination and horizontal integration across projects - Serve as the principal technical interface with the customer and company senior leadership - Ensure that programs adhere to sound engineering principles and comply with relevant company policies, procedures, and quality standards - Oversee and ensure technical performance measures are being met by the Engineering team within allocated cost and schedule resources - Serve as the chairperson of the Technical Review Board (TRB) - Support program managers in risk and opportunity management by identifying and owning risks associated with technical performance - Provide technical leadership, direction and mentoring to technical contributors in the application of systems engineering principles, tools, and techniques to achieve practical end results We need to keep each as

    • . Now Requirements (Basic Qualifications): list: - Bachelor of Science degree in a related Science, Technology, Engineering, or Math (STEM) discipline and 16 years relevant professional/military experience; OR a Master of Science degree in a related STEM discipline and 14 years of relevant experience; OR a PhD in a related STEM disciple and 12 years of relevant experience. - Demonstrated professional experience related to air vehicle flight autonomy, mission autonomy, battle management command & control architectures/implementations, or networking and communications technologies. - Demonstrated experience with interfacing with customers and company leadership - Experience integrating multiple engineering specialties and experience working across multiple Business Units within a company, as well as with industry partners and customer community through strong collaboration skills. - Active US Government Secret or higher clearance (with a background investigation completed within the last 6 years or currently enrolled into Continuous Evaluation) Actually text: "Active US Government Secret or higher clearance (with a background investigation completed within the last 6 years or currently enrolled into Continuous Evaluation)" - Ability to obtain and maintain Special Program Access (SAP) and TS / SCI clearance within a reasonable amount of time as determined by business needs - Ability to travel up to 15% (we already captured in metadata but it's also here; we can keep it in Requirements as well? Might be duplicate. But we should preserve all substantive info; we could keep it in Requirements as it's listed there. However we already have travel in metadata; duplication may be okay but we should avoid duplicated lines per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". So we should not duplicate lines. The travel ability appears both in metadata and in Basic Qualifications