Senior/Principal R&D Systems Engineer - Code Management System, Onsite

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. We need to parse the posting. Key content: - About Sandia (intro) maybe not needed? The instruction: "About Sandia" is not a required heading; we can include as a paragraph maybe under "About the role"? But we have to decide sections. We have sections: - About the role: description of what the job will be like, tasks, etc. Could include "What Your Job Will Be Like" and "On Any Given Day, You May ..." plus "This position will requires occasional travel..." etc. - Responsibilities: maybe the bullet list of duties: "Elicit, define, decompose, allocate, trace, and manage system and component requirements", etc. - Requirements: maybe "Qualifications We Require" (Bachelor's degree + 5 years experience, ability to obtain Q clearance). Also "Due to the nature of the work, the selected applicant must be able to work onsite 100% of the time." Could be part of requirements. - Qualifications: maybe "Qualifications We Desire" (graduate degree, experience with NSE labs, etc.) plus the list of desired experience. - Skills: maybe the specific skill areas: "Requirements development and management", "System architecture, design, and development", "MBSE methods and practical tool use", "Experience with the 6.x process", "Strategic planning", "Ability to learn new tools/processes quickly", "Leadership experience guiding junior staff, influencing senior technical staff, and engaging management", "Track record of leading systems engineering activities within a technical domain". Also "Strong verbal and written communication skills, ability to work effectively in multidisciplinary teams." - Benefits: The posting mentions "Generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance". Also "Flexible work arrangements for many positions include 9/80 ... compressed workweeks, part-time work, and telecommuting". Also "These benefits vary by job classification." So we have benefits content. - Pay: Salary Range $117,500 - $235,700. - Schedule: maybe "Flexible work arrangements ... 9/80 ... 4/10 ... compressed workweeks, part-time work, and telecommuting". Also "Due to the nature of the work, the selected applicant must be able to work onsite 100% of the time." That's schedule/location requirement. Could be under Schedule. We need to avoid boilerplate like EEO, security clearance details? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO paragraph, security clearance details? However security clearance is a qualification (must obtain Q-level). That's substantive. The details about drug test, background, etc. might be considered boilerplate? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Security clearance details might be considered legal? But the requirement to obtain Q-level is a qualification; we can keep that as part of Qualifications. The rest about drug test, background investigation, etc. maybe we can drop as boilerplate. Also "Posting Duration" etc. can be dropped. "Job ID" etc dropped. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the substance: the description of work, responsibilities, qualifications, desired qualifications, skills, benefits, pay, schedule. We must not create sections with filler like "commensurate with experience". We have actual content. We need to output only HTML fragment, no html/body tags, no markdown fences. We'll structure:

About the role

...

Maybe we can combine the introductory paragraph about Sandia as part of About the role? But the instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings. Thus:

About the role

Sandia National Laboratories is seeking an experienced R&D Systems Engineer to join the Code Management System (CMS) team. CMS is used by the Department of Defense (DoD) and the Department of Energy (DOE) to manage Permissive Action Link (PAL) codes and keys and to support critical nuclear weapon operations (e.g., recode/rekey, Limited Life Component Exchange (LLCE), training, deployment readiness, and assembly/disassembly). The system helps ensure authorized use and prevents unauthorized use of air-delivered weapons. In this role, you'll work across the full systems engineering lifecycle, with an initial emphasis on requirements engineering, CONOPS development, and system design. You'll also help shape the strategic direction of the program, building a vision and a practical roadmap to deliver it. This position will require occasional travel to support the mission. Due to the nature of the work, the selected applicant must be able to work onsite 100% of the time.

Then Responsibilities:

Responsibilities

• Elicit, define, decompose, allocate, trace, and manage system and component requirements
• Apply core systems engineering principles to deliver mission-driven outcomes
• Partner closely with domain experts and fellow systems engineers
• Identify, document, and elevate risks and issues that could impact mission execution
• Balance multiple priorities and adapt quickly as technical and program needs evolve
• Build and communicate a roadmap aligned to a long-term strategic vision
• Integrate Model-Based Systems Engineering (MBSE) approaches and tools into day-to-day engineering
• Operate effectively both independently and in a collaborative team environment across multiple sites

Requirements (Qualifications We Require):

Requirements

• 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.
• Ability to obtain and maintain a DOE Q-level security clearance.

Qualifications (Qualifications We Desire):

Qualifications

• 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.

Skills: maybe we separate the desired skill list. But we already included some skills in Qualifications. However the instruction says we can have Skills section separate. The posting also lists "Also, for this posting we are seeking individuals with 2+ years of experience in the following areas:" then a list. Those are skills/experience. Thus we can have a Skills section:

Skills

• Requirements development and management (elicitation through verification/traceability)
• System architecture, design, and development
• MBSE methods and practical tool use (e.g., MagicDraw/Cameo or similar)
• Experience with the 6.x process
• Strategic planning: defining a vision and building a roadmap to achieve it
• Ability to learn new tools/processes quickly and execute within defined engineering frameworks
• Leadership experience guiding junior staff, influencing senior technical staff, and engaging management
• Track record of leading systems engineering activities within a technical domain

Benefits:

Benefits

• Generous vacation
• Strong medical and other benefits
• Competitive 401k
• Learning opportunities
• Relocation assistance
• Amenities aimed at creating a solid work/life balance
• 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)

Pay:

Pay

Salary Range $117,500 - $235,700

Schedule: We have schedule info: flexible work arrangements already in Benefits; also requirement to work onsite 100% of the time. Could be separate Schedule section: maybe mention onsite requirement and occasional travel. Thus:

Schedule

Occasional travel required; must be able to work onsite 100% of the time.

We should not duplicate the flexible work arrangements in both Benefits and Schedule; but we already placed flexible work arrangements under Benefits. That's okay. Check for any duplicated lines: we have not repeated. Check for boilerplate removed: we removed EEO, security clearance details beyond ability to obtain Q-level, posting duration, job ID, etc. Check for any invented content: none. Check for any missing substantive info: The "About Sandia" intro paragraph about Sandia's mission etc. Might be considered substantive but not under any heading. Could we include it as a paragraph before About the role? The instruction says we should not repeat job title as heading, but we can have introductory paragraphs. It's okay to have a leading paragraph before first heading. The content about Sandia's mission is substantive; we should preserve it. So we can put a

at the start. Thus output:

About Sandia 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. Learn more about Sandia at: http://www.sandia.gov These benefits vary by job classification.

But note that we already used flexible work arrangements and benefits in Benefits section; we might be duplicating. The instruction says preserve ALL substantive information; we can keep it in intro but then also in Benefits section leads to duplication. However duplication is allowed? The instruction says remove duplicated lines. So we should avoid duplicating the same content. The intro includes a lot of benefits info that we also placed in Benefits section. To avoid duplication, we could either keep the intro brief about Sandia's mission without repeating benefits,