Jobs · Engineering · North Carolina

Computational Magnetohydrodynamics Engineer

U.S. Fusion Energy · Oak Ridge, NC · 3 wk ago
EngineeringVolunteer
We need to output only HTML fragment, with headings

for 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 etc. Must preserve all substantive info, remove boilerplate, navigation, EEO, etc. Must not create Pay/Schedule/Benefits unless posting actually states them. The posting mentions "ORNL offers competitive pay and benefits programs" and lists benefits. So Benefits section exists. Pay: they say "competitive pay" but not specific numbers; we should not create Pay section if only generic "competitive pay" with no specifics? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits list, so Benefits section is okay. Pay: they say "competitive pay" but no specifics; that might be considered filler? It says "ORNL offers competitive pay and benefits programs". That's a statement about pay but not specific. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive pay" is vague but not exactly placeholder; but it's still not specific. Safer to omit Pay section because no concrete pay info. Schedule: not mentioned. So we omit Pay and Schedule. We need sections: About the role (maybe Overview), Responsibilities (Major Duties/Responsibilities), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe combine? but we can have Skills section for technical skills like CFD codes, mesh generation, CAD, etc). Benefits (list). Also maybe "About ORNL" could be part of About the role? But we have About the role heading; we can put overview there. The posting has Overview paragraph describing role. That fits About the role. Responsibilities: Major Duties/Responsibilities paragraph. Requirements: Basic Qualifications. Qualifications: Preferred Qualifications. Skills: Could extract from requirements: experience with CFD codes, mesh generation, CAD, etc. But we already have those in qualifications; maybe we can put Skills separate for technical skills like CFD codes, mesh generation, CAD, plasma physics codes, etc. However we must not duplicate content; we can keep them in Qualifications or Skills. The instruction: Use headings for sections; we can decide to have Skills section for technical skills, and Qualifications for education/experience. Let's parse. Basic Qualifications: PhD in specific fields, experience in development/application of complex engineering codes, familiarity with fusion reactor concepts, familiarity with Liquid Metal systems and MHD required, working knowledge of CFD codes (list), knowledge of mesh generation software required, excellent verbal, presentation, writing skills. Preferred Qualifications: motivated self-starter, ability to work independently, ability to function in fast-paced, experience designing liquid metal flow loop experiments and performing measurements, knowledge of plasma physics codes (M3D-C1, SOLPS) and familiarity with open-surface flows, working knowledge of CAD software (list). Thus we can put Requirements = Basic Qualifications. Qualifications = Preferred Qualifications. Skills could be a consolidation of technical skills: CFD codes, mesh generation, CAD, plasma physics codes, open-surface methods, etc. But that would duplicate content from both sections. To avoid duplication, maybe we just have Requirements and Qualifications, and not Skills. But we need to decide which headings to include based on content. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one "Requirements" section? But they differentiate basic vs preferred. Might be better to have Requirements (basic) and Qualifications (preferred). Skills maybe not needed. We also need Benefits section: list of benefits. Thus final HTML:

About the role

Overview paragraph...

Responsibilities

Major Duties/Responsibilities paragraph...

Requirements

  • ... each bullet from Basic Qualifications

Qualifications

  • ... each bullet from Preferred Qualifications

Benefits

  • ... each benefit
We must not include any boilerplate like "Apply now", "Date:", "Location:", "Company:", "Requisition Id", "Overview" heading (we used About the role). Also remove "If you have difficulty..." etc. Also remove "Nearest Major Market: Knoxville". Also remove "We accept Word..." etc. Also remove "This position will remain open..." etc. Also remove "ORNL is an equal opportunity employer..." etc. Also remove "UT-Battelle is an E-Verify employer." Also remove "Find Similar Jobs", etc. We need to preserve all substantive information: overview, responsibilities, basic qualifications, preferred qualifications, benefits list. Let's extract text. Overview paragraph: "The Fusion Energy Division at the Oak Ridge National Laboratory seeks applications for a skilled Computational Magnetohydrodynamics Engineer, with intended focus on magnetohydrodynamic (MHD) flows of electrically conducting liquids in a magnetic field, such as liquid metals (LMs) as well as plasma physics relevant to breeding/cooling fusion energy applications. The selected candidate will work on and lead various tasks related to coupled phenomena between fusion plasma and LM MHD flows in a fusion blanket or LM divertor. We seek individuals with advanced computational skills who can lead computational and experimental activities using commercial codes to compare with experiments and also be able to develop new computational models and computer programs. The successful candidate will work with a multidisciplinary team of simulation/design, and technology experts." That's the overview. Major Duties/Responsibilities paragraph: "The successful candidate will be involved in both developing new and applying existing models and simulation tools to understand physical processes in fusion applications that involve liquid metal magnetohydrodynamics and plasma physics, such as breeding blankets and liquid-metal plasma facing components. The selected candidate will be responsible for interaction with division staff and the external collaborators that work with the ORNL research group under the research projects funded by DOE, such as an ongoing SciDAC project on “Center for Simulation of Plasma - Liquid Metal Interactions in Plasma Facing Components and Breeding Blankets of a Fusion Power Reactor” and the FIRE collaborative project “Advancing the maturity of liquid metal (LM) plasma facing materials and first wall concepts”. The candidate will be expected to work independently, lead, perform and collaborate on simulation/design and experimental activities, and fully document the work in technical reports and publications. The candidate will also be responsible for writing research proposals.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." Note there is a run-on sentence: "writing research proposals.Deliver". We'll keep as is. Basic Qualifications list: - PhD in Nuclear Engineering, Mechanical Engineering, Thermal-Mechanics, Fluids, or a closely related field. - Experience in the development and application of complex engineering codes and preferable to have familiarity with fusion reactor concepts. - Familiarity with Liquid Metal systems and MHD is required. - Working knowledge of one or more CFD codes (OpenFOAM, COMSOL, HIMAG, ANSYS CFX, ANSYS FLUENT) that can be utilized in MHD flow computations is necessary, and/or research codes developed for liquid-metal MHD. - Knowledge of mesh generation software is required. - Excellent verbal, presentation, and writing skills are required to enable effective interaction and communication with technical peers, program managers, collaborators, and sponsors. - Candidates must show examples of their academic and work experience. Preferred Qualifications list: - Motivated self-starter with the ability to work independently and to participate creatively in collaborative teams across the laboratory. - Ability to function well in a fast-paced research environment, set priorities to accomplish multiple tasks within deadlines, and adapt to ever changing needs. - Experience in designing liquid metal flow loop experiments and performing measurements of liquid metal flows. - Knowledge of plasma physics codes, such as M3D-C1 and SOLPS and familiarity with computations of open-surface flows (Level-set, Volume of fluid method) is a plus. - Working knowledge of computer-aided design (CAD) software, such as AutoCAD, CATIA, SOLIDWORK, FreeCAD or similar is required. Benefits list: - 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 Also mention "ORNL offers competitive pay and benefits programs to attract and retain individuals who demonstrate exceptional work behaviors. The laboratory provides a range of employee benefits, including medical and retirement plans and flexible work hours, to support the well-being of you and your family. Employee amenities such as on-site fitness, banking, and cafeteria facilities are also available for added convenience." This is generic but we already have benefits list; we could include a short paragraph about benefits overview before list. But we must not invent or summarize away detail. We can include that prose as part of Benefits section before the list. It's substantive: mentions medical and retirement plans, flexible work hours, on-site fitness, banking, cafeteria. That's extra detail not in list. So we should include it. Thus Benefits section:

ORNL offers competitive pay and benefits programs... Employee amenities such as on-site fitness, banking, and cafeteria facilities are also available for added convenience.

then
    list. We must not include "competitive pay" as a separate Pay section; we already mentioned it in benefits prose. That's okay. Now ensure no boilerplate: remove "If you have difficulty using the online application system..." etc. Also remove "This position will remain open..." etc. Also remove "Nearest Major Market: Knoxville". 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 "Find Similar Jobs". Also remove "Apply now". Also remove "Date:", "Location:", "Company:", "Requisition Id". Also remove "Overview" heading (we used About the role). Also remove "Major Duties/Responsibilities" heading (we used Responsibilities). Also remove "Basic Qualifications" heading (we used Requirements). Also remove "Preferred Qualifications" heading (we used Qualifications). Also remove "About ORNL" heading (we integrated into About the role? Actually we have overview from Fusion Energy Division; we could also include a brief about ORNL from the "About ORNL" paragraph. That paragraph describes ORNL legacy, mission, etc. That's substantive and not duplicated. Should we include it? The instruction: preserve ALL substantive information. The "About ORNL" paragraph is substantive. We could either add another section like "About ORNL" but we only have headings list; we could put it under About the role as well, or create a separate section "About ORNL". But the allowed headings are limited to those listed; we cannot create arbitrary headings like "About ORNL". We must use only those headings. So we need to fit that content into one of the allowed headings. Which fits best? "About the role" could include overview of role and also about ORNL? Might be okay. Or we could put it under "Responsibilities"? No. Better to extend About the role paragraph to include ORNL description. Let's combine: After overview paragraph, add a paragraph about ORNL: "As a U.S. Department of Energy (DOE) Office of Science national laboratory, ORNL has an impressive

Similar jobs