Senior Principal Systems Engineer - Electrical Flight Systems, Onsite

We need to output HTML fragment with sections: About the role? Actually the posting includes "What Your Job Will Be Like" which is description. Also "About Sandia" is company description but maybe not needed? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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. We need to decide which sections to include based on content. The posting includes: - About Sandia (company overview) – maybe not needed as a section? Could be "About the company"? Not listed as allowed headings but we could use "About the role"? Not exactly. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also possibly add other headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we should stick to those headings when appropriate. We can also create other headings if needed? Probably better to stick to those. We have content: "What Your Job Will Be Like" which is essentially responsibilities/duties. So we can put that under

  Responsibilities

  with
  • items. We have qualifications: "Qualifications We Require" and "Qualifications We Desire" plus also "Also, for this posting we are seeking individuals with the following experience:" which is more qualifications/skills. So we can have

    Requirements

    (or Qualifications) and maybe

    Skills

    . But we need to avoid thin sections. Could combine Requirements and Qualifications into one section? The instruction says prefer a few substantive sections over many thin ones. So we could have one section for "Qualifications" that includes both required and desired. Or we could have "Requirements" for required, and "Skills" for desired. But that might be thin. Better to have one "Qualifications" section covering both required and desired, plus the additional experience list. We also have Salary Range: $117,500 - $235,700. That's Pay. So we need a Pay section. We have 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 "These benefits vary by job classification." So we have benefits content. So we should include a Benefits section. We have schedule? Not explicitly given besides flexible work arrangements mention (9/80, 4/10 compressed workweeks, part-time, telecommuting). That's schedule info. So we could include a Schedule section. We also have "About Sandia" which is company overview; not required but could be included as "About the role"? Not exactly. Could be omitted as not required. The instruction says include a section ONLY when posting has real, specific content for it. The "About Sandia" is company description, not about the role. Could be omitted. The job title is not to be repeated. We also have "Posting Duration", "Security Clearance", "EEO", "NNSA Requirements For MedPEDs", "Job ID", etc. Those are boilerplate or metadata to be removed. Thus final HTML could have sections: Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to use

    for each section heading. Inside each, use

    for prose and

    • for lists. We must preserve all substantive information. Let's extract details. Responsibilities (from "What Your Job Will Be Like" and bullet list after "On any given day, you may be called on to:"). Paragraph before list: "Sandia Department 5424 Electrical Flight Systems in the 5420 Strike Systems group is seeking an R&D S&E Systems Engineer to complement the Engineering team and help lead concept development efforts for new missile and weapon systems. Opportunities include leading multidisciplinary teams to rapidly identify operational needs for strike and defense applications, translate those needs into mission and technology-informed requirements, and guide the concept maturation. The work would involve interfacing with potential sponsors, services, COCOMs, and OGAs to understand and manage vehicle designs, vehicle and kill chain technology, and mission CONOPs to help them carry out their missions. The result of your work would be the identification of mission-relevant R&D, well-defined requirements for new systems, and support to government investment decisions. The 5420 Strike Systems portfolio includes the Conventional Prompt Strike (CPS) deployed conventional weapon, the Submarine Launched Cruise Missile - Nuclear (SLCM-N) Nuclear tipped cruise missile, and an exciting array of R&D proposals and programs." Then bullet list: - Develop, advise, and manage requirements for hypersonic, ballistic, and cruise missiles both in the R&D and Weapon Development space. - Lead concept studies: shape the scope, develop success criteria, and direct technical approach; coordinate multidisciplinary teams. - Engage with COCOMS, services, and the IC to understand gaps and identify potential solutions. - Translate operational needs into requirements: define L0/L1 requirements, interfaces, constraints, and known unknowns. - Work with peer Systems Engineers and SMEs across many Engineering disciplines - Communicate results to sponsors and decision makers, both technical and non-technical. This includes concise technical briefs, recommendations, and proposals (quads, one-pagers, transition plans). - Due to the nature of the work, this candidate must be able to work onsite. We should keep all. Qualifications: Combine required, desired, and additional experience list. Required: - 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 and potentially SCI access. Desired: - Graduate degree in Engineering or a highly related field. - Experience working with Nuclear Security Enterprise (NSE) laboratories and plants including Pantex, Kansas City National Security Campus (KCNSC), Lawrence Livermore Laboratory (LLNL) 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 and ability to work effectively in multidisciplinary teams Additional experience list (under "Also, for this posting we are seeking individuals with the following experience:"): - Solid experience with Systems Engineering - Experience working leading multi-disciplinary teams with SMEs to develop requirements and concepts - Experience working with COCOMS, services, and OGAs - Experience with taking high-level needs and deriving requirements, solutions, and a technical approach for those solutions - Ability to communicate technical results to high-level decision makers - Ability to engage with potential funding sponsors and write proposals - Ability to hold a Q and SCI clearances - Current clearance holder We can combine these into a list under Qualifications. Benefits: From "Some of the main reasons we love our jobs:" list and later "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: 9/80, 4/10 compressed workweeks, part-time work, and telecommuting (a mix of onsite work and working from home). Also "These benefits vary by job classification." We should capture all benefits items. Let's list: - 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. (maybe tagline) But we should keep substantive. Pay: Salary Range $117,500 - $235,700. Also note: "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." We should keep that note. Schedule: Flexible work arrangements already captured under benefits, but schedule section could include those specifics: 9/80, 4/10 compressed workweeks, part-time work, telecommuting. However we might avoid duplication. The instruction says prefer few substantive sections; we could put schedule info under Benefits or Schedule. Since we already have Benefits section, we could put schedule details there. But we also have a Schedule heading allowed. Could we make a Schedule section with those details? That would be thin if we only have schedule. But we could combine schedule with benefits? The instruction says prefer a few substantive sections over many thin ones. So maybe we have Benefits section that includes flexible work arrangements, and we don't need a separate Schedule section. However the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state flexible work arrangements, which is schedule. So we could have a Schedule section with that info. But we also have benefits like vacation, medical, etc. That's separate. So we could have both Benefits and Schedule sections. That's two sections, not too many. That's okay. Thus we will have sections: Responsibilities, Qualifications, Benefits, Pay, Schedule. Now we need to output HTML fragment only, no /, no markdown. We'll produce:

      Responsibilities

      ...

      • ...
      ...
      Similarly for Qualifications: we can have a

      summarizing? Actually we have list items; we could just use

      • for each qualification. But we also have some prose paragraphs (like required and desired). Could combine into list. Better: Provide a

        intro then list. But we must not invent content. We'll keep the details as list items. We need to ensure we don't duplicate content. Let's draft. Responsibilities section:

        Sandia Department 5424 Electrical Flight Systems in the 5420 Strike Systems group is seeking an R&D S&E Systems Engineer to complement the Engineering team and help lead concept development efforts for new missile and weapon systems. Opportunities include leading multidisciplinary teams to rapidly identify operational needs for strike and defense applications, translate those needs into mission and technology-informed requirements, and guide the concept maturation. The work would involve interfacing with potential sponsors, services, COCOMs, and OGAs to understand and manage vehicle designs, vehicle and kill chain