Reliability Engineer II

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No metadata like Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the job description. Key sections: - About the role: The initial paragraph about BAE Systems, mission, flexible work environment, etc. That's about the role/company. Could be "About the role" or "About BAE Systems". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have "About the role" with that intro. - Responsibilities: list of duties: "Work with a cross-functional team to ensure Reliability and Maintainability requirements are achieved." etc. Many repeated lines. Need to extract unique responsibilities. - Requirements: Required Education, Experience, & Skills: Bachelor’s degree in Electrical Engineering or related engineering/technical/scientific field and 2 or more years of relevant engineering experience within the Reliability Sciences disciplines. Also list of experience with certain tools etc. Those could be under Requirements or Qualifications. The instruction distinguishes Requirements and Qualifications; we can put education/experience under Requirements, and specific technical skills under Qualifications or Skills. But we need to follow typical pattern: Requirements often include education and experience; Qualifications may be preferred or additional. Skills separate. We have "Required Education, Experience, & Skills" block. Then "Preferred Education, Experience, & Skills". Then "Highly Desirable". Also "Pay Information". Also "Employee Benefits". Also schedule? Not mentioned explicitly; maybe full-time implied but not explicit schedule. So we should not create Schedule section unless stated. No schedule info. Thus sections: About the role, Responsibilities, Requirements (required), Qualifications (preferred), Skills (maybe technical skills?), Benefits, Pay. But we need to avoid thin sections. Let's decide: - About the role: intro paragraph. - Responsibilities: list of duties (unique). - Requirements: Required Education, Experience, & Skills (degree + 2 years experience). Could also include the list of specific experience items? Those are more like skills/qualifications. Might be better to put them under Qualifications (required skills). However the instruction: Use headings for Requirements, Qualifications, Skills. So we can separate: Requirements = education + experience; Qualifications = preferred education/experience; Skills = technical skills list (tools, methods). But we also have "Highly Desirable" which could be extra skills. We need to preserve all substantive info. So we must include all details. Let's extract: About the role text: "See what you’re missing. Our employees work on the world’s most advanced electronics – from detecting threats for F-35 pilots to illuminating the night for soldiers. Spanning air, land, sea, and space, we are developing the technology of tomorrow, delivered today. Drawing strength from our differences, we’re innovating for the future. And you can, too. Our flexible work environment provides you a chance to change the world without giving up your personal life. We put our customers first – exemplified by our mission: “We Protect Those Who Protect Us®.” Sound like a team you want to be a part of? Come build your career with BAE Systems. BAE Systems has a stimulating opportunity for an energetic well-qualified Reliability Engineer to join our team. You will work on teams developing and producing a variety of electronic equipment including Countermeasure & Electromagnetic Attack Solutions, providing unparalleled electronic warfare capabilities to enhance mission survivability. BAE Systems’ Reliability Engineers are involved with every stage of the equipment lifecycle from concept through development, Integration & Test, production and field support. You will have significant interaction across the company including program office, all engineering disciplines and production functions and this will provide for a fast-paced, educational, and fulfilling experience. Your efforts will have a positive impact on front line warfighter’s effectiveness and daily quality of life. We are seeking a Level II Reliability Engineer with an earned degree in a relevant engineering discipline to join our Reliability Science engineering team. You will have opportunities to apply your engineering skills and education to investigate digital and analog electronics, power supplies, and systems of electronic modules, to ensure Reliability, Availability, and Maintainability requirements are achieved. Your self-starting enthusiasm for technology, and ability to investigate and solve problems, will propel you to become an integral part of our innovative teams and influence product development." That's a lot; we can keep as paragraph(s). Might be too long but okay. Responsibilities: The bullet list after "In this Reliability Engineer position you will make impacts in the following ways;" then list items. Many duplicates. Let's extract unique responsibilities: - Work with a cross-functional team to ensure Reliability and Maintainability requirements are achieved. - Perform failure trend analysis, failure investigation and root cause analysis. - Coordinate failure analysis with vendors or failure analysis labs. - Prepare and review failure reports and FRACAS metrics for publication. - Present findings and conclusions with recommended corrective actions to both internal management as well as our customers. - Perform internal and external supplier interface to resolve reliability issues. - Perform Design-for Reliability and Maintainability including reliability and maintainability modeling and analysis and assessments requiring the full use and wide application of engineering theories, concepts and precedents. - Conduct research to provide solutions to a wide range of technical problems and proposals. - Make technical choices to improve the reliability & maintainability attributes of the equipment. - Plan and conduct a variety of reliability and maintainability tasks to meet reliability and maintainability goals. - Represent the Company at customer meetings as applicable. - Drive the Failure reporting, Analysis & Corrective Action System (FRACAS) process (duplicate). - Chair/Track the Failure Review Board activities. - Present R&M design and analysis against customer requirements at internal and customer design milestone reviews. - Responsibilities may involve supporting the design team to establish BIT functions, test interface requirements and diagnostic features. We need to deduplicate. Also "Drive the Failure reporting, Analysis & FRACAS process" same as earlier. Also "Perform failure trend analysis, failure investigation and root cause analysis." appears multiple times. We'll create a

• list of unique items. Requirements: Required Education, Experience, & Skills: Bachelor’s degree in Electrical Engineering or related engineering/technical/scientific field and 2 or more years of relevant engineering experience within the Reliability Sciences disciplines. We could also include that they seek Level II Reliability Engineer. But that's part of role. Qualifications: Preferred Education, Experience, & Skills: Knowledge and/or experience with the principles of electrical and/or mechanical design; Internship, Co-op or Research experience, preferably in a reliability engineering role; Demonstrate time and task management with great organizational skills; Awareness of MBSE (Magic Draw, SysML); Familiarity with industry standard practices such as Six Sigma, Lean Manufacturing, etc.; Ability to work in a fast-paced dynamic environment; Collaboration: You love working with a team and receiving input from others; Creativity: You love finding new and creative ways to solve problems. Also "Highly Desirable (these skills/experiences are not required but will set a candidate apart from the rest): Production, test and field reliability support, FRACAS and Root Cause Failure Analysis experience, Fault Tree Analysis, Failure Data Collection, vendor failure analysis, etc.; 8D Root Cause Corrective Action Training; Active development towards sharpening communication skills (i.e. Toastmasters)". This could be part of Qualifications or Skills. We'll treat as Qualifications (preferred) maybe combine. Skills: The list of specific technical skills from Required block: Experience with a few or several of the following: Perform Reliability, Availability & Maintainability (RAM) trade studies for the system design process; Experience using Reliability and Maintainability analysis and reliability growth software tools; experience / awareness using ReliaSoft, Relyence and/or PTC Windchill RR software tool; Define/allocate RAM requirements and assess RAM performance (MTBF, MTBCF, Ao); Perform Reliability Predictions and MTBF Modeling; Perform Failure Modes Effects Criticality Analysis (FMECA); Perform Testability Analysis; Perform Maintainability Analysis; Drive the Failure reporting, Analysis & Corrective Action System (FRACAS) process; Perform failure trend analysis, failure investigation and root cause analysis; Chair/Track the Failure Review Board activities; Present R&M design and analysis against customer requirements at internal and customer design milestone reviews; Responsibilities may involve supporting the design team to establish BIT functions, test interface requirements and diagnostic features. But many of these overlap with responsibilities. Might be better to put them under Skills. We need to avoid duplication but preserve all info. Could combine responsibilities and skills but risk missing. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep everything, but we can organize without duplication? If we duplicate same sentence in two sections, that's duplication but still preserving. Might be okay but better to avoid redundancy. However we must not invent or summarize away detail; we can keep each piece once. Thus we need to decide where each piece goes. Let's list all distinct pieces from the posting: 1. Intro/about company/mission/flexible work etc. (About the role) 2. Role description: stimulating opportunity for energetic well-qualified Reliability Engineer; work on teams developing/producing electronic equipment including Countermeasure & Electromagnetic Attack Solutions; involvement in lifecycle; interaction across company; fast-paced educational fulfilling experience; impact on warfighter effectiveness; seeking Level II Reliability Engineer with earned degree; opportunities to apply skills to investigate digital/analog electronics, power supplies, systems of electronic modules to ensure RAM requirements; self-starting enthusiasm for tech, ability to investigate/solve problems; become integral part of innovative teams and influence product development. (Could be part of About the role or Responsibilities? It's more about role.) But we already have About the role covering company; we could add role specifics there. Better to treat About the role as the introductory paragraphs up to "We are seeking a Level II Reliability Engineer..." That covers role. Then Responsibilities: the list after "In this Reliability Engineer position you will make impacts in the following ways;" plus maybe also the earlier "You will have opportunities to apply your engineering skills..." but that's more about opportunities; could be responsibilities as well. However to avoid duplication, we can keep that in About the role. Let's extract distinct responsibility items from the list (including those that also appear in skills list). We'll keep them under Responsibilities. Now Required Education, Experience, & Skills: Bachelor’s degree in Electrical Engineering or related engineering/technical/scientific field and 2 or more years of relevant engineering experience within the Reliability Sciences disciplines. Also maybe "Level II Reliability Engineer" is a requirement? Could be part of role. Preferred Education, Experience, & Skills: list. Highly Desirable: list. Pay Information: salary range and note. Employee Benefits: description. Now we need to output HTML with sections only if they have real specific content. Thus sections: - About the role (intro + role description) - Responsibilities (list) - Requirements (education + experience) - Qualifications (preferred + highly desirable) - Skills (technical skills list from required block) - Benefits - Pay Schedule: not present, omit. Now we need to ensure we don't include boilerplate like "This position will be posted for at least 5 calendar days..." etc. Remove. Also remove duplicated lines like repeated responsibility items. Let's craft. First, About the role: combine the introductory paragraphs up to "We are seeking a Level II Reliability Engineer..." plus maybe the sentence about opportunities to apply skills etc. But that could be responsibilities. Let's keep About the role as the company description and mission, flexible work, etc. The role-specific stimulating opportunity sentence could be part of Responsibilities? But it's more about the role. I'd include it in About the role to avoid missing. Thus About the role content: "See what you’re missing. Our employees work on the world’s most advanced electronics – from detecting threats for F-35 pilots to illuminating the night for soldiers. Spanning air, land, sea, and space, we are developing the technology of