Spacecraft Subsystem SME

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate like EEO, navigation, etc. Also remove duplicated lines. Need to preserve all substantive info. Let's parse the posting. Title: Spacecraft Subsystem SME Belong. Connect. Grow. with KBR! (But we don't repeat title as heading.) First paragraph: KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security. KBR is seeking a motivated and experienced spacecraft or spacecraft subsystem SME to join our team in El Segundo, CA. The MSEIT effort provides leading-edge Systems Engineering & Integration (SE&I) for the United States Space Force’s (USSF) Space Systems Command (SSC). We acquire state-of-the-art Military and Commercial Satellite Communications (SATCOM) systems, providing global secure, survivable, and protected communications for our nation’s warfighters. We seek technical individuals who will thrive in a highly collaborative work environment of small teams, using the most modern tools and methodologies to tackle the challenges of integrating complex space and ground communications systems. Then "Why Join Us?" with bullet points: Innovative Projects..., Collaborative Environment..., Impactful Work... Then "Key Responsibilities" list. Then "Work Environment" with Location: On-site, Travel Requirements: Infrequent, Working Hours: Standard. Then "Qualifications Required:" list. Then "Basic Compensation: $150,000 to $229,000 in California" plus note. Then "Ready to Make a Difference?" paragraph. Then "KBR Benefits" description. Then "Belong, Connect and Grow at KBR" paragraph. Then "We Deliver – Together." etc. Then EEO boilerplate and Job ID. We need to produce sections: About the role (maybe the introductory paragraph), Responsibilities, Qualifications, Skills (maybe from qualifications?), Benefits, Pay, Schedule. Also maybe "Work Environment" could be part of Schedule? But we have Schedule section only if posting actually states schedule. It says Working Hours: Standard. That's schedule info. So we can include Schedule section with that. Pay: we have Basic Compensation range. Benefits: we have KBR Benefits description. Skills: maybe from qualifications: effective communication, interpersonal skills, ability to perform in highly visible and stressful situations, etc. Could be separate Skills section. Qualifications: list of required qualifications. Responsibilities: list. About the role: introductory paragraph(s) describing role and why join us? Could combine "Why Join Us?" as part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have content for About the role (intro + why join us). Responsibilities (key responsibilities). Qualifications (required). Skills (maybe from qualifications). Benefits (KBR Benefits). Pay (Basic Compensation). Schedule (Working Hours: Standard, Travel Requirements: Infrequent, Location: On-site). Could also include Location under Schedule or separate but we only have those headings. We must not create sections with filler like "commensurate with experience". We have actual data. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, duplicated lines. Also remove "Ready to Make a Difference?" maybe it's fluff but it's substantive? It's a call to action; could be considered boilerplate but it's part of posting. Might keep as part of About the role? Might be considered application instruction? It says "If you’re excited about making a significant impact... we encourage you to apply". That's application instruction; we should remove application instructions. So drop that paragraph. Also "KBR offers a selection of competitive lifestyle benefits which could include..." that's benefits. "Belong, Connect and Grow at KBR" is fluff but maybe part of benefits/culture; could be included in Benefits or maybe omitted as boilerplate? It's not exactly boilerplate but it's generic. Might keep as part of Benefits? But we already have Benefits section; we could incorporate that paragraph into Benefits. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the specifics: e.g., "An active Secret Clearance is required for this position. Ability to obtain, or currently cleared for TS/SCI is a plus." etc. We need to keep the list of responsibilities exactly as given (though there may be duplicated lines). Let's extract responsibilities: From posting: Key Responsibilities Provide the technical leadership and assessment for the ESS Program Office in the prime contractor delivery of the space vehicle in the area of Mechanical, Electrical or Test Lead the trades for unit and subsystem designs if necessary, integration and testing into the spacecraft bus, payload and space vehicle Ensure the technical design and interfaces within the space vehicle, along with the ground and terminal segments Support all component and unit test programs, including space qualification testing ensuring survivability in the space environments. Develop test documentations, e.g. test plan and reports as necessary Support the space vehicle test program, ensuring survivability in the space environments. Develop test documentations, e.g. test plan and reports as necessary Building and maintaining strong, collaborative relationships with various government customer organizations, contractors, and FFRDC teammates Note there is duplication: "Support the space vehicle test program..." appears twice similar. We should keep both? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines are present in source; we should keep them? It says remove duplicated lines. So we should deduplicate. So we need to remove duplicate lines. The two lines are nearly identical: "Support all component and unit test programs, including space qualification testing ensuring survivability in the space environments. Develop test documentations, e.g. test plan and reports as necessary" and "Support the space vehicle test program, ensuring survivability in the space environments. Develop test documentations, e.g. test plan and reports as necessary". They are similar but not identical; one mentions component and unit test programs, the other space vehicle test program. Might be considered distinct. Safer to keep both as they are not exact duplicates. However there is duplication of phrase "Develop test documentations, e.g. test plan and reports as necessary". Might be okay. We'll keep them as separate bullet points. Now Qualifications Required list: - An active Secret Clearance is required for this position. Ability to obtain, or currently cleared for TS/SCI is a plus. - BS in technical field, such as engineering, mathematics, physics, software or computer science - 15 years’ experience with spacecraft bus or subsystems, or Master’s degree and 12 years’ experience - Previous proven coordination experience - Effective communication (both written and oral), and interpersonal skills. - Ability to perform in highly visible and stressful situations - DOD or IC space experience preferred - Space systems engineering experience desired at the unit, subsystem, spacecraft or space vehicle levels - Requirement to work on site at LAAFB 100%. Remote work unavailable - Approximately 10% travel within Southern California and CONUS, depending on prime contractor selection of unit suppliers Note: The last two items about work site and travel could be considered Schedule/Location. We'll treat them under Schedule. Now Skills: maybe we can extract effective communication, interpersonal skills, ability to perform in highly visible and stressful situations as Skills. Also maybe "Previous proven coordination experience" could be skill. But we already have qualifications; we could make a Skills section for soft skills. However we need to avoid thin sections. Could combine Skills into Qualifications? But we have separate headings allowed. We could make Skills section containing: Effective communication (both written and oral), interpersonal skills, Ability to perform in highly visible and stressful situations, Previous proven coordination experience. That seems substantive. Now Benefits: KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development. Also "Belong, Connect and Grow at KBR" paragraph: At KBR, we are passionate about our people and our Zero Harm culture. These inform all that we do and are at the heart of our commitment to, and ongoing journey toward being a People First company. That commitment is central to our team of team’s philosophy and fosters an environment where everyone can Belong, Connect and Grow. We Deliver – Together. That's fluffy but maybe part of benefits/culture. Could include in Benefits section as additional detail. Now Pay: Basic Compensation: $150,000 to $229,000 in California. The offered rate will be based on the selected candidate’s knowledge, skills, abilities and/or experience and in consideration of internal parity. Now Schedule: Location: On-site, Travel Requirements: Infrequent, Working Hours: Standard. Also from qualifications: Requirement to work on site at LAAFB 100%. Remote work unavailable. Approximately 10% travel within Southern California and CONUS, depending on prime contractor selection of unit suppliers. We can combine: Location: On-site at LAAFB (100% on-site, remote unavailable). Travel: Infrequent (~10% within Southern California and CONUS). Working Hours: Standard. Now About the role: combine introductory paragraphs and "Why Join Us?" bullet points. Let's craft About the role paragraph(s): KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to customers in the intelligence and national security communities. In this position, your work will have a profound impact on protecting national security. KBR seeks a motivated and experienced spacecraft or spacecraft subsystem SME to join the team in El Segundo, CA. The MSEIT effort provides leading-edge Systems Engineering & Integration (SE&I) for the United States Space Force’s (USSF) Space Systems Command (SSC), acquiring state-of-the-art Military and Commercial Satellite Communications (SATCOM) systems that deliver global secure, survivable, and protected communications for warfighters. The role requires thriving in a highly collaborative small-team environment using modern tools and methodologies to integrate complex space and ground communications systems. Why Join Us? (we can keep as bullet list under About the role or separate section? There's no heading for Why Join Us; we can incorporate as part of About the role as a bullet list under a subsection? But we only allowed headings list; we could make a subsection under About the role using

• . That's fine. Thus About the role will have prose paragraphs and a bullet list for Why Join Us. Now we need to output HTML fragment with

  headings and appropriate

  and

  • . We must not include or . Just the fragment. Let's structure:

    About the role

    KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to customers in the intelligence and national security communities. In this position, your work will have a profound impact on protecting national security. KBR seeks a motivated and experienced spacecraft or spacecraft subsystem SME to join the team in El Segundo, CA. The MSEIT effort provides leading-edge Systems Engineering & Integration (SE&I) for the United States Space Force’s (USSF) Space Systems Command (SSC), acquiring state-of-the-art Military and Commercial Satellite Communications (SATCOM) systems that deliver global secure, survivable, and protected communications for warfighters. The role requires thriving in a highly collaborative small-team environment using modern tools and methodologies to integrate complex space and ground communications systems.

    Why Join Us?

    but we don't have that