Reliability Engineer II

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Let's extract content: First paragraph: "Application Close Date Applications will be accepted on an ongoing basis until the requisition is closed." This is metadata; we can drop or fold into short p. Probably drop as minor metadata. Then: "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 Blue Origin Operations, which is comprised of Integrated Supply Chain, Test Operations, Safety, Quality, and Mission Assurance. This includes Manufacturing and Supply Chain support across all Blue Origin facilities. We are a diverse team of collaborators, doers, and problem-solvers who are relentlessly committed to a culture of safety. We will directly impact the history of space exploration and will require your commitment and detailed attention towards safe and repeatable space flight. Join us in lowering the cost of access to space and enable Blue Origin's vision of millions of people living and working in space to benefit Earth! This role is part of the Safety, Quality, and Mission Assurance team. This team is focused on monitoring and assessing processes that guide Blue Origin’s design, manufacturing, and operations, ensuring system safety engineering, environmental health, and safety, product integrity, and continuous improvement processes. As part of a small team of engineers, you will develop reliability engineering processes and products for the design of launch vehicles, spacecraft, and supporting systems. You must have a passion for human spaceflight and astronaut safety, and a capacity to work collaboratively or independently on sophisticated and exciting new problems. As a Reliability Engineer at Blue Origin, you will work with systems engineering teams to verify compliance with safety and reliability requirements including verification by analysis or test. The Safety and Mission Assurance team works on the full range of Blue Origin products and systems, from launch vehicles to spacecraft and landers. You will assess reliability allocations and trades, perform fault tree analysis, build reliability block diagrams, produce hazard analysis, and perform failure modes and effects analysis (FMEA/FMECA). Experience with electronics reliability predictions, and reliability test design are a bonus. You will help engineers identify areas of opportunity for design improvements, minimize risk, and increase the probability of mission success. If you enjoy being challenged, working on multiple aspects of large systems, and using all the tools in your belt to tackle real problems limiting access to human spaceflight, come join us! We are looking for someone to apply their technical expertise, leadership skills, and dedication to quality to positively impact safe human spaceflight. Passion for our mission and vision is required." That's a lot of prose; could be "About the role" or "Responsibilities". We need to decide sections. We have "Minimum Qualifications" list. We have "Preferred Qualifications" list. We have "Base Pay Range For WA applicants is $99,201.00 - $138,880.35 Other Site Ranges May Differ". That's pay info. We have "Benefits" list. We have "Culture Statement" (some text about applying even if not meeting all qualifications). Could be part of About? Might be considered "About the role" or separate? Probably not needed as separate heading unless specific content. It's a statement encouraging applicants; could be part of About. We have "Export Control Regulations" (citizenship requirement) - that's a requirement (must be US citizen etc). Already in Minimum Qualifications? Actually Minimum Qualifications includes "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." That's same as Export Control Regulations. So we can keep that in Requirements. We have "Background Check Required for all positions..." etc. That's also a requirement but maybe not needed as separate; could be part of Requirements. We have "Benefits" section with details. We have "Pay" section. We have no explicit schedule info. So we should not create Schedule section. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to avoid thin sections. Let's see content: - About the role: could be the introductory paragraphs describing mission, team, etc. That's substantive. - Responsibilities: could be the list of duties: develop reliability engineering processes, work with systems engineering teams, verify compliance, assess reliability allocations, perform fault tree analysis, build reliability block diagrams, produce hazard analysis, perform FMEA/FMECA, help engineers identify opportunities, minimize risk, increase mission success, apply technical expertise, leadership skills, dedication to quality, etc. That's substantive. - Requirements: Minimum Qualifications list (B.S. degree, experience with reliability analyses including FMECA and FTA, ability to read engineering drawings, strong safety and mission assurance fundamentals, excellent communication skills, ability to form relationships, ability to earn trust, must be US citizen etc). Also background check requirement maybe. - Qualifications: Preferred Qualifications list (experience developing reliability models, reliability/life test design, Weibull analysis, stress-strength interference, probability distribution estimation, reliability growth modeling, probabilistic risk analysis, failure rate prediction for electrical components, experience using AI/Automation, scripting languages VBA/Python, experience with software Reliasoft, SAPHIRE, etc). That's substantive. - Skills: Could be extracted from responsibilities? Might be overlapping. But we could combine some into Skills: e.g., "Ability to read and interpret engineering drawings, fluid schematics, and electrical circuit diagrams", "Excellent written, verbal, and interpersonal skills", "Ability to form relationships with experts", "Ability to earn trust", etc. However these are already in Minimum Qualifications. Might be better to not have Skills separate if it's thin. But we have enough content for Skills maybe: we could list technical skills: reliability analysis, FMECA, FTA, fault tree analysis, reliability block diagrams, hazard analysis, FMEA/FMECA, electronics reliability predictions, reliability test design, reliability models, Weibull analysis, stress-strength interference, probability distribution estimation, reliability growth modeling, probabilistic risk analysis, failure rate prediction, AI/Automation, VBA, Python, Reliasoft, SAPHIRE. Also soft skills: communication, teamwork, leadership, problem solving. That could be a Skills section. But we must avoid duplication; we can keep Minimum Qualifications as Requirements, Preferred Qualifications as Qualifications, and maybe Skills as a separate section highlighting both technical and soft skills derived from the text. However the instructions: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one "Requirements" section? But they ask to use headings for sections like Requirements, Qualifications, Skills. We can include them if they have substantive content. We have both Minimum and Preferred Qualifications lists, each substantive. So we can have Requirements (minimum) and Qualifications (preferred). Skills could be derived but might be thin; we could omit Skills if not enough distinct content. However we have many skill items; but they overlap with qualifications. Might be better to omit Skills to avoid thinness. Benefits: we have substantive list. Pay: we have base pay range. Schedule: none, so omit. About the role: we have introductory paragraphs. Responsibilities: we have duties list. Thus sections: About the role, Responsibilities, Requirements (minimum), Qualifications (preferred), Benefits, Pay. We must not include Job ID etc. Also remove boilerplate like EEO, culture statement? The culture statement about applying even if not meeting all qualifications could be part of About the role or maybe we can include as a short paragraph in About. It's substantive but not a heading. We'll incorporate into About. We must remove Export Control Regulations (already covered in Requirements). Remove Background Check details? Could be included in Requirements as a note. It's substantive; we can include as a bullet under Requirements. We must remove Equal Employment Opportunity, Affirmative Action, etc. Now craft HTML. Structure:

About the role

... paragraphs ...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

• ...
...

Pay

Base Pay Range for WA applicants is $99,201.00 - $138,880.35; other site ranges may differ.

We must not add extra sections. Now we need to extract precise content. Let's pull About the role text: combine first few paragraphs up to before responsibilities? Actually responsibilities start after "As part of a small team of engineers, you will develop reliability engineering processes..." That's part of responsibilities. So About the role could be everything before that: up to "Passion for our mission and vision is required."? Actually that sentence is also part of responsibilities? It says "We are looking for someone to apply their technical expertise, leadership skills, and dedication to quality to positively impact safe human spaceflight. Passion for our mission and vision is required." That's more like a requirement but could be part of About. We'll keep it in About. Thus About the role text: from "At Blue Origin, we envision millions..." through "Passion for our mission and vision is required." Let's copy that. We need to ensure we don't include the "Application Close Date" line. We'll drop it. Now Responsibilities: list of duties: - Develop reliability engineering processes and products for the design of launch vehicles, spacecraft, and supporting systems. - Work with systems engineering teams to verify compliance with safety and reliability requirements including verification by analysis or test. - Assess reliability allocations and trades. - Perform fault tree analysis. - Build reliability block diagrams. - Produce hazard analysis. - Perform failure modes and effects analysis (FMEA/FMECA). - Help engineers identify areas of opportunity for design improvements. - Minimize risk. - Increase the probability of mission success. - Apply technical expertise, leadership skills, and dedication to quality to positively impact safe human spaceflight. - Enjoy being challenged, working on multiple aspects of large systems, using all tools to tackle real problems limiting access to human spaceflight. (maybe incorporate as responsibility) We can combine some. Now Requirements (minimum): - Minimum of a B.S. degree in aerospace engineering or related field. - Experience with performing reliability analyses including Failure Modes, Effects and Criticality Analyses (FMECA), and Fault Tree Analysis (FTA). - Ability to read and interpret engineering drawings, fluid schematics, and electrical circuit diagrams. - Strong safety and mission assurance fundamentals. - Excellent written, verbal, and interpersonal skills, and ability to communicate technical information to non-technical partners. - Ability to form relationships with experts from varying engineering fields and provide constructive feedback about safety and reliability concerns. - Ability to earn trust, maintain positive and professional relationships, and contribute to our inclusive culture. - 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. - Background check required for all positions: Blue’s Standard Background Check (and possibly additional checks depending on role). We can include as bullet: "Successful completion of a standard background check; additional checks may apply based on role (e.g., DBIDS for military installation access, CMV driver requirements, Merchant Mariner Credential)." But we need to preserve all substantive info; we can include a concise bullet summarizing. Now Qualifications (preferred): - Experience developing reliability models of spacecraft, launch site and/or launch