Systems Engineer, Interface Control Documents (ES2)

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 that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, navigation, cookie, application instructions. Must preserve all substantive info. We need to parse the posting. Key content: - Intro: "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 CFD Research. To learn more, click CFDR Position Description: This opportunity will provide systems engineering and system-level integration support for the Space Launch System (SLS) program’s interfaces with the Exploration Ground Systems (EGS) program. This position directly supports the SLS Lead Systems Engineer (LSE) on behalf of the Systems Design & Definition Branch (EV72). This support will include participation in reviews, Technical Interchange Meetings (TIMs), technical performance meetings, teleconferences, working groups and trade studies." That's basically an overview. Could be "About the role" or "Overview". We need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Responsibilities section: bullet list after "Responsibilities:" with subpoints. We have Qualifications section: bullet list after "Qualifications:" with subpoints. We have "Additional desired skills:" maybe Skills. We have "Essential Functions" includes Work Environment, Physical Requirements, Equipment and Machines, Attendance, Other Essential Functions. Could be considered part of Requirements? Might be separate but we only have limited headings. Could put under Requirements or Qualifications? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have Benefits: described in "Prioritize Your Well-Being" and later "Benefits Overview:" with list. We have Pay: "Compensation Details: ES2 The compensation range or hourly rate listed for this position is provided as a good-faith estimate..." This is vague, not a specific number. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation details but not a specific range; it's a statement that compensation range is provided as estimate. Does that count as stating them? It says "The compensation range or hourly rate listed for this position is provided as a good-faith estimate..." but no actual numbers. It's vague. Likely we should not create Pay section because no actual numbers. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since they didn't give actual numbers, it's placeholder. So omit Pay. 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." That's a schedule. So we can include Schedule section with that info. Now we need to decide sections: - About the role: could include the introductory paragraphs describing the role, mission, alignment with CFD Research, support for SLS LSE, etc. That seems appropriate. - Responsibilities: list as given. - Requirements: maybe combine Qualifications and Essential Functions? But we have Qualifications heading separate. The instruction includes both Requirements and Qualifications as possible headings. We need to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = desired? But we have both "Qualifications:" and "Additional desired skills:" plus "Essential Functions". We could treat "Qualifications:" as Requirements (mandatory) and "Additional desired skills:" as Skills. And "Essential Functions" maybe also Requirements? But we can incorporate essential functions into Requirements as they are mandatory. However we must not duplicate content. Let's map: - Requirements: include the mandatory qualifications from "Qualifications:" (degree, experience, etc.) plus maybe "Essential Functions" (work environment, etc.)? But essential functions are more about job demands; could be considered Requirements as well. But we have limited headings; we could put essential functions under Requirements as a list. - Qualifications: maybe we could treat as "Preferred Qualifications" but we already have Requirements. The instruction says we can use Qualifications heading. So we could put the "Additional desired skills:" under Qualifications. Or we could put the mandatory qualifications under Requirements and the desired under Qualifications. That seems logical. - Skills: maybe we could have a Skills heading for technical skills like Microsoft Office, digital engineering tools, etc. But those are already in Qualifications. Could combine. Given we have limited headings, we can do:

About the role

(intro)

Responsibilities

(list)

Requirements

(mandatory qualifications + essential functions)

Qualifications

(desired/additional skills)

Benefits

(benefits overview)

Schedule

(attendance) We must not include Pay. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. Let's extract About the role text: The initial paragraphs up to "This position has been aligned with CFD Research. To learn more, click CFDR Position Description: This opportunity will provide systems engineering and system-level integration support for the Space Launch System (SLS) program’s interfaces with the Exploration Ground Systems (EGS) program. This position directly supports the SLS Lead Systems Engineer (LSE) on behalf of the Systems Design & Definition Branch (EV72). This support will include participation in reviews, Technical Interchange Meetings (TIMs), technical performance meetings, teleconferences, working groups and trade studies." We should keep that as prose in

. Possibly break into multiple paragraphs but we can keep as one. Now Responsibilities: The bullet list after "Responsibilities:" includes: - Engineering support to be performed by the candidate includes: - Provide system functional design and integration support for the SLS program - Support the integrated system architecture through appropriate controlling documents and/or deliverables. - Use digital engineering tools in the management of interface documents, their traces, and verification planning - 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 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 11. - 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 need to preserve all. Use

• for list. The top-level bullet "Engineering support to be performed by the candidate includes:" could be a heading? But we can treat as a
• with sublist? Simpler: make a flat list of all responsibilities. Could include the leading phrase as a list item. But better to keep structure: maybe a

  introducing then

  for each bullet. However instruction: Use
  • for any list of duties/requirements/benefits. So we can make a
    with each duty as
    • . The leading phrase "Engineering support to be performed by the candidate includes:" could be a
    • itself, but then sub-items would be nested? Not required. We'll just list each duty as separate
    • . Ensure we capture all. Now Requirements: Mandatory qualifications from "Qualifications:" block: - 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 or a BS with at least 2 total years of relevant experience. - The candidate is required to have: - At least two 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. Also Essential Functions: Work Environment, Physical Requirements, Equipment and Machines, Attendance, Other Essential Functions. But Attendance we already have separate Schedule section. However Attendance is part of Essential Functions; we could still include it under Requirements? But we have separate Schedule heading, so we should not duplicate. We'll put Attendance under Schedule only. For other essential functions (Work Environment, Physical Requirements, Equipment and Machines, Other Essential Functions) we can include under Requirements as they are mandatory job demands. Let's extract: Work Environment: Office environment. Requires ability to provide clear, concise, accurate and timely communication, both verbally and in writing (100%). Requires ability to interact professionally with co-workers, management, and client (100%). Requires travel in the domestic USA (5%). Requires ability to work at a computer for long periods of time (100%). Physical Requirements: Requires sitting for extended periods of time in meetings with peers, management, and with our client at NASA facilities to discuss technical issues (10%). Also, requires sitting for extended periods of time at a desk to write reports and perform engineering tasks (80%). Requires ability to use stairs or elevators for access between floors and multiple buildings at NASA and our facilities (10%). Equipment and Machines: Requires ability to operate a personal computer, a telephone, fax machine, cop