Cleared Senior/Principal E&O Systems Engineer - FENG & Isolator Final Assembly and Test, Onsite

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 as heading. No Job ID etc. Remove boilerplate. We need to parse the posting and extract relevant content. Let's identify sections: - About Sandia: description of lab, benefits, flexible work arrangements, etc. Could be "About the role"? Actually "About Sandia" is about the organization. Could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading for description of role and maybe about Sandia? But "About the role" likely refers to description of the job. The posting includes "What Your Job Will Be Like" which is role description. Also "About Sandia" is company overview. Could be placed under "About the role"? Might be better to have "About the role" for the role description, and maybe include Sandia info there? But we could also have a separate "About Sandia" not in list; but instruction says use those headings as examples, not strict list? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings when appropriate. If we have content that matches those headings, we use them. If we have other content like "About Sandia", maybe we could still use "About the role" heading and include both Sandia overview and role description? Might be okay. But we need to preserve all substantive information. Let's extract: - Role description: "What Your Job Will Be Like" paragraph: The Neutron Generator Enterprise is seeking a Systems Engineer to support the implementation of Solumina software into production, replacing a portion of the existing Oracle-based production environment. This role focuses on the operational application of systems engineering principles to support production process execution, software testing, requirements management, risk management, verification and validation, logistics, deployment readiness, production planning, shipping coordination, and lifecycle documentation. On any given day you may be called on to: (list bullet points). Then bullet list of duties. - Responsibilities: likely the bullet list under "On any given day you may be called on to:" plus maybe other duties. - Requirements: "Qualifications We Require" bullet list. - Qualifications Desired: maybe "Qualifications We Desire" could be under Skills or Qualifications? Could be separate "Qualifications" heading for required, and "Skills" for desired? But we have both Required and Desired. Could combine under "Qualifications" for required, and "Skills" for desired. Or we could have "Requirements" for required, and "Qualifications" for desired? The instruction list includes both Requirements and Qualifications as separate possible headings. So we can use Requirements for mandatory qualifications, and Qualifications for desired qualifications. - Skills: maybe we can extract from desired qualifications: communication, coordination, problem-solving, etc. - Benefits: The posting mentions flexible work arrangements, generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance, amenities aimed at creating a solid work/life balance. Also mentions "These benefits vary by job classification." So we have benefits info. - Pay: Salary Range $102,400 - $199,700. - Schedule: flexible work arrangements for many positions include 9/80 and 4/10 compressed workweeks, part-time work, and telecommuting. So schedule info. We also have info about security clearance, etc. That could be under Requirements or Qualifications? It's a requirement: Active DOE Q-level security clearance. Also US citizenship requirement. Could be under Requirements. Also "Posting Duration" etc is boilerplate to remove. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we remove EEO paragraph, NNSA Requirements, Job ID, etc. Now produce HTML. Structure:

About the role

... (include Sandia overview and role description?)

But we might split: About the role could include the description of what the job will be like. Sandia overview could be placed there as well, but it's about the organization. Might be okay. Alternatively we could have a heading "About Sandia" but not in list; but instruction says use those headings as examples, not that we cannot use others. However to be safe, we can use "About the role" for the role description and maybe include Sandia overview in a preceding paragraph before any heading? But we need to output only HTML fragment; we can have multiple sections. Let's decide: Section About the role: includes paragraph describing Sandia and the role? Might be too mixed. Better: Use "About the role" for the role description (What Your Job Will Be Like). Then maybe we can have a preceding paragraph outside any heading? But instruction says use headings for sections; we could have a brief intro paragraph before first heading? Not prohibited. But we need to preserve all substantive info; we could include Sandia overview in a paragraph under "About the role" as well. Let's craft:

About the role

Sandia National Laboratories is the nation’s premier science and engineering lab for national security and technology innovation, with teams of specialists focused on cutting-edge work in a broad array of areas. Some of the main reasons we love our jobs: challenging work with amazing impact that contributes to security, peace, and freedom worldwide; extraordinary co-workers; some of the best tools, equipment, and research facilities in the world; career advancement and enrichment opportunities; flexible work arrangements for many positions include 9/80 (work 80 hours every two weeks, with every other Friday off) and 4/10 (work 4 ten-hour days each week) compressed workweeks, part-time work, and telecommuting (a mix of onsite work and working from home); generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance. World-changing technologies. Life-changing careers.

The Neutron Generator Enterprise is seeking a Systems Engineer to support the implementation of Solumina software into production, replacing a portion of the existing Oracle-based production environment. This role focuses on the operational application of systems engineering principles to support production process execution, software testing, requirements management, risk management, verification and validation, logistics, deployment readiness, production planning, shipping coordination, and lifecycle documentation.

Then Responsibilities: list bullet points from "On any given day you may be called on to:" plus maybe other duties like "Support production planning including shipping activities..." etc. Actually those are part of the bullet list. Let's extract bullet points: - Serve as the Neutron Generator Enterprise Oracle Subject Matter Expert, troubleshooting Oracle-related issues that affect production execution, planning, documentation, shipping, material movement, and shop-floor operations. - Work closely with production teams, systems engineers, software developers, process owners, planners, logistics personnel, and program leadership to ensure production systems are effectively configured, tested, verified, maintained, and aligned with operational requirements. - Translate existing Oracle-supported production workflows into future-state software capabilities while also sustaining current Oracle-based operations as needed. - Support production planning including shipping activities associated with the NG FENG and Final Assembly production floor. Coordinate with production planners, logistics teams, and floor personnel to support production schedules, shipping readiness, documentation accuracy, material flow, and the timely movement of completed or in-process hardware through required production and delivery steps. - Apply systems engineering practices to requirements management, risk management, verification and validation, logistics, deployment readiness, lifecycle documentation, and collection of objective evidence. We could also include earlier sentence: "This position requires an Oracle Subject Matter Expert who can provide deep technical and process knowledge of the current Oracle environment supporting the Neutron Generator Enterprise. The selected candidate must have extensive Oracle experience, strong production process knowledge, and the ability to troubleshoot Oracle-related issues that affect production execution, planning, documentation, shipping, and production floor operations." That seems more like a requirement. But we can keep responsibilities as the bullet list. Now Requirements (mandatory): - A Bachelor's degree in a relevant discipline and five (5) years of directly relevant experience, or an equivalent combination of directly relevant education and engineering or scientific experience that demonstrates the knowledge, skills, and ability to perform independent research and development. - Experience using Oracle systems. - Active DOE Q-level security clearance. - Working knowledge of systems engineering practices, including requirements management, risk management, verification and validation, configuration control, lifecycle documentation, and objective evidence collection. Also US citizenship implied by clearance; but we can mention "Applicants must be U.S. citizens to maintain DOE Q-level clearance." Might be part of requirements. Now Qualifications (desired): - Extensive Oracle knowledge, including the ability to serve as a Subject Matter Expert for production troubleshooting, workflow support, data integrity, reporting, and issue resolution within the Neutron Generator Enterprise. - Strong understanding of production processes, manufacturing workflows, shop-floor operations, material movement, production planning, shipping readiness, and documentation requirements. - Ability to support Solumina or similar production software implementation activities, including requirements translation, workflow validation, software testing, deployment support, and user/process transition from Oracle-based capabilities. - Demonstrated ability to develop and execute unique test scenarios, identify software defects or process gaps, troubleshoot complex data and workflow issues, and coordinate solutions with software developers, production personnel, planners, logistics teams, and process owners. - Working knowledge of systems engineering practices, including requirements management, risk management, verification and validation, configuration control, lifecycle documentation, and objective evidence collection. - Strong communication, coordination, and problem-solving skills, with the ability to work independently, support cross-functional teams, and escalate technical, production, planning, shipping, or programmatic concerns when needed. Now Skills: maybe we can extract communication, coordination, problem-solving etc. But those are already in desired qualifications. Could put them under Skills. But we might combine desired qualifications under Skills heading, and Qualifications for desired qualifications? Hmm. We already used Qualifications for desired; we could use Skills for communication etc. But we have overlapping. Better: Use Requirements for mandatory, Qualifications for desired (including both knowledge and skills). Then Skills maybe not needed. But we need to decide to include only sections with real content. If we put desired qualifications under Qualifications, we have content. Skills could be omitted. But we have also "Strong communication, coordination, and problem-solving skills" which is a skill. Could be part of Qualifications. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We'll omit Skills. Now Benefits: flexible work arrangements, generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance, amenities aimed at creating a solid work/life balance. Also note "These benefits vary by job classification." We'll include that. Pay: Salary Range $102,400 - $199,700. Also note that salary range is estimated, actual salary determined after consideration of experience, qualifications, and geographic differential. Schedule: flexible work arrangements for many positions include 9/80 and 4/10 compressed workweeks, part-time work, and telecommuting. We might also mention onsite requirement: "Due to the nature of work, successful candidate must be able to work onsite." That could be under Responsibilities or Requirements. It's a requirement: must be able to work onsite. We'll add to Requirements. Now produce HTML. Make sure to use

• for any list of duties/requirements/benefits. For prose use

  . We'll need to ensure we don't include any boilerplate like EEO, NNSA, Job ID, posting duration, security clearance details beyond requirement, etc. We'll keep security clearance as requirement. Now craft final HTML.