Test Engineer - Spaceflight Hardware

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID/requisition numbers as headings; fold minor metadata into short p or drop. We must preserve all substantive info, no invented details. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to parse the posting. Title: Test Engineer - Spaceflight Hardware Belong. Connect. Grow. with KBR! (title not needed). Then description: "Around here, we define the future..." etc. That's fluff but maybe part of About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. Let's extract: - About the role: maybe the introductory paragraph describing role: "In this role, you play a role in providing test engineering services for product development and certification efforts in support of various space flight projects for human health related systems as NASA continues to evolve systems for exploration missions including Moon Base and Artemis missions. It is expected that this position will support a larger project team and will receive task direction from a more senior project/test engineer or project manager. This position will support the design life cycle of the project. It is expected that this function understands testing requirements from the project and develop test plans to meet those requirements. This position will support the team by designing tests, test fixtures, writing test plans and procedures, conducting Test Readiness Reviews, operating hardware during tests, collecting and deciphering data, and writing test reports. Awareness of the Flight Hardware Development processing as outlined in SA-WI-014 and EA-023 is considered a strength with the expectation that the candidate will become well versed as the solutions are developed. This position interfaces with Project Management, System Engineering, Quality Engineering, Design and Development, Technical Staff, Logistics, and the NASA customer as part of the Flight Hardware Engineering Department." That's a lot of prose. Could be About the role. - Responsibilities: The "You Will:" list bullet points: Maintain Safety records and certifications. Use project requirement documents and verification documents to develop test strategies/planning and produce test plans, test set-ups and procedures. Coordinate with service providers including scheduling test facilities as required. Collaborate with project management, customers, and other stakeholders to establish test schedules, coordinate, and execute development and certification testing events. Complete functional, development, certification, acceptance, and integration testing of the hardware during the different stages of the project life cycles. Correlate test results and complete data analysis as required in a test report format. Provide hardware support and technical knowledge during integrated hardware/software testing. Process hardware at KBR labs and Johnson Space Center Test Facilities. Read, understand, and interpret engineering drawings. Work closely with the customer and project team members. Other duties as assigned. That's responsibilities. - What You Bring: maybe Qualifications? Actually "What You Bring:" includes experience leading product testing etc. Then "Required: Your Qualifications:" Bachelor’s degree ... at least 5 years of related experience. Desired: Experience with JSC projects and test facilities 2 years of experience in flight hardware development Experience with testing in a Lab Experience with pressure systems. Then "Required: Your Skills:" Microsoft Office Products Desired: Experience with Solid Works. Thus we have Qualifications (education + experience), Skills (Microsoft Office, SolidWorks desired). Also maybe Requirements? The posting lumps Required: Your Qualifications and Required: Your Skills. Could treat Qualifications as education+experience, Skills as technical skills. Requirements maybe not separate; but we could combine Qualifications and Requirements? The instruction says use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide if we have content for Requirements separate from Qualifications. The posting has "Required: Your Qualifications:" and "Desired: ..." plus "Required: Your Skills:" and "Desired: Experience with Solid Works". So we could put Qualifications heading for education+experience, Skills heading for technical skills. Requirements maybe not needed; but we could include Requirements as a heading if we have content like "You bring experience leading product testing as a vital part of the Flight Hardware development team. You use your experience and judgment to control activity within your test area. You comply with KBR’s Safety, Health and Environmental Plan, Quality Plan, and all safety policies and procedures, and complete all assigned training." That's more like general requirements/experience. Could treat that as Requirements. Thus we have: - About the role: introductory paragraph(s) before "What You’ll Do:" maybe includes the fluff about KBR mission. But we should preserve substantive info; the fluff about "Around here, we define the future..." is maybe not substantive but still part of posting. However we should avoid boilerplate; but that's not boilerplate, it's company description. Could include in About the role. - Responsibilities: the "You Will:" list. - Requirements: the "What You Bring:" paragraph about experience leading product testing, complying with safety etc. - Qualifications: Bachelor’s degree + 5 years experience; desired items. - Skills: Microsoft Office Products; desired SolidWorks. - Benefits: "Why KBR KBR offers 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 later repeated about Zero Harm culture etc but that's more fluff. We'll include benefits. - Pay: Not mentioned; no pay info. So we should NOT include Pay section. - Schedule: "This position is expected to be 100% on site and 100% in person. Occasional travel may be required." That's schedule info. So include Schedule. Now we need to output HTML fragment with

headings and appropriate

or

• . For lists, use
  • . For prose, use

    . We must not repeat job title as heading. No Job ID/requisition numbers as headings; we can drop the ID R2126261 or put in a short p if we want but better to drop. We must remove duplicated lines: there are duplicated paragraphs about Zero Harm culture etc. We'll include only once maybe. We must not create sections with filler like "commensurate with experience". Not present. Now craft HTML. Structure:

    About the role

    ... (combined intro)

    Responsibilities

    • Maintain Safety records and certifications.
    • Use project requirement documents and verification documents to develop test strategies/planning and produce test plans, test set-ups and procedures.
    • Coordinate with service providers including scheduling test facilities as required.
    • Collaborate with project management, customers, and other stakeholders to establish test schedules, coordinate, and execute development and certification testing events.
    • Complete functional, development, certification, acceptance, and integration testing of the hardware during the different stages of the project life cycles.
    • Correlate test results and complete data analysis as required in a test report format.
    • Provide hardware support and technical knowledge during integrated hardware/software testing.
    • Process hardware at KBR labs and Johnson Space Center Test Facilities.
    • Read, understand, and interpret engineering drawings.
    • Work closely with the customer and project team members.
    • Other duties as assigned.

    Requirements

    You bring experience leading product testing as a vital part of the Flight Hardware development team. You use your experience and judgment to control activity within your test area. You comply with KBR’s Safety, Health and Environmental Plan, Quality Plan, and all safety policies and procedures, and complete all assigned training.

    Qualifications

    Required: Bachelor’s degree from an accredited college or university in engineering or science and at least 5 years of related experience.

    Desired: Experience with JSC projects and test facilities; 2 years of experience in flight hardware development; experience with testing in a lab; experience with pressure systems.

    Skills

    Required: Microsoft Office Products.

    Desired: Experience with Solid Works.

    Benefits

    KBR offers competitive lifestyle benefits which could include a 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. They also support career advancement through professional training and development.

    Schedule

    This position is expected to be 100% on site and 100% in person, with occasional travel possibly required.

    We need to ensure no extra sections like Pay. Check for duplicated content: we used the Zero Harm culture only once? Not included; we omitted because it's more fluff but could be part of About the role? Might be okay to omit as not substantive. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Zero Harm culture is not boilerplate but could be considered fluff; but we can keep if we want. However we already have About the role with intro; we could add a sentence about KBR's mission and Zero Harm culture. But we must preserve ALL substantive information; is that substantive? It's about company culture; maybe considered substantive. But we already have a lot; we could include a brief sentence. Let's craft About the role paragraph: combine the initial fluff about KBR mission and the role description. Original text: "Title: Test Engineer - Spaceflight Hardware Belong. Connect. Grow. with KBR! Around here, we define the future. We are a company of innovators, thinkers, creators, explorers, volunteers, and dreamers. But we all share one goal: to improve the world responsibly and safely. On the Human Health and Performance Contract we are at the forefront of safeguarding astronaut health, ensuring human performance, and advancing technologies for human space exploration. We are seeking a Test Engineer, ENG2 at the NASA Johnson Space Center (JSC) in Houston, TX. What You’ll Do: In this role, you play a role in providing test engineering services for product development and certification efforts in support of various space flight projects for human health related systems as NASA continues to evolve systems for exploration missions including Moon Base and Artemis missions. It is expected that this position will support a larger project team and will receive task direction from a more senior project/test engineer or project manager. This position will support the design life cycle of the project. It is expected that this function understands testing requirements from the project and develop test plans to meet those requirements. This position will support the team by designing tests, test fixtures, writing test plans and procedures, conducting Test Readiness Reviews, operating hardware during tests, collecting and deciphering data, and writing test reports. Awareness of the Flight Hardware Development processing as outlined in SA-WI-014 and EA-023 is considered a strength with the expectation that the candidate will become well versed as the solutions are developed. This position interfaces with Project Management, System Engineering, Quality Engineering, Design and Development, Technical Staff, Logistics, and the NASA customer as part of the Flight Hardware Engineering Department." We can split: About the role could be the paragraph before "What You’ll Do:" (the KBR mission and seeking). Then Responsibilities is the "What You’ll Do:" content (which we already captured as responsibilities). However we also have a separate "You Will:" list later which is more detailed responsibilities. The "What You’ll Do:" paragraph is somewhat similar to the You Will list but less detailed. To avoid duplication, we could