Postdoctoral Research Associate, Advanced Nuclear Reactor and Fuel Cycle Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID/requisition numbers as headings; can fold minor metadata into short p or drop. We need to parse the posting. Key content: Overview: description of ORNL, RNFCA group, role description. Major Duties/Responsibilities: list of duties. Basic Qualifications: PhD, knowledge, experience, programming, writing. Preferred Qualifications: multiphysics, numerical algorithms, security clearance. Special Requirements: PhD within 5 years, appointment length up to 24 months, etc. Also reference letters, export control, PIV, etc. About ORNL: description, benefits list. Pay: Not explicitly stated. There's "ORNL offers competitive pay and benefits programs". No specific pay figure. So we should NOT create Pay section because no specific pay. Schedule: Not mentioned. No schedule details. So no Schedule. Benefits: There's a list of benefits: medical, retirement plans, flexible work hours, on-site fitness, banking, cafeteria, prescription drug plan, dental, vision, 401(k), contributory pension, life insurance, disability, vacation, holidays, parental leave, legal insurance, EAP, flexible spending, HSA, wellness, educational assistance, relocation assistance, employee discounts. So we can include Benefits section. Also maybe "About the role" could be overview description. Responsibilities: major duties. Requirements: maybe basic qualifications? Or we could separate Requirements (basic) and Qualifications (preferred). The instruction says use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have overview (About the role). Responsibilities (Major Duties/Responsibilities). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills maybe from programming/scripting experience? Could be part of Requirements. But we can create Skills section for programming/scripting experience and writing/communication. But we must not create thin sections; prefer few substantive sections. Could combine some. We need to preserve all substantive information. So we need to include all details. Let's decide sections: - About the role: overview paragraph(s) describing ORNL, RNFCA group, role purpose. - Responsibilities: list of duties (design, develop, optimize reactor models; develop fuel cycle models; work individually/team; communicate work; deliver ORNL mission; promote equal opportunity). Use

• . - Requirements: Basic Qualifications (PhD within 5 years, knowledge of nuclear reactor analysis R&D, experience using SCALE, VERA, MCNP, Serpent, OpenMC, MOOSE, programming/scripting experience, writing/communication skills). Could also include special requirements like PhD within 5 years, appointment length, reference letters, export control, PIV, etc. Might be better to put those under Requirements as well. - Qualifications: Preferred Qualifications (multiphysics software, numerical algorithms, ability to obtain security clearance). Also maybe mention "ability to obtain and maintain a security clearance" as preferred. - Skills: maybe programming/scripting languages (C/C++, Python, Fortran, Git, CMake) and writing/communication. Could be part of Requirements but we can separate. - Benefits: list of benefits. We must not include Pay or Schedule. We must not include boilerplate like EEO, equal opportunity, scam warning, navigation, cookie, legal. The posting includes some EEO statements at end; we must remove them. Also remove "This position will remain open for a minimum of 5 days..." etc. That's application instructions; we should remove application instructions. Also remove "Please submit two letters of reference when applying..." etc. That's application instruction; remove. Also remove "Instructions To Upload Documents..." etc. Remove. Also remove "For Foreign National Candidates" etc? That's special requirement about PIV; maybe keep as part of Requirements? It's about eligibility. Might be considered substantive. But it's about process; still maybe keep as part of Requirements or Special Requirements. However the instruction says remove application instructions. The PIV info is not exactly application instruction but eligibility; could keep. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep details like appointment length up to 24 months, potential for extension, subject to performance/funding, need two letters of reference, export control, PIV, etc. Those are substantive. Thus we need to include them somewhere, maybe under Requirements or a separate section like "Appointment Details". But we only allowed headings from list; we could put them under Requirements or Qualifications. But we must not create new headings not in list. So we need to fit them into allowed headings. We could put appointment length, reference letters, export control, PIV under Requirements (as they are requirements). Or under Qualifications (maybe not). Let's put them under Requirements. Now we need to avoid repeating job title. Not include "Postdoctoral Research Associate, Advanced Nuclear Reactor and Fuel Cycle Engineer" as heading. We must not include Job ID/requisition numbers as headings; we can drop them or put in a short p. The posting starts with "Requisition Id 17151 Overview". We can drop that or put in a p as minor metadata. Probably drop. Now produce HTML. Structure:

  About the role

  ... overview text ...

  Responsibilities

  • ...
  ...

  Requirements

  • PhD in nuclear engineering or related field completed within the past 5 years.
  • Knowledge of nuclear reactor analysis R&D demonstrated through research and associated publications.
  • Experience using SCALE, VERA, MCNP, Serpent, OpenMC, and/or MOOSE and familiarity with reactor systems and concepts.
  • Programming/scripting experience including use of one or more of C/C++, Python, Fortran, Git, and CMake (an asset).
  • Writing and communication skills and ability to publish.
  • Ability to obtain and maintain a security clearance (preferred).
  • Appointment length up to 24 months with potential for extension, subject to performance and funding.
  • Must submit two letters of reference with application.
  • Must be qualified for access to export‑controlled technology without an export control license.
  • Must be able to obtain and maintain a federal Personal Identity Verification (PIV) card (or LSSO for foreign nationals without three‑year U.S. residency).
  But we separated preferred qualifications; maybe we should have Qualifications section for preferred. Let's do:

  Qualifications

  • Experience with multiphysics software and simulations (asset).
  • Previous experience with development and implementation of numerical algorithms in advanced modeling and simulation software related to reactor physics analysis (asset).
  • Ability to obtain and maintain a security clearance (asset).
  But we already included security clearance in Requirements; maybe better to move to Qualifications. Let's adjust: Requirements = basic qualifications (PhD, knowledge, experience, programming, writing). Qualifications = preferred (multiphysics, numerical algorithms, security clearance). Then we can also include appointment details, reference letters, export control, PIV under Requirements? Those are not exactly qualifications but conditions. Could be under Requirements as well. But we might create a separate section? Not allowed. Could put them under Requirements as additional items. Thus: Requirements: - PhD in nuclear engineering or related field completed within the past 5 years. - Knowledge of nuclear reactor analysis R&D demonstrated through research and associated publications. - Experience using SCALE, VERA, MCNP, Serpent, OpenMC, and/or MOOSE and familiarity with reactor systems and concepts. - Programming/scripting experience including use of one or more of C/C++, Python, Fortran, Git, and CMake (an asset). - Writing and communication skills and ability to publish. - Appointment length up to 24 months with potential for extension, subject to performance and funding. - Must submit two letters of reference with application. - Must be qualified for access to export‑controlled technology without an export control license. - Must be able to obtain and maintain a federal Personal Identity Verification (PIV) card (or LSSO for foreign nationals without three‑year U.S. residency). Qualifications: - Experience with multiphysics software and simulations (asset). - Previous experience with development and implementation of numerical algorithms in advanced modeling and simulation software related to reactor physics analysis (asset). - Ability to obtain and maintain a security clearance (asset). Skills: maybe we can combine programming/scripting and writing into Skills; but we already have them in Requirements. Could create Skills section for programming/languages and writing/communication. But that would duplicate. Better to not have Skills if we already covered. However instruction says we can include Skills section if we have real specific content. We have programming/scripting experience and writing/communication skills; those are skills. So we could move those to Skills section and keep Requirements more about education/experience. Let's think. We need to preserve all info; we can allocate as we like as long as we don't lose info. Let's define: About the role: overview. Responsibilities: duties. Requirements: education/experience basics (PhD, knowledge, experience with codes, appointment length, reference letters, export control, PIV). Qualifications: preferred qualifications (multiphysics, numerical algorithms, security clearance). Skills: programming/scripting languages and writing/communication. Benefits: list. Now ensure no duplication: programming/scripting appears only in Skills; writing/communication only in Skills. Ensure we still mention experience using SCALE etc in Requirements. Now check that we didn't miss any info: The overview includes ORNL description, RNFCA group, role purpose, mention of world-leading facilities, neutronics and thermal-hydraulics analysis. We'll include that. Responsibilities list: we have 5 items from Major Duties/Responsibilities. Now we need to ensure we didn't include boilerplate: we removed EEO, equal opportunity, scam warning, navigation, cookie, legal, application instructions (like "Please submit two letters of reference when applying...") but we kept reference letters as requirement; that's okay because it's substantive. We removed instructions about uploading documents, etc. We removed "This position will remain open for a minimum of 5 days..." etc. We removed "ORNL is an equal opportunity employer..." etc. We removed "UT-Battelle is an E-Verify employer." etc. Now produce HTML. We need to ensure we use

  for section headings. Use

  • for lists. Use

    for prose. We must not output markdown code fences. Just raw HTML. Let's craft. About the role paragraph: combine overview sentences. "Oak Ridge National Laboratory (ORNL) is the largest US Department of Energy science and energy laboratory, conducting basic and applied research to deliver transformative solutions to compelling problems in energy and security. The Reactor and Nuclear Fuel Cycle Analysis Group (RNFCA) is seeking candidates for the Postdoctoral Research Associate, Advanced Nuclear Reactor and Fuel Cycle Engineer role. This role involves working with state‑of‑the‑art modeling and simulation capabilities for lattice physics, reactor core, spent fuel, and fuel cycle applications through leadership in the development and analysis of SCALE and/or the Virtual Environment for Reactor Applications (VERA) simulations, in collaboration with industry, national laboratories and university researchers. ORNL provides world‑leading nuclear, radiological and scientific facilities, including the High Flux Isotope Reactor, and the position supports neutronics and thermal‑hydraulics analysis." That seems good. Now Responsibilities list items: - Design, develop, optimize and analyze reactor models using world‑class modeling and simulation codes (SCALE, VERA,