Early - Mid Career R&D Systems Engineer - Surety Systems Engineering, Onsite

We need to output HTML fragment with sections: About the role? Actually we need to reformat job posting into clean semantic HTML. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting and decide which sections to include. We have content: - About Sandia (intro about organization). Might be "About the role"? Actually "About Sandia" is about the organization, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have "What Your Job Will Be Like" which is responsibilities. So we can have

Responsibilities

with list of duties. We have "Qualifications We Require" and "Qualifications We Desire". Those are qualifications. Could combine into Requirements/Qualifications sections. The instruction says we can have Requirements and Qualifications separate, but we can combine if thin. Prefer few substantive sections. So maybe one

Qualifications

containing both required and desired. We have "About Our Team" which could be "About the role"? Actually about team maybe not needed. Could be omitted or put under About the role? The instruction says About the role heading for section about the role. Could include description of team and role context. But we already have responsibilities. Might include "About the role" summarizing what the role entails (maybe the first paragraph about what the SSE does). However we have "What Your Job Will Be Like" which is responsibilities. The "About Sandia" is about organization, not role. Could be omitted as boilerplate? It's not exactly boilerplate but it's general about Sandia. Might be considered not needed for role specifics. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Sandia is not those, but it's generic. However we need to preserve ALL substantive information. So we should keep it but maybe under a heading like "About Sandia"? But allowed headings are limited to those list. Could we use

About the role

and include both About Sandia and What Your Job Will Be Like? That might be okay. But we need to avoid filler. We also have Salary Range $102,400 - $199,700. That's Pay. So we need a Pay section. We have benefits: "Flexible work arrangements for many positions include 9/80 ... and 4/10 ... compressed workweeks, part-time work, and telecommuting ... Generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance". Also "These benefits vary by job classification." So we have benefits info. So we need Benefits section. Schedule: The flexible work arrangements mention 9/80 and 4/10 compressed workweeks, part-time, telecommuting. That's schedule info. Could be under Schedule section. But we already have benefits includes flexible work arrangements. Might combine? The instruction says prefer few substantive sections over many thin ones. So we could have Benefits section that includes both benefits and schedule info. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule info (flexible work arrangements). So we could have a Schedule section. But we could also put schedule under Benefits. However they said prefer few sections; maybe combine Benefits and Schedule into one Benefits section that includes both. But the heading list includes Benefits, Pay, Schedule separate. If we combine, we would have only Benefits heading, but schedule info would be inside Benefits. That's okay as long as we don't create a Schedule heading with empty or placeholder. So we can omit Schedule heading. We also have Posting Duration, Security Clearance, EEO, NNSA Requirements, etc. Those are boilerplate/legal; we should remove them. Also Job ID etc drop. Thus final HTML: maybe sections: About the role (including About Sandia and role description), Responsibilities (duties list), Qualifications (required and desired), Benefits (including flexible work arrangements, vacation, medical, 401k, learning, relocation, etc), Pay (salary range). Possibly also Skills? Not explicitly listed; we have desired qualifications includes skills like communication, teamwork, etc. Could be under Qualifications. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus we need to convert paragraphs to

  . For lists, we need to detect bullet-like sentences. The responsibilities section has many bullet-like sentences starting with "¿" or "Apply technical judgment...". Actually the posting uses "¿" as bullet? It shows "¿ On any given day you may be called on to:" then list items each starting with "¿". Also there are "¿¿" double bullet? We'll treat each line after the colon as a list item. We need to extract all responsibilities items. Let's parse responsibilities section: "What Your Job Will Be Like The 2910/2920 ¿ Surety Systems Engineer (SSE) develops, implements, and maintains strategies to lead the R&D project team in successful product qualification and delivery. SSEs interface across multiple enterprises, integrating all team members in relevant multidisciplinary technology areas. They exercise critical thinking to identify, assess, and mitigate risks through the practical application of defect prevention to develop a safe, reliable, and robust product. SSEs provide critical R&D contributions throughout the entire product realization lifecycle; these contributions include requirements engineering and traceability, validation and verification (V&V), supply chain risk management/assessment, and crucial technical documentation. ¿¿ ¿ Projects span across all phases of the product realization lifecycle from conceptual design and development, production, maintenance, and retirement. Projects include components, subsystems, and systems. Opportunities exist in Albuquerque, NM. Some domestic travel is required to support business needs. ¿ On any given day you may be called on to: Apply technical judgment using advanced engineering principles, analysis, and prevention-based methods to recognize and formulate innovative solutions for a wide variety of technical challenges related to electrical engineering, mechanical engineering, software engineering, computer science, and materials science in support of product realization. ¿ Collaborate with R&D teams to cultivate independent, necessary, feasible, unambiguous (to include tolerances), and verifiable system requirements; aid teams in ensuring the design meets performance requirements. ¿ Lead research and development teams in identifying and transforming unknown technical challenges into known technical risks to ensure and improve the safety, security, and reliability of the product. ¿ Determine and manage critical design and production parameters; identify manufacturing activities that affect product performance. ¿ Work with multidisciplinary teams to develop verification methods for complex requirements, often from a combination of analysis and simulated environmental testing. ¿ Interface with NNSA design agency and the production agency to ensure design for manufacturability and mitigate risks and defects early on. ¿ Author analyses, requirements traceability reports, verification/validation plans, qualification plans, and essential engineering authorizations that ensure the product fully meets its requirements and design intent. ¿ Lead drawing reviews and contribute to design reviews for the project team, ensuring requirements have been successfully integrated into the design definition. ¿¿ Use scientific methods to identify issues and risks and formulate well-constructed engineering solutions, collect data through observation and experimentation, and develop and test hypotheses; anticipate, innovate, and deliver technical solutions. ¿ Independently assess supply chain risk management activities and adversarial threats relevant to a specific component, subsystem, system, or program; lead colleagues in developing mitigation and protection plans; advise management on formulated technical solutions. ¿ Apply systems engineering principles to research, design, and develop experiments and processes to demonstrate that the product meets design intent, or to predict its behavior under intended operating conditions. ¿ Lead project teams through the corrective action process ¿ Use statistical knowledge to understand production feasibility, capabilities, or processes; use physical and computational simulation, analysis, and evaluation as verification." We need to extract list items after "On any given day you may be called on to:" and also maybe earlier sentences are prose. Simplify: We'll create a

  for the introductory prose up to the colon, then a

  for the list items. List items (each preceded by ¿ ): - Apply technical judgment using advanced engineering principles, analysis, and prevention-based methods to recognize and formulate innovative solutions for a wide variety of technical challenges related to electrical engineering, mechanical engineering, software engineering, computer science, and materials science in support of product realization. - Collaborate with R&D teams to cultivate independent, necessary, feasible, unambiguous (to include tolerances), and verifiable system requirements; aid teams in ensuring the design meets performance requirements. - Lead research and development teams in identifying and transforming unknown technical challenges into known technical risks to ensure and improve the safety, security, and reliability of the product. - Determine and manage critical design and production parameters; identify manufacturing activities that affect product performance. - Work with multidisciplinary teams to develop verification methods for complex requirements, often from a combination of analysis and simulated environmental testing. - Interface with NNSA design agency and the production agency to ensure design for manufacturability and mitigate risks and defects early on. - Author analyses, requirements traceability reports, verification/validation plans, qualification plans, and essential engineering authorizations that ensure the product fully meets its requirements and design intent. - Lead drawing reviews and contribute to design reviews for the project team, ensuring requirements have been successfully integrated into the design definition. - Use scientific methods to identify issues and risks and formulate well-constructed engineering solutions, collect data through observation and experimentation, and develop and test hypotheses; anticipate, innovate, and deliver technical solutions. - Independently assess supply chain risk management activities and adversarial threats relevant to a specific component, subsystem, system, or program; lead colleagues in developing mitigation and protection plans; advise management on formulated technical solutions. - Apply systems engineering principles to research, design, and develop experiments and processes to demonstrate that the product meets design intent, or to predict its behavior under intended operating conditions. - Lead project teams through the corrective action process - Use statistical knowledge to understand production feasibility, capabilities, or processes; use physical and computational simulation, analysis, and evaluation as verification. Note there is a stray "¿¿" before some items; we ignore. Now Qualifications: "We Require A Bachelor's degree in a relevant discipline, 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. Ability to obtain and maintain a DOE Q- level security clearance" "We Desire The ideal R&D S&E Systems Engineer candidate for Sandia National Laboratories will in addition possess the following: Graduate degree in Engineering or a highly related field where an independent research project was a graduation requirement (e.g., independent project, thesis, or dissertation).Experience working with Nuclear Security Enterprise (NSE) laboratories and plants including Pantex, Kansas City National Security Campus (KCNSC), Lawrence Livermore National Laboratory (LLNL), Los Alamos National Laboratory (LANL), and Kansas City National Security Campus/New Mexico Operations (KCNSC/NMO).Experience working on engineering design, qualification, production, or related modeling/simulation projects.Strong verbal and written communication skills, ability to work effectively in multidisciplinary teams. Also, for this