Requirements Management Engineer V

We need to output HTML fragment with sections: h3 headings for sections present. No job title heading. No Job ID. Remove boilerplate. Include only sections with real content. We need to parse the posting. Content: - About the company? The first paragraph about Axiom Space description. Could be "About the role"? Actually "Position Summary" is a section. Also "Key Duties & Responsibilities". "Qualifications". "Preferred Qualifications". "Core Skills". "Core Competencies". "Work Environment". "Requirements" (export control). "Physical Requirements". Also maybe "Education & Experience" under Qualifications. We need to decide which sections to include based on actual content. We must not create sections with filler like "commensurate with experience". Not relevant. We need to preserve all substantive info. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those standard headings if applicable, but we can also use other headings? Probably we should stick to those headings where appropriate. However we have sections like "Key Duties & Responsibilities" which maps to Responsibilities. "Qualifications" maps to Qualifications. "Preferred Qualifications" could be part of Qualifications or separate; but we could combine. "Core Skills" maps to Skills. "Core Competencies" maybe also Skills? Could be part of Skills or separate. "Work Environment" maybe not in list; but we could omit or put under a generic heading? The instruction says include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't restrict to only those headings; it gives examples. So we can use other headings if needed, but better to map to given ones. We have no Pay, Benefits, Schedule info. So we should not include those sections. We have "Work Environment" content: "Generally, an office environment, but can involve inside or outside work depending on the task." That's substantive. Could be a section "Work Environment". Not in examples but okay. We have "Requirements" (export control) content: "This position may require access to export controlled technical data..." That's substantive. Could be a section "Requirements" (but note we already have Qualifications; maybe rename to "Security Requirements" or "Export Control". But we can use heading "Requirements" as per examples. However that may conflict with Qualifications. But we can have multiple sections: Qualifications and Requirements (like job requirements). The posting already has a section titled "Requirements" near the end about export control. So we should include that as a heading "Requirements". The earlier "Qualifications" section includes Education & Experience etc. So we will have both. We also have "Physical Requirements" content: "Work may involve sitting or standing for extended periods (90% of the time) May require lifting and carrying up to 25 lbs. (5% of the time) Equipment and Machines Standard office equipment (PC, phone, printer, etc.)". That's substantive; could be a section "Physical Requirements". Not in examples but okay. We also have "Core Skills" and "Core Competencies". Could combine into Skills section. But we have both; we could make a Skills section that includes both bullet lists. We need to use

• for any list of duties/requirements/benefits. So we need to turn lists into
  • . The duties are a paragraph with many sentences separated by line breaks? Actually they are a list of duties each starting with a verb. We should convert each duty into a
  • . Similarly qualifications list. We must preserve all substantive info; not invent or summarize away detail. So we need to keep the exact wording? Probably we can keep the wording but format as list items. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement; we should remove that. Also remove "For more information about Axiom Space, visit www.axiomspace.com." That's maybe boilerplate? It's informational but not required? Might be considered boilerplate; but it's not navigation/legal/EEO. It's just a link. Might be considered extra but not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not those; but it's maybe not essential. However we should preserve ALL substantive information; is that substantive? It's just a link to website; maybe not essential but could be considered substantive. However it's not about the job. I'd lean to keep it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The link is not substantive to the job; but it's still info. However it's not a duplicate. I'd keep it maybe as a

    . But it's not a heading. Also "Axiom Space fosters a work environment inclusive of all perspectives." That's part of intro; could be kept. We need to output only HTML fragment, no /, no markdown. Let's structure:

    Position Summary

    maybe? But the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Position Summary is not in list but could be considered "About the role". However we have a "Position Summary" paragraph. Could treat as "About the role". But we already have an introductory paragraph about the company. Might be better to have a section "About the role" containing the position summary and maybe the introductory description. But we must not repeat the job title as a heading. The job title is "Systems Engineer" (actually the posting says "Systems Engineer who is fueled..." then later "Position Summary Since Axiom Space is a very complex work environment, we are looking for a resilient, high-energy Requirements Management Engineer". So the actual role is Requirements Management Engineer. The job title maybe "Systems Engineer" but the role is Requirements Management Engineer. We should not repeat the job title as a heading. So we can avoid a heading that is exactly the job title. We can have a heading "About the role" containing the position summary paragraph. Then "Responsibilities" for Key Duties & Responsibilities. Then "Qualifications" for Education & Experience and maybe also include Preferred Qualifications? Could separate but we can combine. Then "Skills" for Core Skills and Core Competencies. Then "Work Environment" for Work Environment paragraph. Then "Requirements" for export control. Then "Physical Requirements" for physical requirements. We must not include sections with filler. All have content. Now we need to convert lists. Let's extract the Position Summary paragraph: "Position Summary Since Axiom Space is a very complex work environment, we are looking for a resilient, high-energy Requirements Management Engineer, responsible for owning and maintaining system, subsystem, and component requirements for projects related to Axiom Station. This role is onsite in Webster, Texas." We need to keep that as prose

    . Now Responsibilities: The bullet list after "Key Duties & Responsibilities". Let's list each duty: - End-to-end, cradle-to-grave requirements management for Axiom Systems - Responsible for implementing requirements architecture and organization - Requirements solicitation and compilation from stakeholders, contract documents, applicable standards, and more - Develop, communicate, and maintain requirements specific to assigned system - Responsible for Axiom Systems requirements decomposition, including 1) allocation of requirements to architecture, 2) system and subsystem-level requirements, 3) component and procurement specifications, including synthesis, traceability, derivation, change tracking, stakeholder needs, impact assessments, and requirements maintenance and updates - Responsible for initiating, coordinating, and closing formal requirements review and approval per Axiom processes - Maintain bidirectional requirements traceability across lifecycle stages - Support Axiom Systems development by providing down-and-in system and subsystem-level support and information, including change impacts to/from other areas of the System - Monitor design and testing progress and communicate potential issues with respect to requirements compliance - Develop waivers and other variances per Axiom process - Communicate System Engineering and Integration progress and status - Collaborate with system and subsystem engineer, program office personnel, and external customers for SE&I planning, scheduling, and execution - Perform other systems engineering tasks as necessary We need to put each as

    inside

    . Now Qualifications: The section "Qualifications To perform this job successfully, an individual must be able to perform each essential duty satisfactorily. The requirements listed below are representative of the knowledge, skill, and/or ability required. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." Then bullet list: - Bachelor’s Degree in an engineering (aerospace, electrical, mechanical, or related discipline) - 10+ years of experience in System Engineering and Integration - Demonstrated experience authoring and managing software/system requirements (functional, performance, safety, and interface) - Proficiency with at least one requirements management tool (e.g., Jama, DOORS, or Innoslate) - Track record of making things happen in ambiguous, fast-moving environments - Uses good judgement to problem-solve proactively, positively impacting hard challenges - Demonstrated organization skills to meet tight deadlines with high quality results Then "Preferred Qualifications" bullet list: - Experience in aerospace or spaceflight systems, ideally human-rated or safety-critical programs - Experience with JAMA Connect and Cameo Datahub - Working knowledge of JIRA/Confluence - Hands-on experience applying Model-Based Systems Engineering (MBSE), using SysML or an equivalent modeling language, in at least one MBSE tool (e.g., Cameo, Rhapsody, Innoslate) - Experience working in Agile or hybrid Agile/waterfall program environments - INCOSE membership or certification (ASEP/CSEP) We could combine both under Qualifications, maybe separate subheadings? But we only have h3 headings; we could have a single Qualifications section with two lists: "Required Qualifications" and "Preferred Qualifications" as

    headings? But we cannot use headings inside? We could use

    Required Qualifications:

    then list. But the instruction says use

    for prose. So we can include a

    for the intro, then maybe a

    for "Required Qualifications:" then

    . Then a

    for "Preferred Qualifications:" then

    . That's okay. Now Skills: Core Skills and Core Competencies. Core Skills bullet list: - Conceptual thinking - Entrepreneurial, growth mindset - High EQ and ability to collaborate within teams and cross-functionally - Tech-solutioning in using systems and tools to move smarter and faster Core Competencies bullet list: - Embody our core values of leadership, innovation, and teamwork. In addition, to perform the job successfully, an individual should demonstrate the following competencies: - Accountability - Technical Rigor - Execution Discipline - Pride of Delivery Note the first bullet includes a sentence. We'll keep as is. We can combine into a Skills section with two lists: Core Skills and Core Competencies. Now Work Environment: paragraph: "Generally, an office environment, but can involve inside or outside work depending on the task." Now Requirements (export control): paragraph: "This position may require access to export controlled technical data or technology subject to NASA regulations, International Traffic in Arms Regulations (ITAR), or Export Administration Regulations (EAR). In accordance with U.S. export control laws, final candidates may be required to undergo additional export control screening to determine eligibility for access. Meeting these requirements is a condition of employment Management has the prerogative to