Ground Software Integration Engineer (Level 3 or 4) - AHT

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. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: relocation assistance line? Actually relocation assistance may be available is a benefit? It's a line: "RELOCATION ASSISTANCE: Relocation assistance may be available". That's a benefit. Also "CLEARANCE REQUIRED FOR START: No CLEARANCE TYPE: None TRAVEL: Yes, 10% of the Time". Travel is schedule? Could be schedule? Travel 10% of time maybe schedule? Could be included under Schedule? But schedule section only if posting actually states schedule details. Travel is not schedule but maybe we can treat as part of Schedule? The instruction: include a section ONLY when posting has real, specific content for it. Travel is specific: "TRAVEL: Yes, 10% of the Time". That could be considered schedule? Might be better to include under a "Travel" but not a listed heading. Since only allowed headings are those listed, we could put travel under Schedule? But schedule usually refers to work schedule (full-time, part-time, shift). Travel is not schedule. Might be better to omit Schedule section because no explicit schedule like "Full-time" etc. However we have travel info; maybe we can include under a generic "Details" but not allowed. The instruction says use those headings for section headings. It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings. So we should only use those headings. Travel could go under Schedule? Not ideal but maybe we can include travel as part of Schedule? Or we could omit Schedule entirely and not include travel. But we must preserve ALL substantive information. Travel is substantive. If we omit Schedule, we lose travel info. Could we put travel under Benefits? Not really. Could we put under About the role? Could incorporate travel description in About the role paragraph. That would preserve info. Similarly relocation assistance could be under Benefits. Clearance requirement: "CLEARANCE REQUIRED FOR START: No CLEARANCE TYPE: None" is about clearance; could be under Requirements or Qualifications. It says ability to obtain and maintain a US Gov Secret clearance within reasonable period. That's a requirement. Also "U.S. Citizenship is required for all positions with a government clearance and certain other restricted positions." That's also a requirement. So we can include that in Requirements or Qualifications. We need to parse the posting. Key sections: About the role: description paragraph about Northrop Grumman, culture, etc. Also location: Redondo Beach, CA. Also mention that position is contingent upon obtaining and maintaining customer/business funding (note repeated). Also mention Western Region Software Engineering org size etc. That's about the role/team. Responsibilities: list of job responsibilities bullet points. Requirements: Basic Qualifications (education/experience, clearance willingness, experience with ground system interfaces, ICDs, network protocols, coordinating with external providers). Also maybe "Ability and willingness to obtain and maintain a U.S. Government Secret clearance within a reasonable period of time as determined by the company." That's a requirement. Qualifications: Preferred Qualifications list. Skills: Could be derived from responsibilities and qualifications but we might combine into Requirements and Qualifications. The instruction says prefer few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including basic and preferred), Benefits, Pay. Possibly also Skills? Could merge skills into Requirements. But we need to follow headings list; we can omit Skills if not distinct. Benefits: relocation assistance, health insurance, life and disability insurance, savings plan, company paid holidays, PTO, maybe also discretionary bonus, annual bonuses, long term incentives for VP/Director (but not relevant). Also maybe overtime, shift differential, discretionary bonus. Also mention that employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay. Annual bonuses designed to reward individual contributions as well as allow employees to share in company results. Employees in VP or Director may be eligible for Long Term Incentives. Also mention that 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. Pay: Primary Level Salary Range: $114,000.00 - $171,000.00; Secondary Level Salary Range: $142,200.00 - $213,400.00. Also note that salary range is guideline; factors considered. Schedule: Not explicitly given besides travel 10% of time. Could we treat travel as schedule? Might be better to include a Schedule section with "Travel: Yes, 10% of the Time". But schedule heading expects work schedule like full-time, shift etc. However we have no explicit schedule. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Travel is not schedule but maybe we can treat as schedule? The posting states "TRAVEL: Yes, 10% of the Time". That is a specific statement about travel percentage. Could be considered under Schedule? I'd argue it's more like a job detail, not schedule. But we have no other schedule info. If we omit Schedule, we lose travel info. Could we incorporate travel into About the role or Responsibilities? Travel is not a responsibility but a condition. Could add to About the role as a note: "This role requires travel up to 10% of the time." That would preserve info. So we can avoid Schedule section. Thus sections: About the role, Responsibilities, Requirements (maybe combine Basic and Preferred), Benefits, Pay. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO statement, application period, equal opportunity, etc. Also remove lines like "Please be aware that this position will be contingent upon obtaining and maintaining customer and/or business funding*" appears twice; we should keep only once? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we should keep the contingency note only once. Also remove "U.S. Citizenship is required for all positions with a government clearance and certain other restricted positions." That's substantive (requirement). Keep. Also remove "Northrop Grumman is an Equal Opportunity Employer..." boilerplate. 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..." Also remove "#LosAngelesSpace #SpaceEngJobs" maybe not needed. Also remove "Primary Level Salary Range:" etc we keep. Now craft HTML. Structure:

About the role

... paragraph(s) ...

Responsibilities

• ...
...

Requirements

Maybe combine basic and preferred? But we have both basic and preferred qualifications. Could split into Basic Qualifications and Preferred Qualifications as subheadings? But only allowed headings are the generic ones; we could still use

for Basic Qualifications and Preferred Qualifications? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings. It doesn't forbid other headings but says use those for section headings. Safer to stick to those. So we can have Requirements heading and inside we can have paragraphs listing basic and preferred qualifications. Could also have Qualifications heading separate from Requirements? The examples include both Requirements and Qualifications. So we could have Requirements for basic qualifications, and Qualifications for preferred qualifications. That seems appropriate. Thus:

Requirements

Basic qualifications: ...

Qualifications

Preferred qualifications: ...

Then Benefits, Pay. We must not include Schedule. Now craft content. About the role paragraph: combine description of Northrop Grumman, culture, location, team size, opportunity, contingency note. Let's draft: At Northrop Grumman, employees work on revolutionary systems that impact lives worldwide, from historic achievements like the first transatlantic flight and stealth bombers to moon landings. The company seeks individuals with bold ideas, courage, and a pioneering spirit to invent the future while fostering a culture of intellectual curiosity, cognitive diversity, and bringing your whole self to work. This Ground Software Integration Engineer (Level 3 or 4) position is located onsite in Redondo Beach, CA, within the Western Region Software Engineering Directorate, which comprises over 800 professionals across software, DevOps, database, and network engineering roles, offering cross‑program collaboration, professional development, and advancement opportunities. Please note that this position is contingent upon obtaining and maintaining customer and/or business funding. That preserves info. Responsibilities: list each bullet from responsibilities. We need to capture all responsibilities: - Lead Ground Entry Point (GEP) services integration, including development and management of Interface Control Documents (ICDs), and serve as the primary technical interface with commercial GEP and ground station providers. - Design, integrate, and operate end-to-end ground systems that ensure seamless interoperability across mission operations, ground communications, and secure data flows, including automated contact scheduling and data routing. - Implement and maintain secure data exchange solutions (e.g., encryption, IPsec, cross-domain/data diode integrations) and apply protocol standards (CCSDS, SLE, TCP/IP, Ka-/S-band) to ground system and network designs. - Utilize mission operations tools, network planning utilities, and orchestration software to enable reliable and efficient ground operations, and lead interface verification/test campaigns and ICD update cycles. - Apply strong problem-solving skills to rapidly understand and resolve complex technical issues, and prepare technical charts, present data, and provide clear recommendations to internal teams, leadership, and external customers. - Manage tasking and mentor team members across multiple, concurrent program schedules, ensuring high-quality execution of deliverables within tight deadlines. Make sure to keep details. Requirements (Basic Qualifications): list: - Bachelor’s degree in a STEM discipline with 5+ years of relevant software engineering experience or Master’s degree in a STEM discipline with 3+ years of stated experience or Ph.D. in a STEM discipline with 1+ years of stated experience (for Level 3) OR Bachelor’s degree in a STEM discipline with 8+ years of relevant software engineering experience or Master’s degree in a STEM discipline with 6+ years of stated experience or Ph.D. in a STEM discipline with 4+ years of stated experience (for Level 4). Actually the posting says "This requisition may be filled at a higher grade based on the qualifications listed below." Then lists Basic Qualifications Principal Software Engineer (Level 3) and Sr. Principal Software Engineer (Level 4). So we need to include both sets. Could phrase as: Basic qualifications for Level 3: Bachelor’s degree in a STEM discipline with 5+ years of relevant software engineering experience or Master’s degree in a STEM discipline with 3+ years of stated experience or Ph.D. in a STEM discipline with 1+ years of stated experience. For Level 4: Bachelor’s degree in a STEM discipline with 8+ years of relevant software engineering experience or Master’s degree in a STEM discipline with 6+ years of stated experience or Ph.D. in a STEM discipline with 4+ years of stated experience. - Ability and willingness to obtain and maintain a U.S. Government Secret clearance within a reasonable period