Advanced Nuclear Reactor and Fuel Cycle Engineer (Associate)
Knoxville Technology Council · Oak Ridge, TN · 4 wk ago
ManagementFull-time
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 as heading. Must not include Job ID/requisition numbers as headings; can fold minor metadata into short p or drop. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove things like "This position will remain open for a minimum of 5 days..." etc. Also remove "We accept Word..." etc. Also remove "ORNL is an equal opportunity employer..." etc. Also remove "UT-Battelle is an E-Verify employer." Also remove "Special Requirements" maybe? It contains export control, security clearance, PIV etc. That's substantive? Might be considered requirements. Could be part of Requirements or Qualifications. We need to preserve all substantive information. So we need to extract duties, qualifications, preferred qualifications, basic qualifications, etc. Also benefits: list of benefits given. Pay: not specified; we should not create Pay section unless posting actually states them. No pay mentioned. Schedule: not mentioned. So we omit Pay and Schedule sections. Benefits: we have a list of benefits; we can include Benefits section. About the role: we have overview paragraph about ORNL and the group; we can put that under About the role. Responsibilities: major duties/responsibilities list. Requirements: basic qualifications? Could be Requirements. Qualifications: maybe Preferred Qualifications. Skills: maybe programming/scripting experience etc. But we need to avoid duplication. Let's decide sections:
- About the role: overview of ORNL and group, role purpose.
- Responsibilities: list of major duties/responsibilities.
- Requirements: Basic Qualifications (PhD, knowledge, experience, programming, writing).
- Qualifications: Preferred Qualifications (multiphysics, numerical algorithms, software engineering best practices, QA, security clearance).
- Skills: maybe combine programming/scripting etc but that's already in Requirements. Could instead put Skills as separate for technical skills like SCALE, VERA, etc. But we already have those in Requirements. To avoid duplication, maybe we put Skills as a subsection of Requirements? But instruction: use sections only when posting has real specific content. We can have Skills section listing specific software/languages. However we already have them in Requirements. Might be okay to have both but risk duplication. Better to keep Requirements as basic qualifications, and Qualifications as preferred qualifications, and maybe Skills not needed. But we need to include Skills section only if there is specific content. The posting mentions "Programming/scripting experience including the use of one or more of C/C++, Python, Fortran, Git, and CMake an asset." That's a skill. Also "Experience using SCALE, VERA, MCNP, Serpent, OpenMC, and/or MOOSE". That's also skill. Could put those under Skills. But then Requirements would be just PhD and knowledge of nuclear reactor analysis R&D? Might be thin. However we can keep Requirements as basic qualifications (PhD, knowledge, experience). Skills as technical skills. Qualifications as preferred qualifications. Benefits as benefits.
Let's extract content:
About the role: "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. Our diverse capabilities span a broad range of scientific and engineering disciplines, enabling the laboratory to explore fundamental science challenges and conduct the research needed to accelerate the delivery of solutions to the marketplace. The Reactor and Nuclear Fuel Cycle Analysis Group (RNFCA) Group is seeking candidates to apply for the Advanced Nuclear Reactor and Fuel Cycle Engineer (Associate) role. This role is responsible for 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 and in collaboration with industry, national laboratories and university researchers. ORNL has world-leading nuclear, radiological and scientific facilities, including the High Flux Isotope Reactor, and this role would support the neutronics and thermal-hydraulics analysis."
We can keep that as About the role.
Responsibilities: list from "Major Duties/Responsibilities":
- Design, develop, optimize and analyze reactor models using world-class modeling and simulation codes (SCALE, VERA, OpenMC, MCNP, Serpent, MOOSE) to support the design and development of next generation nuclear reactors.
- Develop and analyze fuel cycle models using Cyclus to evaluate advanced fuel cycle strategies to support the design and deployment of advanced nuclear reactors.
- Interact effectively across organization structures with staff scientists and engineers and be an effective representative of ORNL and their research to sponsors and the professional community.
- Conduct work on scope and on budget.
- Communicate effectively the work performed through journal articles, presentations, reports, and code documentation.
- Serve as a role model for integrity and safety in the conduct of research, mentoring of early career staff, and engagement with scientific and professional societies
- Deliver ORNL’s mission by aligning behaviors, priorities, and interactions with our core values of Impact, Integrity, Teamwork, Safety, and Service. Promote equal opportunity by fostering a respectful workplace – in how we treat one another, work together, and measure success.
We should keep all.
Requirements (Basic Qualifications):
- A PhD in Nuclear Engineering or a closely related field.
- Knowledge of nuclear reactor analysis R&D is required as 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 the use of one or more of C/C++, Python, Fortran, Git, and CMake an asset.
- Demonstrated writing and communication skills and ability to publish.
Note: "an asset" indicates preferred but still part of basic? We'll keep as Requirements.
Qualifications (Preferred Qualifications):
- Experience with Multiphysics software and simulations an asset.
- Previous experience with the development and implement numerical algorithms in advanced modeling and simulation software related to reactor physics analysis an asset
- Knowledge of software engineering best practices, including continuous integration, requirements management, and object-oriented programming concepts and design patterns an asset.
- Experience working within a rigorous quality assurance program an asset.
- Ability to obtain a security clearance.
Also Special Requirements: export control, PIV, etc. Could be part of Requirements or Qualifications. Might be better to include under Requirements as "Special Requirements". But we have no section for Special Requirements; we could fold into Requirements as bullet points. However instruction: do not create sections unless posting has real specific content. We can include them under Requirements as additional bullets. Let's add:
- Must be qualified for access to technology subject to export control requirements without an export control license.
- Must be able to obtain and maintain a federal Personal Identity Verification (PIV) card (requires favorable Tier 1 background check, including declaration of illegal drug activities within the last year).
- For foreign national candidates: must have resided in the U.S. for three consecutive years to be eligible for PIV; otherwise need LSSO determination.
We'll include those.
Skills: maybe we can list specific technical skills: SCALE, VERA, OpenMC, MCNP, Serpent, MOOSE, Cyclus, C/C++, Python, Fortran, Git, CMake, Multiphysics software, numerical algorithms, software engineering best practices, QA. But many already in Requirements/Qualifications. To avoid duplication, maybe we omit Skills section. But we need to decide if we want Skills. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine technical skills into Requirements and Qualifications, and not have separate Skills. That seems fine.
Benefits: list from "ORNL offers competitive pay and benefits programs..." then list:
- medical and retirement plans
- flexible work hours
- on-site fitness, banking, and cafeteria facilities
- Prescription Drug Plan
- Dental Plan
- Vision Plan
- 401(k) Retirement Plan
- Contributory Pension Plan
- Life Insurance
- Disability Benefits
- Generous Vacation and Holidays
- Parental Leave
- Legal Insurance with Identity Theft Protection
- Employee Assistance Plan
- Flexible Spending Accounts
- Health Savings Accounts
- Wellness Programs
- Educational Assistance
- Relocation Assistance
- Employee Discounts
We should include all.
We must not include Pay or Schedule sections.
We must not include boilerplate like "This position will remain open..." etc.
We must not include application instructions, EEO statements, etc.
Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...