Propulsion Engineer, Test/Flight - Engine Test, BE-3U

We need to output HTML fragment with sections: About the role? The posting includes description: "At Blue Origin, we envision..." etc. We need to parse content. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. We need to remove boilerplate: Application Close Date, EEO, legal, etc. Also remove duplicated lines. We need to include metadata like location maybe in a short

. We need to include Pay section: Base Pay Range For WA applicants is $99,201.00 - $138,880.35 Other Site Ranges May Differ. So we have pay info. Schedule? Not mentioned. No schedule details. So we should not create Schedule section. Benefits: there is a Benefits paragraph. So include Benefits section. Qualifications: Minimum Qualifications and Preferred Qualifications. Could combine into Requirements? The spec says we can have Requirements, Qualifications, Skills sections. We need to decide. We have Minimum Qualifications list, Preferred Qualifications list. Also there are some skill-like items: Strong written and verbal communication skills, etc. Those could go under Skills. We need to preserve all substantive info; not invent or summarize away detail. So we need to list each qualification as

under appropriate section. We need to decide sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe Minimum Qualifications), Qualifications (maybe Preferred Qualifications), Skills (maybe communication, travel, etc.), Benefits, Pay. We must not create sections with filler text. Let's extract content. First, intro: "At Blue Origin, we envision millions of people living and working in space for the benefit of Earth. We’re working to develop reusable, safe, and low-cost space vehicles and systems within a culture of safety, collaboration, and inclusion. Join our team of problem solvers as we add new chapters to the history of spaceflight! This role is part of the Blue Origin Engines business unit, where our focus is the design, development, manufacturing, and testing of engines and propulsion systems. Built for multiple uses, our family of engines is powering the next generation of rockets for commercial, civil, national security, and human spaceflight." Then repeated: "This role is part of the Blue Origin Engines business unit, where our focus is the design, development, manufacturing, and testing of engines and propulsion systems. Built for multiple uses, our family of engines is powering the next generation of rockets for commercial, civil, national security, and human spaceflight." That's duplicate; we should keep only once. Then: "As part of a diverse and hardworking team of engineers, you will support the design, analysis, and test of BE-3U engine hardware and fluid systems across the development and production life cycle. Your daily responsibilities will include coordinating with a multidisciplinary team to develop test plans, performing steady-state and transient system analysis, supporting component and integrated engine testing, analyzing test data, and supporting Data Reviews and Test Readiness Reviews. Other tasks include generating test reports, supporting engine requirements verification, implementing opportunities for design and test cadence improvement, and supporting anomaly investigations as well as root cause analysis to drive corrective actions and hardware improvements. We are looking for someone to apply their technical expertise, leadership skills, and commitment to quality to positively impact safe human spaceflight. Passion for our mission and vision is required!" Then "Special Mentions Relocation providedTravel expected up to 10% of the timeInterviews will include a technical assessment". This is a line with no spaces; we need to parse: Relocation provided, Travel expected up to 10% of the time, Interviews will include a technical assessment. We'll keep these as bullet points maybe under Responsibilities or a separate section? Could be under Responsibilities or maybe under Skills? Probably under Responsibilities or a separate "Additional Information". But we only have allowed headings; we could put these under Responsibilities as extra items, or maybe under Skills? They are not skills. Could be under Responsibilities as bullet items. We'll include them as list items under Responsibilities. Then Minimum Qualifications list: - Minimum of a B.S. degree in aerospace/mechanical engineering or physics - 2+ years of professional experience in propulsion design, analysis, or test - Strong understanding and ability to apply engineering fundamentals including thermodynamics, fluid mechanics, heat transfer, and structures - Familiarity with data analysis and data processing, including writing scripts in Python - Working knowledge of engine components such as turbopumps, combustion devices, injectors, valves, regulators, check valves, and other high pressure and cryogenic fluid system components - Knowledge of instrumentation including pressure transducers, thermocouples, and accelerometers - Understanding of cryogenic propellants including liquid hydrogen and liquid oxygen - Ability to read and interpret engineering standards and drawings - Ability to find simple, innovative solutions for difficult problems and to make critical decisions under pressure - Curiosity to understand rocket engines at a component and system level and desire to work in a cooperative, fast paced, and dynamic environment - Strong written and verbal communication skills - Willingness to travel to support on site testing - Ability to earn trust, maintain positive and professional relationships, and contribute to a culture of inclusion - Must be a U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum Preferred Qualifications: - M.S. or Ph.D. in an engineering discipline - Experience with liquid rocket engine testing - Experience with data processing and writing automated data scripts in Python - Familiarity with rocket engine cycles and engine system operations - Experience with fluid system modeling tools and hand-calculation methods for sizing and pressure drop - Exposure to systems engineering practices and requirements management - Experience supporting anomaly investigations and root cause analysis Benefits paragraph: "Benefits include: Medical, dental, vision, basic and supplemental life insurance, paid parental leave, short and long-term disability, 401(k) with a company match of up to 5%, and an Education Support Program.Stock Options for all regular employees (working at least 20 hours/week)Paid Time Off: Up to four (4) weeks per year based on weekly scheduled hours, and up to 14 company-paid holidays.Dependent on role type and job level, employees may be eligible for benefits and bonuses based on the company's intent to reward individual contributions and enable them to share in the company's results, or other factors at the company's sole discretion. Bonus amounts and eligibility are not guaranteed and subject to change and cancellation. Please check with your recruiter for more details." We need to preserve all substantive info; we can format as list. Pay: "Base Pay Range For WA applicants is $99,201.00 - $138,880.35 Other Site Ranges May Differ". We'll put as

. Location: "Location: Renton, WA or Huntsville, AL". We'll include as short

maybe under About the role or separate. We must not include boilerplate: Application Close Date, Culture Statement, Export Control Regulations, Background Check, Equal Employment Opportunity, Affirmative Action, etc. Also remove duplicated lines. Now construct HTML. We'll start with

About the role

then

with intro paragraph (maybe combine location). We'll include location sentence. Then

Responsibilities

then

with list items: support design, analysis, test; coordinating...; performing steady-state...; supporting component...; analyzing test data; supporting Data Reviews and Test Readiness Reviews; generating test reports; supporting engine requirements verification; implementing opportunities for design and test cadence improvement; supporting anomaly investigations and root cause analysis; Relocation provided; Travel expected up to 10% of the time; Interviews will include a technical assessment. We need to ensure we didn't miss any: "We are looking for someone to apply their technical expertise, leadership skills, and commitment to quality to positively impact safe human spaceflight. Passion for our mission and vision is required!" That's more of a statement; could be included as a bullet or as prose. Could be a

under Responsibilities. But we already have list; maybe we add a

after list: "We are looking for someone to apply their technical expertise, leadership skills, and commitment to quality to positively impact safe human spaceflight. Passion for our mission and vision is required!" That's substantive. Now

Requirements

maybe for Minimum Qualifications. We'll list each as
• . Then

  Qualifications

  for Preferred Qualifications. Then

  Skills

  maybe for communication, travel, etc. But those are already in Minimum Qualifications. Could skip Skills section if we already covered. However we need to follow instruction: Prefer a few substantive sections over many thin ones. We have About, Responsibilities, Requirements, Qualifications, Benefits, Pay. That's six sections. Could we combine Requirements and Qualifications into one? But spec allows both. We'll keep them. Skills: we could include "Strong written and verbal communication skills", "Willingness to travel to support on site testing", "Ability to earn trust, maintain positive and professional relationships, and contribute to a culture of inclusion". Those are already in Minimum Qualifications; we could move them to Skills to avoid duplication. But we must preserve all info; we can keep them in Minimum Qualifications and not duplicate. If we create Skills section, we would need to list them again, which would be duplication. Better to not create Skills section; we can omit if not needed. The instruction: Use sections only when posting has real specific content. We have content for Skills (communication, travel, etc.) but they are already captured in Minimum Qualifications. However we could still create Skills section with those items; but that would be repeating content, which is allowed? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. We'll omit Skills section. Thus sections: About the role, Responsibilities, Requirements (Minimum Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay. Now ensure we don't include Schedule. Now produce HTML fragment. We need to wrap each section:

  About the role

  ...

  etc. Make sure to not include any extra text outside HTML. Let's craft. About the role paragraph: Combine intro and location. "At Blue Origin, we envision millions of people living and working in space for the benefit of Earth. We’re working to develop reusable, safe, and low-cost space vehicles and systems within a culture of safety, collaboration, and inclusion. Join our team of problem solvers as we add new chapters to the history of spaceflight! This role is part of the Blue Origin Engines business unit, where our focus is the design, development, manufacturing, and testing of engines and propulsion systems. Built for multiple uses, our family of engines is powering the next generation of rockets for commercial, civil, national security, and human spaceflight. Location: Renton, WA or Huntsville, AL." Now Responsibilities list items. We'll list each as
• . Let's enumerate: - Support the design, analysis, and test of BE-3U engine hardware and fluid systems across the development and production life cycle. - Coordinate with a multidisciplinary team to develop test plans. - Perform steady-state and transient system analysis. - Support component and integrated engine testing. - Analyze test data. - Support Data Reviews and Test Readiness Reviews. - Generate test reports. - Support engine requirements verification. - Implement opportunities for design and test cadence improvement. - Support anomaly investigations and root cause analysis to drive corrective actions and hardware improvements. - Relocation provided. - Travel expected up to 10% of the time. - Interviews will include a technical assessment. - We are looking for someone to apply their technical expertise, leadership skills