Sentinel - Sr. Staff Systems Engineer - 18123

We need to produce HTML fragment with sections: About the role? Actually we need to use headings for sections like 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 as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive info. Let's parse content: - Relocation assistance may be available - Clearance required for start: Yes - Clearance type: Secret - Travel: Yes, 10% of the Time Then description paragraphs about Northrop Grumman. Then "What You Will Get To Do" with bullet list of duties. Then "Specific duties to include, but are not limited to the following:" then list of duties. Then "Leads L2 C&L Specification team (10 team members)" etc. Then "Basic Qualifications" list. Then "Preferred Qualifications" list. Then benefits paragraph: "As a full-time employee of Northrop Grumman Space Systems, you are eligible for our robust benefits package including: Medical, Dental & Vision coverage 401k Educational Assistance Life Insurance Employee Assistance Programs & Work/Life Solutions Paid Time Off Health & Wellness Resources Employee Discounts" Then schedule: "This positions standard work schedule is a 9/80. The 9/80 schedule allows employees who work a nine-hour day Monday through Thursday to take every other Friday off." Then pay: "Primary Level Salary Range: $166,500.00 - $249,700.00" plus explanation. Also relocation assistance, clearance, travel info maybe go under a short paragraph. We need sections: About the role (maybe the description paragraph), Responsibilities (the duties), Requirements (basic qualifications?), Qualifications (maybe preferred?), Skills (maybe combine?), Benefits, Pay, Schedule. We must not create sections with filler like "commensurate with experience". We have actual content for Benefits, Pay, Schedule. We need to decide which headings to use. We have: - About the role: could be the introductory description about Northrop Grumman and the Sentinel program. - Responsibilities: the "What You Will Get To Do" and specific duties. - Requirements: Basic Qualifications (must have). - Qualifications: Preferred Qualifications (nice to have). - Skills: maybe we could combine some skill-specific items from requirements? But we already have Requirements and Qualifications; Skills could be separate if there is explicit skill list. The posting includes many skill items within qualifications; but we could treat them as part of Requirements/Qualifications. However we need to decide if we need a Skills section. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine Skills into Requirements or Qualifications. But we have separate headings allowed; we can omit Skills if not distinct. We have Benefits, Pay, Schedule sections. Also we have relocation assistance, clearance, travel info. Could be placed in a short paragraph under About the role or a separate "Key Details" but we don't have a heading for that. Could incorporate into About the role paragraph. We must not include boilerplate like EEO, application period, etc. We must not include navigation, legal, etc. Now produce HTML:

About the role

... paragraphs ...

Then

Responsibilities

• ... each duty ...

We need to capture all duties from the list. List of duties: - Collaborate with program IPT counterparts to develop supporting systems engineering and design artifacts. - Work with both technical teams and stakeholders to develop and mature architecture content of large programs design. - Help develop and incorporate the appropriate requirements for the system and ensure that they are properly represented in the model. - Develop systems architecture using Cameo Enterprise Architecture (behavioral, structural, analytical). - Contribute to system requirements development, management, and analysis. - Develop unifying model techniques, procedures, and processes (for model development, tool integration, and team integration). - Leads L2 C&L Specification team (10 team members) L2 C&L Specification scope: Responsible Engineers (Owner/Accountable) for L2 C&L Specification development, C&L Compliance Appendices, and C&L Verification Activity Module - Leads Interfaces Team (6 team members) Inter-node ICDs scope: Owns Node-to-Node interfaces (10+ interface documents, hundreds of requirements needing agreement on both sides), develops interface documentation, coordinates with Going Vertical interface team for cameo External Interface Control Document Support: Technical support for EICD development, coordination, and agreements. Not the owner of the EICD itself - Leads Tools and Processes Team (2 team members) Scope Tool Integration -Data Architecture (TIDA) and Physical Architecture (PA) Governance: develop, manage, and regulate SE and MBSE processes that will be used across CS/LS. We need to preserve all details. Could break into multiple

items, each maybe a sentence. We could combine some sentences. Now Requirements (Basic Qualifications): - Bachelor's degree in STEM with 14 years of experience; or Master's degree with 12 years of experience; or PhD with 9 years of experience - Must be a U.S. Citizen with an active DoD Secret clearance with an investigation date within the last 6 years. - Must be able to be successfully screened for Enhanced Security Clearances, within a reasonable amount of time as determined by the company to meet its business need. - 1+ years of experience managing requirements in DOORS - 3+ years of experience working with Systems Engineering and Integration and Test (SEIT) processes - 3+ years of experience working with MBSE tools (Cameo) - 1+ year of experience with Agile methodologies and tools (JIRA/Confluence) - 1+ years of experience supporting trades studies - 3+ years of experience with one or more of the following: C2, physical security, cybersecurity, communications systems, facility design, military aerospace development Now Qualifications (Preferred Qualifications): - Active DoD Top Secret Clearance - Experience in SysML or UPDM modeling languages - Proficiency with the DoDAF, UAF, or other modeling frameworks - Experience modeling with Cameo Enterprise Architecture, MagicDraw (No Magic, Inc.) or other architecture modeling tools - Experience using tools to model large systems with multiple developers - Experience exporting documentation out of a model-based environment - Experience in Software and/or Hardware design - Experience in documenting Interface Control Documents, Interface Requirement Specifications, and Interface Description Documents - Experience with software defined hardware structures (i.e., software defined radars and field programmable gate arrays) - Experience with modeling and simulation programs such as the Advanced Framework for Simulation, Integration and Modeling (AFSIM) - Experience with applying hypervisors, cross-domain solutions, multi-level security systems, or modular open systems approach to integrated systems - Experience with scripting and coding languages such as Python - Experience with Agile Development - Experience with ICBM weapon system sustainment engineering and integration - Experience with complex system development on large programs Now Benefits: - Medical, Dental & Vision coverage - 401k - Educational Assistance - Life Insurance - Employee Assistance Programs & Work/Life Solutions - Paid Time Off - Health & Wellness Resources - Employee Discounts Now Schedule: - This position's standard work schedule is a 9/80. The 9/80 schedule allows employees who work a nine-hour day Monday through Thursday to take every other Friday off. Now Pay: - Primary Level Salary Range: $166,500.00 - $249,700.00 - Explanation: The above salary range represents a general guideline; however, Northrop Grumman considers a number of factors when determining base salary offers such as the scope and responsibilities of the position and the candidate's experience, education, skills and current market conditions. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay. Annual bonuses are designed to reward individual contributions as well as allow employees to share in company results. Employees in Vice President or Director positions may be eligible for Long Term Incentives. 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. We might combine benefits explanation with benefits list; but we already have benefits list; the extra explanation about benefits is duplicate; we could incorporate into benefits section but we must not repeat. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that extra benefits explanation as well. However we already have a benefits list; the extra paragraph mentions health insurance coverage, life and disability insurance, savings plan, Company paid holidays and paid time off (PTO) for vacation and/or personal business. Some of these overlap with benefits list but add details like disability insurance, savings plan, company paid holidays. We should keep them. Thus benefits section could include both the list and the extra description. Now relocation assistance, clearance, travel: we could include a short paragraph under About the role or a separate "Key Details". Since we don't have a heading for that, we can incorporate into About the role. Now produce HTML. We must not include any markdown fences. Let's craft. We'll need to escape any HTML special characters? The text includes ampersand (&) in "Health & Wellness Resources". In HTML we need to escape as &. Also "C&L" appears; need to escape & as &. Also "C&L" appears multiple times. Also "C&L Specification". Also "C&L Compliance Appendices". Also "C&L Verification Activity Module". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&L". Also "C&