Postdoctoral Researcher in Computational Subsurface Hydrology and Energy Systems

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 etc. Must preserve all substantive info, no invention. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also must not include sections with filler like "commensurate with experience" etc. So we cannot include Pay if only says "Salaries are competitive and commensurate with experience." That's placeholder; we must not create Pay section. Benefits: there is a list of benefits, we can include Benefits section. Schedule: not mentioned explicitly; maybe flexible schedules mentioned under benefits? It says "Flexible schedules and time off (PTO and holidays)" under benefits. So schedule info is part of benefits; we could include a Schedule section only if explicit schedule info; but we have flexible schedules mentioned; but it's under benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits is stated; we can include Benefits. Schedule: there is mention of flexible schedules, but it's within benefits; still schedule info is present. However we need to decide if we should create a separate Schedule section. The posting says "Flexible schedules and time off (PTO and holidays)" under benefits. That is schedule info. Could we create a Schedule section with that? The instruction: "Prefer a few substantive sections over many thin ones." Might be better to include schedule info within Benefits, not separate. Since they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state flexible schedules, so we could create Schedule section. But we also have Benefits section with list. Might be redundant. I'd choose to include Benefits section only, and not separate Schedule, to avoid thin sections. Pay: not include because only generic. So sections: About the role (maybe from first paragraph?), Responsibilities (specific research directions), Requirements (minimum job requirements), Qualifications (desired qualifications), Skills (maybe programming languages etc), Benefits (list). Also Education could be part of Requirements or Qualifications; but we have Education separate? Could include under Requirements or Qualifications. The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include Education under Requirements or Qualifications. Probably better to have Requirements (minimum job requirements) and Qualifications (desired qualifications). Education is a minimum requirement; could be part of Requirements. We'll include Education within Requirements. We need to preserve all substantive info; not invent. Must not include boilerplate like EEO, drug testing, clearance, etc. Also must not include application instructions (like how to apply, contact). Must not include Note to Applicants, etc. Also must not include duplicated lines. Let's extract substantive content: - Opening paragraph: "You will Do Join a dynamic team ..." Actually first paragraph: "What You Will Do Join a dynamic team of scientists tackling some of the most pressing energy and environmental challenges of our time. The Computational Hydrogeology and Energy Systems in the Subsurface (CHESS) Team within the Earth and Environmental Sciences Division at Los Alamos National Laboratory is seeking outstanding postdoctoral candidates in computational subsurface hydrogeology. The CHESS team develops and applies high-fidelity computational physics models to advance scientific understanding of subsurface systems with applications to carbon storage, geothermal energy, and nuclear waste disposal -work that directly supports the Laboratory's mission of solving national security challenges through cutting-edge scientific innovation. You will contribute to research at the intersection of subsurface flow and transport modeling, reactive geochemistry, and machine learning. Specific research directions may include: Discrete fracture network (DFN) modeling using the dfnWorks software platformCoupled thermo-hydro-mechanical-chemical (THMC) process simulationSingle- and multiphase flow in fractured and porous media using FEHMCarbon mineralization and reactive transport in subsurface systemsApplication of machine learning and foundation models to subsurface energy systems You will publish results in peer-reviewed journals, present work at national and international conferences, and collaborate within a multidisciplinary, integrated research team -helping shape the future of subsurface energy science along the way." We need to split into About the role (overview) and Responsibilities (specific research directions). Let's craft: About the role: paragraph describing team, mission, contribution. Responsibilities: list of specific research directions (DFN modeling, THMC simulation, flow in fractured media, carbon mineralization, ML application) plus publishing, presenting, collaborating. Now Requirements (minimum job requirements): list: - Candidates with a strong background in one or more of the following areas are invited to apply: - 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, demonstrated through the ability to clearly convey complex technical information Also Education: Ph.D. in Computational Hydrology, Applied Mathematics, Computational Physics, Geological Engineering, or a related field is required. Must have completed all Ph.D. requirements by commencement and be within 5 years of Ph.D. completion. We could include Education under Requirements as bullet. Qualifications (desired qualifications): list: - 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: maybe programming languages etc already covered; but we could separate Skills as programming languages, software engineering practices, version control, etc. However we already have proficiency in programming languages under Requirements. Could move to Skills. But we need to avoid duplication. Let's decide: Requirements: background areas, education, experience, potential for publication, communication. Skills: programming languages, code development, HPC, git, CI, visualization tools, etc. Qualifications: desired qualifications list (THMC, DFN, geochemistry, upscaled transport, HPC, UQ, ML, visualization, DOE Q clearance). There's overlap; but we must preserve all info, not invent. Duplication is okay if it's in original; but we should avoid repeating same content unnecessarily? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should try to avoid redundant sections. However we need to follow the headings list; we can decide to put some items under Skills and some under Qualifications. Let's map: Skills: Proficiency in multiple programming languages (Fortran, C++, Python, Julia); Code development experience using modern software engineering practices (git and continuous integration); Experience with HPC (MPI, parallel workflows, GPUs); Data and model visualization using tools such as ParaView, VisIt, or EarthVision. Qualifications (desired): Numerical simulation of coupled THMC processes; Experience with DFN modeling; Computational geochemistry; Upscaled transport modeling (reactive and non-reactive); Uncertainty quantification methods; Machine learning applied to geoscience or subsurface systems; Ability to obtain and maintain a DOE Q clearance. Education: Ph.D. requirement. Now Benefits: list from "Our generous benefits package includes:" bullet list. We must not include Pay section. Schedule: not separate. Now ensure we don't include boilerplate like "Work Location: The work location for this position is onsite and located in Los Alamos, NM." That's substantive location info; could be included under About the role or maybe a separate section? Not in headings list; we could incorporate into About the role as a sentence. It's substantive. We'll include. Also "All work locations are at the discretion of management." That's generic; maybe we can keep but it's not boilerplate? It's somewhat generic but still info. Might keep. We must not include Note to Applicants, application instructions, contact, etc. Also must not include "Due to federal restrictions..." etc. That's legal/boilerplate; remove. Also must not include "Where You Will Work" paragraph? That's substantive description of location and benefits; we already have benefits; we can incorporate location description into About the role or maybe a separate "Location" but not in headings list; we can incorporate. We must not include "Additional Details" etc. Now produce HTML fragment with headings

and content

or

• . Ensure no extra text outside. Let's craft:

  About the role

  Join a dynamic team of scientists tackling pressing energy and environmental challenges. The Computational Hydrogeology and Energy Systems in the Subsurface (CHESS) Team within the Earth and Environmental Sciences Division at Los Alamos National Laboratory seeks outstanding postdoctoral candidates in computational subsurface hydrogeology. The team develops and applies high-fidelity computational physics models to advance understanding of subsurface systems for carbon storage, geothermal energy, and nuclear waste disposal, supporting the Laboratory's mission of solving national security challenges through scientific innovation. You will contribute to research at the intersection of subsurface flow and transport modeling, reactive geochemistry, and machine learning, publish results in peer‑reviewed journals, present work at national and international conferences, and collaborate within a multidisciplinary, integrated research team.

  Responsibilities

  • Discrete fracture network (DFN) modeling using the dfnWorks software platform
  • Coupled thermo‑hydro‑mechanical‑chemical (THMC) process simulation
  • Single‑ and multiphase flow in fractured and porous media using FEHM
  • Carbon mineralization and reactive transport in subsurface systems
  • Application of 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

  Requirements

  • Strong background in one or more of: computational subsurface flow and transport modeling; applied mathematics and numerical analysis or computational science.
  • Proficiency in multiple programming languages (Fortran, C++, Python, 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.
  • Ph.D. in Computational Hydrology, Applied Mathematics, Computational Physics, Geological Engineering, or a related field required; must have completed all Ph.D. requirements by appointment start and be within 5 years of Ph.D. completion.

  Skills

  • Proficiency in multiple programming languages (Fortran, C++, Python, Julia).
  • Code development experience with modern software engineering practices (git, continuous integration).
  • Experience with high‑performance computing (MPI, parallel workflows, GPUs).
  • Data and model visualization using tools such as ParaView, VisIt, or EarthVision.

  Qualifications

  • 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).