Maritime Engineering SME

We need to output HTML fragment with sections: About the role? Actually we have "Position Overview" and "Why Join QinetiQ US?" etc. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content. We need to preserve all substantive info. We need to decide which sections to include: We have Position Overview (maybe "About the role"). We have Responsibilities (list). We have Required Qualifications (list). We have Preferred Qualifications (maybe under Qualifications or Skills). We have Pay Transparency (Pay). We have maybe Benefits? Not explicit benefits listed besides workplace flexibility, health and well-being, opportunities to work with purpose. That's in "Why Join QinetiQ US?" which could be Benefits? But we need to include Benefits only if posting actually states them. It does mention workplace flexibility, commitment to health and well-being, opportunities to work with purpose. That's benefits-ish. Could put under Benefits. Schedule not mentioned, so omit. Skills: maybe we can extract from required/preferred qualifications like strong technical writing, presentation, communication skills, ability to work in multidisciplinary teams, etc. Could put under Skills. But we must not repeat job title as heading. Also we must not include Job ID etc. We need to remove boilerplate: EEO statement, accessibility, etc. Also remove "Why Join QinetiQ US?" maybe we can incorporate into Benefits or About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. Thus: - About the role: Position Overview paragraph. - Responsibilities: list of duties (the bullet list after "Other duties include:" and the list under Responsibilities). We need to combine. - Requirements: maybe Required Qualifications? But we have separate Required Qualifications and Preferred Qualifications. Could put Required Qualifications under Requirements, and Preferred Qualifications under Qualifications? Or we could have Requirements for required, Qualifications for preferred. The instruction list includes Requirements and Qualifications as separate possible headings. So we can use Requirements for required qualifications, and Qualifications for preferred qualifications. - Skills: maybe we can extract skills like technical writing, presentation, communication, teamwork, etc. Could also include ability to interpret drawings, etc. But those are more qualifications. Might be okay to put under Skills. - Benefits: workplace flexibility, health and well-being, opportunities to work with purpose. - Pay: salary range $150,000 - $200,000 USD. - Schedule: not present, omit. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive info. Ensure we don't lose any details. Let's extract paragraphs. About the role: The Position Overview paragraph: "QinetiQ US is seeking a Maritime Systems Engineering Subject Matter Expert (SME) with extensive experience designing, developing and fielding Navy manned and unmanned surface and underwater systems. The successful candidate will provide technical leadership, systems engineering expertise, and lifecycle support for shipboard systems, working with government and industry stakeholders to support modernization, integration, sustainment, and engineering initiatives. This position requires a strong understanding of naval engineering principles, shipboard system integration, and the operational environment of U.S. Navy’s vessels. The SME will serve as a trusted technical advisor throughout the systems engineering lifecycle, ensuring engineering solutions meet mission, performance, and program objectives." We could also include the introductory paragraph about the company? That's not about the role but about company. Might be considered About the role? The instruction says About the role heading for section headings (e.g. About the role...). Could include company overview as part of About the role? Might be okay but we need to preserve all substantive info. The initial paragraph about the team etc. Could be considered company description, not role. Might be okay to include under About the role as context. But we must not invent headings. We could include it as part of About the role. Better: About the role includes both company overview and position overview. But we must not repeat job title as heading. Let's craft:

About the role

We are a world-class team of professionals who deliver next generation technology and products in robotic and autonomous platforms, ground, soldier, and maritime systems in 50+ locations world-wide. Much of our work contributes to innovative research in the fields of sensor science, signal processing, data fusion, artificial intelligence (AI), machine learning (ML), and augmented reality (AR). QinetiQ US’s dedicated experts in defense, aerospace, security, and related fields all work together to explore new ways of protecting the American Warfighter, Security Forces, and Allies. Being a part of QinetiQ US means being central to the safety and security of the world around us. Partnering with our customers, we help save lives; reduce risks to society; and maintain the global infrastructure on which we all depend.

QinetiQ US is seeking a Maritime Systems Engineering Subject Matter Expert (SME) with extensive experience designing, developing and fielding Navy manned and unmanned surface and underwater systems. The successful candidate will provide technical leadership, systems engineering expertise, and lifecycle support for shipboard systems, working with government and industry stakeholders to support modernization, integration, sustainment, and engineering initiatives. This position requires a strong understanding of naval engineering principles, shipboard system integration, and the operational environment of U.S. Navy’s vessels. The SME will serve as a trusted technical advisor throughout the systems engineering lifecycle, ensuring engineering solutions meet mission, performance, and program objectives.

Now Responsibilities: list after "Other duties include:" and the bullet list under Responsibilities. We need to capture all. Let's extract: Other duties include: Responsibilities Provide technical expertise on U.S. Navy systems from concept through to fielding. Support requirements development, systems architecture, interface definition, and engineering trade studies. Evaluate the integration of shipboard mechanical, electrical, combat, communication, navigation, propulsion, and auxiliary systems. Conduct engineering assessments, technical reviews, and design evaluations for modernization and sustainment efforts. Analyze system performance, identify technical risks, and recommend engineering solutions. Review engineering documentation, specifications, drawings, and technical data packages for completeness and compliance. Support configuration management, systems integration, verification, validation, and acceptance activities. Participate in design reviews, technical interchange meetings, and customer briefings. Collaborate with government personnel, shipyards, original equipment manufacturers, and multidisciplinary engineering teams. Develop technical reports, white papers, engineering analyses, and recommendations for proposals. Provide engineering support during installation planning, testing, and fleet introduction activities as required. Mentor junior engineers and contribute to technical best practices across the organization. We'll put each as

. Now Requirements (required qualifications): Required Qualifications Bachelor's degree in Systems Engineering, Mechanical Engineering, Electrical Engineering, Naval Architecture, Marine Engineering, or a related technical discipline. 9+ years of experience supporting U.S. Navy programs. Extensive experience designing, developing and fielding Navy manned and unmanned surface and underwater systems. Secret Clearance Required #qinetiqclearedjob Demonstrated expertise in systems engineering principles and processes. Experience with shipboard systems integration, modernization, or life-cycle sustainment. Ability to interpret engineering drawings, technical specifications, interface control documents, and systems documentation. Experience supporting engineering reviews, requirements analysis, and technical risk management. Strong technical writing, presentation, and communication skills. Ability to work effectively in multidisciplinary teams and customer-facing environments. We'll put as list. Now Qualifications (preferred qualifications): Preferred Qualifications Master's degree in an engineering or technical discipline. Experience supporting acquisition, modernization, or sustainment programs for U.S. Navy surface platforms. Familiarity with systems engineering frameworks and model-based systems engineering (MBSE) concepts. Experience with digital engineering tools and requirements management software. Experience supporting shipboard testing, installation, or certification activities. Active or previously held U.S. security clearance, if required by the program. Now Skills: maybe we can extract from required/preferred: strong technical writing, presentation, communication skills; ability to work effectively in multidisciplinary teams; ability to interpret drawings; etc. But those are already in qualifications. Could still create Skills section summarizing: technical writing, presentation, communication, teamwork, interpretation of engineering drawings, etc. However we risk duplication. The instruction says preserve ALL substantive information; not to invent or summarize away detail. Duplication is okay as long as we don't lose info. But we should avoid creating thin sections. Perhaps we can omit Skills section and put those skills under Qualifications or Requirements. But we have both Requirements and Qualifications already. The instruction list includes Skills as optional heading. We could decide not to include Skills if content is covered elsewhere. However we might lose some nuance like "Strong technical writing, presentation, and communication skills." That's already in Required Qualifications. So it's covered. Thus we can omit Skills. Benefits: from "Why Join QinetiQ US?" paragraph: "If you have the courage to take on a wide variety of complex challenges, then you will experience a unique working environment where innovative teams blend different perspectives, disciplines, and technologies to discover new ways of solving complex problems. In our diverse and inclusive environment, you can be authentic, feel valued, be respected, and realize your full potential. QinetiQ US will support you with workplace flexibility, a commitment to the health and well-being of you and your family and provide opportunities to work with a purpose. We are committed to supporting your success in both your professional and personal lives." We can extract benefits: workplace flexibility, commitment to health and well-being of you and your family, opportunities to work with a purpose, diverse and inclusive environment, ability to be authentic, feel valued, respected, realize full potential, support for success professionally and personally. We'll put as list. Pay: salary range $150,000 - $200,000 USD. Now we need to output only HTML fragment, no markdown fences. Let's construct. Be careful to not include any boilerplate like EEO statement, accessibility, etc. Remove those. Also remove "Pay Transparency" heading maybe we just use

Pay

and then paragraph. Also remove "#qinetiqclearedjob" maybe keep as part of text? It's a tag; we can keep but it's minor metadata. Could drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. This is a tag, we can drop. Now produce final HTML. Let's write:

About the role

We are a world-class team of professionals who deliver next generation technology and products in robotic and autonomous platforms, ground, soldier, and maritime systems in 50+ locations world-wide. Much of our work contributes to innovative research in the fields of sensor science, signal processing, data fusion, artificial intelligence (AI), machine learning (ML), and augmented reality (AR). QinetiQ US’s dedicated experts in defense, aerospace, security, and related fields all work together to explore new ways of protecting the American Warfighter, Security Forces, and Allies. Being a part of QinetiQ US means being central to the safety and security of the world around us. Partnering with our customers, we help save lives; reduce risks to society; and maintain the global infrastructure on which we all depend.

QinetiQ US is seeking a Maritime Systems Engineering Subject Matter Expert (SME) with extensive experience designing, developing and fielding Navy manned and unmanned surface and underwater systems. The successful candidate will provide technical leadership, systems engineering expertise, and lifecycle support for shipboard systems, working with government and industry stakeholders to support modernization, integration, sustainment, and engineering initiatives. This position requires a strong understanding of naval engineering principles, shipboard system integration, and the operational environment of U.S. Navy’s vessels. The SME will serve as a trusted technical advisor throughout the systems engineering lifecycle, ensuring engineering solutions meet mission,