Cleared Senior/Principal E&O Systems Engineer - Configuration Management Implementation Lead, Hybrid
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists,
for prose
3. Do NOT repeat job title as heading
4. Do NOT put Job ID/requisition numbers as headings - fold into short
or drop
5. Preserve ALL substantive information
6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
7. Include section ONLY when posting has real specific content - never emit heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless posting actually states them
9. Prefer few substantive sections over many thin ones
10. Output ONLY HTML fragment - no /, no markdown code fences
Let me analyze the content:
The posting has:
- "About Sandia" - company description
- "What Your Job Will Be Like" - role description and daily duties
- "Salary Range" - $102,400 - $199,700 with details
- "Qualifications We Require" - required qualifications
- "Qualifications We Desire" - desired qualifications
- "About Our Team" - team description
- "Posting Duration" - administrative info
- "Security Clearance" - clearance requirements
- "EEO" - boilerplate
- "NNSA Requirements For MedPEDs" - specific requirement
- Job ID, Job Family, Regular/Temporary, Full/Part-Time - metadata
I need to structure this into semantic sections. Let me map:
- About the role / About the company: "About Sandia" and "What Your Job Will Be Like" (the role description part)
- Responsibilities: the "On any given day, you may be called on to:" list
- Requirements/Qualifications: "Qualifications We Require" and "Qualifications We Desire"
- Benefits: "About Sandia" mentions benefits (flexible work arrangements, vacation, medical, 401k, etc.) - but note it says "These benefits vary by job classification." Should I include? The rule says never create Benefits section unless posting actually states them. It does state some benefits. I'll include a Benefits section with what's mentioned.
- Pay: Salary Range is explicitly stated - include Pay section
- Schedule: mentions flexible work arrangements (9/80, 4/10, part-time, telecommuting) - include Schedule section
- Security Clearance: explicit section
- Team: "About Our Team" - could be "About the team" section
Job ID and other metadata: fold into a short
or drop. I'll include a brief metadata paragraph at the end.
EEO and NNSA MedPEDs: EEO is boilerplate, but NNSA MedPEDs is specific to this job. I'll include NNSA MedPEDs as part of Security Clearance or separate section? It's a specific requirement. Could be under "Security Clearance" or "Additional Requirements". I'll include it as a subsection or separate section.
Posting Duration: administrative, maybe drop or include in metadata.
Let me structure:
About the role
Company description and role overview
Responsibilities
- ...
Qualifications
Required
- ...
Desired
- ...
Benefits
- ...
Pay
Salary range...
Schedule
Flexible work arrangements...
Security clearance
DOE Q clearance required...
MedPED requirements...
About the team
Team description...
Job ID: 699393 | Job Family: EN | Regular/Temporary: R | Full/Part-Time: F
But note: the rules say use for section headings. Should I use for subsections? The rules only mention for section headings. It doesn't forbid , but to be safe, maybe keep all top-level as and use
or
for subsections. However, "Required" and "Desired" are subsections of Qualifications. I could make them separate sections: "Required qualifications" and "Desired qualifications". That might be better.
Also, "About the role" and "About the team" are both "About" sections. Could combine? But they are distinct: one about company/role, one about team. I'll keep separate.
Now, let's extract content precisely.
From "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."
From "What Your Job Will Be Like":
"We are seeking an Engineering and Operations (E&O) Systems Engineer / Configuration Management (CM) Lead to support configuration management activities for the 02232 ND CM Department. In this role, you will work at the systems level with ND systems teams and product realization teams to ensure configuration management requirements are implemented effectively across the product lifecycle. In this role, you will apply expertise in engineering data architecture, change control, high-fidelity technical data package reporting, and the ND systems lifecycle, including the Phase X/6.x process, milestones, and deliverables. You will also support Product Realization Integrated Digital Enterprise (PRIDE) efforts to advance common digital engineering workflows, improve traceability, strengthen digital thread capabilities, and enhance cross-site collaboration across programs."
Then "On any given day, you may be called on to:" list of 9 bullet points.
Salary Range: "$102,400 - $199,700 Salary range is estimated, and actual salary will be determined after consideration of the selected candidate's experience and qualifications, and application of any approved geographic salary differential."
Qualifications We Require: 5 bullet points (including degree+experience, experience areas, PDMLink knowledge, ND programs experience, DOE Q clearance)
Qualifications We Desire: 11 bullet points.
About Our Team: "ND Configuration Management (CM), Org 02232, is comprised of Engineering and Operations (E&O) Systems Engineers (SE) enabling and governing configuration management across ND programs by delivering standardized tools, processes, and expertise that ensure accurate product definition, ease of accessibility and collaboration, traceability, data integrity, and long-term sustainability of engineering data and decisions providing a reliable digital thread across the full product lifecycle. Configuration Management (CM) is a critical aspect of Systems Engineering (SE) that establishes an engineered infrastructure to ensure long-term data integrity throughout the product lifecycle, meet existing policies, and build confidence in the system as it matures."
Posting Duration: administrative, drop.
Security Clearance: "Position requires a Department of Energy (DOE) Q security clearance to start, or equivalent active security clearance with another U.S. government agency (e.g., DOD). Sandia is required by DOE directive to conduct a pre-employment drug test and background review that includes checks of personal references, credit, law enforcement records, and employment/education verifications. Applicants for employment need to be able to maintain a DOE Q-level security clearance, which requires U.S. citizenship. If you hold more than one citizenship (i.e., of the U.S. and another country), your ability to obtain a security clearance may be impacted. Applicants offered employment with Sandia are subject to a federal background investigation to meet the requirements for access to classified information or matter if the duties of the position require a DOE security clearance. Substance abuse or illegal drug use, falsification of information, criminal activity, serious misconduct or other indicators of untrustworthiness can cause a clearance to be denied or terminated by DOE, resulting in the inability to perform the duties assigned and subsequent termination of employment."
EEO: boilerplate, drop.
NNSA Requirements For MedPEDs: "If you have a Medical Portable Electronic Device (MedPED), such as a pacemaker, defibrillator, drug-releasing pump, hearing aids, or diagnostic equipment and other equipment for measuring, monitoring, and recording body functions such as heartbeat and brain waves, if employed by Sandia National Laboratories you may be required to comply with NNSA security requirements for MedPEDs. If you have a MedPED and you are selected for an on-site interview at Sandia National Laboratories, there may be additional steps necessary to ensure compliance with NNSA security requirements prior to the interview date."
Job metadata: Job ID: 699393, Job Family: EN, Regular/Temporary Position: R, Full/Part-Time Status: F.
Now, I need to produce HTML fragment.
I'll write:
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.
We are seeking an Engineering and Operations (E&O) Systems Engineer / Configuration Management (CM) Lead to support configuration management activities for the 02232 ND CM Department. In this role, you will work at the systems level with ND systems teams and product realization teams to ensure configuration management requirements are implemented effectively across the product lifecycle. You will apply expertise in engineering data architecture, change control, high-fidelity technical data package reporting, and the ND systems lifecycle, including the Phase X/6.x process, milestones, and deliverables. You will also support Product Realization Integrated Digital Enterprise (PRIDE) efforts to advance common digital engineering workflows, improve traceability, strengthen digital thread capabilities, and enhance cross-site collaboration across programs.
Responsibilities
- Partner with cross-functional teams, including engineering, project management, and test/qualification, to champion configuration management best practices, improve implementation, identify process improvements, and align efforts with project and enterprise priorities.
- Support technical teams in defining and managing product configuration, including as-designed and as-built baselines, product structures, configuration status accounting, and product and document traceability throughout the lifecycle.
- Perform administrative, physical, and functional configuration audits, and support quality assessments to ensure compliance with federal, corporate, and contractual requirements.
- Help define and document configuration management policies, processes, tools, and plans that establish a consistent framework aligned with digital engineering, continuous improvement, and enterprise objectives.
- Contribute to enterprise product data management by supporting implementation of product structures and authoritative data sources for requirements and configuration information.
- Provide guidance on configuration
for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings - fold into short
or drop 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include section ONLY when posting has real specific content - never emit heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless posting actually states them 9. Prefer few substantive sections over many thin ones 10. Output ONLY HTML fragment - no /, no markdown code fences Let me analyze the content: The posting has: - "About Sandia" - company description - "What Your Job Will Be Like" - role description and daily duties - "Salary Range" - $102,400 - $199,700 with details - "Qualifications We Require" - required qualifications - "Qualifications We Desire" - desired qualifications - "About Our Team" - team description - "Posting Duration" - administrative info - "Security Clearance" - clearance requirements - "EEO" - boilerplate - "NNSA Requirements For MedPEDs" - specific requirement - Job ID, Job Family, Regular/Temporary, Full/Part-Time - metadata I need to structure this into semantic sections. Let me map: - About the role / About the company: "About Sandia" and "What Your Job Will Be Like" (the role description part) - Responsibilities: the "On any given day, you may be called on to:" list - Requirements/Qualifications: "Qualifications We Require" and "Qualifications We Desire" - Benefits: "About Sandia" mentions benefits (flexible work arrangements, vacation, medical, 401k, etc.) - but note it says "These benefits vary by job classification." Should I include? The rule says never create Benefits section unless posting actually states them. It does state some benefits. I'll include a Benefits section with what's mentioned. - Pay: Salary Range is explicitly stated - include Pay section - Schedule: mentions flexible work arrangements (9/80, 4/10, part-time, telecommuting) - include Schedule section - Security Clearance: explicit section - Team: "About Our Team" - could be "About the team" section Job ID and other metadata: fold into a short
or drop. I'll include a brief metadata paragraph at the end. EEO and NNSA MedPEDs: EEO is boilerplate, but NNSA MedPEDs is specific to this job. I'll include NNSA MedPEDs as part of Security Clearance or separate section? It's a specific requirement. Could be under "Security Clearance" or "Additional Requirements". I'll include it as a subsection or separate section. Posting Duration: administrative, maybe drop or include in metadata. Let me structure:
About the role
Company description and role overview
Responsibilities
- ...
Qualifications
Required
- ...
Desired
- ...
Benefits
- ...
Pay
Salary range...
Schedule
Flexible work arrangements...
Security clearance
DOE Q clearance required...
MedPED requirements...
About the team
Team description...
Job ID: 699393 | Job Family: EN | Regular/Temporary: R | Full/Part-Time: F
But note: the rules say use for section headings. Should I use for subsections? The rules only mention for section headings. It doesn't forbid , but to be safe, maybe keep all top-level as and use
for section headings. It doesn't forbid , but to be safe, maybe keep all top-level as and use
and use
or
- for subsections. However, "Required" and "Desired" are subsections of Qualifications. I could make them separate
- Partner with cross-functional teams, including engineering, project management, and test/qualification, to champion configuration management best practices, improve implementation, identify process improvements, and align efforts with project and enterprise priorities.
- Support technical teams in defining and managing product configuration, including as-designed and as-built baselines, product structures, configuration status accounting, and product and document traceability throughout the lifecycle.
- Perform administrative, physical, and functional configuration audits, and support quality assessments to ensure compliance with federal, corporate, and contractual requirements.
- Help define and document configuration management policies, processes, tools, and plans that establish a consistent framework aligned with digital engineering, continuous improvement, and enterprise objectives.
- Contribute to enterprise product data management by supporting implementation of product structures and authoritative data sources for requirements and configuration information.
- Provide guidance on configuration
sections: "Required qualifications" and "Desired qualifications". That might be better.
Also, "About the role" and "About the team" are both "About" sections. Could combine? But they are distinct: one about company/role, one about team. I'll keep separate.
Now, let's extract content precisely.
From "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."
From "What Your Job Will Be Like":
"We are seeking an Engineering and Operations (E&O) Systems Engineer / Configuration Management (CM) Lead to support configuration management activities for the 02232 ND CM Department. In this role, you will work at the systems level with ND systems teams and product realization teams to ensure configuration management requirements are implemented effectively across the product lifecycle. In this role, you will apply expertise in engineering data architecture, change control, high-fidelity technical data package reporting, and the ND systems lifecycle, including the Phase X/6.x process, milestones, and deliverables. You will also support Product Realization Integrated Digital Enterprise (PRIDE) efforts to advance common digital engineering workflows, improve traceability, strengthen digital thread capabilities, and enhance cross-site collaboration across programs."
Then "On any given day, you may be called on to:" list of 9 bullet points.
Salary Range: "$102,400 - $199,700 Salary range is estimated, and actual salary will be determined after consideration of the selected candidate's experience and qualifications, and application of any approved geographic salary differential."
Qualifications We Require: 5 bullet points (including degree+experience, experience areas, PDMLink knowledge, ND programs experience, DOE Q clearance)
Qualifications We Desire: 11 bullet points.
About Our Team: "ND Configuration Management (CM), Org 02232, is comprised of Engineering and Operations (E&O) Systems Engineers (SE) enabling and governing configuration management across ND programs by delivering standardized tools, processes, and expertise that ensure accurate product definition, ease of accessibility and collaboration, traceability, data integrity, and long-term sustainability of engineering data and decisions providing a reliable digital thread across the full product lifecycle. Configuration Management (CM) is a critical aspect of Systems Engineering (SE) that establishes an engineered infrastructure to ensure long-term data integrity throughout the product lifecycle, meet existing policies, and build confidence in the system as it matures."
Posting Duration: administrative, drop.
Security Clearance: "Position requires a Department of Energy (DOE) Q security clearance to start, or equivalent active security clearance with another U.S. government agency (e.g., DOD). Sandia is required by DOE directive to conduct a pre-employment drug test and background review that includes checks of personal references, credit, law enforcement records, and employment/education verifications. Applicants for employment need to be able to maintain a DOE Q-level security clearance, which requires U.S. citizenship. If you hold more than one citizenship (i.e., of the U.S. and another country), your ability to obtain a security clearance may be impacted. Applicants offered employment with Sandia are subject to a federal background investigation to meet the requirements for access to classified information or matter if the duties of the position require a DOE security clearance. Substance abuse or illegal drug use, falsification of information, criminal activity, serious misconduct or other indicators of untrustworthiness can cause a clearance to be denied or terminated by DOE, resulting in the inability to perform the duties assigned and subsequent termination of employment."
EEO: boilerplate, drop.
NNSA Requirements For MedPEDs: "If you have a Medical Portable Electronic Device (MedPED), such as a pacemaker, defibrillator, drug-releasing pump, hearing aids, or diagnostic equipment and other equipment for measuring, monitoring, and recording body functions such as heartbeat and brain waves, if employed by Sandia National Laboratories you may be required to comply with NNSA security requirements for MedPEDs. If you have a MedPED and you are selected for an on-site interview at Sandia National Laboratories, there may be additional steps necessary to ensure compliance with NNSA security requirements prior to the interview date."
Job metadata: Job ID: 699393, Job Family: EN, Regular/Temporary Position: R, Full/Part-Time Status: F.
Now, I need to produce HTML fragment.
I'll write:
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.
We are seeking an Engineering and Operations (E&O) Systems Engineer / Configuration Management (CM) Lead to support configuration management activities for the 02232 ND CM Department. In this role, you will work at the systems level with ND systems teams and product realization teams to ensure configuration management requirements are implemented effectively across the product lifecycle. You will apply expertise in engineering data architecture, change control, high-fidelity technical data package reporting, and the ND systems lifecycle, including the Phase X/6.x process, milestones, and deliverables. You will also support Product Realization Integrated Digital Enterprise (PRIDE) efforts to advance common digital engineering workflows, improve traceability, strengthen digital thread capabilities, and enhance cross-site collaboration across programs.