Postdoctoral Scholar BF9457

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to extract content. The posting includes: - Position Description (responsibilities) - Qualifications - Employment Conditions (salary and benefits statements) - About The Department (maybe not needed as heading? Could be About the role? Actually "About the role" is generic; we could use "About the role" heading for position description? But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About the role: maybe a brief overview? The posting includes "Post Doctoral Scholar – Evapotranspiration Forecasting and Irrigation Decision Support" and description of project. Could be used as About the role. - Responsibilities: the bullet list of tasks under Position Description. - Requirements: maybe qualifications? But they have Qualifications heading separate. Could treat Requirements as "Required qualifications"? But they said we can have both Requirements and Qualifications sections if content exists. However we should not duplicate. The posting has "Qualifications" section with bullet list. Could map that to Qualifications heading. Requirements could be maybe "Required skills"? But we have Skills heading; we could put technical skills there. - Benefits: posting mentions "Salary and benefits are competitive and commensurate with education, training, and experience. Retirement and long-term disability, medical, dental, and life insurance programs are available to the employee." That's benefits info. Also maybe "Pay" not specified (just says competitive). Since they said do NOT create Pay/Schedule/Benefits sections unless posting actually states them. Benefits is stated, so we can include Benefits section. Pay: they say competitive and commensurate, but not specific numbers; that is vague but still mentions salary. However they said never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create Pay section because it's just "competitive and commensurate with education, training, and experience" which is placeholder. So omit Pay. - Schedule: not mentioned. - Skills: we could list technical skills: Python, scientific programming, geospatial/time-series datasets, etc. Could be under Skills. - Requirements: maybe we could include "Valid driver’s license and willingness to travel" as requirement. But we could also put under Qualifications. However we have Qualifications heading already for degree etc. We could split: Requirements for mandatory items (driver's license, travel) and Qualifications for education/experience. But the posting lumps them together under Qualifications. To avoid duplication, we could have only Qualifications section and maybe Skills section for technical skills. Requirements maybe not needed. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from posting, but we can format them under appropriate headings. Let's extract details: About the role / project overview: - The Department of Biosystems and Agricultural Engineering is seeking a highly motivated Postdoctoral Scholar to lead the Oklahoma component of the project, which centers on turning NASA Earth observations into forecasts that irrigators and water agencies can act on. - Groundwater from the Ogallala–High Plains Aquifer supports millions of irrigated acres across Kansas, Oklahoma, and Texas, and its continued decline is among the most consequential water sustainability challenges in the United States. - The project delivers 10-day forecasts of crop evapotranspiration and irrigation demand, with modeling indicating potential water savings of 10–15% without a yield penalty. That's substantive. Responsibilities (Position Description bullet list): - Develop and evaluate a baseline crop evapotranspiration (ETc) forecasting capability that integrates OpenET historical and near-real-time ET retrievals with GraphCast weather predictions, targeting a 10-day forecast horizon under non-limiting water conditions. - Enhance ET forecasts through soil moisture assimilation, using NISAR L-band backscatter with SMAP and Sentinel-1 as complementary datasets, and machine learning approaches that downscale coarse soil moisture products to field-relevant resolution across heterogeneous irrigated fields. - Translate forecasted crop water demand into crop-stage-aware irrigation demand estimates, incorporating dynamic crop coefficients, effective rooting depth, growing degree days, and satellite vegetation indices for the region’s dominant irrigated crops — corn, soybean, cotton, sorghum, and alfalfa. - Evaluate operational feasibility within producer-facing advisory platforms, including the Oklahoma Agricultural Scientific Irrigation Scheduling (OASIS) tool under deployment at OSU, and support prototype deployment with the Oklahoma Water Resources Board and the Oklahoma Mesonet. - Build and maintain reproducible data pipelines, including automated OpenET API access, NISAR and SMAP retrieval, and Oklahoma Mesonet ingestion; perform quality assurance on eddy covariance ET, soil moisture, and producer irrigation records; and prepare metadata and derived products for archiving in NASA-approved repositories under the project’s Open Science and Data Management Plan. - Coordinate seasonal field campaigns at OSU irrigation research sites and cooperating producer fields across Oklahoma, and validate forecasts against eddy covariance towers, Mesonet observations, and producer irrigation records. - Disseminate results through peer-reviewed publications, technical reports, and presentations at regional and international meetings, and contribute to stakeholder workshops and proposal development. Qualifications (bullet list): - Ph.D. in Biosystems or Agricultural Engineering, Civil or Water Resources Engineering, Environmental Engineering, Hydrology, Agronomy or Soil Science, Remote Sensing, Geography, Data Science, or a closely related field, completed by the appointment start date. - Demonstrated research productivity evidenced by first-authored peer-reviewed publications. - Proficiency in scientific programming and experience working with large geospatial or time-series datasets. - Python is strongly preferred, as existing project workflows are Python-based; strong proficiency in R, MATLAB, or Julia, with the ability to work in Python, will also be considered. - Research experience in evapotranspiration estimation, soil water balance modeling, hydrologic or crop water modeling, or satellite remote sensing of agricultural water use. - Strong written and oral communication skills in English, and the ability to work both independently and as part of a multi-institution team. - Valid driver’s license and willingness to travel to field research sites across Oklahoma. Employment Conditions: - Review of applications will begin 20 days after job is posted. For full consideration, submit all materials as soon as possible. - Review of applications will continue until a suitable candidate is identified. - Salary and benefits are competitive and commensurate with education, training, and experience. - Retirement and long-term disability, medical, dental, and life insurance programs are available to the employee. - The position is available as soon as an outstanding candidate is available. We should not include application instructions (like how to apply) per instruction: remove application instructions. So we need to drop the "Application" paragraph about cover letter, CV, etc. Also drop contact info, links, etc. Also remove boilerplate like OKLAHOMA COOPERATIVE EXTENSION SERVICE etc. Also remove "About The Department" maybe? It's not required but could be considered "About the role"? However we already have About the role from project overview. The "About The Department" is extra description of department; could be considered part of About the role? But they said use About the role for section headings; we could include department description under About the role as well. However we must not repeat job title as heading. It's okay. We need to output only HTML fragment, no /. Use

for each section heading. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which sections to include: - About the role: combine project overview and maybe department description? We'll include the project overview paragraphs (the three bullets) as prose under About the role. Could also include department description but it's not essential; but we can include as prose. - Responsibilities: the bullet list of tasks. - Qualifications: the bullet list of qualifications. - Skills: maybe we could extract technical skills: Python, scientific programming, geospatial/time-series datasets, R/MATLAB/Julia, evapotranspiration estimation, soil water balance modeling, hydrologic/crop water modeling, satellite remote sensing, etc. However these are already in Qualifications. To avoid duplication, we could put Skills separate but risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Skills into Qualifications or Responsibilities. But they gave Skills as possible heading; we could include if we have specific skill list not covered elsewhere. However the qualifications already list many skills. Could we treat Qualifications as requirements and Skills as technical proficiencies? Might be okay to have both. But we must not invent or summarize away detail. If we split qualifications into two sections, we need to ensure we don't lose any detail. We could put education and experience under Qualifications, and technical skills under Skills. Let's parse: Qualifications bullet list includes: 1. Ph.D. in specific fields. 2. Demonstrated research productivity evidenced by first-authored peer-reviewed publications. 3. Proficiency in scientific programming and experience working with large geospatial or time-series datasets. 4. Python is strongly preferred... (technical skill) 5. Research experience in evapotranspiration estimation, soil water balance modeling, hydrologic or crop water modeling, or satellite remote sensing of agricultural water use. 6. Strong written and oral communication skills in English, and ability to work independently and as part of a multi-institution team. 7. Valid driver’s license and willingness to travel. We could separate: - Qualifications: education, productivity, communication skills, driver's license, travel. - Skills: scientific programming, geospatial/time-series, Python, R/MATLAB/Julia, evapotranspiration estimation, soil water balance modeling, hydrologic/crop water modeling, satellite remote sensing. But we need to ensure we don't lose any detail. Let's do that. Benefits: we have retirement, long-term disability, medical, dental, life insurance programs available. Also mention salary and benefits competitive but we omit Pay section. So Benefits section will list those. Schedule: none. Now we need to ensure we don't include boilerplate like "Review of applications will begin 20 days after job is posted..." That's application instruction/process; we should remove. Also "The position is available as soon as an outstanding candidate is available." That's also maybe metadata; but it's substantive? It's about availability. Could be considered part of Employment Conditions but not a heading we have. We could include it under Benefits? Not really. Might be considered minor metadata; we could drop it as per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." This is minor metadata; we could drop it. So we can drop the lines about review of applications and position availability. Thus we keep only substantive content: project overview, responsibilities, qualifications (education, productivity, communication, driver license), skills (technical), benefits (insurance). Also maybe we include a short paragraph about salary being competitive? But that's placeholder; we should not create Pay section; but we could include a short paragraph under Benefits? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits is stated; we can include Benefits section. The salary statement is about pay; but we could mention it in Benefits? It says "Salary and benefits are competitive and commensurate with education, training, and experience." That's about salary; we could include it in Benefits section as a note, but it's vague. However they said never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). If we include Benefits section, we must not include filler text. The phrase "competitive