Senior Principal Systems Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Key info: - Relocation assistance: No relocation assistance available. - Clearance required: Yes, Top Secret. - Travel: Yes, 10% of the time. - Description: multiple paragraphs about Northrop Grumman, mission, culture, etc. This is "About the role" maybe? Actually description is about company and role. We'll put under About the role. - Responsibilities: The Successful Candidate Will Have The Opportunity To Work within multi-disciplined teams, performing in one or more of the following functions: list of functions. Also: Develop systems engineering work products..., Prepare and brief technical packages..., Support project and program processes..., Develop content and present during milestone reviews..., Support capture and proposal activities. Also maybe "Support capture and proposal activities." Also "Though not required, experience with Navy customers..." is more qualification. - Requirements: Basic Qualifications: list: keen interest in maritime surface/undersea domain; bachelor's degree in STEM; 8 years experience with BS; 6 with MS; 4 with PhD; demonstrated experience in one or more SE processes; excellent verbal/written communication; willingness to learn additional discipline areas; current ACTIVE Top Secret clearance, willingness to obtain TS/SCI with CI polygraph. - Preferred Qualifications: list many. - Skills: maybe we can extract from Preferred Qualifications: proficiency in requirements management tools (IBM DOORS), familiarity with architecture frameworks (SysML, UML, DoDAF, UPDM, UAF), proficiency in Model-Based tools (Cameo, ModelCenter, SIEMENS Teamcenter), proficiency executing SE functions within digital ecosystem, demonstrated leadership capabilities (mentorship, customer interfacing), experience leading teams of SE, experience preparing work products associated with engineering milestones, experience in naval warfare domains, industry recognition, patents, etc. Also maybe "Experience with Navy customers and underwater/naval systems..." is desired but not required. - Benefits: "Northrop Grumman provides a comprehensive benefits package..." includes Health Plan, Savings Plan, Paid Time Off and Additional Benefits including Education Assistance, Training and Development, 9/80 Work Schedule (where available), and much more! Also later: health insurance coverage, life and disability insurance, savings plan, Company paid holidays and paid time off (PTO) for vacation and/or personal business. So we can list benefits. - Pay: Primary Level Salary Range: $135,800.00 - $203,600.00. Also mention that base salary may consider factors, overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director. So we have pay info. - Schedule: "This is a full-time on-site position located in Annapolis, MD." Also "9/80 Work Schedule (where available)" mentioned under benefits. So schedule: full-time on-site. Possibly also mention travel 10% of time. But schedule section maybe just full-time on-site. Travel could be under responsibilities? But we can include schedule: Full-time on-site (Annapolis, MD). Travel: 10% of time. However schedule heading maybe only for schedule specifics; travel could be separate but not required. We could include schedule: Full-time on-site; Travel: 10% of time. We must not include placeholder text like "commensurate with experience" etc. The posting says: "This is a multi-level requisition; offers will be made commensurate with candidate experience and qualifications." That's placeholder-ish but it's actual statement. However rule: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "offers will be made commensurate with candidate experience and qualifications." is somewhat filler but it's actual content. Might be considered placeholder? It's vague. Safer to avoid including that line if it's just that phrase. However we have salary range already, so we can omit that line. Also "Interested candidates should consider applying, even with lesser or greater levels of experience compared to the qualifications noted below." That's filler; we can drop. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the specifics: e.g., list of functions, list of qualifications, etc. We must not include boilerplate like EEO, citizenship, etc. Remove those. Now produce HTML. Structure:

About the role

... paragraphs describing Northrop Grumman mission, culture, role context.

We need to combine the description paragraphs into maybe one or two

elements. Keep all substantive info: mention pioneering spirit, history, looking for bold ideas, culture thrives on intellectual curiosity, etc. Also mention joining mission to push boundaries across land, sea, air, space, cyberspace; culture where voice valued; contributing to team; purposeful work; Defining Possible; competitive pay and comprehensive benefits; Naval & Oceanic Systems business unit headquartered in Annapolis, MD values proactive, respectful, communicative, authentic self-starters with ability to own tasking and deliver commitments; SEIT&L Department seeking systems engineering generalist; support complex dynamic maritime programs of national strategic importance; contribute to development of state-of-the-art oceanic systems, exposure to advanced technologies including UUVs, ROVs, undersea payloads, acoustic and non-acoustic sensors, sensor processing, navigation, platform integration, subsea and maritime-surface communication technologies, advanced algorithms, digital engineering, etc. We'll put that in

. Then Responsibilities:

Responsibilities

• Work within multi-disciplined teams, performing in one or more of the following functions: mission engineering, requirements development & management (using DOORS), system architecture development, system modeling including Model-Based Systems Engineering (MBSE), establishing and integrating components of a digital design thread, interface development & management, concept of operations (CONOPS) development & management, trade studies / analysis of alternatives, integration & test, and verification & validation.
• Develop systems engineering work products associated with the functions above.
• Prepare and brief technical packages to program, company, and customer leadership teams.
• Support project and program processes, reviews, and technical planning activities.
• Develop content and present during milestone reviews including Systems Requirement Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Test Readiness Review (TRR), Consent to Ship Review (CSR).
• Support capture and proposal activities.

We could also include "Though not required, experience with Navy customers..." but that's more qualification. Requirements (Basic Qualifications):

Requirements

• Keen interest in working in the maritime surface / undersea domain.
• Bachelor’s degree in a STEM field.
• 8 years of experience with a Bachelor's degree; 6 years with a Masters Degree; or 4 years with a PhD.
• Demonstrated experience in one or more Systems Engineering processes, including (but not limited to) requirements development & management, system modeling, system architecture development, interface traceability, integration & test, and verification & validation.
• Excellent verbal and written communication skills.
• Willingness to learn additional discipline areas.
• Current ACTIVE Top Secret clearance, and willingness to obtain a TS/SCI with CI polygraph.

Preferred Qualifications could go under Qualifications or Skills. The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where to put Preferred Qualifications. Could be under Qualifications (maybe separate from Requirements). Or we could put under Skills. Since they list many proficiencies, maybe better under Skills. But we also have a "Qualifications" heading; we could put both basic and preferred under Qualifications? But they said "Requirements" and "Qualifications" separate. Usually Requirements = basic qualifications, Qualifications = preferred qualifications. We'll follow that. Thus:

Qualifications

• Broad experience with systems engineering applied throughout the systems “V” lifecycle model.
• Proficiency in requirements management and tools such as IBM DOORS.
• Familiarity with architecture frameworks/modeling languages (e.g., SysML, UML, DoDAF, UPDM and/or UAF).
• Proficiency in Model-Based tools (e.g., Cameo, ModelCenter, SIEMENS Teamcenter).
• Proficiency executing systems engineering functions within a digital ecosystem.
• Demonstrated leadership capabilities to include mentorship and working/interfacing with customers.
• Experience leading teams of systems engineers (e.g., as SEIT Lead).
• Experience preparing work products associated with the engineering milestones (e.g., SRR, PDR, CDR, TRR).
• Experience in naval warfare domains such as Anti-Submarine Warfare (ASW), Anti-Surface Warfare (ASUW), Mine-Warfare (MIW), Cyber Warfare, and/or other.
• Industry/company recognition and awards, attendance and participation in industry/engineering conferences and symposiums, and/or patents/disclosures/publications.
• Active TS/SCI clearance with CI polygraph.

Note: The last item "Active TS/SCI clearance with CI poly" is a preferred qualification but also we already have current TS clearance requirement. We'll keep. Skills: Could be overlapping with Qualifications; but we might not need a separate Skills section if we already covered skills under Qualifications. However instruction: Use headings for Skills if there is real specific content. We could extract specific skills like "proficiency in requirements management tools (IBM DOORS)", "familiarity with architecture frameworks", etc. But those are already in Qualifications. To avoid duplication, maybe we put under Skills the specific technical skills: proficiency in DOORS, familiarity with SysML/UML/DoDAF/UPDM/UAF, proficiency in Model-Based tools (Cameo, ModelCenter, SIEMENS Teamcenter), proficiency executing SE functions within digital ecosystem, demonstrated leadership capabilities, etc. But that duplicates. Perhaps better to treat Qualifications as preferred qualifications and Skills as technical skills like "requirements management, system modeling, system architecture development, interface traceability, integration & test, verification & validation, MBSE, DOORS, SysML, UML, DoDAF, UPDM, UAF, Cameo, ModelCenter, Teamcenter, digital ecosystem, leadership, mentorship, customer interfacing, leading SE teams, preparing work products for SRR/PDR/CDR/TRR, naval warfare domains". That seems redundant. Given instruction to prefer a few substantive sections over many thin ones, we could combine Qualifications and Skills into one section called "Qualifications & Skills". But headings are prescribed; we cannot create new headings. We could put under Qualifications the preferred qualifications and under Skills we could list the specific technical skills like "DOORS, SysML, UML, DoDAF, UPDM/UAF, Cameo, ModelCenter, Teamcenter, MBSE, digital engineering". However that may be thin. Maybe better to put under Skills the list of tools and proficiencies, and under Qualifications the broader experiential items (leadership, naval warfare, etc). Let's decide: Qualifications (preferred): broad experience across V lifecycle, experience leading teams, experience preparing work products for milestones, experience in naval warfare domains, industry recognition, active TS/SCI clearance. Skills