Senior/Principal R&D Computer Engineer - Embedded Systems, Onsite

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to extract content. Let's parse the posting: - About Sandia: description of lab, benefits etc. Could be "About the role"? Actually "About the role" maybe corresponds to description of job. But we have "About Sandia" which is about organization. Might be considered "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. Content: - About the role: Could be the paragraph "What Your Job Will Be Like" and "On Any Given Day, You May Be Expected To ..." plus maybe "About Our Team". That seems like role description. - Responsibilities: Could be the bullet list of duties: "Perform reverse engineering...", "Design, develop...", "Create comprehensive test plans...", "Communicate technical progress...", "Collaborate closely...", "Take initiative to lead technical thrusts...". Those are responsibilities. - Requirements: Might be the "Qualifications We Require" (Bachelor's degree + 5 years experience, ability to obtain DOE Q and SCI clearance). Also maybe "Due to the nature of the work, the selected applicant must be able to work onsite." That's a requirement. - Qualifications: Could be "Qualifications We Desire" (graduate degree, etc.) plus list of desired experiences. - Skills: Could be the list of desired skills/experience: "Experience in embedded system design, hardware design, testing, and evaluation and/or programming. Experience in one or more of the following areas: reverse engineering, software vulnerability assessment, computer networking, computer architecture, compilers, or related computer security disciplines. Demonstrated experience in a subset of the following: Circuit design fundamentals and interpretation of hardware schematics Embedded systems development using microcontrollers or digital signal processors (embedded C/C++ and real-time operating systems) Proficiency in C or other programming languages Networking architectures and protocols, including serial communication interfaces Design, development, and testing of electrical or electronic systems Use of laboratory diagnostics and testing equipment for hardware validation Software development methodologies and best practices Strong communication skills with a proven ability to clearly articulate technical concepts and results in both written and oral formats, tailored to diverse audiences." - Benefits: The posting mentions "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 content. - 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." That's pay info. - Schedule: Not explicitly given. There's mention of flexible work arrangements (9/80, 4/10) but that's more benefits/work arrangement. Could be considered schedule? The instruction: include Schedule section only if posting actually states them. It does mention flexible work arrangements, which could be schedule. But we already used that in Benefits. Might be better to put schedule info under Benefits? However we have separate Benefits and Schedule sections. The posting mentions flexible work arrangements (9/80, 4/10) which are schedule types. Could treat as Schedule. But we also have benefits like vacation, medical, 401k, relocation assistance. So we could split: Benefits: generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance, amenities. Schedule: flexible work arrangements including 9/80, 4/10 compressed workweeks, part-time work, telecommuting. We need to avoid filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO, NNSA Requirements, Security Clearance details? Actually security clearance is part of qualifications (requirement). We should keep that. The posting includes a lot of security clearance details; we should preserve that as part of Requirements or Qualifications. It's substantive. We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we need to drop the EEO paragraph, NNSA Requirements, maybe the security clearance details beyond requirement? But the requirement to obtain clearance is substantive; we can keep a concise statement: "Ability to obtain and maintain a DOE Q and SCI clearance which may require a polygraph test." The rest about background investigation etc may be considered boilerplate? It's still part of security clearance process. Might be considered required info. But we can keep the requirement line and maybe a brief note about US citizenship. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all substantive info, not just summarize. But we can keep it as is, but we need to remove boilerplate like EEO, NNSA Requirements, etc. The security clearance details beyond the requirement might be considered substantive? It's about process; could be considered substantive. However it's quite detailed. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Security clearance is not EEO. It's a requirement. So we should keep it. But we need to avoid duplication: there is a paragraph about "Security Clearance Sandia is required by DOE to conduct a pre-employment drug test and background review..." and later "Applicants offered employment with Sandia are subject to a federal background investigation...". That's somewhat duplicated. We can keep the requirement line and maybe note that US citizenship required. But we must preserve all substantive info; we could keep both paragraphs but they are similar. Might be considered duplicated lines; we should deduplicate. Let's extract substantive sections: - About Sandia: description of lab, benefits, flexible work arrangements, etc. This could go under About the role? Actually "About the role" maybe includes description of team and work. But we have separate "About Our Team". Could combine. Better to follow the headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll assign: About the role: Paragraph "What Your Job Will Be Like" and maybe "About Our Team". Also the initial "About Sandia" could be considered company overview, not role. But we can include it under About the role as context. Responsibilities: bullet list of duties (On Any Given Day...). Requirements: "Qualifications We Require" plus the onsite work requirement and clearance requirement. Qualifications: "Qualifications We Desire" plus the list of desired experience/skills? But we also have Skills section for skill list. Might split: Qualifications = education/degree/experience requirements; Skills = technical skills list. Thus: Qualifications: Graduate degree desire, etc. Also maybe the "ideal R&D Computer Engineering candidate..." paragraph. Skills: The detailed list of desired experience areas (embedded system design, hardware design, testing, etc.) plus the subset list, plus communication skills. Benefits: Flexible work arrangements (9/80, 4/10, part-time, telecommuting) + generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance, amenities. Pay: Salary range $117,500 - $235,700 plus note about estimate. Schedule: Not explicitly separate; but we already used flexible work arrangements under Benefits. Could we still have Schedule? The posting does not mention specific schedule like "Monday-Friday 9-5". So maybe we omit Schedule section. But we need to include sections only when posting has real specific content. If we omit Schedule, that's fine. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include or . We must not include markdown fences. Let's craft. First, About the role: We can combine:

  About Sandia National Laboratories: 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.

  Then maybe a paragraph about the role:

  What Your Job Will Be Like: Are you an Electrical or Computer Engineer driven to apply cutting-edge technologies toward impactful national security challenges? Join the Systems Research Department at Sandia's Integrated Threat Intelligence Center, where we specialize in vulnerability assessments, forward and reverse engineering of embedded systems, and the development of innovative tools supporting unique national security missions. As a motivated R&D Engineer with expertise in embedded systems, you will collaborate within a multidisciplinary environment and partner across Sandia. Our work spans the complete embedded systems lifecycle - from initial concept and design through fabrication, firmware and software development, to rigorous testing and deployment - focusing on innovative, low-power solutions. Our expertise covers a diverse range of technologies, including embedded systems, mobile devices, IoT, Wi-Fi systems, and networked devices. If you are passionate about end-to-end embedded system engineering and eager to make a difference through technology innovation, we invite you to apply.

  Then About Our Team maybe also part of About the role:

  About Our Team: The Systems Research Department specializes in vulnerability assessments and research, as well as forward/reverse engineering embedded systems. We develop tools to support a variety of unique national security missions. Our expertise encompasses a diverse range of technologies, including embedded systems, mobile devices, IoT, Wi-Fi systems, and networked devices.

  We could merge. Now Responsibilities: list of duties from "On Any Given Day, You May Be Expected To". We'll make
  • each. Responsibilities: - Perform reverse engineering and vulnerability assessments on embedded systems to identify and mitigate potential risks. - Design, develop, and integrate hardware and software solutions that meet mission-critical requirements. - Create comprehensive test plans and execute rigorous testing protocols to validate novel system capabilities. - Communicate technical progress and findings effectively to mission partners and interdisciplinary colleagues. - Collaborate closely with electrical, computer, and software engineers to innovate and refine approaches that advance key mission objectives. - Take initiative to lead technical thrusts in specific areas of embedded systems development, driving strategy, execution, and team coordination to deliver impactful results. Now Requirements: include Qualifications We Require and onsite requirement and clearance. We can make a

    for prose and maybe a

    for list. Qualifications We Require: "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