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:
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
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