Early Career R&D S&E Electrical Engineer - Surety System Engineer, Onsite
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. 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. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones.
We need to extract substantive content: About Sandia (intro) maybe not needed as heading? Could be "About the role" or "About Sandia"? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We have sections: "About Sandia" (intro about organization). Could be "About the role" maybe not. Actually "About Sandia" is about the organization, not role. Could be "About the role" but we have "What Your Job Will Be Like" which describes role. So we can use heading "About the role" for that content.
We have responsibilities/duties: many bullet-like sentences under "What Your Job Will Be Like" and "On any given day you may be called on to:" etc. Those are duties.
We have qualifications: "Qualifications We Require" and "Qualifications We Desire". Those can be under Requirements or Qualifications.
We have skills: maybe list of desired skills like experience with design, development, etc. Could be under Skills.
We have benefits: The posting mentions "Flexible work arrangements for many positions include 9/80 ... 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 there is some benefits info. Also "Salary Range $97,500 - $190,200". That's pay. So we can include Pay section with that salary range. Benefits section with flexible work arrangements, vacation, medical, 401k, learning, relocation assistance. Schedule? Not explicitly given besides flexible work arrangements; but we could treat flexible work arrangements as Benefits, not Schedule. There's no explicit schedule like "full-time". The posting mentions "Full/Part-Time Status: F" but that's metadata; we could drop. No explicit schedule like "Monday-Friday". So we may not create Schedule section.
We must not create sections with placeholder text. So we will include sections: About the role (or What Your Job Will Be Like), Responsibilities, Requirements (maybe combine Qualifications), Skills, Benefits, Pay.
We need to ensure we don't repeat job title as heading. Not needed.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them as lists or paragraphs.
We must remove boilerplate: EEO, NNSA Requirements for MedPEDs, Security Clearance details? Those are legal/boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the EEO paragraph, the NNSA Requirements for MedPEDs, the Security Clearance paragraph (though security clearance is relevant to qualifications? It says "Ability to obtain and maintain Q-level clearance" is a qualification; we should keep that as part of qualifications. The rest of the security clearance paragraph about drug test, background review, etc is legal boilerplate; we should remove that. Also remove "Posting Duration", "Job ID", "Job Family", etc as minor metadata; we can fold into a short
or drop. Probably drop.
We need to keep "Due to the nature of the work, at least 80% on-site work at the Pantex facility is required for this position." That's substantive; could be under Responsibilities or maybe under Benefits? It's a work requirement; maybe under Responsibilities.
We need to keep "Occasional travel between Albuquerque and production facilities is required."
We need to keep "Salary Range $97,500 - $190,200" and note that it's estimated.
We need to keep "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)". That's benefits.
We need to keep "Generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance". That's benefits.
We need to keep "These benefits vary by job classification." That's benefits note.
We need to keep "World-changing technologies. Life-changing careers. Learn more about Sandia at: http://www.sandia.gov" maybe not needed; it's promotional; could be dropped as boilerplate? It's not legal but maybe not substantive to role. Could be omitted.
We need to keep "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 worldwideExtraordinary co-workersSome of the best tools, equipment, and research facilities in the worldCareer advancement and enrichment opportunitiesFlexible 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" This is a big intro; we could treat as "About Sandia" but not required heading. Could be omitted? The instruction says preserve ALL substantive information; but we can decide to keep it as a paragraph under maybe no heading? However we need to output only HTML fragment; we could include a
with that intro. But we must not repeat job title as heading; we can just start with a
about Sandia. However the instruction about sections: "Prefer a few substantive sections over many thin ones." So we could combine the intro into a section like "About Sandia" but they didn't list that as example heading; but we can still use
for any section heading; they gave examples but not exclusive. So we could add About Sandia
with that paragraph. That seems okay.
But we must avoid filler/placeholder text. The intro has substantive content.
Now responsibilities: we need to capture all duties listed.
Let's extract duties from "What Your Job Will Be Like" paragraph and the bullet list after "On any given day you may be called on to:" and also the later sentences about partnering, presenting, etc.
We'll create a - list for responsibilities.
We need to ensure we don't miss any.
Let's parse the text:
"What Your Job Will Be Like We are seeking an R&D Electrical/Electronics Engineer to join our dynamic team in a Surety System Engineering role with special emphasis on Category 1 Electrical Equipment Assurance. Our department provides system and software surety, with this position specifically focusing on Category 1 Acceptance Testers, Use Control Systems, and T-gear for the DoD. This position requires performing multiple engineering functions, from deep dive circuit analysis and failure mode determination, to testing actual prototypes, performing software safety analyses, qualifying Category 1 equipment, interfacing with Independent Assessment, and presenting to the NESSG. This role also involves engaging and collaborating regularly with personnel across multiple Sandia organizations, as well as with Los Alamos National Laboratory, Lawrence Livermore National Laboratory, the National Nuclear Security Administration (NNSA), Pantex production facility, and Department of Defense (DOD) organizations. Additional duties may include software surety for weapons and weapons-related product. This Surety Engineer would provide R&D contributions throughout the entire product realization lifecycle including monitoring every phase of the development process to ensure software product design, development, and verification activities delivers an assured software product that meets its requirements safely and reliably. The Surety Engineer applies engineering principles across a wide range of projects including components, subsystems, and systems. Projects span across all phases of the product realization lifecycle from conceptual design and development to production and maintenance/retirement. On any given day you may be called on to: Analyze and interpret electrical schematics, environmental specifications, and system level documentation using the Sandia NW drawing and authorization system. Perform Fault Tree and Failure analysis at the system, subsystem, component, and ancillary equipment level to identify failure modes in analog and digital circuit designs. Develop testing approaches and test configurations to ensure that designs effectively meet requirements in a safe manner across a wide range of environmental conditions. Understand component functionality in light of its parent product use, from FPGA/ASIC/SoC through PWB/PWAs, subassemblies, systems, and software to effectively verify functionality and safety of those products in normal and abnormal environments. Develop qualification and safety plans to ensure successful authorization of high-consequence hardware and software products. Partner with component/system design teams, test organizations, safety and surety engineering, and independent assessment to devise and execute analysis and testing of Category 1 designs. Present at program technical reviews and nuclear explosive safety studies ¿ specifically regarding failure modes, risks, and issues identified. Interface with colleagues within Sandia and externally at LANL, LLNL, Pantex, Kansas City, and the NNSA. Interface with the Nuclear Explosive Safety Study Group (NESSG). Work independently and within teams to coordinate and execute large scale Category 1 design projects. Apply technical judgement and software engineering principles to recognize problems, develop requirements, monitor and support design/development methods, and deliver qualified, accepted digital product. Lead R&D teams in identifying and transforming unknown technical challenges into known technical risks to ensure and improve the safety, security, and reliability of the product. Occasional travel between Albuquerque and production facilities is required. Due to the nature of the work, at least 80% on-site work at the Pantex facility is required for this position."
That's a lot; we can turn each sentence into a list item.
Now qualifications: "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 Q-level clearance"
"Qualifications We Desire The ideal R&D S&E Electrical Engineer candidate for Sandia National Laboratories will in addition possess the following: Graduate degree in Electrical Engineering or a highly related field where an independent research project was a graduation requirement (e.g., independent project, thesis, or dissertation).Ability to work independently and collaborate well in a multidisciplinary team of designers and test engineers.Outstanding verbal and written skills, including the ability to develop and present briefings that are clear and compelling. Also, for this posting we are seeking individuals with the following experience: Experience with design, development, and delivery of high-consequence Category
for prose. 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. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content: About Sandia (intro) maybe not needed as heading? Could be "About the role" or "About Sandia"? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have sections: "About Sandia" (intro about organization). Could be "About the role" maybe not. Actually "About Sandia" is about the organization, not role. Could be "About the role" but we have "What Your Job Will Be Like" which describes role. So we can use heading "About the role" for that content. We have responsibilities/duties: many bullet-like sentences under "What Your Job Will Be Like" and "On any given day you may be called on to:" etc. Those are duties. We have qualifications: "Qualifications We Require" and "Qualifications We Desire". Those can be under Requirements or Qualifications. We have skills: maybe list of desired skills like experience with design, development, etc. Could be under Skills. We have benefits: The posting mentions "Flexible work arrangements for many positions include 9/80 ... 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 there is some benefits info. Also "Salary Range $97,500 - $190,200". That's pay. So we can include Pay section with that salary range. Benefits section with flexible work arrangements, vacation, medical, 401k, learning, relocation assistance. Schedule? Not explicitly given besides flexible work arrangements; but we could treat flexible work arrangements as Benefits, not Schedule. There's no explicit schedule like "full-time". The posting mentions "Full/Part-Time Status: F" but that's metadata; we could drop. No explicit schedule like "Monday-Friday". So we may not create Schedule section. We must not create sections with placeholder text. So we will include sections: About the role (or What Your Job Will Be Like), Responsibilities, Requirements (maybe combine Qualifications), Skills, Benefits, Pay. We need to ensure we don't repeat job title as heading. Not needed. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them as lists or paragraphs. We must remove boilerplate: EEO, NNSA Requirements for MedPEDs, Security Clearance details? Those are legal/boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the EEO paragraph, the NNSA Requirements for MedPEDs, the Security Clearance paragraph (though security clearance is relevant to qualifications? It says "Ability to obtain and maintain Q-level clearance" is a qualification; we should keep that as part of qualifications. The rest of the security clearance paragraph about drug test, background review, etc is legal boilerplate; we should remove that. Also remove "Posting Duration", "Job ID", "Job Family", etc as minor metadata; we can fold into a short
or drop. Probably drop. We need to keep "Due to the nature of the work, at least 80% on-site work at the Pantex facility is required for this position." That's substantive; could be under Responsibilities or maybe under Benefits? It's a work requirement; maybe under Responsibilities. We need to keep "Occasional travel between Albuquerque and production facilities is required." We need to keep "Salary Range $97,500 - $190,200" and note that it's estimated. We need to keep "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)". That's benefits. We need to keep "Generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance". That's benefits. We need to keep "These benefits vary by job classification." That's benefits note. We need to keep "World-changing technologies. Life-changing careers. Learn more about Sandia at: http://www.sandia.gov" maybe not needed; it's promotional; could be dropped as boilerplate? It's not legal but maybe not substantive to role. Could be omitted. We need to keep "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 worldwideExtraordinary co-workersSome of the best tools, equipment, and research facilities in the worldCareer advancement and enrichment opportunitiesFlexible 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" This is a big intro; we could treat as "About Sandia" but not required heading. Could be omitted? The instruction says preserve ALL substantive information; but we can decide to keep it as a paragraph under maybe no heading? However we need to output only HTML fragment; we could include a
with that intro. But we must not repeat job title as heading; we can just start with a
about Sandia. However the instruction about sections: "Prefer a few substantive sections over many thin ones." So we could combine the intro into a section like "About Sandia" but they didn't list that as example heading; but we can still use