Systems Engineer Interface Control Documents (SME2)

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about growth, community, well-being, together we soar. Those could be considered "About the role" or maybe "About the company". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have content for About the role? The first paragraphs talk about growth, community, well-being, together we soar. That's more about company culture. Could be "About the role" but maybe better as "About the role" summarizing the position description. However we also have a "Position Description:" paragraph. That could be used as About the role. We'll include About the role with that description. Responsibilities: we have a Responsibilities section with bullet points (list). We'll output

• for each. Requirements: The posting has Qualifications section (education, experience). Also there is a "Qualifications:" heading. We'll treat that as Requirements or Qualifications. The instruction includes both Requirements and Qualifications as possible headings. We need to decide which to use. Since the posting has "Qualifications:" we can use that heading. Also there is "Additional desired skills:" which could be Skills. We'll include Skills section for those. Benefits: there is a Benefits Overview section with list. We'll include Benefits. Pay: there is Compensation Details with a note about range but says "The compensation range or hourly rate listed for this position is provided as a good-faith estimate..." but no actual numbers given. It says "Actual compensation may vary...". There's no specific figure. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. Since no specific compensation figure is given, we should not include Pay section. Similarly Schedule: there is Attendance: Normal workday 7:30-4:30, Monday thru Friday. Minimal overtime may be required (10%). That is schedule info. So we can include Schedule section with that info. We must not include boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Original Posting: 09/17/2026 - 10/31/2026" etc. Also remove "Amentum anticipates this job requisition will remain open..." etc. Also remove "#ESSCA #ASED #Amentum". Also remove "Proof of U.S. Citizenship is required."? That is a requirement; maybe include in Requirements/Qualifications? It's a requirement but not listed under Qualifications. Could be part of Requirements. We'll include it as a bullet under Requirements or Qualifications? Probably under Requirements. We need to preserve all substantive information. So we need to include U.S. Citizenship requirement somewhere. Also "Essential Functions Work Environment:" etc. That includes many details like travel, physical requirements, equipment, attendance, other essential functions. Some of that could go under Requirements or maybe a separate section like "Working Conditions". But we only allowed headings from list. Could incorporate into Requirements or maybe Schedule? But we have Schedule for work hours. The essential functions details (travel 5%, ability to work at computer, etc.) are substantive. We could include them under a section like "Requirements" as bullet points. Or we could create a "Working Conditions" but not allowed. So we will put them under Requirements (or Qualifications). Since the posting already has Qualifications heading for education/experience, we can add additional bullets under Requirements for essential functions. However we need to decide which heading to use: we have Qualifications (education/experience) and maybe Requirements (essential functions). We'll output both headings if they have content. Thus sections: - About the role: using Position Description paragraph(s). Could also include the introductory paragraphs about growth, community, well-being, together we soar? Those are more about company but could be considered About the role? The instruction says use headings e.g. About the role, Responsibilities, etc. It doesn't forbid using About the role for company overview. We'll include About the role with the introductory paragraphs (the first four paragraphs before Position Description). That seems appropriate. - Responsibilities: list. - Qualifications: education/experience requirements (degree, years, ABET, etc.) plus U.S. Citizenship requirement? Might be separate. - Skills: Additional desired skills list. - Benefits: list. - Schedule: attendance details. We must not include Pay. We must not include any filler like "commensurate with experience". Not present. We need to ensure we don't repeat job title as heading. Now craft HTML. We'll need to escape any HTML special characters? Not needed. We'll produce:

  About the role

  Join Our Journey At Amentum Space Exploration Division (ASED) your growth is our priority! That’s why we offer an array of exciting opportunities for your career development. From the transformative Team Lead Academy to education reimbursement, personalized mentoring, and engaging company-sponsored networking events, you have the power to shape your professional journey in a way that aligns with your aspirations. Find Your Community At the heart of our thriving business are the incredible people who make it all possible. We celebrate a vibrant array of cultures, backgrounds, and experiences. Here, we foster an environment where everyone—employees, clients, and partners alike—are treated with the dignity and respect they deserve. Prioritize Your Well-Being Our extensive benefits package is designed with your health in mind. Enjoy wellness programs, paid holidays, generous time off, employee perks, and so much more. We’re here to help you achieve a harmonious balance in your life—both at work and at home. Together, We Soar Our dynamic team consists of 10 companies united in a single mission: to venture from Moon to Mars and beyond. Join us on this extraordinary adventure! This position has been aligned with Amentum Space Exploration Division. To learn more, click here

  But we should remove the "To learn more, click here" as it's application instruction? It's a link instruction; maybe considered boilerplate. The instruction says remove application instructions. So we should drop that sentence. Also remove "This position has been aligned with Amentum Space Exploration Division." maybe keep as it's descriptive. The "click here" is definitely application instruction. We'll remove that sentence. Thus About the role paragraph will be the introductory paragraphs up to "Join us on this extraordinary adventure!" plus maybe the sentence about alignment. We'll keep "This position has been aligned with Amentum Space Exploration Division." as it's part of description. Now Responsibilities: we need to capture each bullet under "Responsibilities:" and sub-bullets. The text: Responsibilities: Engineering support to be performed by the candidate includes: Provide system functional design and integration support for the SLS program Control the integrated system architecture through appropriate controlling documents and/or deliverables. Perform technical integration across multiple NASA Centers, diverse engineering and program/project organizations, and a variety of engineering disciplines such as propulsion, structures, avionics and power, guidance and navigation, flight software, and human engineering. Develop digital engineering tools used to manage baseline, traces, and verification tracking Develop strategic plans and negotiate resolution of open requirement and design issues and concerns to ensure closure of TBDs, TBRs, etc. within the SLS and EV organization schedule allowance. Supply leadership and support for the development of key system engineering products for SLS program/project milestones and provide technical leadership to these SLS program/project milestone reviews and events. EGS integration support to be provided by the candidate includes: Provide leadership and support for integration activities between SLS, EGS, Element and Prime Contractor teams for the NASA SLS LSE, SLS LSE Team and the SLS Chief Engineer. Provide inputs to reviews and coordination for the Space Launch System (SLSP)-to-Ground Systems Development and Operations Program (GSDOP) Interface Control Document (ICD), Volumes 1 to 13. Provide leadership and support for special studies as requested by EV72 management in support of the GSDOP ICD Development as it applies to the SLS and its Elements. Provide leadership and support for resolving issues between SLS and EGS such as hardware or software design, bandwidth, C&DH etc. Assist in technical evaluations of verification closure data and rationale. We'll turn each line into
• . Ensure we keep the content exactly. Now Qualifications: The section: Qualifications: Degree in Mechanical, Electrical, Aerospace, or Systems Engineering or related field required. Degree from an ABET-accredited university is preferred. Typically, educational requirements are the equivalent of a Masters with at least 18 total years of relevant experience or a BS with at least 20 total years of relevant experience. The candidate is required to have: At least 13 years of relevant experience in systems engineering and integration, requirements management, system architecture definition, functional design, and design integration. Demonstrated experience working across organizational boundaries and engineering disciplines to identify requirements and resolve vehicle/propulsion systems integration issues. Excellent oral, written, and customer relation skills, and be proficient using Microsoft Office Suite (Word, Excel, PowerPoint, and Outlook). Working knowledge of digital engineering tools (databases such as DNG; MagicDraw; Power VI) Personnel are required to be self-directed, effective team players familiar with working in a fast-paced, dynamic work environment who are willing to assume lead roles in the SLS requirements management, verification, and validation planning effort. Additional desired skills: ... (we'll treat as Skills) Also "Proof of U.S. Citizenship is required." appears later under Essential Functions? Actually after Essential Functions list, there is "Proof of U.S. Citizenship is required." before the hashtags. We'll include that as a qualification bullet. Thus Qualifications bullets include all those lines. Now Skills: Additional desired skills list: Additional desired skills: The presence of one or more of these qualifications will be used as distinguishing factors in selecting applicants: An understanding and knowledge of the current SLS program and a working understanding of the SLS Element interfaces. Experience in requirements development and maintenance through relational database management and an understanding of Model Based Systems Engineering (MBSE). Familiarity with NASA Systems Engineering policies and procedures related to verification, and have experience using tools/systems to manage verification compliance data. Experience in developing verification strategies, verification planning, and facilitating the successful completion of verification compliance activities. Knowledge of launch vehicle programmatic planning processes and experience performing oversight of prime contractor hardware production, test, and certification efforts. We'll make each a
• . Now Benefits: Benefits Overview list: Offerings include: Health, dental, and vision insurance Paid time off and holidays Retirement benefits (including 401(k) matching) Educational reimbursement Parental leave Employee stock purchase plan Tax-saving options Disability and life insurance Pet insurance Note: Benefits may vary based on employment type, location, and applicable agreements. Positions governed by a Collective Bargaining Agreement (CBA), the McNamara-O'Hara Service Contract Act (SCA), or other employment contracts may include different provisions/benefits. We'll include the list items; we can ignore the note as it's boilerplate? It's not boilerplate but it's a note about variability. Might be considered not specific content? It's still substantive but it's a note. The instruction: do not create Benefits sections unless posting actually states them. It does state benefits list. The note is extra but we can include it as a

  after the list maybe. However the note may be considered boilerplate? It's not navigation/legal/EEO. It's a note about benefits variability. I'd keep it as a

  after the list. Now Schedule: Attendance: Normal workday 7:30-4:30, Monday thru Friday. Minimal overtime may be required (10%) to meet schedule milestones and to support technical demands of the job. Regular attendance is a necessity, and adequate arrangements for delegating duties during absences are required. We'll