Project Engineering Specialist, In-space Chemical Propulsion

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate. Preserve all substantive info. We have job description paragraphs, essential functions (list of duties), qualifications (list), preferred additional skills (list), pay range, schedule info. We need to decide sections: - About the role: could be the initial description paragraph(s) before Essential Functions. That seems appropriate. - Responsibilities: essential functions list. - Requirements: maybe the qualifications bullet list? But we also have Qualifications section separate? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have qualifications (education/experience) and also preferred additional skills. Could treat "Qualifications" as the mandatory qualifications (education/experience, years). "Skills" as preferred additional skills. Also we have Pay and Schedule sections. We need to include only sections with real specific content. Pay: we have salary range $92,500 - $171,500. That's specific. So include Pay. Schedule: we have "9/80: Employees work 9 out of every 14 days, totaling 80 hours worked, and have every other Friday off". That's specific. Include Schedule. Benefits: not mentioned. So omit Benefits. Now we need to output HTML fragment only, no /. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Do not put Job ID etc. We need to preserve all substantive info; not invent or summarize away detail. So we need to include all details from description, essential functions, qualifications, preferred skills, pay, schedule. We need to format lists appropriately. Let's extract content. About the role: The paragraph(s) before Essential Functions: "At Rocketdyne, this role sits at the center of turning chemical propulsion hardware into accepted, test-proven deliverables that are ready for space. This is a strong fit for an engineer who likes real hardware responsibility, thrives in a cross-functional environment, and enjoys bringing clarity to ambiguous technical problems. You will work closely with customers, manufacturing, test, quality, and business capture teams. You will also work across engineering disciplines to drive the reviews, inputs, and technical alignment needed to keep hardware and customer deliverables moving. Your impact will be visible in shipped hardware, successful hot-fires, and propulsion systems that reach space, the Moon, and Mars. If you want extensive ownership, close teamwork, and the opportunity to turn hard work into thrusters that power real spacecraft, we encourage you to apply." We can put that in a

  . Responsibilities: Essential Functions list items (each bullet). Let's list them: - Own day-to-day technical execution of in-space chemical thruster projects through production and test for development, qualification, and commercial programs. - Work in close coordination with program management, manufacturing, and test to accelerate issue resolution. - Drive closure of nonconformances, production issues, and test anomalies with technical rigor and deep understanding of your propulsion products. - Maintain working partnerships with quality. - Coordinate and review work across engineering disciplines such as systems, structures, thermal, and drawing development. - Drive the inputs, reviews, and document completion needed to support customer deliverables and program commitments. - Author the technical documentation required to move hardware forward. This includes test plans, procedures, reports, and anomaly documentation. - Provide clear and timely technical responses to customer technical questions. Topics may include hardware status, issue resolution, and test results. - Partner with program management to maintain customer relationships. - Prepare and lead formal presentations and reports for customer communication and gated product reviews (PDR, CDR, TRR, etc.). Presentations may include technical recommendations, trade studies, and issue summaries. - Serve as an engineering point of contact and reviewer for proposals. Develop technical inputs and review scope assumptions for applicable engines or hardware efforts. - Analyze and review hotfire test data to ensure thrusters conform to product line standards and customer specifications. May need to support testing in-person and provide quick judgment calls to support program needs within technical bounds. - No routine travel is expected for this role. We need to ensure we keep all details. Requirements: Might be the qualifications (education/experience) but we have separate Qualifications heading. The instruction includes both Requirements and Qualifications as possible headings. We need to decide what goes where. Usually Requirements could be the mandatory qualifications (education/experience, years). Qualifications could be the same? But we have both headings available; we need to avoid duplication. Perhaps we put the mandatory qualifications under "Requirements" and the preferred additional skills under "Skills". Or we could put education/experience under "Qualifications" and the specific experience areas under "Requirements". However the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's just examples; we can choose which to include based on content. We need to avoid thin sections. So we could combine education/experience and years into one section called "Qualifications". Then the preferred additional skills under "Skills". The "Requirements" heading could be omitted if we don't have distinct content beyond qualifications. But we have specific requirements like "Bachelor's degree in Engineering or Physics and a minimum of 4 years of prior project engineering experience; or a Graduate Degree and a minimum of 2 years of prior project engineering experience. In lieu of a degree, minimum of 8 years of prior project engineering experience." plus "4+ years of experience supporting development, production, integration, qualification testing, or delivery of complex hardware in aerospace, marine, or similar high-reliability engineering environments." plus "4+ years of experience in at least one of the following areas is required: production support or qualification/development testing; experience in both is preferred." plus "4+ years of experience owning technical work and driving closure with strong cross-functional relationships." plus "Strong technical foundation and ability to work effectively across engineering disciplines. This includes reviewing technical inputs from areas such as systems, structures, thermal, and design documentation." plus "4+ years of experience authoring technical documentation such as procedures, reports, nonconformance dispositions, or engineering presentations." plus "Ability to take ownership of ambiguous problems, quickly assess evolving requirements and customer feedback, and determine next steps needed to move hardware forward." plus "Proven capacity to deliver results in a fast-paced, technically complex setting by leveraging strong engineering expertise, adaptability, and collaborative problem-solving skills." That's a lot of content; could be under "Requirements". Then "Qualifications" could be the education/experience? But we already used that. Hmm. Better to follow typical job posting: "Qualifications" includes education and experience requirements. "Skills" includes preferred skills. "Requirements" maybe not needed. But we have to decide. Given the instruction to prefer a few substantive sections over many thin ones, we could combine education/experience and the detailed experience requirements into a single "Qualifications" section. Then "Skills" for preferred additional skills. Then we can omit "Requirements". That seems reasonable. Thus sections: About the role (p), Responsibilities (ul), Qualifications (ul or p?), Skills (ul), Pay (p), Schedule (p). We need to use

  • for any list of duties/requirements/benefits. For Qualifications, it's a list of requirements; we can use
    • . For Skills also
      • . For About the role, we can use

        . For Pay and Schedule, we can use

        . Now we need to ensure we preserve all substantive info. Let's copy the qualifications bullet points exactly as they appear. Qualifications bullet points (from posting): - Bachelor's degree in Engineering or Physics and a minimum of 4 years of prior project engineering experience; or a Graduate Degree and a minimum of 2 years of prior project engineering experience. In lieu of a degree, minimum of 8 years of prior project engineering experience. - 4+ years of experience supporting development, production, integration, qualification testing, or delivery of complex hardware in aerospace, marine, or similar high-reliability engineering environments. - 4+ years of experience in at least one of the following areas is required: production support or qualification/development testing; experience in both is preferred. - 4+ years of experience owning technical work and driving closure with strong cross-functional relationships. - Strong technical foundation and ability to work effectively across engineering disciplines. This includes reviewing technical inputs from areas such as systems, structures, thermal, and design documentation. - 4+ years of experience authoring technical documentation such as procedures, reports, nonconformance dispositions, or engineering presentations. - Ability to take ownership of ambiguous problems, quickly assess evolving requirements and customer feedback, and determine next steps needed to move hardware forward. - Proven capacity to deliver results in a fast-paced, technically complex setting by leveraging strong engineering expertise, adaptability, and collaborative problem-solving skills. We need to keep them exactly; maybe we can keep the wording. Now Preferred Additional Skills (list): - Strong technical communication with customers, leadership, and cross-functional teams in a fast-moving hardware environment. - Prior experience with propulsion development or hot-fire testing. - Experience with anomaly investigation, nonconformance disposition, and root cause analysis. - Experience with corrective action or out-of-plan manufacturing support in a hardware environment is preferred. - Familiarity with propellant and material compatibility, contamination-sensitive hardware handling, and spacecraft propulsion integration practices - Demonstrated leadership in managing conflicting priorities while providing product/process expertise in multi-disciplinary project teams We need to keep them. Now Pay: "In compliance with pay transparency requirements, the salary range for this role in Washington State is $92,500 - $171,500. This is not a guarantee of compensation or salary, as final offer amount may vary based on factors including but not limited to experience and geographic location." We need to keep that sentence. It's substantive. Schedule: "Job Schedule: 9/80: Employees work 9 out of every 14 days, totaling 80 hours worked, and have every other Friday off" We need to keep that. Now we need to output HTML fragment. Let's craft:

        About the role

        At Rocketdyne, this role sits at the center of turning chemical propulsion hardware into accepted, test-proven deliverables that are ready for space. This is a strong fit for an engineer who likes real hardware responsibility, thrives in a cross-functional environment, and enjoys bringing clarity to ambiguous technical problems. You will work closely with customers, manufacturing, test, quality, and business capture teams. You will also work across engineering disciplines to drive the reviews, inputs, and technical alignment needed to keep hardware and customer deliverables moving. Your impact will be visible in shipped hardware, successful hot-fires, and propulsion systems that reach space, the Moon, and Mars. If you want extensive ownership, close teamwork, and the opportunity to turn hard work into thrusters that power real spacecraft, we encourage you to apply.

        Responsibilities

        • Own day-to-day technical execution of in-space chemical thruster projects through production and test for development, qualification, and commercial programs.
        • Work in close coordination with program management, manufacturing, and test to accelerate issue resolution.
        • Drive closure of nonconformances, production issues, and test anomalies with technical rigor and deep understanding of your propulsion products.
        • Maintain working partnerships with quality.
        • Coordinate and review work across engineering disciplines such as systems, structures, thermal, and drawing development.
        • Drive the inputs, reviews, and document completion needed to support customer deliverables and program commitments.
        • Author the technical documentation required to move hardware forward. This includes test plans, procedures, reports, and anomaly documentation.
        • Provide clear and timely