Postdoctoral Researcher in Computational Subsurface Hydrology and Energy Systems

We need to output HTML fragment with sections: About the role (maybe "What You Will Do"), Responsibilities? The posting includes "What You Will Do" describing contributions. Also "What You Need" includes Minimum Job Requirements and Desired Qualifications. Also Education. Also Work Environment (Work Location). Also Compensation And Appointment (salary competitive, renewable). Also Benefits (list). Also maybe "Where You Will Work" (but that's similar to Work Location). Also "Additional Details" includes many boilerplate (clearance, drug testing, EEO, etc.) which we should remove. Also "Instructions on How to Activate/ Create a LANL Jobs Account" etc. Remove all boilerplate, navigation, legal, EEO, scam-warning, duplicated lines, application instructions. We need to preserve substantive information. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. We have: - About the role: Could be "What You Will Do" (description of role). That's substantive. - Responsibilities: Could be same as What You Will Do? Might be overlapping. We could treat "What You Will Do" as Responsibilities. But we need to follow instruction: use headings only when posting has real specific content. We can have sections: About the role (maybe overview), Responsibilities (specific tasks), Requirements (minimum job requirements), Qualifications (desired qualifications), Skills (maybe programming languages etc), Benefits (list), Pay (salary competitive and commensurate with experience), Schedule (maybe not given; we should not create if not stated). The posting does not mention schedule specifics (flexible schedules mentioned under benefits). Actually benefits include "Flexible schedules and time off (PTO and holidays)". That's schedule info but under benefits. Could we create a Schedule section? The posting does not explicitly state schedule like full-time, but we have "Employment Status Full Time". That's schedule info. Could include Schedule section with "Full-time". However instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Full Time" under Employment Status. So we can include Schedule with that. Also Pay: "Salaries are competitive and commensurate with experience." That's substantive but vague; still it's stated. Should we include Pay section? It says "Salaries are competitive and commensurate with experience." That's not a specific number but it's stated. According to instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The phrase "competitive and commensurate with experience" is somewhat filler but it's still stated. It's not a specific number but it's still a statement. The instruction says never emit a heading followed by filler/placeholder text like "commensurate with experience". That suggests we should not create a Pay section if the only content is that phrase. So we should omit Pay section. Benefits: we have a list of benefits. So we can include Benefits section. Schedule: we have "Full Time" under Employment Status. That's not filler; it's specific. So we can include Schedule section with "Full-time". Also maybe mention onsite work location? That's under Work Environment. We also have "Work Location: onsite and located in Los Alamos, NM." That's location; could be part of About the role or Work Environment. We could have a section "Where You Will Work" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to fit location into one of those. Perhaps About the role includes location. Or we could add a short paragraph under About the role that mentions location. We need to preserve all substantive information: description of role, research directions, responsibilities, minimum job requirements, desired qualifications, education, work environment (onsite location), compensation (appointment length, renewable, fellowships), benefits list, schedule (full-time). Also note about clearance? Not required. Also note about drug testing etc is boilerplate; remove. We must not include application instructions, account creation instructions, EEO, etc. We need to output only HTML fragment, no markdown fences. Let's structure:

About the role

Postdoctoral Researcher in Computational Subsurface Hydrology and Energy Systems at Los Alamos National Laboratory's EES-16/Energy And Natural Resources Security division. Join the Computational Hydrogeology and Energy Systems in the Subsurface (CHESS) Team working on high-fidelity computational physics models for subsurface systems with applications to carbon storage, geothermal energy, and nuclear waste disposal. You will contribute to research at the intersection of subsurface flow and transport modeling, reactive geochemistry, and machine learning, including discrete fracture network (DFN) modeling using dfnWorks, coupled thermo-hydro-mechanical-chemical (THMC) process simulation, single- and multiphase flow in fractured and porous media using FEHM, carbon mineralization and reactive transport, and application of machine learning and foundation models to subsurface energy systems. Expect to publish results in peer‑reviewed journals, present at national and international conferences, and collaborate within a multidisciplinary team.

Maybe we can split responsibilities into separate section.

Responsibilities

• Develop and apply high‑fidelity computational physics models (dfnWorks, FEHM) for subsurface flow and transport.
• Work on discrete fracture network (DFN) modeling.
• Perform coupled thermo‑hydro‑mechanical‑chemical (THMC) process simulation.
• Model single‑ and multiphase flow in fractured and porous media.
• Investigate carbon mineralization and reactive transport in subsurface systems.
• Apply machine learning and foundation models to subsurface energy systems.
• Publish results in peer‑reviewed journals.
• Present work at national and international conferences.
• Collaborate within a multidisciplinary, integrated research team.

But note that some of these are already in description; we need to avoid duplication but preserve all substantive info. It's okay to have some overlap as long as we don't invent. We can keep responsibilities as bullet list derived from "What You Will Do". Ensure we don't miss any. Now Requirements (minimum job requirements):

Requirements

• Strong background in computational subsurface flow and transport modeling.
• Applied mathematics and numerical analysis or computational science.
• Proficiency in multiple programming languages, such as Fortran, C++, Python, or Julia.
• Code development experience using modern software engineering practices in research or HPC environments (git and continuous integration).
• Demonstrated potential for peer‑reviewed publication.
• Excellent written and oral communication skills in English, able to convey complex technical information clearly.

Qualifications (desired qualifications):

Qualifications

• Experience with numerical simulation of coupled THMC processes.
• Experience with discrete fracture network (DFN) modeling.
• Computational geochemistry.
• Upscaled transport modeling (reactive and non‑reactive).
• High‑performance computing (MPI, parallel workflows, and/or GPUs).
• Uncertainty quantification methods.
• Machine learning applied to geoscience or subsurface systems.
• Data and model visualization using tools such as ParaView, VisIt, or EarthVision.
• Ability to obtain and maintain a DOE Q clearance.

Skills: Could be programming languages etc but we already covered. Maybe we can combine programming languages under Skills. But we already have proficiency in programming languages under Requirements. Could create Skills section for specific tools: dfnWorks, FEHM, ParaView, etc. However we might avoid duplication. The instruction: prefer a few substantive sections over many thin ones. So maybe we skip Skills section and incorporate those into Requirements/Qualifications. But we need to use headings only when posting has real specific content. We have content for Skills (programming languages, tools). Could create Skills section with those. But we already have programming languages under Requirements; we could move them to Skills. However we need to preserve all info; we can decide to put programming languages under Skills, and keep Requirements focused on background and experience. Let's think. Better: Requirements: background areas (computational subsurface flow, applied math, etc). Qualifications: desired qualifications (experience with THMC, DFN, etc). Skills: programming languages, software engineering practices, tools (git, CI, ParaView, etc). Benefits: list. Schedule: full-time. Let's craft:

Skills

• Proficiency in Fortran, C++, Python, or Julia.
• Code development experience using modern software engineering practices (git, continuous integration).
• Experience with dfnWorks and FEHM software platforms.
• Data and model visualization with ParaView, VisIt, or EarthVision.

Now Benefits:

Benefits

• PPO or High Deductible medical insurance with nationwide network.
• Dental and vision insurance.
• Free basic life and disability insurance.
• Paid childbirth and parental leave.
• Award‑winning 401(k) plan (6% matching plus 3.5% annually).
• Learning opportunities and tuition assistance.
• Flexible schedules and time off (PTO and holidays).
• Onsite gyms and wellness programs.
• Extensive relocation packages (outside a 50‑mile radius).

Schedule:

Schedule

Full‑time, onsite position located in Los Alamos, NM.

We also need to include appointment details: initial postdoc appointments for two years, renewable for third year, eligibility for fellowships. That's substantive; where to put? Could be under About the role or maybe a separate section like "Appointment". But not in allowed headings. Could incorporate into About the role paragraph. We'll add a sentence: "Initial appointments are for two years, renewable for a third year, with eligibility for LANL Director's Fellowship or named fellowships (Marie Curie, Richard P. Feynman, J. Robert Oppenheimer, Frederick Reines)." Also education requirement: Ph.D. in Computational Hydrology, Applied Mathematics, Computational Physics, Geological Engineering, or related field required; must have completed Ph.D. by commencement and be within 5 years of completion. That's substantive; could be under Requirements or Qualifications. Probably under Requirements as a minimum requirement. Let's add to Requirements list. Also note about clearance: "Ability to obtain and maintain a DOE Q clearance" is under Desired Qualifications; we already have that. Now we need to ensure we didn't include boilerplate: removed EEO, drug testing, account creation, etc. Check for any leftover boilerplate: The "Work Environment" section includes "Work Location : The work location for this position is onsite and located in Los Alamos, NM. All work locations are at the discretion of management." We incorporated location in Schedule paragraph. The "All work locations are at the discretion of management." is generic; maybe we can omit as it's boilerplate. We'll keep only substantive location. Now check for any repeated lines: We have not duplicated. Now ensure we didn't create Pay section (we omitted). Good. Now output HTML fragment. Let's craft final HTML:

About the role

Postdoctoral Researcher in Computational Subsurface Hydrology and Energy Systems at Los Alamos National Laboratory