Principal Nuclear Facilities Operations Specialist

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

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

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

  for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting: The posting has: - Job Description (intro paragraph) - Responsibilities (Key Responsibilities with bullet points) - Qualifications (detailed list) - About Us (company description) - Pay information (salary range) - Schedule information (4/10s Monday-Thursday) - Benefits information (medical, dental, vision, pension, 401k, PTO, holidays, relocation, tuition assistance) - Security clearance requirements - Drug testing/background check info - EEO statement (boilerplate - should remove) - Company structure info I need to organize this into appropriate sections. The rules say to use specific heading names: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Looking at the content: - "About the role" could cover the introductory paragraph - "Responsibilities" for the key responsibilities list - "Qualifications" for the qualifications section (this is detailed) - "Requirements" might overlap with qualifications - but the posting has a "Qualifications" heading, so I'll use that - "Skills" - there are some skills mentioned (communication, computer skills) - "Benefits" - there is a benefits section - "Pay" - there is salary range - "Schedule" - there is work schedule info I should also include the security clearance and location info. The location is mentioned in the qualifications section: "The primary work location will be at the Nevada National Security Site (located 70 miles northwest of Las Vegas, Nevada)." That could go in a "Location" section or folded into "About the role" or "Schedule". The rules don't mention "Location" as a standard heading, but I could include it as a short paragraph. The security clearance and background check info is substantial - could be a "Clearance" or "Security" section, but not in the standard list. I'll include it as a separate section with a relevant heading, maybe "Security Clearance" or fold into "Requirements". The rules say to use the listed headings, but also say "include a section ONLY when the posting has real, specific content for it". The standard headings are examples. I think I can use other headings if needed, but should prefer the standard ones. Let me structure: 1. About the role - introductory paragraph 2. Responsibilities - bullet list 3. Qualifications - bullet list (the qualifications are detailed) 4. Skills - maybe separate out the skills mentioned (communication, computer skills, planning/scheduling) 5. Pay - salary range 6. Schedule - work schedule 7. Benefits - benefits list 8. Security Clearance - clearance requirements 9. Location - work location But the rules say "Prefer a few substantive sections over many thin ones." So I should combine where appropriate. The qualifications section is very long and detailed. I'll keep it as Qualifications. The skills are embedded in qualifications: "Must possess excellent communication... Computer skills in MS Word, Excel, and MS Outlook are desired." Could be a separate Skills section. The security clearance info is extensive: DOE Q Clearance, citizenship, background investigation, drug test, etc. That's substantial. The location is a single sentence. The About Us section is company description - could be "About Us" or "Company Overview". The rules don't list "About Us" but it's a common section. I'll include it as "About the Company" or similar. Now, I need to remove boilerplate: EEO statement, "MSTS is an Equal Opportunity Employer...", "MSTS is a background screening, drug-free workplace." That's boilerplate. Also remove duplicated lines: The qualifications section has some repetition (DOE orders listed twice). I'll preserve all substantive info but avoid duplication. The posting says "Qualifications" then lists bullet points. I'll convert to

  • . The responsibilities are listed as bullet points. Benefits are listed in prose: "MSTS offers our full-time employees highly competitive salaries and benefits packages including medical, dental, and vision; both a pension and a 401k; paid time off and 96 hours of paid holidays; relocation (if located more than 75 miles from work location); tuition assistance and reimbursement; and more." I'll convert to bullet list. Pay: "Annual salary range for this position is: $119,849.60 - $182,769.60. Starting salary is determined based on the position market value, the individual candidate education and experience and internal equity." That's pay info. Schedule: "Work schedule will be 4/10s Monday-Thursday (subject to change)." That's schedule. Location: "The primary work location will be at the Nevada National Security Site (located 70 miles northwest of Las Vegas, Nevada)." That's location. Security clearance: multiple paragraphs. I'll create sections: - About the Role - Responsibilities - Qualifications - Skills (maybe combine with qualifications? But separate might be better) - Pay - Schedule - Benefits - Security Clearance - Location - About the Company But the rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those exact headings where appropriate. "About the role" not "About the Role". "Requirements" vs "Qualifications" - the posting uses "Qualifications". I'll use "Qualifications". "Skills" is separate. I'll map: - About the role: introductory paragraph - Responsibilities: key responsibilities list - Qualifications: the qualifications list - Skills: the specific skills mentioned (communication, computer, planning) - Pay: salary range - Schedule: work schedule - Benefits: benefits list - Security Clearance: clearance requirements (not in example list but substantial) - Location: work location (not in example list but specific) - About the Company: company description (not in example list but substantial) The rules say "include a section ONLY when the posting has real, specific content for it". All these have real content. Now, I need to output only HTML fragment, no markdown fences. Let me write the HTML. First, About the role: The first paragraph: "The Device Assembly Facility (DAF) is seeking a Principal Nuclear Facility Operations Specialist to support operations at the NNSS. As an integral part of our DAF team, you will collaborate with external and internal partners to attain desired success and sustain successful operations. As a Principal Nuclear Operations Specialist, you may assume multiple following key responsibilities as the DAF mission evolves." That's prose, so

    . Responsibilities: The list under "Key Responsibilities". Each bullet point. Qualifications: The list under "Qualifications". It's a long list with some sub-bullets. I'll make each top-level bullet a

    , and if there are sub-items, maybe nested

    or just include in the same
    • . The posting has: - Bachelor’s degree... plus at least 9 years... which included 3 years’ experience in: - Nuclear operations or nuclear maintenance... - Conduct of Operations... - High explosives handling... - chemical handling... - Conduct of Operations... (repeated) - Candidate must have a working knowledge of... - Experience working with requirements-based systems... - Ability to read and follow... - Experience with planning and scheduling... - Experience working in schedule-driven environments. - Must possess excellent communication... - Computer skills... There's duplication: "Conduct of Operations (DOE O 422.1), Transportation & Packaging (DOE O 460.1C and 461.1B), and Quality Assurance requirements (DOEO 414.1D)." appears twice. I'll keep both but maybe combine. The rule says preserve ALL substantive information; do NOT invent or summarize away detail. So I should keep all, but avoid exact duplication? The posting has it twice, maybe it's a mistake. I'll include each unique point. I'll structure as a flat list for simplicity. Skills: Could extract "excellent communication (verbal and written) and interpersonal skills", "Computer skills in MS Word, Excel, and MS Outlook", "Experience with planning and scheduling", "Experience working in schedule-driven environments". But these are already in qualifications. The rules say "Prefer a few substantive sections over many thin ones." So maybe I should not create a separate Skills section if they're covered in Qualifications. However, the example headings include Skills. I'll include a Skills section with those specific skills. Pay: salary range paragraph. Schedule: work schedule paragraph. Benefits: convert the prose to bullet list. Security Clearance: the paragraphs about DOE Q Clearance, citizenship, background investigation, drug test, counterintelligence evaluation. Location: the location sentence. About the Company: the "About Us" paragraph. Now, I need to remove boilerplate: EEO statement, "MSTS is an Equal Opportunity Employer...", "MSTS is a background screening, drug-free workplace." Also the "Reference DOE Order 472.2..." etc. are part of security clearance, keep. The "Reviews and tests for the absence of any illegal drug..." is part of security clearance. The "Applicant selected will be subject to a Federal background investigation..." keep. The "Successful completion of a counterintelligence evaluation..." keep. The "Reference 10 CFR Part 709..." keep. The "Pre-placement physical examination, which includes a drug screen, is required. MSTS maintains a substance abuse policy that includes random drug testing. Must possess a valid driver’s license." These are requirements, could go in Qualifications or a separate Requirements section. The example headings include "Requirements". I could make a "Requirements" section for these. But the posting has "Qualifications" heading. I'll include these in Qualifications or a separate Requirements section. The rules say "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So both Requirements and Qualifications are example headings. The posting uses "Qualifications". I'll use Qualifications for the main qualifications, and maybe Requirements for the physical, drug test, driver's license, background check. But the background check is also security clearance. I'll combine. Let me decide on sections: 1. About the role 2. Responsibilities 3. Qualifications 4. Skills 5. Pay 6. Schedule 7. Benefits 8. Security Clearance 9. Location 10. About the Company That's 10 sections, maybe too many. But each has substance. I'll write the HTML. Note: The rules say "Do NOT repeat the job title as a heading (the page already shows it)". So no heading for job title. Also "do NOT put Job